Re: [MacRuby-devel] The future of MacRuby
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 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 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 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, >> [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 y
Re: [MacRuby-devel] The future of MacRuby
> > 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? I love the enthusiasm! While MacRuby's goal is not to run Rails apps I agree that it's a great test of maturity. Kouji did a great job getting MacRuby to run Rails: http://www.slideshare.net/kouji/macruby-on-rails-9570032 But you are right that more could be done. Since compliancy is something that matters to you, there are a few things you can do: * help move the tickets over to GitHub and then do some triage (are the bugs still valid, do they have a reduction etc..) * run the test suite and tag/untag the specs to see where we are at * report bugs with reduction as you try different things (autotest for instance). Don't stop at: "autotest doesn't run on MacRuby", try to see what part doesn't and why so the bug is easier to fix. Also, Joshua started working on moving the site to GitHub and might need help: https://github.com/macruby/macruby/tree/gh-pages Allan worked on a new design that you guys might want to reuse: https://github.com/Alland/MacRubyWebsite/ - Matt On Tue, Apr 10, 2012 at 9:39 PM, Kevin Kim wrote: > 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 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 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 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, >>> [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 >>
[MacRuby-devel] Update
Hi guys, So we had a team chat, and we agreed on the following. First, we will release master as 0.12 (and just forget about 0.11). It is important since master has changes for the latest Xcode that have never been snipped yet. I will work on this. In the meantime, if you can, please do install one of the latest nightly builds and let us know of any regression. It is likely that 0.12 will be one of the last releases before 1.0. Second, we will prepare a new landing page for the project, which will be hosted on GitHub. The page will be very minimal, as we intend to use the wiki for the real content. Josh volunteered to work on this, he does not need more help. Watson has been working on the necessary Wiki pages, but we might need more. If you're interested, the Wiki is open to anyone, you can create new pages or edit existing ones: https://github.com/macruby/macruby/wiki Third, we will migrate the tickets from trac to GitHub. Jake Smith and Dan Sinclair volunteered to work on this. We will coordinate so that the process will be as smooth as possible. No more help is required here. Fourth, we will move the nightly build system to a new infrastructure. I will provide a Mac Mini that will do the builds and push them on Amazon S3 (costs will be covered by my company). This will not happen right now, but somewhere in the future. We will probably do the first 3 items at once :) Laurent ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
