[tahoe-dev] GSoC Project Advice

[yu xue]

Hello, Dear Jacob:
     I am also a student who plan to join the GSOC. I feel you *must* submit
a proposal to GSOC website. Because all the process of selection is through
that. Otherwise, google will not have your project application record...
    If you have submitted one, you can try your best to improve it. If not,
 I pesronally suggest you propose quickly, because there is only
several hours left. As for the *thorough* proposal, you can try your best.
At least there will be your application record in google. *Maybe the very
detailed* project plan could be discussed with the all the mentors and
developers after that.
   I know your questions should be answered by mentors. But there is very
little time left...
   Regards
     Yu Xue

2010/4/9 Jacob Lyles <jacob.lyles at gmail.com>

> Unfortunately my school work load in the surrounding 24 hours has prevented
> me from completing a thorough proposal by the deadline. However I will be
> able to dive into the source code and write out a proposed timeline for the
> project over the weekend. Would this be useful? Would you be able to take
> this timeline into consideration when deciding on my project proposal?
>
>
> On Thu, Apr 8, 2010 at 7:29 PM, Zooko O'Whielacronx <zookog at gmail.com>wrote:
>
>> On Thu, Apr 8, 2010 at 5:25 PM, Jacob Lyles <jacob.lyles at gmail.com>
>> wrote:
>> > Thanks for the advice. I am also interested in the distributed wiki or
>> blog
>> > apps using Caja and Tahoe. Is one of these projects preferred to the
>> other
>> > by the Tahoe team? Should I submit applications for both?
>>
>> The limiting factor at this point is likely to be your ability to
>> finish a good thorough Proposal before the deadline, which is coming
>> up about sixteen hours after I write this [1]. (By the way, the Google
>> Summer of Code folks are absolutely merciless about deadlines. I have
>> yet to see them give anyone the slightest lenience on a deadline. A
>> good strategy is to upload a barebones Proposal to the GSoC site and
>> then iteratively improve it in-place.)
>>
>> So you should choose whichever thing you are the most interested in
>> and write a thorough Proposal for that first. In fact, yeah there is
>> no point in writing a Proposal to do the other one. Just concentrate
>> on your favorite.
>>
>> I'm glad you are interested in those projects! I really hope to see
>> some good cloud apps built on top of Tahoe-LAFS this summer. By the
>> way if there is something that catches your fancy more than a wiki or
>> a blog then by all means write that up. Multiplayer game? Social
>> networking software? There are probably a lot of things that would
>> make good cloud apps that nobody has thought of yet. Josip Lisec had
>> the idea of a music player [2], which sounded to me kind of crazy
>> and/or kind of an ill fit for Tahoe-LAFS at first, but he went ahead
>> and wrote up a very detailed proposal with mock-ups of the user
>> interface and everything and it is sounding better and better.
>>
>> Good luck writing a thorough Proposal with detailed functionality, a
>> basic timeline, and how we and you can evaluate progress at different
>> points in the summer (e.g. if there are some kind of tests that we can
>> run which demonstrate that the code written so far does what it is
>> supposed to do).
>>
>> See the recent thread on this mailing list for an example of what a
>> detailed Proposal looks like:
>>
>> http://allmydata.org/pipermail/tahoe-dev/2010-April/004232.html
>>
>> Feel free to look up the Tahoe-LAFS mentors on irc.freenode.net#tahoe-lafs .
>>
>> Regards,
>>
>> Zooko
>>
>> [1]
>> http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#timeline
>> [2] http://allmydata.org/pipermail/tahoe-dev/2010-March/004208.html
>>
>
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at allmydata.org
> http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
>
>


-- 
    此致
敬礼!
                      薛宇

                  身前身后
                  是时间的深渊
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://allmydata.org/pipermail/tahoe-dev/attachments/20100409/af213a9c/attachment-0001.htm