Return-Path: X-Original-To: apmail-community-dev-archive@minotaur.apache.org Delivered-To: apmail-community-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8C13717EBB for ; Sat, 14 Mar 2015 14:45:09 +0000 (UTC) Received: (qmail 96432 invoked by uid 500); 14 Mar 2015 14:45:09 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 96187 invoked by uid 500); 14 Mar 2015 14:45:09 -0000 Mailing-List: contact dev-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list dev@community.apache.org Received: (qmail 96176 invoked by uid 99); 14 Mar 2015 14:45:09 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Mar 2015 14:45:09 +0000 Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 946FD1A038C for ; Sat, 14 Mar 2015 14:45:08 +0000 (UTC) Received: by wixw10 with SMTP id w10so6384594wix.0 for ; Sat, 14 Mar 2015 07:45:07 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.24.35 with SMTP id r3mr46177297wjf.125.1426344307059; Sat, 14 Mar 2015 07:45:07 -0700 (PDT) Received: by 10.195.11.194 with HTTP; Sat, 14 Mar 2015 07:45:06 -0700 (PDT) In-Reply-To: References: <54F61ED3.6040105@apache.org> Date: Sat, 14 Mar 2015 15:45:06 +0100 Message-ID: Subject: Fwd: [ALL] Badges for github README.md From: Benedikt Ritter To: dev@community.apache.org Content-Type: multipart/alternative; boundary=047d7b5d8d9dbff569051140a94f --047d7b5d8d9dbff569051140a94f Content-Type: text/plain; charset=UTF-8 Hi, is anybody aware of any (legal) problems if projects use services like Travis CI [1] or coveralls.io [2] for mirrors at github? An example of how that would look like can be found at [3] Thanks, Benedikt [1] http://travis-ci.org [2] http://coveralls.io [3] https://github.com/britter/commons-lang ---------- Forwarded message ---------- From: Gary Gregory Date: 2015-03-04 20:24 GMT+01:00 Subject: Re: [ALL] Badges for github README.md To: Commons Developers List On Wed, Mar 4, 2015 at 9:59 AM, Benedikt Ritter wrote: > 2015-03-03 21:51 GMT+01:00 Andy Seaborne : > > > 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. > > > > Good point. I don't think this will be an issue, but we should be sure. Who > can I talk to about this? legal@? > You can! :-) Since you've taken the lead on the badges, you could follow it through to @legal. You probably know more about them than the rest of us. Gary > > > > > > 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-unsubscribe@commons.apache.org > > For additional commands, e-mail: dev-help@commons.apache.org > > > > > > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter > -- E-Mail: garydgregory@gmail.com | ggregory@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition Spring Batch in Action Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter --047d7b5d8d9dbff569051140a94f--