|
|
|
|
|
|
by jaredcnance
1954 days ago
|
|
|
I don’t know that you can overstate the importance of being on GitHub. The vast majority of developers are familiar with GitHub and can quickly contribute to something that is well written and documented. I’m not familiar with Fossil, but the way you described contributions is not at all community friendly. You need to allow users to fork your repo and PR their changes back in openly. The platform must facilitate inline discussion around code changes. No, you should not allow direct write access but they should be able to propose a diff and you should be able to have a threaded conversation about each line of code if necessary. If they can’t do that, then you will never grow a community. |
|
|
I will allow others to propose a diff, and others can also fork the repository if they want to; nothing is stopping that. (Although, those who wish to fork it must store their own copy (or use chiselapp); I will not host it for them.) If other people want to use GitHub, that is also OK.
Threaded discussions are possible with NNTP. Making a threaded conversation about each line of code (or a group of contiguous lines of code) is also possible; if the message body is formatted in a certain way to find the code in there, then a header could be added to reference the individual line of code (or range) being commented on. (The relevant line(s) of code should also be quoted in the follow-up message.)
However, code patches are not the only kinds of contributions that can be made; there are also documentation, bug reports, feature requests, FAQ, artwork, discussion about how something should be implemented, etc.