That's already in progress as part of this year's budget planning :-) Of course this is distinct from policy. For example: Should the policy say projects are limited to items on the infra core services list?
Ross Sent from my Windows Phone ________________________________ From: Shane Curcuru<mailto:a...@shanecurcuru.org> Sent: 1/15/2015 4:55 PM To: Marvin Humphrey<mailto:mar...@rectangular.com>; general@incubator.apache.org<mailto:general@incubator.apache.org> Subject: Re: What is "The Apache Way"? Dear David: I would *love* to see you propose whatever set of requirements that ASF infra as a service sees as appropriate for our projects, given our history, budget, and a view to ensuring reliable service for the future. Then, include a clear list of bullet points which should go into the Project Requirements document. Then president@/board@ can decide what to officially stamp as hard policy vs. recommended suggestions, put them in Project Requirements, and take the *DRAFT* off. But everything happens better when there's a concrete plan up front, and I'm confident your infra team will come up with the right requirements as relates to infra for projects. - Shane On 1/15/15 6:51 PM, Marvin Humphrey wrote: > On Tue, Jan 13, 2015 at 9:37 AM, David Nalley <da...@gnsa.us> wrote: > >> My assumption was that 'setting binding policy on projects' was >> something specifically excluded from my level of authority, as an >> officer derived from the Office of the President. If that is not the >> case, I am happy to define and publish such things within the realm of >> infrastructure. > > Hi David, > > Since it's seems that you're willing and we have good rapport, I think it > might work well to kick things off with Infra. Here's my provisional agenda: > > 1. Hash out DRAFT policies with Infra. > 2. Work with Legal Affairs to complete the release policy codification > initiative. > 3. Review the top level "Project Requirements" document. > 4. ... > > I'm presently contemplating that Infrastructure would curate two policies: > > * Infrastructure Policy > * Release Distribution Policy > > Infrastructure Policy would cover topics such as canonical repository location > and usage of external services, as you and Doug discussed upthread. > > Release Distribution Policy would cover technical details of releasing, such > as cryptographic signature specs, responsibility for keeping dist dirs tidy, > and so on. These aspects are covered (incompletely) in the present "Releases > Policy" (<http://www.apache.org/dev/release>), but are omitted from the > clarified release policy which Legal Affairs is being asked to take ownership > of (<https://github.com/rectang/asfrelease>) because they are outside Legal's > domain. > > If that sounds workable, let me mull things over for a bit, then I plan to > show up on infrastructure-dev@apache with some sketches. The content is > ultimately your call and I don't expect to get all the details right, but > before discussions commence in earnest, I'd like to mess around with language > and high-level organization to seek out approaches that are as minimalist and > flexible as possible. > > Marvin Humphrey > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
