On Wed, Feb 18, 2015 at 11:31 PM, Aaron Meurer <asmeu...@gmail.com> wrote:
> If you wanted to make any edits, now is the time. I am finishing up my
> edits now and am going to submit what I have. I will also check again on
> Friday to see if anyone made any changes and submit again if there are
> (also please let me know here if you do make changes so that I won't
> forget).
>
> We also need people to update the ideas page and the application template.
> The idea page is very important. At the summits, we've heard from Google
> that the ideas page is the most important part of the application. The
> template is perhaps less important for Google (although who knows), but
> more important for the students, as it tells them how to get started with
> the project, and what to put in their proposals.
>
> I have a question about the application. There is a paragraph:
>
> This year we plan to require each student to spend at least 10% or more of
>> their time in reviewing other people's pull requests (PRs) (most of these
>> will
>> invariably be from other GSoC students, since they tend to be the most
>> active
>> contributors during the summer time).
>
> I think this 10% figure can be hard to measure. Can we have something
concrete like being a lead reviewer (for the lack of a better term) to at
least one PR (newbie PRs might be good for this purpose since they are
usually easy to review). This 'one patch + one review' might be a good idea.
Thoughts?
Saurabh
> That way, they will become more
>> integrated in our community and hopefully more likely to stay after the
>> GSoC
>> is over. Historically, students that were active in our PR queue were more
>> likely to stay afterwords.
>
>
> ("this year" refers to last year, as this is unmodified from the 2014
> application)
>
> Did we actually do this? Should we leave it in that we want to do this? I
> don't particularly remember making strong on this requirement, but maybe
> other mentors did a better job than I did. If you did make your students
> review pull requests, did it help?
>
> Aaron Meurer
>
> On Sun, Feb 15, 2015 at 2:10 PM, Aaron Meurer <asmeu...@gmail.com> wrote:
>
>> I am going through and making small changes now. Kudos to Sean for
>> fixing up the application and making his own changes already.
>>
>> Does anyone have any suggestions for larger changes that should be
>> made to the application?
>>
>> Note that the deadline is this Friday (the 20th).
>>
>> As a side note, as part of updating one of the sections, I cleaned up
>> the push access list a little bit, removing anyone who hasn't pushed
>> anything to the SymPy main repo in a over a year. If you used to have
>> push access and you don't any more, just let me know and I can add you
>> back.
>>
>> Aaron Meurer
>>
>> On Mon, Feb 9, 2015 at 4:58 PM, Aaron Meurer <asmeu...@gmail.com> wrote:
>> > The GSoC organization application period has started. The application
>> > deadline is February 20. Action items:
>> >
>> > - If you are a prospective student, you don't need to do anything yet.
>> > Just continue to interact with the community here, on GitHub, and on
>> > Gitter.
>> >
>> > - If you are willing to mentor, please add your name to the bottom of
>> > https://github.com/sympy/sympy/wiki/GSoC-2015-Ideas. This is very
>> > important. Google won't accept our application if we don't have any
>> > potential mentors. It also affects how many slots we get. Even if you
>> > are only willing to mentor certain kinds of projects, still put your
>> > name there, with the projects you will mentor.
>> >
>> > - Everyone, please review the application
>> > https://github.com/sympy/sympy/wiki/GSoC-2015-Organization-Application.
>> > As of yet, this is still a copy of last year's application. I will go
>> > through later and at least make sure that the questions are still
>> > correct.
>> >
>> > Feel free to just make changes to the wiki page. I will review all
>> > changes that come in.
>> >
>> > If you have any suggestions that you would like to discuss regarding
>> > the application, feel free to do so here.
>> >
>> > Aaron Meurer
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sympy+unsubscr...@googlegroups.com.
> To post to this group, send email to sympy@googlegroups.com.
> Visit this group at http://groups.google.com/group/sympy.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2BkZ%3DuntY1V8s2ATgWwDmfYY3BUhTSiS23zxx7XMRSXMg%40mail.gmail.com
> <https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2BkZ%3DuntY1V8s2ATgWwDmfYY3BUhTSiS23zxx7XMRSXMg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sympy+unsubscr...@googlegroups.com.
To post to this group, send email to sympy@googlegroups.com.
Visit this group at http://groups.google.com/group/sympy.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sympy/CAP%2BqjMgbm5CqKmOCr1voUGqW9zcDhOQxh1F9Cyt2oCdvSehKHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
