Apache Example project?

2016-10-02 Thread Stian Soiland-Reyes 
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/ 
justinmclean /
ApacheWombat

Re: Apache Example project?

2016-10-02 Thread James Bognar 
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  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/ 
> justinmclean /
> ApacheWombat
> 
>


-- 
James Bognar

Re: [VOTE] HTrace 4.2-incubating release

2016-10-02 Thread Drew Farris 
Mike,

If this release can only be built with Maven 3.0.4, would it make sense to
set up the enforcer plugin to fail the build if an attempt is made to build
with something other than that version? It could help others avoid some
gnashing of teeth and document the specific requirement.

Drew

On Sat, Oct 1, 2016, 6:31 PM Mike Drob  wrote:

> Justin,
>
> Yes, the compilation issue is MSHADE-148, also captured in HTRACE-236. [1]
>
> Although MSHADE-148 is resolved, you can see discussion towards the end of
> the JIRA that identifies it as still a problem for HTrace and others. For
> now, the workaround is to either build with Maven 3.0.4, which I will agree
> is inconvenient and needs to be better documented.
>
> I will file JIRA issues for your other suggestions shortly.
>
> Mike
>
> [1]: https://issues.apache.org/jira/browse/HTRACE-236
>
> On 2016-09-30 21:40 (-0500), Justin Mclean 
> wrote:
> > Hi,
> >
> > +0 binding as I had issues compiling (see below). Happy to change to +1
> if I can compile everything else is good.
> >
> > I checked:
> > - incubating in name
> > - signature and hashes good
> > - DISCLAIMER exists
> > - LICENSE is missing MIT licensed normalise.css bundled in several
> bootstrap files. e.g. [2]. Please fix for net release.
> > - NOTICE good
> > - All Apache files have ASF header
> > - No unexpended binary files
> > - Can’t compile
> >
> > You may want to remove the copyright line from this ASF header [1]
> >
> > The compile seem to get stuck in an infinite loop at this point:
> > [INFO] Replacing original artifact with shaded artifact.
> > [INFO] Replacing
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/target/htrace-hbase-4.2.0-incubating.jar
> with
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/target/htrace-hbase-4.2.0-incubating-shaded.jar
> > [INFO] Dependency-reduced POM written at:
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > [INFO] Dependency-reduced POM written at:
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > [INFO] Dependency-reduced POM written at:
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > [INFO] Dependency-reduced POM written at:
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > …
> >
> > Issue may be related to this bug? [3] However changing the pom to use
> shade 2.4.1 didn’t fix the issue.
> >
> > Thanks,
> > Justin
> >
> > 1. ./bin/gen_thrift.sh
> > 2. ./htrace-htraced/go/web/lib/bootstrap-3.3.1/css/bootstrap.css
> > 3. https://issues.apache.org/jira/browse/MSHADE-148
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] HTrace 4.2-incubating release

2016-10-02 Thread John D. Ament 
All,

You can also build using mvn clean install
-DcreateDependencyReducedPom=false (which is what I did).

John

On Sun, Oct 2, 2016 at 8:53 AM Drew Farris  wrote:

> Mike,
>
> If this release can only be built with Maven 3.0.4, would it make sense to
> set up the enforcer plugin to fail the build if an attempt is made to build
> with something other than that version? It could help others avoid some
> gnashing of teeth and document the specific requirement.
>
> Drew
>
> On Sat, Oct 1, 2016, 6:31 PM Mike Drob  wrote:
>
> > Justin,
> >
> > Yes, the compilation issue is MSHADE-148, also captured in HTRACE-236.
> [1]
> >
> > Although MSHADE-148 is resolved, you can see discussion towards the end
> of
> > the JIRA that identifies it as still a problem for HTrace and others. For
> > now, the workaround is to either build with Maven 3.0.4, which I will
> agree
> > is inconvenient and needs to be better documented.
> >
> > I will file JIRA issues for your other suggestions shortly.
> >
> > Mike
> >
> > [1]: https://issues.apache.org/jira/browse/HTRACE-236
> >
> > On 2016-09-30 21:40 (-0500), Justin Mclean 
> > wrote:
> > > Hi,
> > >
> > > +0 binding as I had issues compiling (see below). Happy to change to +1
> > if I can compile everything else is good.
> > >
> > > I checked:
> > > - incubating in name
> > > - signature and hashes good
> > > - DISCLAIMER exists
> > > - LICENSE is missing MIT licensed normalise.css bundled in several
> > bootstrap files. e.g. [2]. Please fix for net release.
> > > - NOTICE good
> > > - All Apache files have ASF header
> > > - No unexpended binary files
> > > - Can’t compile
> > >
> > > You may want to remove the copyright line from this ASF header [1]
> > >
> > > The compile seem to get stuck in an infinite loop at this point:
> > > [INFO] Replacing original artifact with shaded artifact.
> > > [INFO] Replacing
> >
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/target/htrace-hbase-4.2.0-incubating.jar
> > with
> >
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/target/htrace-hbase-4.2.0-incubating-shaded.jar
> > > [INFO] Dependency-reduced POM written at:
> >
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > > [INFO] Dependency-reduced POM written at:
> >
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > > [INFO] Dependency-reduced POM written at:
> >
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > > [INFO] Dependency-reduced POM written at:
> >
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > > …
> > >
> > > Issue may be related to this bug? [3] However changing the pom to use
> > shade 2.4.1 didn’t fix the issue.
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. ./bin/gen_thrift.sh
> > > 2. ./htrace-htraced/go/web/lib/bootstrap-3.3.1/css/bootstrap.css
> > > 3. https://issues.apache.org/jira/browse/MSHADE-148
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: Apache Example project?

2016-10-02 Thread Jean-Baptiste Onofré 

It sounds like a good idea.

+1

Regards
JB

On 10/02/2016 01:17 PM, Stian Soiland-Reyes 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/ 
justinmclean /
ApacheWombat




--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] HTrace 4.2-incubating release

2016-10-02 Thread Jean-Baptiste Onofré 

+1 (binding)

Checked:
- signature
- DISCLAIMER, NOTICE, LICENSE
- ASF headers

I didn't try to build.

Regards
JB

On 09/30/2016 07:16 PM, Mike Drob wrote:

Resending this after being told that I used an incorrect subject format.

On 2016-09-29 21:20 (-0500), "Mike Drob" wrote:

Dear IPMC, please vote on our latest release candidate as an Apache Incubator 
project.

Apache HTrace (incubating), has voted to release the below referenced Apache 
HTrace 4.2.0-incubating release candidate.

Vote thread here:
https://lists.apache.org/thread.html/4123e994c752eabaf3f11d5ca13af4182530f001f7a5cbd52862@%3Cdev.htrace.apache.org%3E

And results thread here:
https://lists.apache.org/thread.html/6dfe32eaa84ff36519816029e730e7a5ae9d5ab13ecc1d686fff@%3Cdev.htrace.apache.org%3E

The source tarball, hashes, and signing are here:
https://dist.apache.org/repos/dist/dev/incubator/htrace/htrace-4.2.0RC0/

Related maven artifacts are posted here:
https://repository.apache.org/content/repositories/orgapachehtrace-1017

The tag for the RC is here:
https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=tree;h=7db3ed8cd93ed49366b518474a44d9267742960e;hb=7c0ae16b71683b71908cae0e59472f3a92074c19

The KEYS file with the key used signing is available here:
https://dist.apache.org/repos/dist/dev/incubator/htrace/KEYS

The vote will be open for 72 hours.

[ ] +1 Release this package as Apache HTrace 4.2.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release this package because ...

Thanks,
Mike

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Apache Example project?

2016-10-02 Thread Roman Shaposhnik 
On Sun, Oct 2, 2016 at 4:17 AM, Stian Soiland-Reyes  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

Re: [DISCUSS] Olympian Incubation Proposal

2016-10-02 Thread Roman Shaposhnik 
On Sat, Oct 1, 2016 at 8:05 AM, Niclas Hedhman  wrote:
> Agree with you on all points, Taylor.
>
> And I am even quite surprised to see the number of people backing the
> project, yet Apache is adamant to get involved. It feels a little bit like
> the "Community over Code" and "Independent of any Corporate Influences"
> have both received a big fat slap in their faces, and I think this hurts
> the ASF more than any fallout with named corporation.
>
> Disappointing to me...

That was my initial reaction as well, but then I thought some more and
ultimately
decided that expecting a bit more up-front community action was a
prudent choice.

What I'd like to see is a proof that ASF or no ASF the community wants to take
matters into its own hands and fork away. For now it isn't actually
obvious to me.

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Apache Example project?

2016-10-02 Thread Dylan Bethune-Waddell 
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  on behalf of Roman Shaposhnik 

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  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

Re: [DISCUSS] Olympian Incubation Proposal

2016-10-02 Thread P. Taylor Goetz 


> On Oct 2, 2016, at 11:55 AM, Roman Shaposhnik  wrote:
> 
> 
> ultimately
> decided that expecting a bit more up-front community action was a
> prudent choice.
> 
> What I'd like to see is a proof that ASF or no ASF the community wants to take
> matters into its own hands and fork away. For now it isn't actually
> obvious to me.
> 
> Thanks,
> Roman.

Now that a move to the ASF is (currently) off the table, the community is 
regrouping to host the project elsewhere. Once basic infrastructure is in place 
there will likely be some sort of announcement. Proof will come.

-Taylor
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] HTrace 4.2-incubating release

2016-10-02 Thread justin 
Hi,

Chang my vote to +1 binding as I managed to get it ti compile.

Thanks,
Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Apache Example project?

2016-10-02 Thread Luciano Resende 
+1,

I had started something similar, at least on the website side, with best
practices and required branding items.

Please consider adding it to the "example" project :

https://github.com/apache/apache-website-template


On Sun, Oct 2, 2016 at 9:05 AM, Dylan Bethune-Waddell <
dylan.bethune.wadd...@mail.utoronto.ca> wrote:

> 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  on behalf of Roman
> Shaposhnik 
> 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 
> 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
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/