Developer Community Kickoff - Project Management Decisions
Welcome top backers of Eco! I wanted to kick it off with a discussion of the things we're currently thinking about as we work towards our alpha, and our evolving thinking about to integrate this awesome community into the game.
One thing we're considering is how to open the source to Eco safely. We're planning to do something really unprecedented with Eco, opening up as much of the code and art assets as we can and sharing it with this community. There's a number of dangers in doing so, specifically it's a given that the code will instantly be pirated and spread through the internet. The question becomes: is the damage done by that worth the benefit of having a community of awesome developers joining us? I think the answer is yes, and that the damage of having our source in the public view is less than expected.
The other issue is licensing. This is something that I think needs to be fairly stringent, to protect against the case of someone simply taking all the code, compiling it themselves, and selling the game separately. That needs to be illegal to protect the IP investments we've , so if it happens on a significant scale we have some recourse. We're going to be looking into source licenses that allow us to share the code, but anything that is created with the code belongs to us. However, I also think it's fair that major contributors would get a cut of the profits, and I hope to figure that out on a case by case basis.
There's also the danger that people will secretly take the code and change it enough so that we don't recognize it in their product, but I'm less worried about that - they would have a hard time catching up to the progress of our community.
<b>Technology to use</b>
We'll need to figure out what are the best apps to use for community development, as this is a new endeavor for us. We'll need to figure out these categories:
Source control: GitHub probably? But we will need a separate depot for our art assets as they are rather large.
Bug database: Jira?
Project planning: Trello
Chat and project management: Slack?
Once we figure these out we can start preparing the code for sharing with the community. Looking forward to hearing your thoughts.
Have fun and let the people inspire you.
<blockquote>Ya know, we are building an entire voting and proposal system for ECO, perhaps we could use that one day... (Going to demo it at PAX today! See ya there)</blockquote>
Townhall dev meetings in the Eco world itself? :D
Wow! That smiley had a big grin! haha
Kinda scary... Must be what the ghosts in PacMan sees...
@thomthom Ok everyone, scrum at the iron ore mine at 10:30.
Careful now, if we overhunt we could drive the bugs to extinction!
I love Trello, I'm following the <a href="https://trello.com/b/yxoJrFgP/subnautica">Subnautica's Trello</a>. I think they are doing a great job with that.
Update: working on GitHub with LFS, and issue tracking through GitHub as well. Slack and Trello updates coming too.
@lizard455 the bugs are an invasive species. We want them to be extinct. :P
For source control and bug tracking I'm looking at two open source products: