I've been posting some screenshots and short updates in the http://forum.revolutionarygamesstudio.com/t/switching-engines/340 thread. Perhaps I could also post updates like that on twitter?
Awesome! Yeah I would say if you have the time and interest go for it! Otherwise, I could message one of the mods on the forums to see if they'd be interesting in writing it up for you.
I think we should focus more on our github by making each item in the release plans an issue on github, which can be assigned to people. And then creating milestones and assigning all of the tasks to some milestones. That way new people can easily find small tasks (with "easy" tag) to work on. Right now there's just some ancient bugs / ideas there which aren't very useful.
Definitely, I think GitHub would work great. From what I know we can bundle the milestones under a single release (or maybe the milestone is the release), and then as you said have sub-tasks within each milestone and that flow from macro to micro is perfect. I'll go check it out right now and get familiar with it.
I've been planning on creating some tutorials for different development tasks. The wiki is probably quite a good choice for them. Just need to make sure that we have backups in case the wiki goes down, I've also thought about putting such things on my own website as I would have better backups then.
I don't think I have edit access to the wiki, so that's an issue.
Exactly, I've been interning at a new job lately and it's taught me a lot about how effective good wiki documentation can be for a newcomer. Each tutorial we can put on there will be a good long term investment.
I try to save the important pages on my PC, but that's the best I can think of. Also send me your email on Slack, I'll add you to the wiki's editing group.
Slightly related to this is the engine refactor thing I've been working on (with using my engine: https://bitbucket.org/hhyyrylainen/leviathan1) has simpler setup procedures. There are probably quite a lot of edge cases to handle initially when people start trying to build it, but I hope that if other devs can build it will be quite easy for new people to also build thrive.
I've also been working on continuous integration for my engine and getting an online version of the engine documentation. Thrive should also be pretty easy to setup with the same ci solution once the engine switch is done, so we can add more tests to thrive (this is also on my todo list while I work on the switch) which are automatically ran. This should immensely improve the code quality. I've also planned on doing code reviews on all parts of thrive and opening issues for every piece of unclear or undocumented code.
Perfect! Again that'd be an awesome long term investment, making it so much easier for new programmers to get on board. Good luck working on that.
@Naggorath : Fantastic! I'll put you down for now as assigned to Outreach and I'll get back to you once we start working on that (probably later this week or next week).
EDIT: The OP has been updated with a link to the new thread for managing workflow on GitHub.