On 1 March 2012 16:16, Miles Bader <miles@xxxxxxx> wrote: > Andrew Ardill <andrew.ardill@xxxxxxxxx> writes: >> Additionally, if we are not prepared to use non-Free tools, we should >> probably stop using github. > > I think the issue isn't "using" non-free tools so much as it's getting > _locked into_ non-free tools. > > So if JIRA makes all its data trivially exportable in a format which > is easy to use, JIRA provides the ability to trivially export any 'filter' as XML or CSV data files. A filter is simply a search, and can contain every single issue in the database. Some pieces of information are slightly more difficult to migrate. - Issue attachments such as screenshots are not stored in the database, and we would have to request them in order to retrieve them. - User information and configuration data is only available in a full site backup (which is available on request). - CSV export option does not include comments. (XML, and Word formats do) Additionally, there are quite a number of tools to allow migration between JIRA and other tools, and in my experience Atlassian are quite helpful when you try and move off their products. > and there's some way of isolating references to it so > that it's possible to switch to something else without undue hardship JIRA has the capacity to automatically link issues to commits which mention issue numbers, however this is by no means essential or necessary functionality. JIRA will be happy completely detached from the rest of the world, and will provide additional functionality gradually as it becomes more integrated. Some functionality it can provide without forming hard links with the outside world (like polling the repository and providing continuous builds) The primary thing to look out for would be other sites linking to the issue tracker. Unfortunately, there is no way at the moment to provide an alternate URI for the tracker, so it is hard to avoid this from happening. Regards, Andrew Ardill -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html