recommended way to communicate?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

recommended way to communicate?

mtherieau
I've been trying to troubleshoot and isolate this defect: http://musescore.org/en/node/12599
and have made a little progress so far.  I've been adding comments to the issue describing how far I've gotten in understanding the code paths involved.  Am sending a note here to inquire what the recommendation is for posting those types of messages?  I know that each project has its own conventions for asking questions or highlighting issues about the code...am wondering what the preference is for the MS developers?  continue to post messages in the issue tracker?  send messages to this list?  other?

regards,
markt
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: recommended way to communicate?

Thomas Bonte
Administrator
IRC: #musescore on freenode.net

For all non developer related issues: http://musescore.org/en/forum
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: recommended way to communicate?

lasconic
Regarding a specific issue, commenting in the issue tracker is the
best option. We have the whole history there.
I didn't check the issue yet but a patch is welcome if you sorted out.
I will apply the patch on the branch if it's not too invasive and the
issue is critical.

Lasconic

2011/9/22 Thomas Bonte <[hidden email]>:

> IRC: #musescore on freenode.net
>
> For all non developer related issues: http://musescore.org/en/forum
>
> --
> View this message in context: http://musescore-developer.685061.n2.nabble.com/recommended-way-to-communicate-tp6821398p6821530.html
> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Mscore-developer mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: recommended way to communicate?

mtherieau
thanks thomas and lasconic -- I'll likely need to ask some questions on #musescore before I get to the point of generating a patch.  Will also continue to update the defect as I progress.

regards,
markt
Loading...