[MacRuby-devel] The future of MacRuby

Tue Apr 10 12:39:44 PDT 2012

All this traffic on the group is great! I was worried that MacRuby was
going to whither a die.
I've been trying on and off for a while (since 0.6 ?), to try to get into
MacRuby dev and help out, but, sadly, life and work gets in the way.
>From my perspective, the best thing would be better developer documention.
If I want to fix X, I should look in file Y.
This may not be possible immediately, but I think getting Laurent to help
out here would be critical.

Second, I'd like to see MacRuby be on par with all the other Ruby
implementations.
To me the simplest benchmark would be supporting Rails and being an option
on Travis CI.
I've encountered problems with this with respect to running autotest, but I
think we can get there!

I'm ready. What can I do to help?

-kevin

On Tue, Apr 10, 2012 at 12:38 AM, Jake Smith <jake at theviolentbear.com>wrote:

> 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 <dj2 at everburning.com> 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 <jake at theviolentbear.com>wrote:
>
>> I have already tried importing the tickets to GitHub at
>> http://github.com/theviolentbear/macruby-issues using
>> https://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,
>> macruby-devel-request at lists.macosforge.org wrote:
>>
>> Send MacRuby-devel mailing list submissions to
>> macruby-devel at lists.macosforge.org
>>
>> 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
>> macruby-devel-request at lists.macosforge.org
>>
>> You can reach the person managing the list at
>> macruby-devel-owner at lists.macosforge.org
>>
>> 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 <eloy.de.enige at gmail.com>
>> To: "MacRuby development discussions."
>> <macruby-devel at lists.macosforge.org>
>> Subject: Re: [MacRuby-devel] The future of MacRuby
>> Message-ID: <D23125EB-0B40-4F7B-BB6C-6D739ED4D32A at gmail.com>
>> 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 <dj2 at everburning.com>
>> To: "MacRuby development discussions."
>> <macruby-devel at lists.macosforge.org>
>> Subject: Re: [MacRuby-devel] The future of MacRuby
>> Message-ID:
>> <CAB0vK_JU6iF5z1pv38z1izsJeE+qHn=Pb9k2ZpuuctS3n-G_jg at mail.gmail.com>
>> 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 <eloy.de.enige at gmail.com>
>> 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
>> MacRuby-devel at lists.macosforge.org
>> 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 <eloy.de.enige at gmail.com>
>> To: "MacRuby development discussions."
>> <macruby-devel at lists.macosforge.org>
>> Subject: Re: [MacRuby-devel] The future of MacRuby
>> Message-ID: <D10916E5-8078-4C70-87DF-9B05E593F54B at gmail.com>
>> 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
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>> End of MacRuby-devel Digest, Vol 50, Issue 19
>> *********************************************
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> 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/20120410/894ad77c/attachment.html>