RASTER EFFECTS CODE
RASTER EFFECTS LICENSE

You’ve given admin access to that can do anything with them. Users and developers can comment on these and again, it’s only the people These sites have support for forums and bug reports, features lists, etc. To send you “pull requests” to merge a feature back into your version, and Repository and make changes there that do not affect yours. Since it’s the “do what ever you want, no warrenty, and can’t use my name

RASTER EFFECTS LICENSE

When creating the project you can specify the license (I also prefer MIT Source space so you’re more likely to get help from other devs, bitbucketĪllows free private repros so the project can be in the same place as your Make the project on github or bitbucket (github has more “cred” in the open I’m not sure of a source that details it, but here is the basic approach I Pasting below to see if it works this time: Well, it looks like the email -> forums feature ate my entire post.

RASTER EFFECTS CODE

You can start doing that later, but for now you can just put the code out there, and focus on programming and getting users. You’ll probably not get people flocking to make contributions at first (usually you need users before you get contributors), but when they come, just treat them as humans who wish to help : )Ĭommunity management skills are important if you want to actively grow a community of contributors. You can start by simply putting the source online (for example on Github, like Tiled), and linking to it. In the vast majority of cases better for everyone to work together. Maintaining a fork takes lots or resources though. On the flip side, if someone disagrees with your direction, they can “fork” – release their own copy with their own modifications. But still it will be you who defines the direction of the project. Later (if you’re lucky), you might start getting more contributions and your work might become more of a steward of the code and reviewer of new contributions, and less of an actual programmer. If someone makes contributions, they might share them with you, and if you like them you can incorporate them into your library. You’re the author your roadmap and list of goals are what drive the project. I don’t know about books, but no, I wouldn’t describe it as an anarchy. How new features make its way to the roadmap? Who have the rights to make commits? etc… So if you can recommend some literature, I’ll read it. I have a rodamap, a list of things that I’d like to implement, and an “identity” about what Tilkengine is that shouldn’t be lost. I’m sure this is not how actually works, but I need knowledge about this. From my ignorance I fear that open source projects are a kind of anarchy where everybody can put its hands on it, and projects end growing out of control. What I need now is a good source of information (book or website) about open source management.

Raster effects