Hi All,
I think picking one feature and concentrating on that is a great idea.
I also think maybe setting a goal like fixing all "critical" bugs
would be good too. Thanks to all the developers and contributers for
working so hard on MuseScore. It is seriously one of those apps
that--as music student and Linux user--I absolutely have to have.
Regarding a different topic, I was wondering if the development team
accepts or would consider a "bounty" system as a fund raiser, where
users could donate a specified amount for a specific feature or bug
fix. I've seen this done in other F/OSS projects as means to raise
support, and was wondering what you guys think about it.
~Nathan R. Hale
Rom. 12:2
---------------------------------------------------------------------
http://nathanrhale.com - personal site
http://linuxmusicians.com - create music freely
---------------------------------------------------------------------
On Tue, Sep 8, 2009 at 4:36 AM, Lasconic<
[hidden email]> wrote:
> Some random ideas
>
> On a maintenance & developer documentation level == make it easy for new
> developers
> - Make several logic directories instead of the big mscore one we have
> (plugins, output, ui etc...)
> - A couple of schemas or pages to explain how layouting works, how the model
> looks, how synthesizer and audio output works...
>
> Pick one or more new feature and design/develop it
> - Horizontal/panoramic layout
> - Windows/Mac midi out
> - External music font description a la Rosegarden
> - Fret diagrams
> - Tab staff
>
> Discuss
> - Plugins
> - Unit testing
> - UI testing
> - Ergonomy
>
>
> Lasconic
>
>
> 2009/9/8 Thomas Bonte <
[hidden email]>
>>
>> Suppose there would be a code sprint with MuseScore developers & users,
>> what
>> topics or goals do you personally think should be addressed?
>>
>> Wikipedia explains a
>>
http://en.wikipedia.org/wiki/Sprint_(software_development) code sprint as
>> followed: "A sprint is a time-boxed period of software development focused
>> on a given list of goals (but with variable scope)."
>>
>> This is an open question. Feel free to answer on it in any way.
>> --
>> View this message in context:
>>
http://n2.nabble.com/Figuring-out-the-goals-of-a-MuseScore-code-sprint-tp3601372p3601372.html>> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>> trial. Simplify your report design, integration and deployment - and focus
>> on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.
http://p.sf.net/sfu/bobj-july>> _______________________________________________
>> Mscore-developer mailing list
>>
[hidden email]
>>
https://lists.sourceforge.net/lists/listinfo/mscore-developer>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.
http://p.sf.net/sfu/bobj-july> _______________________________________________
> Mscore-developer mailing list
>
[hidden email]
>
https://lists.sourceforge.net/lists/listinfo/mscore-developer>
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.
http://p.sf.net/sfu/bobj-july_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
