The IronRuby project is a community project, and has contributors inside and outside of Microsoft. We have integrated the work of several external folks into the product (thanks!), and we are making rapid progress. We''d like to try to make things easier. We''d like to not be in the way of community work on IronRuby; we''d like to give the community a little more ownership over this project. Ideally, we would all work out of the same repository, but this can''t happen right now. However, we have some ideas to make things easier. First, we''re moving to Github. I''ll be creating the Ironruby project on Github at http://github.com/ironruby/ironruby. This will be the same user on Github that we use for IronRuby-contribs, and our versions of RubySpec. The biggest upside of this is that anyone can fork IronRuby and work on it, and submit a pull request to get it integrated back into the main tree. However, we don''t want to be in the way of accepting patches. Next, we''re going to institute a Linux-like system of Lieutenants. We''re looking for people who are passionate and knowledgeable about the IronRuby project to take on this role. The goal of this system is to streamline the process, and make it easier for our external contributors to get code into IronRuby. We''d like to have Lieutenants who can take the patches and pull requests, code review them, and then commit them to their trees. Then we can pull these forks into our repository when we do pushes, and integrate it into one repo. Our hope is that we can be viewed as just one node in the tree, or ring. We shouldn''t have to be the central repository; we''re just one of the repositories. Finally, we are going to be getting rid of the history in SVN, which for the most part is a bunch of commits saying "sync to the head of TFS." We are doing this to get a fresh start. The layout of the new Git repository is going to exactly match our internal layout. That makes maintaining the transforms from TFS to GIT much easier. It also will make things easier when talking about the locations of files. We hope that these changes will make things easier for all of you. Thanks, ~~~~ JD http://blog.jredville.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081124/0de74982/attachment-0001.html>
Whoo hoo! Great job guys! This is very exciting. One question though, will folks still need to have a signed agreement to contribute code? On Mon, Nov 24, 2008 at 5:05 PM, Jim Deville <jdeville at microsoft.com> wrote:> The IronRuby project is a community project, and has contributors inside > and outside of Microsoft. We have integrated the work of several external > folks into the product (thanks!), and we are making rapid progress. > > > > We''d like to try to make things easier. We''d like to not be in the way of > community work on IronRuby; we''d like to give the community a little more > ownership over this project. Ideally, we would all work out of the same > repository, but this can''t happen right now. However, we have some ideas to > make things easier. > > > > First, we''re moving to Github. I''ll be creating the Ironruby project on > Github at http://github.com/ironruby/ironruby. This will be the same user > on Github that we use for IronRuby-contribs, and our versions of RubySpec. > The biggest upside of this is that anyone can fork IronRuby and work on it, > and submit a pull request to get it integrated back into the main tree. > However, we don''t want to be in the way of accepting patches. > > > > Next, we''re going to institute a Linux-like system of Lieutenants. We''re > looking for people who are passionate and knowledgeable about the IronRuby > project to take on this role. The goal of this system is to streamline the > process, and make it easier for our external contributors to get code into > IronRuby. We''d like to have Lieutenants who can take the patches and pull > requests, code review them, and then commit them to their trees. Then we can > pull these forks into our repository when we do pushes, and integrate it > into one repo. Our hope is that we can be viewed as just one node in the > tree, or ring. We shouldn''t have to be the central repository; we''re just > one of the repositories. > > > > Finally, we are going to be getting rid of the history in SVN, which for > the most part is a bunch of commits saying "sync to the head of TFS." We are > doing this to get a fresh start. The layout of the new Git repository is > going to exactly match our internal layout. That makes maintaining the > transforms from TFS to GIT much easier. It also will make things easier when > talking about the locations of files. > > > > We hope that these changes will make things easier for all of you. > > > > Thanks, > > > > ~~~~ > > JD > > http://blog.jredville.com > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081124/ad17df96/attachment.html>
You have no idea what this news means to me. It''s like... IronRuby is really getting started... More then willing to continue helping in any way I can. :) On Mon, Nov 24, 2008 at 7:05 PM, Jim Deville <jdeville at microsoft.com> wrote:> The IronRuby project is a community project, and has contributors inside > and outside of Microsoft. We have integrated the work of several external > folks into the product (thanks!), and we are making rapid progress. > > > > We''d like to try to make things easier. We''d like to not be in the way of > community work on IronRuby; we''d like to give the community a little more > ownership over this project. Ideally, we would all work out of the same > repository, but this can''t happen right now. However, we have some ideas to > make things easier. > > > > First, we''re moving to Github. I''ll be creating the Ironruby project on > Github at http://github.com/ironruby/ironruby. This will be the same user > on Github that we use for IronRuby-contribs, and our versions of RubySpec. > The biggest upside of this is that anyone can fork IronRuby and work on it, > and submit a pull request to get it integrated back into the main tree. > However, we don''t want to be in the way of accepting patches. > > > > Next, we''re going to institute a Linux-like system of Lieutenants. We''re > looking for people who are passionate and knowledgeable about the IronRuby > project to take on this role. The goal of this system is to streamline the > process, and make it easier for our external contributors to get code into > IronRuby. We''d like to have Lieutenants who can take the patches and pull > requests, code review them, and then commit them to their trees. Then we can > pull these forks into our repository when we do pushes, and integrate it > into one repo. Our hope is that we can be viewed as just one node in the > tree, or ring. We shouldn''t have to be the central repository; we''re just > one of the repositories. > > > > Finally, we are going to be getting rid of the history in SVN, which for > the most part is a bunch of commits saying "sync to the head of TFS." We are > doing this to get a fresh start. The layout of the new Git repository is > going to exactly match our internal layout. That makes maintaining the > transforms from TFS to GIT much easier. It also will make things easier when > talking about the locations of files. > > > > We hope that these changes will make things easier for all of you. > > > > Thanks, > > > > ~~~~ > > JD > > http://blog.jredville.com > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >-- Michael Letterle [Polymath Prokrammer] http://blog.prokrams.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081124/0e01abdd/attachment.html>
We still need contribution agreements, but that is no different than Apache, Mozilla, and other major Open Source projects. JD -----Original Message----- From: Mike Moore <blowmage at gmail.com> Sent: November 24, 2008 4:12 PM To: ironruby-core at rubyforge.org <ironruby-core at rubyforge.org> Subject: Re: [Ironruby-core] IronRuby moving to Github Whoo hoo! Great job guys! This is very exciting. One question though, will folks still need to have a signed agreement to contribute code? On Mon, Nov 24, 2008 at 5:05 PM, Jim Deville <jdeville at microsoft.com<mailto:jdeville at microsoft.com>> wrote: The IronRuby project is a community project, and has contributors inside and outside of Microsoft. We have integrated the work of several external folks into the product (thanks!), and we are making rapid progress. We''d like to try to make things easier. We''d like to not be in the way of community work on IronRuby; we''d like to give the community a little more ownership over this project. Ideally, we would all work out of the same repository, but this can''t happen right now. However, we have some ideas to make things easier. First, we''re moving to Github. I''ll be creating the Ironruby project on Github at http://github.com/ironruby/ironruby. This will be the same user on Github that we use for IronRuby-contribs, and our versions of RubySpec. The biggest upside of this is that anyone can fork IronRuby and work on it, and submit a pull request to get it integrated back into the main tree. However, we don''t want to be in the way of accepting patches. Next, we''re going to institute a Linux-like system of Lieutenants. We''re looking for people who are passionate and knowledgeable about the IronRuby project to take on this role. The goal of this system is to streamline the process, and make it easier for our external contributors to get code into IronRuby. We''d like to have Lieutenants who can take the patches and pull requests, code review them, and then commit them to their trees. Then we can pull these forks into our repository when we do pushes, and integrate it into one repo. Our hope is that we can be viewed as just one node in the tree, or ring. We shouldn''t have to be the central repository; we''re just one of the repositories. Finally, we are going to be getting rid of the history in SVN, which for the most part is a bunch of commits saying "sync to the head of TFS." We are doing this to get a fresh start. The layout of the new Git repository is going to exactly match our internal layout. That makes maintaining the transforms from TFS to GIT much easier. It also will make things easier when talking about the locations of files. We hope that these changes will make things easier for all of you. Thanks, ~~~~ JD http://blog.jredville.com _______________________________________________ Ironruby-core mailing list Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org> http://rubyforge.org/mailman/listinfo/ironruby-core -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081124/2f87a953/attachment.html>
On Mon, Nov 24, 2008 at 5:43 PM, Jim Deville <jdeville at microsoft.com> wrote:> We still need contribution agreements, but that is no different than Apache, Mozilla, and other major Open Source projects. > > So is it the lieutenants'' responsibility to ensure that whoever they pullcode from has an agreement in place? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081124/14983671/attachment-0001.html>
This is absolutely brilliant and same here - i''m keen to be of some assistance (although i''m more passionate than knowledgable about ironruby). On Tue, Nov 25, 2008 at 11:30 AM, Michael Letterle < michael.letterle at gmail.com> wrote:> You have no idea what this news means to me. It''s like... IronRuby is > really getting started... > > More then willing to continue helping in any way I can. :) > > On Mon, Nov 24, 2008 at 7:05 PM, Jim Deville <jdeville at microsoft.com>wrote: > >> The IronRuby project is a community project, and has contributors inside >> and outside of Microsoft. We have integrated the work of several external >> folks into the product (thanks!), and we are making rapid progress. >> >> >> >> We''d like to try to make things easier. We''d like to not be in the way of >> community work on IronRuby; we''d like to give the community a little more >> ownership over this project. Ideally, we would all work out of the same >> repository, but this can''t happen right now. However, we have some ideas to >> make things easier. >> >> >> >> First, we''re moving to Github. I''ll be creating the Ironruby project on >> Github at http://github.com/ironruby/ironruby. This will be the same user >> on Github that we use for IronRuby-contribs, and our versions of RubySpec. >> The biggest upside of this is that anyone can fork IronRuby and work on it, >> and submit a pull request to get it integrated back into the main tree. >> However, we don''t want to be in the way of accepting patches. >> >> >> >> Next, we''re going to institute a Linux-like system of Lieutenants. We''re >> looking for people who are passionate and knowledgeable about the IronRuby >> project to take on this role. The goal of this system is to streamline the >> process, and make it easier for our external contributors to get code into >> IronRuby. We''d like to have Lieutenants who can take the patches and pull >> requests, code review them, and then commit them to their trees. Then we can >> pull these forks into our repository when we do pushes, and integrate it >> into one repo. Our hope is that we can be viewed as just one node in the >> tree, or ring. We shouldn''t have to be the central repository; we''re just >> one of the repositories. >> >> >> >> Finally, we are going to be getting rid of the history in SVN, which for >> the most part is a bunch of commits saying "sync to the head of TFS." We are >> doing this to get a fresh start. The layout of the new Git repository is >> going to exactly match our internal layout. That makes maintaining the >> transforms from TFS to GIT much easier. It also will make things easier when >> talking about the locations of files. >> >> >> >> We hope that these changes will make things easier for all of you. >> >> >> >> Thanks, >> >> >> >> ~~~~ >> >> JD >> >> http://blog.jredville.com >> >> >> >> _______________________________________________ >> Ironruby-core mailing list >> Ironruby-core at rubyforge.org >> http://rubyforge.org/mailman/listinfo/ironruby-core >> >> > > > -- > Michael Letterle > [Polymath Prokrammer] > http://blog.prokrams.com > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081125/ab2e6980/attachment.html>
Ideally, yes, but we need to figure out how to make it easy. JD -----Original Message----- From: Mike Moore <blowmage at gmail.com> Sent: November 24, 2008 5:04 PM To: ironruby-core at rubyforge.org <ironruby-core at rubyforge.org> Subject: Re: [Ironruby-core] IronRuby moving to Github On Mon, Nov 24, 2008 at 5:43 PM, Jim Deville <jdeville at microsoft.com<mailto:jdeville at microsoft.com>> wrote: We still need contribution agreements, but that is no different than Apache, Mozilla, and other major Open Source projects. So is it the lieutenants'' responsibility to ensure that whoever they pull code from has an agreement in place? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081124/4543fcc0/attachment.html>
Well, the first step is done. The IronRuby Git repository is live at http://github.com/ironruby/ironruby. You can start working against it, but to compile, you will have to set the MERLIN_ROOT environment variable to <<your IR Git repo>>/merlin/main. This will be part of rake eventually, but right now it''s a workaround. Please don''t file any patches against it yet, you can start preparing them, but we won''t be able to get them in until we have the whole tool chain working with Git. ETA for the tool chain is a few weeks. Enjoy! JD From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville Sent: Monday, November 24, 2008 6:14 PM To: ironruby-core at rubyforge.org Subject: Re: [Ironruby-core] IronRuby moving to Github Ideally, yes, but we need to figure out how to make it easy. JD -----Original Message----- From: Mike Moore <blowmage at gmail.com> Sent: November 24, 2008 5:04 PM To: ironruby-core at rubyforge.org <ironruby-core at rubyforge.org> Subject: Re: [Ironruby-core] IronRuby moving to Github On Mon, Nov 24, 2008 at 5:43 PM, Jim Deville <jdeville at microsoft.com<mailto:jdeville at microsoft.com>> wrote: We still need contribution agreements, but that is no different than Apache, Mozilla, and other major Open Source projects. So is it the lieutenants'' responsibility to ensure that whoever they pull code from has an agreement in place? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081126/c60dcdef/attachment.html>
An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081127/c86bfe63/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.jpg Type: image/jpeg Size: 8147 bytes Desc: not available URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20081127/c86bfe63/attachment.jpg>