[SciPy-Dev] SciPy Central in GSoC 2013

Surya Kasturi suryak@ieee....
Thu Apr 18 10:43:50 CDT 2013


Thanks for dropping by!


On Wed, Apr 17, 2013 at 8:49 PM, Sebastián Ventura <lomegor@gmail.com>wrote:

> 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.
>

Yeah, I even thought of doing CMS thing first. Regarding the proposal -- I
am working on it. primarily, I am looking for new ideas!!

>
> 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.
>

Actually, I never played with Django-cms or similar projects so far. This
should probably take 1 or 2 days time (not sure).
Regarding the reading paths..

1. reading django-documentation, and a some advanced stuff where ever
required.
2. Even though I understand databases basics, I never formally read a book
(oops). I guess I should be
reading<http://sql.learncodethehardway.org/book/> it.
Will try my best to complete most of the important stuff before gsoc
begins.

>
>
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.
>

Gists was discussed on the mailing list some time ago (not a heavy
discussion).. I guess, its just for better reach as you said.
But, I just got an silly idea (excuse if its really damn bad).. can't we
completely rely on Gists?

We can primarily story entire snippets source on Gists.. display them,
whenever needed on SPC using GitHub API. I wouldn't myself even support
this idea.. but I just want to make a note of it. (pros: we don't need to
have a DVCS in static content.. and maintain the source)

Also, regarding "commenting system", why not use Disqus <http://disqus.com>?
a lot of guys are relying on it now a days..

The problem with replying on the third-party platforms is that we loose
complete control over the data at the core. This is not going to be good if
we want to build a self-contained application/ platform..What if we want to
shift to other platform one day.. I don't know if we can migrate all Gists,
comments on it etc..

Similarly with Disqus. Should be build our own commenting system or use
Disqus

>
>
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.
>


Thanks a lot. Actually, it would be great if you can point out some areas
where Scipy Central can be developed...


> Cheers,
> Sebastian
>
>
> On 16 April 2013 23:03, Ralf Gommers <ralf.gommers@gmail.com> wrote:
>
>>
>>
>>
>> On Tue, Apr 16, 2013 at 5:18 PM, Surya Kasturi <suryak@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@ieee.org> wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Fri, Apr 12, 2013 at 1:43 PM, Ralf Gommers <ralf.gommers@gmail.com>wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>>  On Tue, Apr 9, 2013 at 8:20 AM, Ralf Gommers <ralf.gommers@gmail.com>wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Apr 9, 2013 at 6:06 AM, Surya Kasturi <suryak@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@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@scipy.org
>>> http://mail.scipy.org/mailman/listinfo/scipy-dev
>>>
>>>
>>
>> _______________________________________________
>> SciPy-Dev mailing list
>> SciPy-Dev@scipy.org
>> http://mail.scipy.org/mailman/listinfo/scipy-dev
>>
>>
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev@scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/scipy-dev/attachments/20130418/4dcd5461/attachment.html 


More information about the SciPy-Dev mailing list