We are very happy to announce that we just released Datastringer’s official road-map.
The launch of Datastringer was a success, with more than 150 stars and 20 forks on Github, as well as great feedback received on Hacker News and Github. OpenNews Source blog also honoured us with a guest post about the tool and its creation.
We received a lot of emails, tweets, and Github comments. Many want to get involved in taking Datastringer to the next step.
However, we don’t want to rush anything, and we would like to help you helping us. The program as it is today needs to be improved and more thoroughly tested before we can stop calling it a pre-release. We also want to be as clear as possible about our intentions for its development and what’s in the pipe. It is also very important to be coordinated in order to take everybody’s ideas into account.
Hence, a roadmap. We will update it with the planned improvements and the major features we want in each release. It will also be the place for listing all the ideas we have for Datastringer, and that we might consider in the future.
This road-map will serve as a guide for all contributions. Pull-requests will be accepted or refused depending on whether or not they contribute to the general philosophy of the next release.
For all other ideas, we encourage you to produce a perfectly-working fork, then to give us a shout, so we can add them to our list of showcased forks.
Our first goal is version 1.0, a proper official release for a product we can support:
Version 1.0 should be as simple to use as it can be.
In order to achieve that, we should aim for a simpler installation process, the support of (at least) Linux and Mac OS X, and a graphical user interface (GUI).
The GUI should allow the user to see the activated and available stringers, and to turn them on/off, in a dashboard style.
Tests must be made available for this version.
We hope that you will be interested in helping us build these important features.