Committing somewhere would be good as otherwise I don't know whether I
need to suggest the following (I wasn't sure of the best thread for this
to go in anyway):
May I suggest that, where appropriate, the documentation is backed
up with pointers to examples of existing projects that are
considered to represent the current best practice on various
aspects. Whilst clear documentation is fantastic, there is nothing
like good examples for building confidence that one is doing things
in the right way.
Cheers,
Gary
On 08/08/2012 10:42 AM, Greg Stein wrote:
Commit the content. Otherwise, we're just hand-waving.
On Aug 8, 2012 5:29 AM, "Bertrand Delacretaz" <bdelacre...@apache.org>
wrote:
Hi,
Like others, I'm not too happy with the current
http://incubator.apache.org/ content.
How about starting a new, minimal set of docs that are more
maintainable and understandable?
IMO, the following would be sufficient, with one page per topic:
1. What's the Apache Incubator? (homepage)
2. Lifecycle of a podling, from proposal to graduation, with many
links to existing examples (proposals, committer votes, graduation
threads, etc.)
3. Release checklist: criteria for approving a release
4. Previously asked questions (a la
http://www.apache.org/legal/resolved.html, includes IP clearance info)
6. Glossary of terms (though that might belong to the top-level
apache.org site instead)
I'm just considering the narrative info, not the podling status pages
or clutch stuff in this refactoring. That status info might move to
podlings.incubator.apache.org to better separate it and keep the main
site minimal.
I've got some draft content for 2. and 3., that I've been collecting
in my mentoring activities.
WDYT?
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
