Date: prev next · Thread: first prev next last

On 06/21/2011 10:19 AM, drew wrote:
On Tue, 2011-06-21 at 09:14 -0400, webmaster for Kracked Press
Productions wrote:
On 06/21/2011 06:00 AM, Florian Effenberger wrote:

drew wrote on 2011-06-20 22.09:

Well, it seems to me that the action item I had from May was to explore
how much work (or of a hassle) this would be.

  From Florian's responses I would say - a good bit.

That and given the fact there really does not seem to be consensus on
this at the moment I propose we table the idea till the next meeting.

Right now there are other more pressing uses of our time and energies,
it requires a few hours of time for me, but that wouldn't be the
problem. I am just curious to hear the reasons. We discussed rather
lenghty on why to have "us". I see you feel a need, but how do we
organize things? How can we avoid having splitted mailing lists? I
don't want to end up with, based on the German example, having "de",
"bavaria", "allgaeu" and "schwaben", where two of these will vanish
some day, and all is just cluttered.

If there is a compelling reason, I am happy to do the change, but
still I do not understand why "northamerican" is so much better than
"us". Or, why did you then want to have a specific "us" list in the


I was wondering about using "NorthAmerican" [lower case for the letters
is fine] but for some reason I was thinking we needed to have a two or
three letter sub-domain listing for the list.

I do not know right now what the sub-domain for the NA pages would be on
the CMS server that is being worked on.
Actually that has been posted to the list numerous times is the location where we will build
the dosc - that right now throws a 404 error, because I rearrange some
pages in the SS admin screen and it didn't like that - I WILL have that
fixed today, no excuses. is the distribution site for the disc

   It would be nice, IMO, that the
marketing@ would be using the same name as the NA web pages would be.
Not necessarily IMO - please remember this is only one project the group
is working on and I would say that although it is important it is not
the most important.

It will be nice to not have to download and then upload the newest
versions of the install files, to the testing site.  I
would be happy to take that site and have info about LibreOffice and
screen shots, plus having links to the CMS server site for the project
and info about getting on the marketing and users lists.
Right - and I will do everyting necessary to see to it that by July 7th
there is no reason to use the site for anything beyond
another distribution point for the .iso image - in other words to have
all of the working files moved and 'working' at

And to have an .iso image for download available at

the page gives me a small text saying "The requested page could not be found", while the "dvd." page shows the not found with our globe image.

""; has a link on the "dvd." page and it goes to an information page that looks like internal information for the CMS server system.

It gives info like this:

session.hash_function    0    0    PHPSESSID    PHPSESSID
session.referer_check    no value    no value
session.save_handler    files    files
session.save_path    /var/lib/php5    /var/lib/php5

List later goal actually could, might, even happen first - using
the .iso built from the current layout.

Best wishes,


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.