Music Production > NitroTracker News
NitroTracker is now open source!
0xtob:
Hey guys! Finally, I got around to work on NitroTracker again, and the result is here:
https://github.com/0xtob/nitrotracker
That's right, NitroTracker is 100% open source GPL v3 code (the XM player is even zlib licensed, meaning it's open source, but can be included in closed source software).
Also check out the news on the NitroTracker page here.
I know, development hasn't been fast recently. The reason for this is that I graduated from university and started a (awesome!) job. Unfortunately, this has severely reduced my coding time, which is why I decided to finally make NitroTracker open source.
With this I intend to make development faster by getting some capable developers into the boat. If you're interested, don't hesitate to ask me! There's plenty of things to do, and it shouldn't be awfully hard to get started with the code.
Of course, not everyone is a coder :-) But you guys are doing an awesome job posting feature suggestions and bug reports on this forum! In order to streamline the development process, I've decided to move the place for feature requests and bug reports to the Google Code issue tracker. Read more about it in my post here.
So, in the next days I will go through all of the issues you posted here and add them to the issue tracker. I'll add some issues of my own, and this will result in a detailed plan for the following three-or-so releases. Then, with (hopefully) more developers on board work will go forth much more quickly and tracking on the DS will become totally awesome!
To awesomeness, and beyond!
Tob
Edit by Saga Musix: Updated code repository URL from Google Code to GitHub
devin:
Glad to hear it ( the job I mean, and the open source bit.)
I'm not a coder but I'd like to help out in any way that I can.
0xtob:
Great! I could really use a hand converting the feature requests and bug reports from the forum to the issue tracker.
The procedure is as follows:
* open a post from the forum
* if it's a bug, try to reproduce it in NitroTracker. If it's a feature request, check if the feature isn't already implemented in the tracker.
* If successful:
* Enter it into the issue tracker. You can copy the text of the post, but try to give a descriptive title.
* to mark the post as ported, reply to the post with: "Ported to the issue tracker"
* Else:
* Reply to the post with the reason why it was not ported.
As an example, here's an original bug report:
http://modarchive.org/forums/index.php?topic=1447.0
And here's the issue tracker version:
http://code.google.com/p/nitrotracker/issues/detail?id=8
It's a little tedious but it'll help me a lot organizing development.
Thanks in advance to whoever wants to help with this!
Tob
zoikkis:
Happy to help you with that!
MatrixMaster3:
I'll try to help you with this! I'm probably going to focus on the feature request forum, but I'll try to help with bugs if I can.
Navigation
[0] Message Index
[#] Next page
Go to full version