http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/rowanjones84/1
Here's a link to my proposal that I missed out in my last email. :)
On 2 May 2013 22:55, "Rowan Jones" <rowan.jones-2...@brookes.ac.uk> wrote:
> Hi Ryan,
>
> Thanks for the advice, I've just submitted the first draft of my proposal.
> Let me know if there's any areas that I need to go into more detail.
>
> Cheers,
>
> RowanJ
>
>
>
>
> On 2 May 2013 01:23, RJ Ryan <rr...@mixxx.org> wrote:
>
>> Hi Rowan,
>>
>> Part of the reason we encourage you to pick up an easy bug and solve it
>> is to get you reading through the code. We expect your proposal to have a
>> fair number of implementation details or at least a rough implementation
>> plan. In order to do this, it is super helpful if you have poked around the
>> code and know how the subsystem you propose to modify is currently
>> designed. So, to answer your question -- it's not required but from
>> experience we know that it is highly correlated with high quality proposals.
>>
>> My suggestion is to get a draft of your proposal up on melange as soon as
>> you can. That way, the mentors can give you feedback before the deadline.
>> (You can edit your proposal on Melange before the deadline on Friday).
>>
>> Cheers,
>> RJ
>>
>>
>>
>>
>> On Wed, May 1, 2013 at 7:10 PM, Rowan Jones <
>> rowan.jones-2...@brookes.ac.uk> wrote:
>>
>>> Hi Everyone,
>>>
>>> Firstly, I'd like to introduce myself :) I am an Computer Science
>>> masters student studying at Oxford Brookes, with an undergraduate BSc in
>>> Audio Production. I just found out about GSoc and Mixxx and would really
>>> love to get involved. Seriously great work on Mixxx btw, it gives Traktor a
>>> damn good run for its money!
>>>
>>> So, I have downloaded the mixxx source code and compiled it both using
>>> the command line and with Eclipse and the Sconsolidator plugin. I have
>>> also thoroughly read through the code and I am getting to grips with its. I
>>> realise the application deadline is very soon and am wondering what to
>>> focus on. Is it more important that I spend time on my application,
>>> describing what I have in mind for the loop recorder in great detail or do
>>> I need to fix a bug or two first, for my application to be taken seriously
>>> (how important is fixing a bug in other words!)? I have some cool ideas
>>> including a slicing feature, similar to that on Novation's Twitch.
>>>
>>> Best,
>>>
>>> Rowan
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
>>> Get 100% visibility into your production application - at no cost.
>>> Code-level diagnostics for performance bottlenecks with <2% overhead
>>> Download for free and get started troubleshooting in minutes.
>>> http://p.sf.net/sfu/appdyn_d2d_ap1
>>> _______________________________________________
>>> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
>>> http://mixxx.org
>>>
>>>
>>> Mixxx-devel mailing list
>>> Mixxx-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>>>
>>
>>
>
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
