There''s a lot of traffic on this list asking what the options exist for login solutions, file upload solutions, search solutions, etc. Looking over the Wiki is one way to figure out what''s there, and the mailing list is certainly good, but two even better solutions come to mind: 1) RailsForge: Hosts, indexes, and serves add-on solutions. Pros: Mimics SourceForge, RubyForge; centralized repository for this stuff Cons: May break script/plugin model of installation 2) Rails Extensions ''r'' Us Lists extensions by category with a brief description and pointer to source and wiki articles. Allows for user rating and comments. Pros: Allows you to host your own plugins and engines in svn as you''re used to. Provides richer feedback on how good an extension may be. Cons: Each person still has to host his own extension or plugin I don''t know if this has been considered, but I thought I''d toss it out there to see what people think. -- Posted via http://www.ruby-forum.com/.
Nathaniel S. H. Brown
2006-Jan-13 02:44 UTC
[Rails] Anyone Think a RailsForge Is a Good Idea?
This is already handled quite well with RubyForge from what I can tell. A wiser choice would be to extend RubyForge, as it is already an established repository for Ruby/Rails projects and provide hooks for the script/plugin''s to be able to grab a list similar to the same fashion as the gems are being used and listed at the moment. Where all gems are listed on a single URL. This could be used in such a fashion as only providing this cross-integration for the RubyForge projects that have converted to the new Subversion feature just launched. With this new list, we could integrate with web services to provide meta data for each package instead of doing a straight file list. This would definitely increase the speed for searching, in addition to providing inherent caching opportunity on the RubyForge side of things, as well as the script/plugin side. With a script/plugin discover --rubyforge --purge or something of that nature. By default it uses the cache if it is less than (configured time) 1 day old, otherwise it will fetch the most recent list from the server and cache it locally. Thoughts? -Nb ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Nathaniel S. H. Brown http://nshb.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> -----Original Message----- > From: rails-bounces@lists.rubyonrails.org > [mailto:rails-bounces@lists.rubyonrails.org] On Behalf Of Steve Ross > Sent: January 12, 2006 2:08 PM > To: rails@lists.rubyonrails.org > Subject: [Rails] Anyone Think a RailsForge Is a Good Idea? > > There''s a lot of traffic on this list asking what the options > exist for login solutions, file upload solutions, search > solutions, etc. Looking over the Wiki is one way to figure > out what''s there, and the mailing list is certainly good, but > two even better solutions come to mind: > > 1) RailsForge: Hosts, indexes, and serves add-on solutions. > > Pros: Mimics SourceForge, RubyForge; centralized repository > for this stuff > Cons: May break script/plugin model of installation > > 2) Rails Extensions ''r'' Us > > Lists extensions by category with a brief description and > pointer to source and wiki articles. Allows for user rating > and comments. > > Pros: Allows you to host your own plugins and engines in svn > as you''re used to. Provides richer feedback on how good an > extension may be. > Cons: Each person still has to host his own extension or plugin > > I don''t know if this has been considered, but I thought I''d > toss it out there to see what people think. > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails >