[jdev] GSoC

[Kevin Smith]

A gentle poke for people - so far only Swift has any ideas up there
and we need the list to look a lot lot better in the next couple of
days to stand much chance of being selected this year.

/K

On Fri, Mar 2, 2012 at 3:50 PM, Kevin Smith <kevin at kismith.co.uk> wrote:
> On Fri, Mar 2, 2012 at 11:02 AM, Kevin Smith <kevin at kismith.co.uk> wrote:
>> Over the next week we need to sort out the XSF's GSoC application -
>> this includes the ideas page. I'll send out a format for these in the
>> near future, so we can have consistency between them - in the meantime
>> (bearing in mind the deadline of 7 days from now), could:
>>
>> Members of projects that'd like to be involved under the XSF's
>> umbrella (if accepted) start thinking of ideas to add.
>>
>> Users of projects they'd like to see involved get in touch with the
>> project members and encourage them to do the above.
>
> I've now started filling out the ideas page at
> http://wiki.xmpp.org/web/Summer_of_Code_2012
>
> When adding your project at the bottom, please use a consistent format
> - this is what I've been using for the Swift ideas (example below):
>
> [Project name (e.g. Swift)]
> Description of software project. Must include details of how to find
> the potential mentors to chat to.
>
> {foreach idea}
> [Idea name (e.g. Conversation History)]
> Summary: [one-liner summary]
> Difficulty: [e.g. Easy-Medium]
> Details: [multi-line description of what's involved]
>
> So that gives us something like:
> == Swift ==
> [http://swift.im Swift]'s goal is to provide an IM client that does
> things 'right' with a good user interface, solid quality, and
> standards-compliance. This year there are again several opportunities
> for working on new functionality in Swift. This page lists some of the
> high priority tasks the Swift development team has. If you're
> interested in any of these (or other) Swift ideas, please jump into
> the [xmpp:swift at rooms.swift.im?join swift at rooms.swift.im] room and
> chat it over with Remko and Kev. Swift is a C++ project, so C++
> proficiency is required, with either knowledge of or willingness to
> learn about unit testing (and ideally test-driven development).
>
> === Conversation History ===
> * '''Summary''': Implement all aspects of keeping conversation
> history, both local and remote.
> * '''Difficulty''': Easy-Medium
> * '''Details''': Swift doesn't currently store any transcripts. A
> student would likely start by producing a prototype user interface for
> accessing chat history, then write the library code to access a remote
> archive, and plug these together and finally work on a local archive.
> This is likely to be a very satisfying project, with enough challenge
> to be interesting, but not so much that it's frustrating - plus it's a
> very popular feature request.
>
>
> I'd consider this the minimum necessary 'details' part - I'll be going
> back to expand on these.
>
> We need to have a good selection of projects up on the ideas page by
> ~middle of next week, I think, so please have at it.
>
> /K