incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <robw...@apache.org>
Subject Re: The Old OOo Site
Date Tue, 08 Nov 2011 17:38:30 GMT
On Tue, Nov 8, 2011 at 11:55 AM, Louis Suárez-Potts
<lsuarezpotts@gmail.com> wrote:
> On 8 November 2011 11:49, Rob Weir <robweir@apache.org> wrote:
>> On Tue, Nov 8, 2011 at 11:38 AM, Louis Suárez-Potts <louis@apache.org> wrote:
>>> Hi,
>>> I periodically (read: every day) receive requests from OOo community
>>> members and OOo users to fix, alter or otherwise change the OOo site
>>> (www.openoffice.org). These requests include such things as expunging
>>> private information as well as normal updates.
>>>
>>> As we all know, the old OOo site is pretty much in the past, and we
>>> are progressively moving to the new.
>>>
>>> But: I'd like to have some more concrete information to provide, and
>>> ideally, be able to address the requests, too.
>>>
>>
>> Hopefully there is not a lot of personal information on the public
>> website.
>
> There is not. We at OOo also had a high bar—OOo site was predicated on
> the Apache model, and that's no coincidence: Brian B. had a hand in
> both. However, personal info does creep in when people erroneously
> post their private information, such as phone numbers, to public
> lists, unaware—!!— just how public the lists are.
>

Understood.

>  But this does happen, with mailing list archives, for
>> example.  Apache has a policy for this.  It essentially sets a high
>> bar for removing information from public archives:
>>
>> http://apache.org/foundation/public-archives.html
>>
>> For other information on the website, I'd recommend having them enter
>> an issue in Bugzilla, classified as the "www" product.  Hopefully
>> we'll be cutting over to the new Apache-hosted version of these pages
>> soon, and we can apply requested changes then.
>
> Rob, you don't get just how naive some of the users of OOo are and how
> naive even those posting to the lists were. Perhaps you are unaware of
> how popular OOo remains? Few of these users would even know how to
> file an issue.
>

Well, you could enter an BZ issue for them if needed.  Or ask them to
send a note to ooo-dev list or even the legacy OOo users list.  We
have eyes almost everywhere...except for your personal mail box.  So
getting them to make a request on any public list associated with the
project will be noted.

>>
>> Of course, if there is something of a truly urgent nature, then
>> escalate that, via ooo-private if appropriate.
>
> I am referring to www.openoffice.org/ You have not answered the
> question—but I didn't think you could. The point is double:
>

We've already migrated huge chunks of the old OOo website over to
Apache, such as the support forums and the wiki.  The static webpages
have also been moved over, but we have not yet change the DNS entries
to point to the new Apache copy.  So right now we effectively have two
copies of the website.  I'd consider the openoffice.org copy to be
"dead".  The living copy is in SVN at Apache now.  We should be
working on that copy, and when it is ready then we can make it appear
at the familiar openoffice.org URL.

> 1. Can I alter the old site, www.openoffice.org/

If you do that, the changes will likely be lost.  It is better, I
think, to make changes in the ooo-site copy that we have at Apache.
Or get the change requests into BZ one way or another so they can be
applied.

> 2. When will the old site fully migrate to the new, and when that
> happens, what sort of content control would I (or someone like me)
> have?
>

Others can comment on the timing.  As far as I can tell, the answer is
"when we're ready".

Since the website files are checked into version control, any project
committer can change the website, including you.  This could be done
at the fille/SVN level for those who like command lines, or via the
web-based Apache CMS, which allows you do make these changes in your
browser.

-Rob

> thanks
> louis
>
>
>>
>>> Thanks
>>> Louis <-the person formerly known as the OOo Community Manager
>>>
>>
>

Mime
View raw message