[SciPy-Dev] SciPy Central in GSoC 2013

Wed Apr 17 11:19:28 EDT 2013

Hi, Ralf, Surya and everyone else!

Sorry for not answering sooner, it seems that I missed this thread. I agree
with Ralf on the grouping of the ideas, it not only makes it more
organized, but it will help you when you are trying to creating a rough
schedule of how you are going to do it. Order them in term of priority so
you know which is more important to do. In my opinion, migrating to a CMS
is one of the first things you should do, as it will make it easier to
improve the design and probably avoid having to take time for that again
after migrating.

One thing I think is missing from this is investigating
different possibilities, both for the CMS and the design. This means
testing or investigating different CMS or templates or whatever to see
which one suits this project best. Although I particularly like Django (and
I think you do too), it doesn't mean it's the only solution or even the
best one. Therefore, I think that should be a point of its own. In that
point, you can also include time learning the technologies you are going to
use (if you are not already familiar with them), because that may take some
small time.

One more thing regarding submissions. Although I like your ideas of having
the code in gists and the submission available on PDF, it's important
before implementing things to think about who needs it and if it's really
going to be used. I'm not sure if there's anything to gain with hosting the
code on gists, except better reach, but if people are still going to use
the main page to look at code, it wouldn't be too important. That means
that more time could be spent in improving maintainability, performance and
things like that.

Great ideas, by the way, and great initiative on having the blog. It's
always good to have communication on those things. Keep it coming, and
remember to add a rough schedule and order things by priority.

Cheers,
Sebastian

On 16 April 2013 23:03, Ralf Gommers <ralf.gommers at gmail.com> wrote:

>
>
>
> On Tue, Apr 16, 2013 at 5:18 PM, Surya Kasturi <suryak at ieee.org> wrote:
>
>> Hi all,
>>
>> I created a blog to post proposal, ideas for proposal etc.. on spc.
>> http://surya-gsoc2013.blogspot.in/
>>
>> The proposal is under making.. but I looking for someone to comment of my
>> ideas. It would be great if someone could help me choosing some of them or
>> all of them..
>>
>> (Let me know if they have to be posted in mailing list)
>>
>
> Hi Surya, I think posting on your blog is fine. It looks to me like you
> have a lot of good ideas, but it would help your proposal to group them
> together into a couple of themes. For example:
> 1. Finish and deploy new site design
> 2. Improve site performance and maintainability by:
>   - adding a caching mechanism
>   - using Django-CMS and migrating to Django 1.4.5
>   - add design documentation
> 3. Code/snippet submission by:
>   <your points 6, 8, 12>
> 4. Other new features
>   <your points 1, 2, 3, 4>
>
> Then you have to have some idea on relative importance of all these things
> and how long they'll take in order to make a plan with a rough timeline
> attached.
>
> Cheers,
> Ralf
>
>
>
>> On Tue, Apr 16, 2013 at 3:47 PM, Surya Kasturi <suryak at ieee.org> wrote:
>>
>>>
>>>
>>>
>>> On Fri, Apr 12, 2013 at 1:43 PM, Ralf Gommers <ralf.gommers at gmail.com>wrote:
>>>
>>>>
>>>>
>>>>
>>>>  On Tue, Apr 9, 2013 at 8:20 AM, Ralf Gommers <ralf.gommers at gmail.com>wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Apr 9, 2013 at 6:06 AM, Surya Kasturi <suryak at ieee.org> wrote:
>>>>>
>>>>>> Hi everyone,
>>>>>>
>>>>>> How about SciPy Central on GSoC 2013?
>>>>>>
>>>>>> I was thinking to participate in GSoC this year and thought of
>>>>>> contributing to this project as GSoC student. Firstly, I was luck enough to
>>>>>> find SPC which closely matched my interests. Since, I am already slightly
>>>>>> familiar with the existing code, made some small contributions, I thought
>>>>>> it would be very nice to continue my work as GSoC student during summer.
>>>>>>
>>>>>> Is it possible?
>>>>>>
>>>>>
>>>>> Hi Surya, it's definitely possible I think. And a good idea. Improving
>>>>> SciPy Central meets the requirements for a project set by Google and you've
>>>>> already met the requirement of submitting at least one patch before
>>>>> applying.
>>>>>
>>>>> I would encourage you to start working on a proposal, and discuss it
>>>>> on this list. Maybe you've seen this already, but just in case:
>>>>> http://wiki.python.org/moin/SummerOfCode/Application
>>>>>
>>>>> The other thing to do is find a mentor. We have several people that
>>>>> indicated that they'd like to be a mentor this year, maybe one of those
>>>>> people is interested in SPC? Or other people on the list?
>>>>>
>>>>
>>>> Hi, we do have a potential mentor for this project, Sebastián Ventura.
>>>> Since he's not yet active in the Scipy community, I'll briefly introduce
>>>> him. Sebastian is an experienced web developer, and has participated before
>>>> in GSoC both as a student and a mentor. We came into contact via the PSF
>>>> (our GSoC umbrella org), to which he had indicated that he was available as
>>>> a mentor for Python GSoC projects. Once he has signed up for this mailing
>>>> list - which may take a day or two because scipy.org is unresponsive
>>>> right now - he'll join the discussion.
>>>>
>>>> Cheers,
>>>> Ralf
>>>>
>>>>
>>>> _______________________________________________
>>>> SciPy-Dev mailing list
>>>> SciPy-Dev at scipy.org
>>>> http://mail.scipy.org/mailman/listinfo/scipy-dev
>>>>
>>>>
>>> I am waiting for him.. did he joined the mailing list?
>>>
>>
>>
>> _______________________________________________
>> SciPy-Dev mailing list
>> SciPy-Dev at scipy.org
>> http://mail.scipy.org/mailman/listinfo/scipy-dev
>>
>>
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20130417/e36ea43e/attachment.html>