An exciting new app package?  (I don't have a particular one in mind.)

On Tue, Feb 3, 2015 at 1:45 PM, Steve Loughran <[email protected]>
wrote:

> Maybe we should start with some discussion on the list.
>
> What do we think we could get someone with no knowledge of the project do
> in 3 months. Assuming Java coding skills, but probably not OSS & test-first
> processes?
>
> What would we like them to do?
>
> -steve
>
>
>
> On 3 February 2015 at 20:41:25, Sumit Mohanty ([email protected]
> <mailto:[email protected]>) wrote:
>
> I think we should. How do we gather project ideas?
> Should we create JIRAs and then select one or more from the list and then
> add the gsoc2015 labels to the selected ones.
>
> -Sumit
> ________________________________________
> From: Steve Loughran <[email protected]>
> Sent: Tuesday, February 03, 2015 7:51 AM
> To: Slider Dev
> Subject: Fw: Google Summer of Code 2015 is coming
>
> Do we want to do some GSoC mentoring in the summer?
>
> This is a great chance to get something self-contained done.
>
> Of course, it must (a) be something interesting and (b) have the guarantee
> of support from the rest of the team. The goal is to get someone used to
> developing OSS projects, as part of a team: not coding on their own fixing
> random JIRAs.
>
>
>
>
> On 2 February 2015 at 22:46:09, Ulrich Stärk ([email protected]<mailto:
> [email protected]>) wrote:
>
> Hello PMCs (incubator Mentors, please forward this email to your podlings),
>
> Google Summer of Code [1] is a program sponsored by Google allowing
> students to spend their summer
> working on open source software. Students will receive stipends for
> developing open source software
> full-time for three months. Projects will provide mentoring and project
> ideas, and in return have
> the chance to get new code developed and - most importantly - to identify
> and bring in new committers.
>
> The ASF will apply as a participating organization meaning individual
> projects don't have to apply
> separately.
>
> If you want to participate with your project we ask you to do the
> following things by no later than
> 2015-02-13 19:00 UTC (applications from organizations close a week later)
>
> 1. understand what it means to be a mentor [2].
>
> 2. record your project ideas.
>
> Just create issues in JIRA, label them with gsoc2015, and they will show
> up at [3]. Please be as
> specific as possible when describing your idea. Include the programming
> language, the tools and
> skills required, but try not to scare potential students away. They are
> supposed to learn what's
> required before the program starts.
>
> Use labels, e.g. for the programming language (java, c, c++, erlang,
> python, brainfuck, ...) or
> technology area (cloud, xml, web, foo, bar, ...) and record them at [5].
>
> Please use the COMDEV JIRA project for recording your ideas if your
> project doesn't use JIRA (e.g.
> httpd, ooo). Contact [email protected] if you need assistance.
>
> [4] contains some additional information (will be updated for 2015
> shortly).
>
> 3. subscribe to [email protected]; restricted to potential
> mentors, meant to be used as a
> private list - general discussions on the public [email protected]
> list as much as possible
> please). Use a recognized address when subscribing (@apache.org or one of
> your alias addresses on
> record).
>
> Note that the ASF isn't accepted as a participating organization yet,
> nevertheless you *have to*
> start recording your ideas now or we might not get accepted.
>
> Over the years we were able to complete hundreds of projects successfully.
> Some of our prior
> students are active contributors now! Let's make this year a success again!
>
> Cheers,
>
> Uli
>
> P.S.: Except for the private parts (label spreadsheet mostly), this email
> is free to be shared
> publicly if you want to.
>
> [1] http://www.google-melange.com/gsoc/homepage/google/gsoc2015
> [2] http://community.apache.org/guide-to-being-a-mentor.html
> [3] http://s.apache.org/gsoc2015ideas
> [4] http://community.apache.org/gsoc.html
> [5] http://s.apache.org/gsoclabels
>
>

Reply via email to