Jimmy Schementi
2009-Apr-02 22:35 UTC
[Ironruby-core] Proposal: Moving IronRuby bugs to CodePlex
(I originally planned on sending this yesterday, but I waited until today to remove the "April Fools" possibility =P) I''d like to propose moving IronRuby''s bugs off of RubyForge. CodePlex looks like the best option, mainly due to the voting feature for bugs. Here are some possible options for defect tracking, and what I think about them: Lighthouse: http://lighthouseapp.com Sample site: http://silverline.lighthouseapp.com Very usable, nice UI, and I''m a sucker for those types of things. They support multiple projects, so splitting up the project into Compiler, Libraries, Silverlight, etc, would be very clear. There''s also a nice UI for milestone progress, making it fairly clear how the progress is going. Also, other Ruby projects are moving here, so a move to Lighthouse would follow the logic of why we started on RubyForge. Lighthouse also has integration with GitHub, keeping our lighthouse page up-to-date with any changes in git. Lighthouse is usually a pay-service, but I believe they have free hosting for open-source projects. However, there might be limits on how many projects can be created, or users can be admins, so it''d be good to find out these details. Unfortunately, there''s no good way to prioritize tickets other than milestones, and non-project-admins can''t change the milestone, so we can''t accomplish any type of user-prioritization (voting) on tickets. RubyForge: http://rubyforge.org Sample site: http://rubyforge.org/projects/ironruby We''re on RubyForge currently, so switching to RubyForge would be easy. =P Unfortunately, that''s about the only benefit it provides. While RubyForge has been instrumental in shaping the Ruby community, it appears that its heydays have passed, in favor of GitHub and lighthouse. RubyForge also appears to be unmaintained, especially in light of our crazy mailing list delays. File releases are still being used by the Ruby community, mainly because of it being a Ruby Gems repository, so we should keep releasing on it. CodePlex: http://codeplex.com Sample site: http://ironpython.codeplex.com CodePlex has turned into a pretty awesome open-source project site. In the past I wouldn''t have wanted to move to CodePlex, but now there defect tracking features seem like the best, and much faster than they use to be. You can use the web interface, the team foundation client, or CodePlex client to look at bugs, which makes it pretty easy to keep on-top of them. Since CodePlex uses TFS underneath to store work-items and bugs, we can use the TFS API to do git commit integration and things like that (though the TFS API isn''t the greatest, it exists =P). But mainly the web interface has voting support, so our tickets can be prioritized by community feedback very easily ... this is definitely the killer feature for me. As I said, I''m leaning heavily towards CodePlex, mainly for the voting support. IronPython uses this very successfully, and it would help prioritize IronRuby''s work, especially post-1.0. So here''s the proposal: 1. Go through open RubyForge bugs, closing bugs as necessary, and narrowing in on a subset to move to CodePlex (jdeville has begun closing bugs). 2. Create http://ironruby.codeplex.com (already reserved, just waiting to set things up and turn it on), and use it for *Issues* and *Releases* only. We will link to http://wiki.github.com/ironruby/ironruby for other developer information, and http://ironruby.net for general users, from the project homepage, and no other wiki pages will be used. 3. Releases will be the only things remaining on RubyForge, as it''s still the standard place for Ruby releases, though any release announcements/blogs will point to the CodePlex release. 4. CodePlex discussion forums will not be used, as they and will remain on RubyForge for now (though we need to resolve the crazy delays soon). Thoughts? ~Jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20090402/029260e4/attachment-0001.html>
Jimmy Schementi
2009-Apr-08 00:02 UTC
[Ironruby-core] Proposal: Moving IronRuby bugs to CodePlex
No objections/concerns/thoughts/concerns/praises/gifts-of-gold-frankincense-and-myrrh? Ok then ... http://ironruby.codeplex.com/ has been created, and once live all bugs will be stored there. Jim is going through RubyForge bugs slowly, closing ones that are fixed, and possibly moving important ones over to CodePlex. I''ll let you all know when CodePlex is open for business. ~js From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jimmy Schementi Sent: Thursday, April 02, 2009 3:36 PM To: ironruby-core at rubyforge.org Subject: [Ironruby-core] Proposal: Moving IronRuby bugs to CodePlex (I originally planned on sending this yesterday, but I waited until today to remove the "April Fools" possibility =P) I''d like to propose moving IronRuby''s bugs off of RubyForge. CodePlex looks like the best option, mainly due to the voting feature for bugs. Here are some possible options for defect tracking, and what I think about them: Lighthouse: http://lighthouseapp.com Sample site: http://silverline.lighthouseapp.com Very usable, nice UI, and I''m a sucker for those types of things. They support multiple projects, so splitting up the project into Compiler, Libraries, Silverlight, etc, would be very clear. There''s also a nice UI for milestone progress, making it fairly clear how the progress is going. Also, other Ruby projects are moving here, so a move to Lighthouse would follow the logic of why we started on RubyForge. Lighthouse also has integration with GitHub, keeping our lighthouse page up-to-date with any changes in git. Lighthouse is usually a pay-service, but I believe they have free hosting for open-source projects. However, there might be limits on how many projects can be created, or users can be admins, so it''d be good to find out these details. Unfortunately, there''s no good way to prioritize tickets other than milestones, and non-project-admins can''t change the milestone, so we can''t accomplish any type of user-prioritization (voting) on tickets. RubyForge: http://rubyforge.org Sample site: http://rubyforge.org/projects/ironruby We''re on RubyForge currently, so switching to RubyForge would be easy. =P Unfortunately, that''s about the only benefit it provides. While RubyForge has been instrumental in shaping the Ruby community, it appears that its heydays have passed, in favor of GitHub and lighthouse. RubyForge also appears to be unmaintained, especially in light of our crazy mailing list delays. File releases are still being used by the Ruby community, mainly because of it being a Ruby Gems repository, so we should keep releasing on it. CodePlex: http://codeplex.com Sample site: http://ironpython.codeplex.com CodePlex has turned into a pretty awesome open-source project site. In the past I wouldn''t have wanted to move to CodePlex, but now there defect tracking features seem like the best, and much faster than they use to be. You can use the web interface, the team foundation client, or CodePlex client to look at bugs, which makes it pretty easy to keep on-top of them. Since CodePlex uses TFS underneath to store work-items and bugs, we can use the TFS API to do git commit integration and things like that (though the TFS API isn''t the greatest, it exists =P). But mainly the web interface has voting support, so our tickets can be prioritized by community feedback very easily ... this is definitely the killer feature for me. As I said, I''m leaning heavily towards CodePlex, mainly for the voting support. IronPython uses this very successfully, and it would help prioritize IronRuby''s work, especially post-1.0. So here''s the proposal: 1. Go through open RubyForge bugs, closing bugs as necessary, and narrowing in on a subset to move to CodePlex (jdeville has begun closing bugs). 2. Create http://ironruby.codeplex.com (already reserved, just waiting to set things up and turn it on), and use it for *Issues* and *Releases* only. We will link to http://wiki.github.com/ironruby/ironruby for other developer information, and http://ironruby.net for general users, from the project homepage, and no other wiki pages will be used. 3. Releases will be the only things remaining on RubyForge, as it''s still the standard place for Ruby releases, though any release announcements/blogs will point to the CodePlex release. 4. CodePlex discussion forums will not be used, as they and will remain on RubyForge for now (though we need to resolve the crazy delays soon). Thoughts? ~Jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20090408/0d88fcec/attachment.html>
Jimmy Schementi
2009-Apr-09 23:38 UTC
[Ironruby-core] Proposal: Moving IronRuby bugs to CodePlex
http://ironruby.codeplex.com is live. Please direct any bug submissions and downloads of IronRuby to this site, rather than RubyForge. RubyForge bugs will be moved (as appropriate) to CodePlex over time, and v0.3 is on CodePlex, along with sources. Releases may be posted to both sites, simply for exposure, but please link to the CodePlex copy (as http://ironruby.net/Download does). RubyForge''s only use is now the mailing list, though I''m looking to move that as well (with minimal downtime to this list). I''ll keep you all posted. ~Jimmy From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jimmy Schementi Sent: Tuesday, April 07, 2009 5:02 PM To: ironruby-core at rubyforge.org Subject: Re: [Ironruby-core] Proposal: Moving IronRuby bugs to CodePlex No objections/concerns/thoughts/concerns/praises/gifts-of-gold-frankincense-and-myrrh? Ok then ... http://ironruby.codeplex.com/ has been created, and once live all bugs will be stored there. Jim is going through RubyForge bugs slowly, closing ones that are fixed, and possibly moving important ones over to CodePlex. I''ll let you all know when CodePlex is open for business. ~js From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jimmy Schementi Sent: Thursday, April 02, 2009 3:36 PM To: ironruby-core at rubyforge.org Subject: [Ironruby-core] Proposal: Moving IronRuby bugs to CodePlex (I originally planned on sending this yesterday, but I waited until today to remove the "April Fools" possibility =P) I''d like to propose moving IronRuby''s bugs off of RubyForge. CodePlex looks like the best option, mainly due to the voting feature for bugs. Here are some possible options for defect tracking, and what I think about them: Lighthouse: http://lighthouseapp.com Sample site: http://silverline.lighthouseapp.com Very usable, nice UI, and I''m a sucker for those types of things. They support multiple projects, so splitting up the project into Compiler, Libraries, Silverlight, etc, would be very clear. There''s also a nice UI for milestone progress, making it fairly clear how the progress is going. Also, other Ruby projects are moving here, so a move to Lighthouse would follow the logic of why we started on RubyForge. Lighthouse also has integration with GitHub, keeping our lighthouse page up-to-date with any changes in git. Lighthouse is usually a pay-service, but I believe they have free hosting for open-source projects. However, there might be limits on how many projects can be created, or users can be admins, so it''d be good to find out these details. Unfortunately, there''s no good way to prioritize tickets other than milestones, and non-project-admins can''t change the milestone, so we can''t accomplish any type of user-prioritization (voting) on tickets. RubyForge: http://rubyforge.org Sample site: http://rubyforge.org/projects/ironruby We''re on RubyForge currently, so switching to RubyForge would be easy. =P Unfortunately, that''s about the only benefit it provides. While RubyForge has been instrumental in shaping the Ruby community, it appears that its heydays have passed, in favor of GitHub and lighthouse. RubyForge also appears to be unmaintained, especially in light of our crazy mailing list delays. File releases are still being used by the Ruby community, mainly because of it being a Ruby Gems repository, so we should keep releasing on it. CodePlex: http://codeplex.com Sample site: http://ironpython.codeplex.com CodePlex has turned into a pretty awesome open-source project site. In the past I wouldn''t have wanted to move to CodePlex, but now there defect tracking features seem like the best, and much faster than they use to be. You can use the web interface, the team foundation client, or CodePlex client to look at bugs, which makes it pretty easy to keep on-top of them. Since CodePlex uses TFS underneath to store work-items and bugs, we can use the TFS API to do git commit integration and things like that (though the TFS API isn''t the greatest, it exists =P). But mainly the web interface has voting support, so our tickets can be prioritized by community feedback very easily ... this is definitely the killer feature for me. As I said, I''m leaning heavily towards CodePlex, mainly for the voting support. IronPython uses this very successfully, and it would help prioritize IronRuby''s work, especially post-1.0. So here''s the proposal: 1. Go through open RubyForge bugs, closing bugs as necessary, and narrowing in on a subset to move to CodePlex (jdeville has begun closing bugs). 2. Create http://ironruby.codeplex.com (already reserved, just waiting to set things up and turn it on), and use it for *Issues* and *Releases* only. We will link to http://wiki.github.com/ironruby/ironruby for other developer information, and http://ironruby.net for general users, from the project homepage, and no other wiki pages will be used. 3. Releases will be the only things remaining on RubyForge, as it''s still the standard place for Ruby releases, though any release announcements/blogs will point to the CodePlex release. 4. CodePlex discussion forums will not be used, as they and will remain on RubyForge for now (though we need to resolve the crazy delays soon). Thoughts? ~Jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20090409/f92e0213/attachment.html>