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.
Andy
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 README.md
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]
- coveralls.io coverage service [2]
- Latest maven release [3]
- shield.io license badge [4]
This services can be activated and a nice badge can be added to the
README.md. 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 README.md 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] http://travis-ci.org
[2] http://coveralls.io
[3] https://github.com/jirutka/maven-badges
[4] http://shield.io
[5] https://github.com/britter/commons-lang
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
