Re: [MacRuby-devel] The future of MacRuby
I have already tried importing the tickets to GitHub at http://github.com/theviolentbear/macruby-issues usinghttps://github.com/adamcik/github-trac-ticket-import. I was doing it so I could have offline access to tickets, but someone let me know that it was being discussed on the mailing list. It didn't properly escape code blocks nor did it import most of the metadata or respect the GitHub API limits, but it kind of worked as you can see. -- Jake Smith pace e bene On Sunday, April 8, 2012 at 10:00 AM, [email protected] wrote: > Send MacRuby-devel mailing list submissions to > [email protected] (mailto:[email protected]) > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > or, via email, send a message with subject or body 'help' to > [email protected] > (mailto:[email protected]) > > You can reach the person managing the list at > [email protected] > (mailto:[email protected]) > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MacRuby-devel digest..." > > > Today's Topics: > > 1. Re: The future of MacRuby (Eloy Duran) > 2. Re: The future of MacRuby (dan sinclair) > 3. Re: The future of MacRuby (Eloy Duran) > > > -- > > Message: 1 > Date: Sat, 7 Apr 2012 23:40:39 +0200 > From: Eloy Duran mailto:[email protected])> > To: "MacRuby development discussions." > (mailto:[email protected])> > Subject: Re: [MacRuby-devel] The future of MacRuby > Message-ID: (mailto:[email protected])> > Content-Type: text/plain; charset=windows-1252 > > > Can we get the issues section enabled on github and move off of Trac? (Not > > sure how hard it would be to import all of the old trac stuff to Github). > > > > Would be nice to consolidate everything in one place. > > I think that?s an excellent idea. However, it?s probably better to first > import tickets from Trac before we open it up for new tickets, because that > won't leave any risk for damaging any tickets opened before the old tickets > are imported and also avoids people spending time on duplicate tickets. > > Are you interested in investigating this? > > -- > > Message: 2 > Date: Sat, 7 Apr 2012 14:53:19 -0700 > From: dan sinclair mailto:[email protected])> > To: "MacRuby development discussions." > (mailto:[email protected])> > Subject: Re: [MacRuby-devel] The future of MacRuby > Message-ID: > (mailto:[email protected])> > Content-Type: text/plain; charset="windows-1252" > > Can you import before it's open? I just assumed it wasn't accessible at all > until enable? It looks like forgeplucker (http://home.gna.org/forgeplucker/) > has support to pull tickets out of trac and dump to JSON. Should be pretty > easy to go from JSON to GitHub API I'd expect. > > I can take a look and see what's involved. > > dan > > > > > On Sat, Apr 7, 2012 at 2:40 PM, Eloy Duran (mailto:[email protected])> wrote: > > > > Can we get the issues section enabled on github and move off of Trac? > > (Not sure how hard it would be to import all of the old trac stuff to > > Github). > > > > > > Would be nice to consolidate everything in one place. > > > > I think that?s an excellent idea. However, it?s probably better to first > > import tickets from Trac before we open it up for new tickets, because that > > won't leave any risk for damaging any tickets opened before the old tickets > > are imported and also avoids people spending time on duplicate tickets. > > > > Are you interested in investigating this? > > ___ > > MacRuby-devel mailing list > > [email protected] > > (mailto:[email protected]) > > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > > > -- next part -- > An HTML attachment was scrubbed... > URL: > <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20120407/5b4ccf1d/attachment-0001.html> > > -- > > Message: 3 > Date: Sun, 8 Apr 2012 00:01:36 +0200 > From: Eloy Duran mailto:[email protected])> > To: "MacRub
Re: [MacRuby-devel] The future of MacRuby
I will have time, but not until the 16th or 17th. If that time frame works, then I should be able to handle it. @bill I don't need the SQL dump unless we need something that's not exposed by the CSV reports. @matt As far as I can tell so far, I can map email addresses to github usernames as long as their email address is public on github. I'm still looking into the different possibilities. Sent from my iPad On Apr 9, 2012, at 7:22 PM, dan sinclair wrote: > Jake, > > Would you have time to continue with this effort, or should I continue > looking into the import? > > Thanks, > dan > > > > On Sun, Apr 8, 2012 at 9:00 AM, Jake Smith wrote: > I have already tried importing the tickets to GitHub at > http://github.com/theviolentbear/macruby-issues > usinghttps://github.com/adamcik/github-trac-ticket-import. I was doing it so > I could have offline access to tickets, but someone let me know that it was > being discussed on the mailing list. It didn't properly escape code blocks > nor did it import most of the metadata or respect the GitHub API limits, but > it kind of worked as you can see. > > -- > Jake Smith > pace e bene > > On Sunday, April 8, 2012 at 10:00 AM, > [email protected] wrote: > >> Send MacRuby-devel mailing list submissions to >> [email protected] >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> or, via email, send a message with subject or body 'help' to >> [email protected] >> >> You can reach the person managing the list at >> [email protected] >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of MacRuby-devel digest..." >> >> >> Today's Topics: >> >> 1. Re: The future of MacRuby (Eloy Duran) >> 2. Re: The future of MacRuby (dan sinclair) >> 3. Re: The future of MacRuby (Eloy Duran) >> >> >> -- >> >> Message: 1 >> Date: Sat, 7 Apr 2012 23:40:39 +0200 >> From: Eloy Duran >> To: "MacRuby development discussions." >> >> Subject: Re: [MacRuby-devel] The future of MacRuby >> Message-ID: >> Content-Type: text/plain; charset=windows-1252 >> >>> Can we get the issues section enabled on github and move off of Trac? (Not >>> sure how hard it would be to import all of the old trac stuff to Github). >>> >>> Would be nice to consolidate everything in one place. >> >> I think that?s an excellent idea. However, it?s probably better to first >> import tickets from Trac before we open it up for new tickets, because that >> won't leave any risk for damaging any tickets opened before the old tickets >> are imported and also avoids people spending time on duplicate tickets. >> >> Are you interested in investigating this? >> >> -- >> >> Message: 2 >> Date: Sat, 7 Apr 2012 14:53:19 -0700 >> From: dan sinclair >> To: "MacRuby development discussions." >> >> Subject: Re: [MacRuby-devel] The future of MacRuby >> Message-ID: >> >> Content-Type: text/plain; charset="windows-1252" >> >> Can you import before it's open? I just assumed it wasn't accessible at all >> until enable? It looks like forgeplucker (http://home.gna.org/forgeplucker/) >> has support to pull tickets out of trac and dump to JSON. Should be pretty >> easy to go from JSON to GitHub API I'd expect. >> >> I can take a look and see what's involved. >> >> dan >> >> >> >> >> On Sat, Apr 7, 2012 at 2:40 PM, Eloy Duran wrote: >> >>>> Can we get the issues section enabled on github and move off of Trac? >>> (Not sure how hard it would be to import all of the old trac stuff to >>> Github). >>>> >>>> Would be nice to consolidate everything in one place. >>> >>> I think that?s an excellent idea. However, it?s probably better to first >>> import tickets from Trac before we open it up for new tickets, because that >>> won't leave any risk for damaging any tickets opened before the old tickets >>> are imported and also avoids people spending time on duplicate tickets. >>> >>> Are you interested in investigating this? >>> _
Re: [MacRuby-devel] migrating tickets to GitHub
Matt, I took responsibility for that project, but unfortunately was out of the country for a week and this past week have been swamped. So, I scheduled the migration as a client job with a deadline of Friday the 4th, so it will be done by then at the absolute latest. As far as status, it's about 30% as I switched from using the CSV report to the SQL database and had to start over, but will hopefully have the project completed Tuesday. -- Jake Smith pace e bene On Friday, April 27, 2012 at 4:58 AM, Matt Aimonetti wrote: > So it looks like we are waiting for the tracker tickets to be migrated from > MacOS Forge to GitHub to also do the website update and the release. > Who's working on that, what's the status of the migration? > > Thanks, > > - Matt > ___ > MacRuby-devel mailing list > [email protected] (mailto:[email protected]) > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] GitHub Issue import
Just wanted to apologize to everyone for spamming you on GitHub! I was testing an import tool and meant to only run a subset of Trac tickets, but accidentally ran the whole database and spammed everyone with notifications. If you're on GitHub, but use a different email address than the one on Trac, feel free to email me with your GitHub username so issues and comments can be assigned/attributed to you. + Jake Smith pace e bene ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
