incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shane Curcuru <>
Subject Which website is which (was: New goals for OOo)
Date Thu, 23 Jun 2011 16:30:10 GMT
Since people have been wondering about the various websites, here's a 
brief explanation:

* Apache Podling public homepage

This is the official homepage of the Podling.  It is typically what 
would become the official homepage of the Project once the project as a 
whole graduates from the incubator.  It's the rough equivalent of as a homepage (although obviously the current 
technology and content are different).

This should have general information about the project as a whole, which 
currently should include information about how the community is working 
to create an Apache project, along with the obvious pointers to all the 
other information about the project, various products, languages, 
everything else associated.

You must be a committer to update this page, since it's part of the 
official Podling's website.

* Podling status page

This is where the Apache Incubator project tracks the incubation status 
of this podling.  I.e., it's not for information about the Apache code or product; it's for information about how this 
community is working, and for tracking IP clearance issues and the like. 
  It's essentially the metadata about how this community and this 
project works as we're all moving towards a hopeful graduation to an 
official Apache project.

You must be a committer to update this page, since it's part of the 
official Incubator website.

* Wiki pages
Wiki pages are traditionally used for working areas for project 
communities to develop new plans, or sometimes for informal or 
supplementary documentation.  A few projects use a wiki for their main 
documentation, although we typically prefer that the main docs and the 
main website are on the new Apache CMS system.  But obviously, every 
project is allowed to organize it's work in it's own fashion, as long as 
the Apache infrastructure exists to support it.
This is - for the time being - a place for project committers and others 
to organize a project plan for the podling.  For the next several weeks, 
I imagine it will have a lot of planning going on, figuring out how to 
transition all the different kinds of services and sites and 
documentation on the current oo.o websites over to Apache infrastructure.

This site simply requires a wiki login to edit, so it's definitely a 
place where we want all sorts of folks to help out.

I'd imagine that this is a working space for project committers to work 
on the specific structural issues around transitioning the code, various 
websites, and other stuff (wikis, forums, etc.) from it's existing home 
to a future Apache infrastructure hosted home.  This site requires a CLA 
to contribute.

Hopefully my longwinded explanation is helpful to someone!  There's a 
LOT going on - both with the oo.o code itself, with the community (each 
of the communities, really), with the project, and with the podling as 
respects to rebooting in the Apache Way.

- Shane

P.S. I'm a Member of the ASF, and have signed up as a Mentor to help the 
podling and it's community work towards graduation.   I'd love to be 
able to work on the code as well - I spent a decade working on Lotus 
1-2-3 and really miss being able to work on end-user software - but that 
depends on my available time.  8-)

Kay Schenk wrote:
> On Wed, Jun 22, 2011 at 4:53 PM, Dave Fisher <> wrote:
>> You already are a contributor! You sent this email!
>> Please join the Community Wiki -
> hmmmm...well OK, I didn't think I could actually edit anything! Well I'll
> send the ICLA anyway.
>> We have started to outline plans there. No ICLA required for that Wiki.
> OK...I was actually thinking of editing
> as opposed to the wiki.
>>> Well, as someone who has been involved in the project for about 10 yrs
>>> now...I LIKE your picture, but I wonder how it actually fleshes out given
>>> what we have to work with on the Apache site now.
>> I wonder also.
> Well, I'm assuming that since we are now under the Apache license/rules, the
> intent is for more direct community participation than we've had in the
> past, perhaps esp in regards to web site/wiki postings.  So...I/we need to
> look into this. Fro example, I'm assumign we no longer have a "community
> council" though I'm sure we could designate a "manager" of sorts. it's all
> up to this group at the moment.
>>> I am going to apply as an Apache contributor and hope I can at least make
>> a
>>> few small changes to the current OOo Apache site. Until we get a whole
>> scale
>>> site redirect in place vis a vis DNS servers in the great stratosphere
>> (and
>>> hopefully this will NOT happen until we've got more ported over -- or
>> maybe
>>> not, see below), I think we should start cobbling together what we can. I
>>> really don't know what the rules are regarding jumps form the given
>> Apache
>>> site to a secondary server, etc.
>> Here is where we are thinking of building the DNS map:
>> There is information from the last week that needs to be found and added
>> here. I've no time yet.
> OK...I'll take a closer look and try to review messages... gak!
>>> Are you basically suggesting that the "new" site or the new entity follow
>>> the areas that you've outlined in your picture? In other words, if OOo
>> does
>>> in fact evolve into an Apache project vs what it is now -- a vanilla open
>>> source project -- what does that mean in terms of governance and
>> structure.
>>> And how does this translate, if at all, to an actual site.
>> It is certainly a possible framework to discuss components. Does this
>> already match OOo well, or is it a new organization.
> Well it matches it well "in concept" but not in actual content totality. For
> example, the "Support" area on OO.o, which is sort of omitted from your
> current diagram, included not only user forums, but a lot of published
> information. Anyway, all this can be fleshed out later. The BIGGEST thing in
> terms of inclusion are the native language projects.
>>> I would like to hear more on this. To me, these are kind of separate
>>> entities, yet now, in this new environment. We need to learn to retool
>> given
>>> the Apache governance process to start with. And then ????
>>> Obviously we need to do a lot more research on this new paradigm.
>> True.
> OK, much to's just confusing going from what you need an Apache ID
> for -- like the jumping off page,
> and our starting site page....
> vs the wiki.
>> Regards,
>> Dave
>>> On Wed, Jun 22, 2011 at 3:38 PM, Jomar Silva <> wrote:
>>>> I'm not sure if this is the right place to present that, and seeing
>>>> that I'm still learning The Apache Way, I'll try :)
>>>> I've published a few days ago at my blog an idea about what I believe
>>>> we could aim as the architecture of Apache OOo. I believe that this
>>>> could help us to organize the project, tasks and teams, and I did it
>>>> based on several other OOo architecture diagrams I've found online.
>>>> The diagram can be found here
>>>> ( and just for the record I
>>>> also wrote a blog post with my thoughts about the project
>>>> (
>>>> ).
>>>> The text is also available in Brazilian Portuguese and as far as I
>>>> know it was the first text about the project published in Brazil. I'm
>>>> also working here in Brazil with some other friends that are already
>>>> in this list to gather more BR developers.
>>>> Just my R$ 0,02 (which is by far less than the other currencies used
>>>> to present people's cents on this discussion :)).
>>>> Best,
>>>> - Jomar
>>> --
>> ---------------------------------------------------------------------------------------
>>> MzK
>>> "He's got that New Orleans thing crawling all over him, that good stuff,
>>> that
>>> 'We Are the Champions', to hell with the rest and I'll just start over
>> kind
>>> of attitude."
>>>                  — "1 Dead in the Attic", Chris Rose

View raw message