Release 0.4.0 Thread

[hhyyrylainen]

@NickTheNick

Regular social media updates. There have been a few suggestions that we post more to social media. We should find people who have the time and interest to do so. I was thinking we could get some of the mods from the forum to help on that front.

I’ve been posting some screenshots and short updates in the Switching engines thread. Perhaps I could also post updates like that on twitter?

@NickTheNick

Efficient workflow. I don’t want to compromise the free and voluntary nature of the project, because I think that’s what is one of the best parts of working on it and makes it enjoyable instead of stressful. At the same time, I want to try and integrate some sort of system of setting objectives or milestones, like with this thread, that we can aim for and complete so that we don’t get releases or features delayed by months or years.

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.

@NickTheNick

Self sufficient documentation. A clear, informative, and well designed wiki would be awesome. I think the wiki has huge potential to be able to fill newcomers in on most of the information that they need to know when joining the project. It can even greatly help current developers who want to learn more about the work of a different team or what have you. This could ideally save so much time for developers from having to explain things to other people by just pointing them to the wiki first. Again I don’t want to overload people with all these objectives I’m throwing out there so this is something that certain people should specifically focus on (For example I will work on this among other things since I cannot help on the development side).

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.

Slightly related to this is the engine refactor thing I’ve been working on (with using my engine: Bitbucket) 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.[quote=“NickTheNick, post:1, topic:378”]
Team lead supervision. Maybe it’s just my perspective, but I feel like we could use the role of team leads more to its full potential. Some sort of habit of having team leads check up on people working in their team and then updating their progress on a central hub thread like this could help create an effective communication between our overall planning and the individual tasks people work on. Obviously we don’t want to overload team leads with the work they already have to do, but I think this can be done very effectively with minimal effort.
[/quote]

Good idea, but at least with the programming team there might be an issue as @crovea hasn’t been very active lately. Now that I think about it has been more than 6 months since he has done more than answer the occasional questions on slack.