We should move rdesktop from Sourceforge to github. We gained some experience when we moved TigerVNC.
See bug 5043 for how it was done for TigerVNC.
- Create github rdesktop organization and three repositories: rdesktop, seamlessrdp and rdpproxy. - Create google groups to replace the mailing lists on SF - Create a new static rdesktop web page (www.rdesktop.org) on github.io pages and initialize a update of www.rdesktop.org dns pointer. - Migrate svn repository to git - Lock down SF project to read only state. Do NOT change to moved state due this might initialize a total remove of the project from sourceforge as what happened with tigervnc.
> - Create github rdesktop organization and three repositories: rdesktop, > seamlessrdp and rdpproxy. > Done. https://github.com/rdesktop > - Create google groups to replace the mailing lists on SF > Done by Pierre. https://groups.google.com/forum/#!forum/rdesktop-announce https://groups.google.com/forum/#!forum/rdesktop-users https://groups.google.com/forum/#!forum/rdesktop-devel > - Migrate svn repository to git > Done, with this step i put sourceforge svn repository into read only.
Create a bountysource team and connect the github rdesktop project to it. This will replace the sourceforge donation function and support bounties.
(In reply to comment #4) > Create a bountysource team and connect the github rdesktop project to it. This > will replace the sourceforge donation function and support bounties. Finally the BountySource team is created and connected to the GitHub Organization. https://www.bountysource.com/teams/rdesktop Need to update the static web page with information about BountySource.
(In reply to comment #5) > > Need to update the static web page with information about BountySource. > Fixed upstream.
Here is a summary what is left to do in order: - Update DNS record for www.rdesktop.org - Update visual texts such as description for SF project that announce the move to GitHub and include links. - Send announcement mail about the move to GitHub to all rdesktop mailinglists. - Lock down the mailinlist and verify that SF project is read only and its clear that the project is moved.
(In reply to comment #7) > > - Update DNS record for www.rdesktop.org > Mail is now sent to Matthew both the known edu address and the one registered with the rdesktop.org domain (whois).
(In reply to comment #8) > (In reply to comment #7) > > > > - Update DNS record for www.rdesktop.org > > > > Mail is now sent to Matthew both the known edu address and the one registered > with the rdesktop.org domain (whois). DNS pointers are now updated and new www.rdesktop.org is now live.
(In reply to comment #7) > > - Send announcement mail about the move to GitHub to all > rdesktop mailinglists. > Mail sent and mailing lists are now locked down.
rdesktop.sf.net still gives you the old page. Should probably be updated. Also, SeamlessRDP is now in its own repo with its own issue tracker. Perhaps this needs to be pointed out when people are filing bugs?
The move is also not very clearly described on the sourceforge project page. There is merely a github URL under the title. It should be more explicit that everything has been moved and the sourceforge page is merely an historic archive.
The issue tracker is not locked down. I could still create a ticket: https://sourceforge.net/p/rdesktop/feature-requests/165/
(In reply to comment #11) > rdesktop.sf.net still gives you the old page. Should probably be updated. > Added a redirect to http://rdesktop.org
(In reply to comment #11) > > Also, SeamlessRDP is now in its own repo with its own issue tracker. Perhaps > this needs to be pointed out when people are filing bugs? > Added information about SeamlessRDP repo and issuetracker.
(In reply to comment #12) > The move is also not very clearly described on the sourceforge project page. > There is merely a github URL under the title. It should be more explicit that > everything has been moved and the sourceforge page is merely an historic > archive. Project metadata is now updated with information and links.
Looks good, with one small detail: There is no configure script in the release tar balls. (it is also odd that a bunch of other generated files are checked in. e.g. config.guess)
(In reply to comment #17) > Looks good, with one small detail: There is no configure script in the release > tar balls. > Update doc/makerelease.txt with correct information how to create tarballs and a release in general on GitHub..
Looks good now. Would be nice to get rid of the automatic download links, but that's probably not possible.
