incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Bognar <james.bog...@salesforce.com>
Subject Re: Apache Example project?
Date Sun, 02 Oct 2016 12:34:56 GMT
As someone currently trying to set up the process for a new podling, this
would have made my life so much simpler.  We've been working on it for
about 3 months now setting it up, trying to glean information from various
sites, and trying to figure out which information is outdated.

It sounds like it would be a good resource for existing projects as well
trying to standardize on newer technologies.

+1!

On Sunday, October 2, 2016, Stian Soiland-Reyes <stain@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...? :-)
>
> 1. https://vimeo.com/171210141
> 2. https://github.com/ <https://github.com/justinmclean/ApacheWombat>
> justinmclean <https://github.com/justinmclean/ApacheWombat>/
> <https://github.com/justinmclean/ApacheWombat>ApacheWombat
> <https://github.com/justinmclean/ApacheWombat>
>


-- 
James Bognar

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message