I'm starting this thread so as to stop derailing the "TouchOrbiter - Auto-configuring new orbiter" thread.
I'd really like to contribute to bug-fixing but find I'm being held back by some of the issues that are being discussed in the aforementioned thread. One thing that might help is if the more experienced devs can identify some bugs that would be easier for the less experienced to tackle (if there are any). That way, the experienced devs can focus on the bugs that only they (at present) can tackle, and we have a more efficient system of delegation.
I know this creates more work for the devs in the short term, but I'd like to think it would be a good investment in the long haul.
Test asteriks and provide feedback
See ticket and comments
http://svn.linuxmce.org/trac.cgi/ticket/315
Quote from: davegravy on October 18, 2010, 04:30:32 PM
I'm starting this thread so as to stop derailing the "TouchOrbiter - Auto-configuring new orbiter" thread.
Thanks :-)
Andrew
Quote from: davegravy on October 18, 2010, 04:30:32 PM
I'd really like to contribute to bug-fixing but find I'm being held back by some of the issues that are being discussed in the aforementioned thread. One thing that might help is if the more experienced devs can identify some bugs that would be easier for the less experienced to tackle (if there are any). That way, the experienced devs can focus on the bugs that only they (at present) can tackle, and we have a more efficient system of delegation.
Great idea davegravy! I'm in about the same position as you. I'm new to LinuxMCE and would like to contribute to bug-fixing so that I can learn more about how the internals work. I have Linux development experience and know C++, but just don't know where to jump in and be helpful with a project this big.
So far I've just been fixing small bugs (http://svn.linuxmce.org/trac.cgi/query?status=new&status=assigned&status=reopened&status=closed&reporter=~esev&order=priority) that I've encountered along the way. I was going to work on ticket 831 (http://svn.linuxmce.org/trac.cgi/ticket/831) which deals with getting MythTV working smoother for those of us outside the US. But if there is something more important that I can work on, please let me know.
TIA,
Eric
Quote from: esev on October 18, 2010, 04:53:43 PM
So far I've just been fixing small bugs (http://svn.linuxmce.org/trac.cgi/query?status=new&status=assigned&status=reopened&status=closed&reporter=~esev&order=priority) that I've encountered along the way.
thank you so much, you really rock!!
br Hari
http://forum.linuxmce.org/index.php?topic=10662.0
Here is already an attempt to maintain open tickets.
Quote from: esev on October 18, 2010, 04:53:43 PM
Quote from: davegravy on October 18, 2010, 04:30:32 PM
I'd really like to contribute to bug-fixing but find I'm being held back by some of the issues that are being discussed in the aforementioned thread. One thing that might help is if the more experienced devs can identify some bugs that would be easier for the less experienced to tackle (if there are any). That way, the experienced devs can focus on the bugs that only they (at present) can tackle, and we have a more efficient system of delegation.
Great idea davegravy! I'm in about the same position as you. I'm new to LinuxMCE and would like to contribute to bug-fixing so that I can learn more about how the internals work. I have Linux development experience and know C++, but just don't know where to jump in and be helpful with a project this big.
So far I've just been fixing small bugs (http://svn.linuxmce.org/trac.cgi/query?status=new&status=assigned&status=reopened&status=closed&reporter=~esev&order=priority) that I've encountered along the way. I was going to work on ticket 831 (http://svn.linuxmce.org/trac.cgi/ticket/831) which deals with getting MythTV working smoother for those of us outside the US. But if there is something more important that I can work on, please let me know.
TIA,
Eric
Ticket 831 looks like a great place to start! Go for it!
All the best
Andrew