4 ms·
> I don't need the added burden of responding to issues and pull requests You don't have to. open sourcing does not mean putting it on Github with an open bug
by progval 5y ago
> I don't need the added burden of responding to issues and pull requests
You don't have to. open sourcing does not mean putting it on Github with an open bug tracker, you could simply offer tarball downloads, mention you don't support it, and ignore any email about it.
- eminence32 5y agoOr host it on gitlab, which lets you entirely disable forking, merge requests, and the issue tracker
- blondin 5y agowhy gitlab? host it on github, just don't make the repo public! but yeah this thread is correct about the burden of issue tracking and pull requests management.
- rightbyte 5y ago> disable forking That seems mean?
- wongarsu 5y agoYou can always clone the repo, change the git remote to a newly created one and upload there. You get a perfect copy, just that it isn't recognized as a fork, thus you can't make pull requests (you can still merge changes via the Git cli as always)
- gjsman-1000 5y agoThis is actually how Apple does some of their open-source projects. For example, the XNU kernel at the heart of macOS is open source, along with some of its kernel extensions. Apple isn’t interested in having other people work on it though or having their commit history unveil vulnerabilities, so they just squash all the commits into one and release the tarball for every new macOS version. Open-source kernel? Check.