You can clone with
HTTPS or Subversion.
This is a big and important ticket. After 6 years of using Trac, the Piwik project and community have expressed much interest in moving to another ticket system.
We've looked into other self hosted ticket systems, but our conclusion has been to simply use Github issues. They are fast, easy, practical, and many users are already familiar with Github. We moved our code from SVN to Git and Github 16 months ago.
After this ticket:
Hopefully using Github issues will see more participation in tickets and feature requests, more users joining discussions.
This will help make Piwik the best open analytics platform, built by the community for the community!
About redirects from http://dev.piwik.org/trac/ticket/X to https://github.com/piwik/piwik/issues/X: IMHO we do not need a "transition period" where we leave Trac tickets as read only.
About: http://dev.piwik.org/ - I would leave the trac wiki page up for a few weeks, or we can redirect it to a page on http://piwik.org
Didn't find any existing tool to mirror Github issues. Probably has to be developed if REALLY necessary
We need to copy all the attachments upfront and have it available under the same or similar URL before closing Trac and before migrating to Github
Blog post should be published in advance (1-2 weeks upfront) notifying users about this migration. As users are identified by their email address on Github they should also be able to send us a veto in case they do not want to have their Github user linked depending on their email address.
In e4ec91c: refs #5273 make sure to use theme color instead of hardcoded value
Mirror is really important for few reasons: SEO purposes and "Data ownership" of this knowledge. Github services do not really go down ever, they are very reliable... but technically they could go down for few hours or days, and we wouldn't want this to stop our work :-)
Attachments can be uploaded to new site: http://issues.piwik.org (which will host the github issues mirror)
The goal would be to show each issue, with its comments, at a URL such as: http://issues.piwik.org/472 mirrors: #472
@tsteur How much effort would it be to make the simplest mirror of Github issues, synched eg. once a day? (no need to sync attachments, only text...).
I'd say 3-6 days
I've created separate ticket for creating a Github issues mirror: #5299
** Other tickets **
see also: #5380 Changelog generator for Piwik that will credit people who participated in the release
see also #5381 Create a CONTRIBUTING.md file to let users know how to contribute to Piwik
@tsteur maybe we could release our script as open source (even if not perfect / tuned to our needs) ? I think it would help some people out there :)
ANNOUNCEMENT: to have all your trac comments and tickets use your Github username, please opt-in in this gist:
Refs #5273 Replace Trac ticket URL to Github
Refs #5273 Replace other Trac URLs with Github URLs
updating URls to reference Github after migrating issues to github
Removing references to Trac
Nice work @tsteur ! This is done. Welcome to Github issues!
refs #5273 make sure to use theme color instead of hardcoded value