Along those lines - I have some time (mostly on the weekends) available to
bugfix as well, so I'd take a "starter bug" or two as well, particularly if
they're on the list of 2.0 must-fix bugs.
Thanks,
Geoff
On Thu, Feb 20, 2014 at 3:09 PM, moonlake <[email protected]> wrote:
> I've set up a development environment and read up on Qt. Now I'm trying to
> understand the codebase, but given its size, I feel the best way would be
> to
> have a specific issue to hunt down.
>
> I'm a beginner trying to understand the codebase, but given its size, I
> feel
> my best route would be to have a specific issue to hunt down. What would
> be
> a good "starting bug" or project? I've skimmed through the issue tracker,
> but I can't quite weigh the depth of the different issues or which ones
> would be instructive. Any suggestion are greatly appreciated.
>
>
>
> --
> View this message in context:
> http://dev-list.musescore.org/Starter-work-tp7578610.html
> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
> _______________________________________________
> Mscore-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
