After the technical briefing sent by Carlos, the news about porting Turpial to Javascript has aroused much interest among the community and, as I said before, I think that this is the right moment to grow and make more developers get involved with the project.
But to get involved you need to know what to do. We need a "How to contribute" page, that's first.
Other thing that comes to my mind immediately is: What are we going to do with Turpial 2.x? Are we going to develop a full featured 2.0 version or are we going to release a minimum version to let people test the power of Webkit and HTML? We could switch to 3.0 development directly, deprecating 2.0 before its birth, but is important to notice that the last stable version is 1.6.9 (really old for me) and we should try to release new versions often.
This is the first question we need to answer before start coding.
After answering that questions there are lots of things to do. I did a brief list of most important tasks that aren't done yet and I would like to share with you:
About platform:
* Keep up-to-date the PPA and all the development repos for packages (Arch, Debian, Fedora), that way people can enjoy and test last changes
* We need to improve the alpha test flow. Right now there is
files.turpial.org.ve but, we need to use it
* Fill the empty spaces on our collaboration platform (wiki, SMTP, etc)
* Develop some unit tests or even integration tests to ensure the quality of our app
About information, documentation and diffusion:
* Posts about the awesome work that Carlos has been doing with the Qt interface
* Posts about the amazing tutorials that Andrea is doing to teach how to build mobile apps [1]
* Posts about the progress/growing of Turpial as project and all the efforts we are doing to try to port Turpial to mobile devices
* Zen of Turpial, a decalogue with our very basic principles as FLOSS project
* Styles guides for coding
* Donation campaign (posts, wiki pages, twitter, identica, etc)
* How to contribute (Wiki page for developers)
And when we solve most of these things, we can continue with:
About Turpial 2.0:
* The main idea is try to reach the same features we have now with 1.6.9 but nicer and better. The list of pending issues is huge, so If you want details go to [2]
About Turpial 3.0 (Javascript):
* Build basic structures (like classes) in js to hold the whole libturpial models
* Migrate http interface of libturpial with support for OAuth (as base for all communications)
* Migrate all basic models (account, status, etc)
* Design and implement an optimal way to handle configuration (probably using the storage feature of HTML5)
* Implement a new HTML template system based on JS
* Implement controller and views for the new backend
So, who starts? :)
P.D.: Probably there are much more things to do, so if you think that I missed one just add it to this thread
--
“Yo construyo Soberanía, uso Software Libre”
Wil A. Alvarez
Linux Counter #415026
Debian Counter #259