The benefits of such an example project to the open source community would extend to projects that do not yet or will never incubate at Apache. If there is some consideration given to that group from the outset, even more so. Wouldn't this broadcast The Apache Way to a wider audience and let those wishing to found any open source project "take what they need" from it without requiring them to conform entirely?
In any case I think this is a great idea. +1 (non-binding). ________________________________ From: shaposh...@gmail.com <shaposh...@gmail.com> on behalf of Roman Shaposhnik <ro...@shaposhnik.org> Sent: Sunday, October 2, 2016 11:24:53 AM To: general@incubator.apache.org Subject: Re: Apache Example project? On Sun, Oct 2, 2016 at 4:17 AM, Stian Soiland-Reyes <st...@apache.org> wrote: > Hi, > > There's been many discussions recently around what is the best practice for > git tagging, release procedures, licencing notes, web site publishing etc. > > The landscape is always changing as technologies and INFRA procedures > evolve (yay!). Hunting around the different existing projects for > inspiration can be fun for podlings, but time consuming , as well as being > a bit variable as different mentors have different reference points. > > I'm all for diversity and that projects settle this themselves. However I > wonder if it would make sense to gather these things as a kind of Examplar > project? > > I'm thinking of extending Justin's excellent LICENSE and NOTICE example > project [1] [2] but make it a real with its own apache.org git repository > and website that anyone in the incubator can help update. > > That way new podlings can have a quick look, bootstrap and "mutate" > accordingly (as well as shop around other projects or bring in whatever > they had outside) > > We can call it Apache Example, and even do an actual org.apache.example > release of it; natively from the Incubator IPMC! > > So for instance I think it would make sense to have a multi-module Maven > project with an assembly-based source releases and artifacts to Central, > Github pull requests enabled, and a Jekyll-based Markdown site managed with > git2pubsubkub. That way we can showcase the "modern" Apache way without > being all bleeding edge. > > Thoughts? Do I need to write a proposal...? :-) Huge +1 Thanks, Roman. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
