Okay, apologies for the short notice on this one, have been dropping hints and notes here and there, but have been too busy to get some stuff in place I wanted ready before announcing this.
We'll aim to do a dev meeting on IRC this coming Saturday around 5 pm EST. Focus is on project organization for ourselves and collaboration with Spout - a project a fair bit more mature than us with good experience we could take pointers from. So pinging any interested Spout members like Afforess RoyAwesome Zidane Olloth etc. Topics:
We'll aim to do a dev meeting on IRC this coming Saturday around 5 pm EST. Focus is on project organization for ourselves and collaboration with Spout - a project a fair bit more mature than us with good experience we could take pointers from. So pinging any interested Spout members like Afforess RoyAwesome Zidane Olloth etc. Topics:
- Formal organization - who is MovingBlocks and why does it matter? For starters we'll likely be moving the copyright notices from begla to the group as a whole. Do we need to register something officially?
- License - currently we use the Apache 2.0 license but that choice was made in the Blockmania days when this project was a one-man tech demo. Spout has an interesting license setup where after 180 days the license swaps from a more restrictive setup (better positioning) to a looser setup (allows recovery of code that might otherwise go inactive due to restrictive licensing).
- Money - scary topic, we actually had a few donations! Go go double-digit paypal balance. For now we'll just pay off part of the server hosting, but what happens if more money shows up? Does that impact licensing? What about merchandising - Gooey plushies? Who can sell what? I'm not a lawyer, so more experienced feedback would be appreciated
- Potential contribution reward system - more on this (likely an incubator thread) at meeting-time. This might be hiding somewhere already visible to confirmed contributors.
- We share TeraBullet now with Spout (or Vanilla?), might also do some math lib collaboration, and AlbireoX tinkered with a TeraSpout prototype. What other potential might there be, could we perhaps one day use SpoutServer for multi with a Terasology plugin rather than roll our own? What other small things can we do to get closer?
- Release management - making Kai Kratz take over some of the scary Git stuff for the project (like code integration) and we might make the branches / releases fancier. Putting this at the end as we might flow from meeting into actually working on that. May include some talk on what repos to use for what (mods? art?). Our Jenkins is also getting nicer, with a fancy prototype job with checkstyle and unit tests enabled