Bugzilla – Bug 5043
Move TigerVNC to github
Last modified: 2014-10-06 15:55:44
You need to
before you can comment on or make changes to this bug.
Sourceforge is horrible, and their new platform has hardly made things better.
Github seems like a much better alternative where collaboration is much easier,
which should hopefully mean more contributions.
Some features we lose though:
- Wiki. Github has static pages though, and our wiki has hardly been active.
Also, the pages are stored as a git repo so people can send pull requests to it
- Mailing lists. Google groups is a good alternative for those though.
(In reply to comment #0)
> Some features we lose though:
> - Wiki.
Scratch that. They seem to have some undocumented wiki functionality. Not sure
if we can point a domain at it though like with the static pages.
The migration should be pretty much done. Most of the stuff on sourceforge is
put into read-only mode, and there are pointers all over the place directing
people to github.
Currently we're still using the file storage facilities at sourceforge. Not
ideal, but there are no clear alternatives right now.
Info about github integration at bintray:
Unclear what their limits are though. Maximum file size of 50 MiB though, and
some unknown total limit (found via Google).
Found the limit:
"Quota: Currently, the amount of data you can upload is 500 MB of your best
The last TigerVNC release was 150 MiB, so this could quickly become a problem.
Talked to the bintray people and I got a quota of 2 GiB instead. I've also put
the 1.3.1 release there and it seems to be working fine.
Nightly builds are still on sourceforge, but brian is playing around with some
publicly hosted jenkins services.
This is done as far as I can tell.
Sourceforge issues are not migrated, and this is not documented/mentioned
anywhere. (See also https://github.com/ttencate/sf2github).
(In reply to comment #7)
> Sourceforge issues are not migrated, and this is not documented/mentioned
> anywhere. (See also https://github.com/ttencate/sf2github).