adaliabooks: If it's possible to host a userscript properly so it installs easily and auto updates for people then I'm happy to make the move to Github and whatever advantages it might offer.
To be clear: I've served a couple of very minor userscripts off GitHub projects before. I'm not aware of any obvious pitfalls or any significant work involved—again, so long as you keep the release version in a fixed location. I know you've already sunk a lot of work into Adalia Fundamentals (
thank you!) and I wouldn't suggest moving the script to a GitHub project if I thought it would require any significant effort on your part.
I really think that being able to use GitHub's issue tracker would be a major improvement—for you
especially—over fifty pages of posts here on the forum. Note: the issue tracker supports templates, so you can ask for certain kinds of information right there in each new issue before it's created.
I don't know for certain, but some of the other features might be useful to you in the future. Besides the wiki, there's tagging, changelogs, a 'releases' feature—and my experience is that collaboration is easier with the full project system.
Also, maybe this is obvious, but: since GitHub is quite widely used, there's no shortage of userscripts for GitHub besides the cosmetic one I linked in my last response, and some of them could be quite useful. I'm also seeing a growing amount of integration between GitHub and developer-focused text editors, as well as IDEs. If you're already using Atom to edit your userscripts, well, it's a GitHub project, so the integration is as good as you might expect. Sublime Text has excellent integration as well, if you leverage the
package management system. I believe Notepad++ has integration, and so on and so forth.