This is a really interesting article, thanks for posting it. I really like the concept of an "in-between" stage between using the application and directly contributing to changes to it, where...
This is a really interesting article, thanks for posting it. I really like the concept of an "in-between" stage between using the application and directly contributing to changes to it, where functionality and updates are explained comprehensively, but in a more understandable way than the code itself.
This is why dev blogs for games are so important: Good for recruiting devs Good for explaining what the hell is going on behind the scenes to players Good for showing roadmap and future ideas to...
This is why dev blogs for games are so important:
Good for recruiting devs
Good for explaining what the hell is going on behind the scenes to players
Good for showing roadmap and future ideas to players
With open source Dev it's basically like a mod community, onboard players to eventually make their own cool levels and gear.
I think in the switch to GitHub, that kind of community fostering was lost and there are just workarounds and hacks to get it back like Gitter, Slack channels, community guidelines and PR guidelines.
Thanks for posting this article. It isn't often that someone is able to so concisely and clearly communicate a bunch of different organizational structures and how they matter for the output of...
Thanks for posting this article. It isn't often that someone is able to so concisely and clearly communicate a bunch of different organizational structures and how they matter for the output of that structure. The incentives and goals of a structure have a huge impact on what result comes out of the process, and it's great to see it so well articulated for programming projects.
Wow, wickedly good eye opening read you have there. I hadn't encountered this convocational model before. We should take this to heart when tildes development gets underway.
Wow, wickedly good eye opening read you have there. I hadn't encountered this convocational model before. We should take this to heart when tildes development gets underway.
This is a really interesting article, thanks for posting it. I really like the concept of an "in-between" stage between using the application and directly contributing to changes to it, where functionality and updates are explained comprehensively, but in a more understandable way than the code itself.
This is why dev blogs for games are so important:
With open source Dev it's basically like a mod community, onboard players to eventually make their own cool levels and gear.
I think in the switch to GitHub, that kind of community fostering was lost and there are just workarounds and hacks to get it back like Gitter, Slack channels, community guidelines and PR guidelines.
Thanks for posting this article. It isn't often that someone is able to so concisely and clearly communicate a bunch of different organizational structures and how they matter for the output of that structure. The incentives and goals of a structure have a huge impact on what result comes out of the process, and it's great to see it so well articulated for programming projects.
Wow, wickedly good eye opening read you have there. I hadn't encountered this convocational model before. We should take this to heart when tildes development gets underway.
Agreed, ~tildes.convocation and treat it like a mix of /r/theoryof~ & opensource code contribution related resources/discussions was my suggestion. ;)
Seems like we want a three-tier model...