From: Abhishek S. <i.a...@gm...> - 2011-10-17 23:16:21
|
Hello everyone, Since we are in the process of formally moving to Github from Sourceforge, I've wrote a script that would migrate tickets from Sourceforge TRAC to GIthub Issues. (Thanks to Boopathi for pointing out this pending issue to me). Please find it here : https://github.com/abhishekdelta/tragit (I named it 'Tragit', derived from 'TRAc to GIThub') The script is very generic and configurable so that it supports all forms of Trac data. For Pragyan CMS, I've modified the Report 9 of Trac to generate the proper CSV file with all the data we need to create equivalent issues in Github. However, there are 2 things left: 1) User assignment So currently, I'm not sure how the Github Issues assign feature works. Because you cannot just randomly assign someone to some ticket. Can anyone please find out and tell me what is the requirement for the user to be able to assigned a ticket to. I suspect he should be a developer in some way, either have made some commits or have forked the repository atleast. I need to to know that. 2) Comments in Tickets As of now, my script will only move Tickets and its description and other details like milestone, priority, assigned to, severity, etc. But it won't fetch the comments and discussions made on that ticket. So does anyone have any idea how can we fetch those comments from Trac without having to access the DB ? I'll be running the script in the Integriti/Pragyan repository day after tomorrow. Also, I'll be needing the Github username of all Pragyan developers and contributors (as in Sourceforge). Regards. -- Abhishek Shrivastava B.Tech Graduate in ECE (07-11 batch) National Institute of Technology Trichy, India |