Hi folks,
As we have some renewed interest in working on STeVe, this would also be
a good time to sort out some practicalities and names.
# Version control:
I think it would be a good move to switch to git for the next iteration.
Not because I'm a fan of git in particular, but because of the added
interactions with the larger community at GitHub, as well as the tools
provided there.
If we do go down this road, the next step is to figure out how to have
old steve and new steve side by side. We can either keep old steve on
svn and make a new steve.git for the next gen product, or we can come up
with some sort of (code)name for this next piece of software, such as
steve-nextgen, steve-2, steve-buscemi etc. I don't have any good ideas
myself just yet. Ideas are very much welcome here!
# Lingo etc:
I think we're pretty fixed on using Python 3 for this next version,
which works out great for me personally as well as our newcomer Sean.
Front-end-wise we're probably looking at html+js with a json api or some
such? Up for debate, do let me know what your thoughts are.
# Architecture:
TBD - I'll start some topics in separate threads on this.
Anywho, these are my thoughts/questions at the moment.
With regards,
Daniel.
