commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Seaborne <>
Subject Re: [ALL] Badges for github
Date Tue, 03 Mar 2015 20:51:31 GMT
Sorry to interrupt - this is not a "for" or "against" comment but 
something I want to make sure was considered.

Apache is independent of any commercial entity.

For example, there was a discussion about the "github/forkme" stripe in 
project home pages.  The outcome was that it was too much like endorsing 
one commercial player.

This isn't the same but some of those are commercial operations. 
Anything that implies endorsement of their services needs to be 
carefully handled.


On 03/03/15 19:31, Benedikt Ritter wrote:
> Hi all,
> as you probably know, I'm a big fan of github :-) I've added
> files to some of our components. It should make the github repositories
> more welcoming for github contributors.
> There are a variety of services available which integrate nicely with
> github repositories:
> - Travis CI build service [1]
> - coverage service [2]
> - Latest maven release [3]
> - license badge [4]
> This services can be activated and a nice badge can be added to the
> I really like the combination of the travis and the coveralls
> badge, because it will build and evaluate coverage for PR requests
> automatically. This way you don't have to look at PR which break the build
> or have a negative impact on the coverage.
> I've activated these services for my commons-lang fork [5]. If nobody has
> objections, I would like to add this to the generation target in
> the commons-build-plugin.
> Note that travis and converalls have to be activated by a INFRA. I've
> already seen jira requests for this, which have been resolved by INFRA, so
> this should not be a problem.
> Regards,
> Benedikt
> [1]
> [2]
> [3]
> [4]
> [5]

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message