Bug 5043 - Move TigerVNC to github
Summary: Move TigerVNC to github
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VNC (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.3.0
Assignee: Pierre Ossman
Keywords: astrand_tester, prosaic
Depends on:
Reported: 2014-03-27 09:28 CET by Pierre Ossman
Modified: 2014-10-06 15:55 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2014-03-27 09:28:53 CET
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 for improvements.

 - Mailing lists. Google groups is a good alternative for those though.
Comment 1 Pierre Ossman cendio 2014-03-27 09:50:38 CET
(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.
Comment 2 Pierre Ossman cendio 2014-07-03 13:56:08 CEST
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.
Comment 3 Pierre Ossman cendio 2014-07-07 10:21:37 CEST
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).
Comment 4 Pierre Ossman cendio 2014-07-07 10:28:15 CEST
Found the limit:

"Quota: Currently, the amount of data you can upload is 500 MB of your best material."

The last TigerVNC release was 150 MiB, so this could quickly become a problem.
Comment 5 Pierre Ossman cendio 2014-08-18 14:23:20 CEST
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.
Comment 6 Pierre Ossman cendio 2014-08-20 12:46:21 CEST
This is done as far as I can tell.
Comment 7 Peter Åstrand cendio 2014-09-22 13:38:42 CEST
Sourceforge issues are not migrated, and this is not documented/mentioned anywhere. (See also https://github.com/ttencate/sf2github).
Comment 8 Pierre Ossman cendio 2014-09-22 14:34:34 CEST
(In reply to comment #7)
> Sourceforge issues are not migrated, and this is not documented/mentioned
> anywhere. (See also https://github.com/ttencate/sf2github).

Comment 9 Peter Åstrand cendio 2014-09-22 14:40:15 CEST
Good now.

Note You need to log in before you can comment on or make changes to this bug.