From gary.weaver at duke.edu Fri Feb 12 17:03:15 2010 From: gary.weaver at duke.edu (Gary Weaver) Date: Fri, 12 Feb 2010 17:03:15 -0500 Subject: [Rails-portlet-bugs] rails-portlet and GitHub Message-ID: <4B75D023.8010409@duke.edu> Hello! Just curious if the rails-portlet project was planning to move its source to GitHub for hosting, or if possibly it is there already and I missed it? Thanks in advance for any information you can provide about this. Best Regards, Gary From mikael.lammentausta at gmail.com Fri Feb 12 17:21:20 2010 From: mikael.lammentausta at gmail.com (Mikael Lammentausta) Date: Sat, 13 Feb 2010 00:21:20 +0200 Subject: [Rails-portlet-bugs] rails-portlet and GitHub In-Reply-To: <4B75D023.8010409@duke.edu> References: <4B75D023.8010409@duke.edu> Message-ID: Gary Weaver kirjoitti 13.2.2010 kello 0.03: > Hello! > > Just curious if the rails-portlet project was planning to move its source to GitHub for hosting, or if possibly it is there already and I missed it? > No. While git is good, Rubyforge is needed for the gem hosting and it would be confusing to use both Github and Rubyforge. > Thanks in advance for any information you can provide about this. > Thanks for the interest into the project. The website is updating soon.. From gary.weaver at duke.edu Mon Feb 15 09:31:04 2010 From: gary.weaver at duke.edu (Gary Weaver) Date: Mon, 15 Feb 2010 09:31:04 -0500 Subject: [Rails-portlet-bugs] rails-portlet and GitHub In-Reply-To: References: <4B75D023.8010409@duke.edu> Message-ID: <4B795AA8.4050007@duke.edu> Mikeal, I didn't know this until recently, but apparently in-general new development in Ruby is moving from Rubyforge to GitHub for project source hosting and Gemcutter for gem hosting. I think it is confusing as well, but I've seen a number of articles like this one: http://www.rubyinside.com/gemcutter-is-the-new-official-default-rubygem-host-2659.html http://tomayko.com/linkings/f1c7ee55c88ffc5060fa3e9b5c9920c8 http://update.gemcutter.org/2009/10/26/transition.html http://www.rubyinside.com/gemcutter-a-fast-and-easy-approach-to-ruby-gem-hosting-2281.html From what I can tell there was a lot of hoopla about it in the beginning and then not a lot of talk since. I'm guessing that a lot of projects will stay in Rubyforge until told to leave, because it is less confusing than telling the users that it moved to 2 places, and because it is more work to have to move them. The reason I asked at all is because we might start looking into the feasibility of adding uPortal support to rails-portlet (if you wouldn't mind), but I was thinking if we were to fork the rails-portlet in GitHub then maybe we wouldn't get in the way as much. However, I'm not even sure whether this would be a good idea or not at this point. I know that so far the rails-portlet has been Liferay-focused, and uPortal isn't supposed to support JSR-286 until v3.3 due by the end of this year (currently they only support JSR-168). As for the reason, basically we have more Rails developers on our team than Java developers and were hoping to start writing portlets in Rails. Over the past week we looked into using other options such as uPortal's WebProxyPortlet and also an iframes-based solution. But, the WebProxyPortlet doesn't have great support for Ajax (it pretty much expects that you do some custom workarounds and I'm told the JSR-168 portlet standard itself limits what can be done). And, developing with iframes requires an expectation in the web app that is iframed to expect that it is running within an iframe and have to control the parent document to do iframe resizing. In addition, if we wanted to link to Rails apps hosted on other servers (since most of our Rails apps aren't hosted on the portal servers), cross-domain iframe communication for resizing is very hackish and looks like it would get in the way of smooth Rails app development. So at this point, we were thinking we should either look into extending rails-portlet and maybe caterpillar for our use (if it makes sense, and allows rapid and unencumbered development of functionality using Rails), or we should look into Grails portlets (but if we do that, I don't know that the Rails developers would be happy), or we should bite the bullet and go back to using Spring Portlet MVC, etc. even though that means that we will have fewer resources available for work. Please let me know what you think! Thanks! Gary Mikael Lammentausta wrote: > Gary Weaver kirjoitti 13.2.2010 kello 0.03: > > >> Hello! >> >> Just curious if the rails-portlet project was planning to move its source to GitHub for hosting, or if possibly it is there already and I missed it? >> >> > > No. While git is good, Rubyforge is needed for the gem hosting and it would be confusing to use both Github and Rubyforge. > > > >> Thanks in advance for any information you can provide about this. >> >> > > Thanks for the interest into the project. The website is updating soon.. > > >