Re: ASF accepted as a mentoring organization for Google Summer of Code 2015
Thanks, Greg! That works --better to be a bit wordy and clear vs. brief and vague g We can always write QUOTE, said Greg Stein, ASF Vice Chairman (and co-creator of the GSoC program, while working at Google in 2005). Now for the quote itself... I'll put that in the draft that I'll be sending over later. Cheers chat soon,Sally From: Greg Stein gst...@gmail.com To: Sally Khudairi s...@apache.org Cc: Ulrich Stärk u...@spielviel.de; pr...@apache.org pr...@apache.org; dev@community.apache.org dev@community.apache.org Sent: Saturday, 14 March 2015, 18:36 Subject: Re: ASF accepted as a mentoring organization for Google Summer of Code 2015 Sure, that sounds great! … are you looking for something like co-creator of the GSoC program, while working at Google in 2005 ?? That's a bit of a mouthful, but is that the direction you're thinking? And please go ahead an draft up a quote. I'm not quite sure the angle you're looking at, so best if you go first :-) Thx,-g On Sat, Mar 14, 2015 at 5:13 PM, Sally Khudairi s...@apache.org wrote: Greg, I'd like to put a placeholder for a quote for you in the announcement as well (the lead quote will be coming from Uli). How would you like to have your attribution described in relation to GSoC? ASF Vice Chairman and @@WHATEXACTLY Of course, I'll be happy to get a quote directly from you (vs. having to de-Sally-fy my proposed blurb) :-) If you don't want to be quoted, that's OK; I can use Ross as backup. Thanks so much, Sally From: Greg Stein gst...@gmail.com To: Sally Khudairi s...@apache.org Cc: Ulrich Stärk u...@spielviel.de; pr...@apache.org pr...@apache.org; dev@community.apache.org dev@community.apache.org Sent: Friday, 13 March 2015, 17:22 Subject: Re: ASF accepted as a mentoring organization for Google Summer of Code 2015 The very first year was 2005. Thus, 2015 would be the 11th GSoC. As one of the two people to launch/create GSoC, you can call me authoritative on the dates :-P On Fri, Mar 13, 2015 at 4:13 PM, Sally Khudairi s...@apache.org wrote: What? Really? I had it in the Did You Know? section last week as 10th also. AND, more importantly, if my calculations are off, then in https://blogs.apache.org/foundation/date/20141119 the 2013 entry as eighth consecutive year is wrong too. Who has the correct count? It really is 11? Not that I don't trust you, I now am feeling quite lost. Cheers, Sally From: Ulrich Stärk u...@spielviel.de To: pr...@apache.org pr...@apache.org Cc: dev@community.apache.org; Sally Khudairi s...@apache.org Sent: Friday, 13 March 2015, 17:09 Subject: Re: ASF accepted as a mentoring organization for Google Summer of Code 2015 Hey Sally, I just read the announcement and it says The ASF has been accepted as a Google Summer of Code mentoring organization for the 10th consecutive year. If I'm not mistaken it's the 11th year ;) Cheers, Uli On 2015-03-12 18:42, Sally Khudairi wrote: Thanks, Uli. I did post about it in our weekly news round-up. Happy to work with you on a press release. Who is the ASF lead on GSoC. You? Who from ComDev will be at ApacheCon? Are you planning to do something special there? Cheers,Sally From: Ulrich Stärk u...@spielviel.de To: pr...@apache.org pr...@apache.org; Sally Khudairi s...@apache.org Cc: dev@community.apache.org dev@community.apache.org Sent: Thursday, 12 March 2015, 13:31 Subject: Re: ASF accepted as a mentoring organization for Google Summer of Code 2015 And again recycling this. I think we missed 2014 so I want to make sure to get an announcement out this year. Cheers, Uli On 2013-04-09 14:11, Ulrich Stärk wrote: Recycling last years email on the topic. All dates and links updated. It would be cool if we could get this out asap. Is there anything else you need? Uli Original Message Subject: Apache Software Foundation accepted as a mentoring organization for Google Summer of Code 2012 Date: Sat, 17 Mar 2012 23:21:40 +0100 From: Ulrich Stärk u...@spielviel.de To: pr...@apache.org CC: dev@community.apache.org Hey Sally Co., this year we won't forget to provide you with some infos on our GSoC endeavours. Yesterday, we have been accepted as a mentoring organization for Google Summer of Code 2015 [1],[2]. This means that over the summer, our committers will mentor students that are sponsored by Google and will be working on our projects. The program helps us not only to get some code written but also to introduce students into open source development and hopefully recruit some new long-term committers. More information on the program is available at [3]. Students are now encouraged to discuss ideas with the respective projects and begin drafting proposals. An extensive list of already existing project ideas is available at [4]. The actual application phase is from March 16 until March 27,
Re: commit rights to ComDev non-community.a.o site resources
Hi, On Mar 14, 2015, at 11:38 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: Hi, I lately gave patches for projects-new that were not applied: it seems there is a problem to determine who should do it (to avoid projects-new to be a single-man affair). Then I made some investigations: in the last board report for ComDev [1], I think I found the cause: Since artifacts produced by ComDev are usually documentation on our website which is writable for all Apache committers, we usually do not add committers to the ComDev project. Then should projects(-new).apache.org become writeable for all Apache committers too? Same for reporter.apache.org? +1 That makes sense to allow all the Apache committers to contribute. Antoine Regards, Hervé [1] https://whimsy.apache.org/board/minutes/Community_Development.html
Fwd: [ALL] Badges for github README.md
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 garydgreg...@gmail.com Date: 2015-03-04 20:24 GMT+01:00 Subject: Re: [ALL] Badges for github README.md To: Commons Developers List d...@commons.apache.org On Wed, Mar 4, 2015 at 9:59 AM, Benedikt Ritter brit...@apache.org wrote: 2015-03-03 21:51 GMT+01:00 Andy Seaborne a...@apache.org: 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-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ 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
commit rights to ComDev non-community.a.o site resources
Hi, I lately gave patches for projects-new that were not applied: it seems there is a problem to determine who should do it (to avoid projects-new to be a single-man affair). Then I made some investigations: in the last board report for ComDev [1], I think I found the cause: Since artifacts produced by ComDev are usually documentation on our website which is writable for all Apache committers, we usually do not add committers to the ComDev project. Then should projects(-new).apache.org become writeable for all Apache committers too? Same for reporter.apache.org? Regards, Hervé [1] https://whimsy.apache.org/board/minutes/Community_Development.html
