Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

On Thu, Feb 3, 2011 at 12:02 PM, David Nelson <> wrote:
At that time, LibO will have a decent website to fulfill needs for the
next few months, and those of you with those radically-different,
imaginative, creative visions can develop them at leisure for
presentation to the SC and community. I'll be pleased to contribute in
any way you want me to.
Then, I suggest that we thoroughly explore all other possible options
via confcalls, wiki writing and modeling on the pumbaa server until we
arrive at a v2.0 SilverStripe website to offer to the SC for approval
- something tangible, backed-up by written presentations and

David, one thing I think should be clear, is that the website team
creates, maintains and is responsible for the website.
Instead of working independently and presenting competing work to the
SC for some kind of royal approval as you have suggested and has
occurred in the past, we should work collaboratively without any need
for Steering Committee intervention or requests for approvals.
As the website team we have the mandate and authority to improve the
website content and infrastructure, we simply need to compromise then
come to a conclusion.

I know very well that the subject of Drupal is not gone from the minds
of several of you. Therefore, I suggest that, when
v1.0 is at a finalized state, we should request the SC to request
Christian to set-up a Drupal sandbox on the pumbaa server, in parallel
to the SilverStripe sandbox. That way, you could thoroughly explore
your ideas, and could experiment and model, and build properly-working
demos that can be shown to the SC, for consideration, for whatever
applications you imagine.

We already have a Drupal development site, why would we move it to
another persons server.
It is hosted on my server and I am more than happy to continue
supporting the Drupal development when we kick it off again in a few
Also the 'pumbaa' server you are talking about drives me nuts as it is
not on port 80/8080/8000 and some of the proxies I use don't allow
other ports.

For the "Why?" pages, I like Wheatbix's idea of concrete usage
examples for each marketing target category, and - speaking my own
view - I feel we should work on that. Me, I want to start by
re-working "Why for Home?" in that direction. But I'd see these as
being quite in-depth pages of maybe 500 words or more each.

'500 words' is a long way from what I envisaged when developing the idea.
Considering there are people who would like to try out more visually
pleasing content how about we set the challenge for these 'why' pages
and see what people come up with?

If there is anyone out there who does not have/want a Silverstripe
username you can forward content you have created on to me and I will
publish it. Please include any images as files.

We'd need to evaluate a choice between the SilverStripe blogging and
news modules on pumbaa, and then ask Christian to provide it on the
main site.

IMO 'LibreOffice News' is already provided by the LibreOffice Blog and Planet.
We simply need a way to import the XML to page content and setup a
list of the pages.
Again, I am not sure how Silverstripe works, but this is pretty basic
functionality and should be very easy to set up.

Just a few thoughts,
Michael Wheatland

Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.