Re: Process, policy and best practice
Marvin Humphrey <[email protected]>
| Newsgroups | gmane.comp.apache.community.devel,gmane.comp.apache.commons.general |
|---|---|
| Message-ID | <CAAS6=7h1dGjwXgWU=JwRdUQME96O7JrspcbC=T0fxe-rXavOTQ@mail.gmail.com> |
On Mon, Apr 1, 2013 at 3:22 PM, Ross Gardler <rgardler-yabmN0NJNhHwJSu5WlVMogC/[email protected]> wrote: > The role of ComDev would not be to define policy, only to document and > curate it. As Greg said when this first came up over a year ago - most of > the actual writing is done. There is no single source of policy for ComDev to document and curate -- there are many conflicting interpretations of policy which are continually relitigated year after year. Consider what it took to assemble the licensing how-to at <http://www.apache.org/dev/licensing-howto.html>. There was a fair amount of debate once we had a draft (see LEGAL-155), but that's the tip of the iceberg -- the real work was developing a sophisticated enough understanding of a difficult issue to write up a draft which was inoculated against all major objections and could withstand the review phase. I expect that refining <http://incubator.apache.org/guides/releasemanagement.html> will be a similarly challenging undertaking. I don't see how what needs to be done can be achieved by anybody other than volunteers with significant expertise and patience. Marvin Humphrey