Google Code-In

[Aaron Meurer]

Google has announced the application period for Google Code-In 2012.
As decided earlier
(https://groups.google.com/d/topic/sympy/KrpvxADqAxM/discussion), we
should apply. See
http://www.google-melange.com/gci/homepage/google/gci2012 for more
information about it, as well as
http://code.google.com/p/google-code-in/wiki/GCIMentorInformation2012.

The application deadline is November 5, two weeks from today. I need
help doing two things:

- Edit the application. I have started the organization application
based on last year's at
https://github.com/sympy/sympy/wiki/GCI-2012-Organization-Application.
But we need to edit it to talk about our experiences with the program
from last year.

- We need to create tasks. I have recreated the GCI labels in the
issue tracker. A couple of notes here:

* There are only five categories this year. They have consolidated
outreach/research and documentation/training into single tasks, and
they have eliminated translation tasks. I haven't yet fixed this in
the issue tracker (but anyone who can add labels can bulk edit issues,
so feel free to do this).

* They have removed the difficulty ratings. All tasks should now have
the same difficulty. The metric that they are telling us is that a
task should take an experienced project member (that's you guys)
approximately two hours to complete. Anything harder should be broken
into multiple tasks.

We can also create tasks for SymPy-Bot, which uses the GitHub issue
tracker. See https://github.com/sympy/sympy-bot/issues?state=open. I
don't know how the permissions work with labels on GitHub, so let me
know if you are unable to add labels to issues. SymPy Live and SymPy
Gamma are also good sources for tasks (add these to the Google Code
issue tracker).

We need to have a good chunk of tasks ready by the 5th to show Google,
but not all of them have to be created at that point. We do need to
have a certain number of each type, though. Additionally, this year,
we can add tasks at any time, so there will not be a hard deadline for
that later on like there was last year.

- If you are interested in mentoring, please add your name to the
bottom of the application. I guess we should also create a mentors
page like the one we had last year. Also, go to google-melange.com
and create a profile (you have to do it again even if you've mentored
before, as it resets with each program).

I would greatly appreciate help with this.

Aaron Meurer

[Aaron Meurer]

If you are interested in helping out for GCI, at the very least add

your name to the bottom of

https://github.com/sympy/sympy/wiki/gci-2012-organization-application
(under the "Please tell us about how your organization has prepared
for Google Code-in..." question). It would also help out if you
edited the application to update it and/or did some work
creating/tagging issues for tasks.

So far, no one except for Sean seems to have done anything with this.
If no one helps out with this, I will take that to mean that we don't
have enough people interested in volunteering to be mentors, and I
won't submit the application.

Aaron Meurer

[Dia Ken]

Hello,

I really want to help in creating or tagging issues for tasks but i'll participate as a student so i don't know  if i can do that or not .

--
You received this message because you are subscribed to the Google Groups "sympy" group.
To post to this group, send email to sy...@googlegroups.com.
To unsubscribe from this group, send email to sympy+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sympy?hl=en.

--

Greeting!
Kendhia :)

[Aaron Meurer]

Well, you can give us ideas, and the worse that can happen is that
we'll reject them.

What I really need right now is commitment by mentors. So far, only
two people (Sean and myself) have committed on the application.

Aaron Meurer

[Dia Ken]

ok, when can you bee available on irc channe ?

[Matthew Rocklin]

I've added myself to the mentor list. I'll probably be selective in the tasks I help out on though. 

[Aaron Meurer]

In the evening, mountain time. 

Aaron Meurer

[Stefan Krastanov]

I added myself and will add the plotting tasks shortly.

I think a very nice addition to our application would be a
before-after screenshot of sympy-live and sympy-gamma.

Stefan

[Stefan Krastanov]

Is there a spreadsheet for the tasks? Where should I start moving them
(the gci guys at the summit mentioned that it is a very bad idea to
submit a link to the bug tracker as a "list of tasks").

[Stefan Krastanov]

By the way the presence of "=" in the names of the CodeIn tasks seems
to break the search functionality.

[Bharath M R]

I can also help with GCI. I think Stefan Krastanov has covered most of the tasks

related to plotting. I will also add them if there is any.

Thanks,

Bharath M R

[Aaron Meurer]

Last year, I just did a CSV export of the issues and imported it into
Google Docs. Feel free to get a jump on this as well if you want.

By the way, did they make a distinction between just linking to a bug
tracker and saying that we've tagged a bunch of issues in the tracker?
I agree that just submitting a link to the issue tracker and saying
that any of them could be tasks is not very good.

Aaron Meurer

[Stefan Krastanov]

About the bug tracker: They were quite clear that they would like to
see a page that is not the bug tracker (even if we use special labels
for GCI and so on). A google docs spreadsheet is ok.

And they mentioned that the initial number of tasks should be around
100. I can easily prepare 20 to 30 tasks for the plotting module
(documentation, code and QA). You will have them by Wednesday. At that
point I will also prepare the screenshots of sympy live that I
mentioned.

Besides this there was no interesting information given out.

By the way, I will probably be able to mentor actively only the tasks
that I submit.

Finally, does the wiki on github support latex?

[Stefan Krastanov]

I tried to export to CSV, however the old categories are still not
corrected/removed and I can not remove them myself. I would prefer to
have this corrected before proceeding.

By the way, if I remember correctly in the list that we submitted last
year there were tasks that were not in the issue tracker. Shouldn't we
check them out? I have no idea where to find the old list.

[Aaron Meurer]

On Oct 29, 2012, at 1:23 PM, Stefan Krastanov <krastano...@gmail.com> wrote:

I tried to export to CSV, however the old categories are still not
corrected/removed and I can not remove them myself. I would prefer to
have this corrected before proceeding.

You should be able to edit issue labels, as well as bulk edit them. 

By the way, if I remember correctly in the list that we submitted last
year there were tasks that were not in the issue tracker. Shouldn't we
check them out? I have no idea where to find the old list.

The old list is at https://docs.google.com/spreadsheet/lv?key=0AiMKW-ZM-_fedFpSWm51VFBFZkdTRnh3WkhYRndSVXc (let me know if you can't read that). I'm pretty sure they all had issues, though. 

On 29 October 2012 20:09, Stefan Krastanov <krastano...@gmail.com> wrote:

About the bug tracker: They were quite clear that they would like to

see a page that is not the bug tracker (even if we use special labels

for GCI and so on). A google docs spreadsheet is ok.

And they mentioned that the initial number of tasks should be around

100. I can easily prepare 20 to 30 tasks for the plotting module

(documentation, code and QA). You will have them by Wednesday. At that

point I will also prepare the screenshots of sympy live that I

mentioned.

Note that we have to submit the application by pasting the answers into a form at google-melange.com. So if you want to include images, they will have to be on some separate page that we link to. 

Besides this there was no interesting information given out.

By the way, I will probably be able to mentor actively only the tasks

that I submit.

Finally, does the wiki on github support latex?

It used to, but I guess it doesn't any more. See https://github.com/sympy/sympy/wiki/Mathtest (that used to show a bunch of equations). 

[Stefan Krastanov]

about the latex math being unsupported anymore:
https://github.com/github/gollum/issues/288

[Stefan Krastanov]

I have moved training to documentation, research to QA and code, and
closed as wontfix the translation tasks.

I left open a few research tasks, but removed them from the CGI list
as they did not fit the new format.

[Stefan Krastanov]

I have started

https://docs.google.com/spreadsheet/ccc?key=0Allq_N-5TER9dHhDRVJxSTU4SEZ5X3FRZ1hhM3FIN3c#gid=0

If I remember correctly last year we agreed that from the point from
which we have this spreadsheet we should add tasks both to the
spreadsheet and to the issue tracker. Right?

Anyway, the spreadsheet is just the import of the tasks, it is not
formated and augmented yet. Help needed...

[Stefan Krastanov]

By the way, on first glance some of the tasks in the list seem like
they have already be done last year and we forgot to close the issues.

[Aaron Meurer]

On Mon, Oct 29, 2012 at 6:07 PM, Stefan Krastanov
<krastano...@gmail.com> wrote:
> I have started
>
> https://docs.google.com/spreadsheet/ccc?key=0Allq_N-5TER9dHhDRVJxSTU4SEZ5X3FRZ1hhM3FIN3c#gid=0
>
> If I remember correctly last year we agreed that from the point from
> which we have this spreadsheet we should add tasks both to the
> spreadsheet and to the issue tracker. Right?

If it will help, you can add another tag to Google Code,
CodeInAddedToSpreadsheet, to keep track of what's been added to the
spreadsheet.

>
> Anyway, the spreadsheet is just the import of the tasks, it is not
> formated and augmented yet. Help needed...

Hopefully we won't need to do this (at least to much of a degree)
until later. Just a simple import should be OK for the application
period, no?

Aaron Meurer

[Aaron Meurer]

On Mon, Oct 29, 2012 at 11:48 PM, Aaron Meurer <asme...@gmail.com> wrote:
> On Mon, Oct 29, 2012 at 6:07 PM, Stefan Krastanov
> <krastano...@gmail.com> wrote:
>> I have started
>>
>> https://docs.google.com/spreadsheet/ccc?key=0Allq_N-5TER9dHhDRVJxSTU4SEZ5X3FRZ1hhM3FIN3c#gid=0
>>
>> If I remember correctly last year we agreed that from the point from
>> which we have this spreadsheet we should add tasks both to the
>> spreadsheet and to the issue tracker. Right?
>
> If it will help, you can add another tag to Google Code,
> CodeInAddedToSpreadsheet, to keep track of what's been added to the
> spreadsheet.

Let me know if you want to do this, and I can add it as an official
tag in the tracker (or if you want to add any other label, for that
matter). I've already added a new issue that isn't in the
spreadsheet. So probably this is a good idea.

>
>>
>> Anyway, the spreadsheet is just the import of the tasks, it is not
>> formated and augmented yet. Help needed...

One thing I should note is that last year's spreadsheet has some
functions in some of the cells (Google Docs supports Excel-like
programming in the cells). So take a look at that to see if there is
anything useful.

>
> Hopefully we won't need to do this (at least to much of a degree)
> until later. Just a simple import should be OK for the application
> period, no?
>
> Aaron Meurer

Thanks a ton for doing this, by the way. I don't think I'd have had
time to get to it myself.

Aaron Meurer

[Stefan Krastanov]

I will update the plotting tasks a bit and rewrite those that need to
be multiple tasks as such. Concerning the diff between the issue
tracker and the spreadsheet, I will add the label.

[Stefan Krastanov]

31 tasks for plotting are ready (and more can be added when these are
done). I have separated them by 5 empty lines in the spreadsheet, just
for my convenience. I will remove the empty lines before the deadline.

64 tasks in the rest of sympy.

I think that getting 20-30 more tasks will be great. At the moment we
are at the minimum of what I consider OK (the GCI guys (and ladies)
during the summit mentioned that around 100 tasks will be a good
initial quantity).

[Stefan Krastanov]

> 31 tasks for plotting are ready

make that 36. This is all for today from me.

[Aaron Meurer]

Cool. Do we also have a good distribution among the categories? I
think we need at least five of each.

Almost everything from
https://github.com/sympy/sympy-bot/issues?labels=&page=1&state=open
can be made into a task. So there's several more there.

I made your CodeInImportedIntoGoogleDocs label official, so it will
show up in the autocomplete.

Aaron Meurer

[Stefan Krastanov]

Today is the deadline, right? Is there anything to do, besides
registering sympy on melange?

[Sean Vig]

I think the deadline is Monday. We still have to finish up/update the application [1].

Sean

[1] https://github.com/sympy/sympy/wiki/GCI-2012-Organization-Application

[Aaron Meurer]

I will be working on the application as well as other GCI related things this evening.  If anyone wants to collaborate, pop into IRC.

Aaron Meurer

[Aaron Meurer]

I am adding everyone from https://groups.google.com/forum/#!topic/sympy/KrpvxADqAxM/discussion who said they would help mentor to the application (who hasn't added himself already). Namely, I am adding Ondrej, Vladimir, and Sergiu. 

If anyone else can mentor, please add let me know tonight, so I can add you to the application.  The more mentors we have, the more likely Google will be to pick us.

Aaron Meurer

[Aaron Meurer]

OK, I've submitted the application, so if you make any more changes to it, make sure to ping me so that I can update it on Melange.  I'm not sure when the actual deadline is, but it sounds like it will be the end of the (Pacific time) day tomorrow (Monday). 

Otherwise, if you want to help, add more tasks, and also add yourself to https://github.com/sympy/sympy/wiki/gci-2012-mentors.  I suppose it wouldn't hurt to make sure that https://github.com/sympy/sympy/wiki/gci-2012-landing is up-to-date as well.  

On the application, instead of putting a screenshot of SymPy Live, I uploaded the version from right before the program and added a link to it: http://1.sympy-live.appspot.com/, as well as a link to the current version.

Aaron Meurer