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 <[email protected] (mailto:[email protected])> > To: "MacRuby development discussions." > <[email protected] > (mailto:[email protected])> > Subject: Re: [MacRuby-devel] The future of MacRuby > Message-ID: <[email protected] > (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 <[email protected] (mailto:[email protected])> > To: "MacRuby development discussions." > <[email protected] > (mailto:[email protected])> > Subject: Re: [MacRuby-devel] The future of MacRuby > Message-ID: > <CAB0vK_JU6iF5z1pv38z1izsJeE+qHn=pb9k2zpuucts3n-g...@mail.gmail.com > (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 <[email protected] > (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 <[email protected] (mailto:[email protected])> > To: "MacRuby development discussions." > <[email protected] > (mailto:[email protected])> > Subject: Re: [MacRuby-devel] The future of MacRuby > Message-ID: <[email protected] > (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. > > Well, we?d open it once the import is ready to be performed. Until then it > can be tested out with a dummy repo :) > > > I can take a look and see what's involved. > > Awesome! Thanks. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20120408/dc0f1ed3/attachment-0001.html> > > ------------------------------ > > _______________________________________________ > MacRuby-devel mailing list > [email protected] (mailto:[email protected]) > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > > End of MacRuby-devel Digest, Vol 50, Issue 19 > ********************************************* > >
_______________________________________________ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
