Dear Mongrels, The same questions keep coming up over and over on the list, which is ok, but not really optimal. If we added a wiki to the Mongrel site to handle FAQs, what wiki should it be? Required features would be: * Spam protection * Doesn''t look shitty I would probably spring for Trac (and also migrate the bugtracker) if noone else has opinions, but I''m sure some of you do. What do you think? Evan, and the Mongrel Team -- Evan Weaver Cloudburst, LLC
Evan- I''d be happy to donate a devjavu account with trac and svn for the project if you want. Cheers- -Ezra On Nov 7, 2007, at 7:08 PM, Evan Weaver wrote:> Dear Mongrels, > > The same questions keep coming up over and over on the list, which is > ok, but not really optimal. If we added a wiki to the Mongrel site to > handle FAQs, what wiki should it be? > > Required features would be: > > * Spam protection > * Doesn''t look shitty > > I would probably spring for Trac (and also migrate the bugtracker) if > noone else has opinions, but I''m sure some of you do. > > What do you think? > > Evan, and the Mongrel Team > > -- > Evan Weaver > Cloudburst, LLC > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users
On Nov 8, 2007 12:08 AM, Evan Weaver <evan at cloudbur.st> wrote:> Dear Mongrels, > > The same questions keep coming up over and over on the list, which is > ok, but not really optimal. If we added a wiki to the Mongrel site to > handle FAQs, what wiki should it be? > > Required features would be: > > * Spam protection > * Doesn''t look shitty > > I would probably spring for Trac (and also migrate the bugtracker) if > noone else has opinions, but I''m sure some of you do. >Yes, me!> What do you think? >The wiki idea is good. Maybe JuneBug [1] will be up to the task? The Trac idea is good, but we should migrate all the pending tickets in rubyforge and remove the whole section because will fall in the oblivion -- since no one will longer monitor it. Ezra''s suggestion is a good one, also we could get more powerful release planing for the upcoming releases ;-) -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi
On Nov 7, 2007 10:24 PM, Ezra Zygmuntowicz <ezmobius at gmail.com> wrote:> > Evan- > > I''d be happy to donate a devjavu account with trac and svn for the > project if you want.I''d vote for that option. ~Wayne
On Nov 8, 2007 12:28 AM, Wayne E. Seguin <wayneeseguin at gmail.com> wrote:> On Nov 7, 2007 10:24 PM, Ezra Zygmuntowicz <ezmobius at gmail.com> wrote: > > > > Evan- > > > > I''d be happy to donate a devjavu account with trac and svn for the > > project if you want. > > I''d vote for that option. >Almost forgot: we will need to store our ssh keys again I think :-P -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi
Yeah... devjavu would require migrating the SVN too which is not a big problem. I was thinking I would use svnmirror on my own server against Rubyforge to support a Trac. I already run some tracs so that''s not a big deal. But yeah... if we get a new ticket system I will migrate all the remaining open ones. But Trac is only marginally better than GForge when it comes to ticket handling :/ . Evan On Nov 7, 2007 10:26 PM, Luis Lavena <luislavena at gmail.com> wrote:> On Nov 8, 2007 12:08 AM, Evan Weaver <evan at cloudbur.st> wrote: > > Dear Mongrels, > > > > The same questions keep coming up over and over on the list, which is > > ok, but not really optimal. If we added a wiki to the Mongrel site to > > handle FAQs, what wiki should it be? > > > > Required features would be: > > > > * Spam protection > > * Doesn''t look shitty > > > > I would probably spring for Trac (and also migrate the bugtracker) if > > noone else has opinions, but I''m sure some of you do. > > > > Yes, me! > > > What do you think? > > > > The wiki idea is good. Maybe JuneBug [1] will be up to the task? > > The Trac idea is good, but we should migrate all the pending tickets > in rubyforge and remove the whole section because will fall in the > oblivion -- since no one will longer monitor it. > > Ezra''s suggestion is a good one, also we could get more powerful > release planing for the upcoming releases ;-) > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-- Evan Weaver Cloudburst, LLC
Ezra, would that be the premium devjavu account? We already have more than 5 committers. Evan On Nov 7, 2007 10:31 PM, Evan Weaver <evan at cloudbur.st> wrote:> Yeah... devjavu would require migrating the SVN too which is not a big > problem. I was thinking I would use svnmirror on my own server against > Rubyforge to support a Trac. I already run some tracs so that''s not a > big deal. > > But yeah... if we get a new ticket system I will migrate all the > remaining open ones. But Trac is only marginally better than GForge > when it comes to ticket handling :/ . > > Evan > > > On Nov 7, 2007 10:26 PM, Luis Lavena <luislavena at gmail.com> wrote: > > On Nov 8, 2007 12:08 AM, Evan Weaver <evan at cloudbur.st> wrote: > > > Dear Mongrels, > > > > > > The same questions keep coming up over and over on the list, which is > > > ok, but not really optimal. If we added a wiki to the Mongrel site to > > > handle FAQs, what wiki should it be? > > > > > > Required features would be: > > > > > > * Spam protection > > > * Doesn''t look shitty > > > > > > I would probably spring for Trac (and also migrate the bugtracker) if > > > noone else has opinions, but I''m sure some of you do. > > > > > > > Yes, me! > > > > > What do you think? > > > > > > > The wiki idea is good. Maybe JuneBug [1] will be up to the task? > > > > The Trac idea is good, but we should migrate all the pending tickets > > in rubyforge and remove the whole section because will fall in the > > oblivion -- since no one will longer monitor it. > > > > Ezra''s suggestion is a good one, also we could get more powerful > > release planing for the upcoming releases ;-) > > > > -- > > Luis Lavena > > Multimedia systems > > - > > Leaders are made, they are not born. They are made by hard effort, > > which is the price which all of us must pay to achieve any goal that > > is worthwhile. > > Vince Lombardi > > > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > > > > -- > Evan Weaver > Cloudburst, LLC >-- Evan Weaver Cloudburst, LLC
On Nov 7, 2007 10:31 PM, Evan Weaver <evan at cloudbur.st> wrote:> Yeah... devjavu would require migrating the SVN too which is not a big > problem. I was thinking I would use svnmirror on my own server against > Rubyforge to support a Trac. I already run some tracs so that''s not a > big deal. > > But yeah... if we get a new ticket system I will migrate all the > remaining open ones. But Trac is only marginally better than GForge > when it comes to ticket handling :/ . > > EvanAnother option would be to setup a redmine instance. You can point it at an SVN repo and specify how you''d like to associate items in the commit logs. It has issue tracking, wiki, etc. http://redmine.org/ ~Wayne
On 11/8/07, Wayne E. Seguin <wayneeseguin at gmail.com> wrote:> > Another option would be to setup a redmine instance. You can point it > at an SVN repo and specify how you''d like to associate items in the > commit logs. It has issue tracking, wiki, etc. http://redmine.org/ >RedMine is too overkill and too "corporate-or-enterprisey" for the task. Agile sounds better :-) -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi
Yeah I have a private ey namespace of devjavu so it would be an unlimited account. -Ezra On Nov 7, 2007, at 7:32 PM, Evan Weaver wrote:> Ezra, would that be the premium devjavu account? We already have more > than 5 committers. > > Evan > > On Nov 7, 2007 10:31 PM, Evan Weaver <evan at cloudbur.st> wrote: >> Yeah... devjavu would require migrating the SVN too which is not a >> big >> problem. I was thinking I would use svnmirror on my own server >> against >> Rubyforge to support a Trac. I already run some tracs so that''s not a >> big deal. >> >> But yeah... if we get a new ticket system I will migrate all the >> remaining open ones. But Trac is only marginally better than GForge >> when it comes to ticket handling :/ . >> >> Evan >> >> >> On Nov 7, 2007 10:26 PM, Luis Lavena <luislavena at gmail.com> wrote: >>> On Nov 8, 2007 12:08 AM, Evan Weaver <evan at cloudbur.st> wrote: >>>> Dear Mongrels, >>>> >>>> The same questions keep coming up over and over on the list, >>>> which is >>>> ok, but not really optimal. If we added a wiki to the Mongrel >>>> site to >>>> handle FAQs, what wiki should it be? >>>> >>>> Required features would be: >>>> >>>> * Spam protection >>>> * Doesn''t look shitty >>>> >>>> I would probably spring for Trac (and also migrate the >>>> bugtracker) if >>>> noone else has opinions, but I''m sure some of you do. >>>> >>> >>> Yes, me! >>> >>>> What do you think? >>>> >>> >>> The wiki idea is good. Maybe JuneBug [1] will be up to the task? >>> >>> The Trac idea is good, but we should migrate all the pending tickets >>> in rubyforge and remove the whole section because will fall in the >>> oblivion -- since no one will longer monitor it. >>> >>> Ezra''s suggestion is a good one, also we could get more powerful >>> release planing for the upcoming releases ;-) >>> >>> -- >>> Luis Lavena >>> Multimedia systems >>> - >>> Leaders are made, they are not born. They are made by hard effort, >>> which is the price which all of us must pay to achieve any goal that >>> is worthwhile. >>> Vince Lombardi >>> >>> _______________________________________________ >>> Mongrel-users mailing list >>> Mongrel-users at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/mongrel-users >>> >> >> >> >> -- >> Evan Weaver >> Cloudburst, LLC >> > > > > -- > Evan Weaver > Cloudburst, LLC > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users
Sounds good. Let''s wait for a few more suggestions and then later this week you can hook us up. What about the SVN mirror business? Would we just close the Rubyforge one? Evan On Nov 7, 2007 10:46 PM, Ezra Zygmuntowicz <ezmobius at gmail.com> wrote:> > Yeah I have a private ey namespace of devjavu so it would be an > unlimited account. > > -Ezra > > > > On Nov 7, 2007, at 7:32 PM, Evan Weaver wrote: > > > Ezra, would that be the premium devjavu account? We already have more > > than 5 committers. > > > > Evan > > > > On Nov 7, 2007 10:31 PM, Evan Weaver <evan at cloudbur.st> wrote: > >> Yeah... devjavu would require migrating the SVN too which is not a > >> big > >> problem. I was thinking I would use svnmirror on my own server > >> against > >> Rubyforge to support a Trac. I already run some tracs so that''s not a > >> big deal. > >> > >> But yeah... if we get a new ticket system I will migrate all the > >> remaining open ones. But Trac is only marginally better than GForge > >> when it comes to ticket handling :/ . > >> > >> Evan > >> > >> > >> On Nov 7, 2007 10:26 PM, Luis Lavena <luislavena at gmail.com> wrote: > >>> On Nov 8, 2007 12:08 AM, Evan Weaver <evan at cloudbur.st> wrote: > >>>> Dear Mongrels, > >>>> > >>>> The same questions keep coming up over and over on the list, > >>>> which is > >>>> ok, but not really optimal. If we added a wiki to the Mongrel > >>>> site to > >>>> handle FAQs, what wiki should it be? > >>>> > >>>> Required features would be: > >>>> > >>>> * Spam protection > >>>> * Doesn''t look shitty > >>>> > >>>> I would probably spring for Trac (and also migrate the > >>>> bugtracker) if > >>>> noone else has opinions, but I''m sure some of you do. > >>>> > >>> > >>> Yes, me! > >>> > >>>> What do you think? > >>>> > >>> > >>> The wiki idea is good. Maybe JuneBug [1] will be up to the task? > >>> > >>> The Trac idea is good, but we should migrate all the pending tickets > >>> in rubyforge and remove the whole section because will fall in the > >>> oblivion -- since no one will longer monitor it. > >>> > >>> Ezra''s suggestion is a good one, also we could get more powerful > >>> release planing for the upcoming releases ;-) > >>> > >>> -- > >>> Luis Lavena > >>> Multimedia systems > >>> - > >>> Leaders are made, they are not born. They are made by hard effort, > >>> which is the price which all of us must pay to achieve any goal that > >>> is worthwhile. > >>> Vince Lombardi > >>> > >>> _______________________________________________ > >>> Mongrel-users mailing list > >>> Mongrel-users at rubyforge.org > >>> http://rubyforge.org/mailman/listinfo/mongrel-users > >>> > >> > >> > >> > >> -- > >> Evan Weaver > >> Cloudburst, LLC > >> > > > > > > > > -- > > Evan Weaver > > Cloudburst, LLC > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-- Evan Weaver Cloudburst, LLC
On Nov 7, 2007 11:22 PM, Evan Weaver <evan at cloudbur.st> wrote:> Sounds good. Let''s wait for a few more suggestions and then later this > week you can hook us up. > > What about the SVN mirror business? Would we just close the Rubyforge one?Or... switch to git. ~Wayne
On Nov 8, 2007 1:37 AM, Wayne E. Seguin <wayneeseguin at gmail.com> wrote:> On Nov 7, 2007 11:22 PM, Evan Weaver <evan at cloudbur.st> wrote: > > Sounds good. Let''s wait for a few more suggestions and then later this > > week you can hook us up. > > > > What about the SVN mirror business? Would we just close the Rubyforge one? > > Or... switch to git. >No, please no. Another OSS project going to git... and mingw-git not production ready (and without support for git-svn or any other). That will mean the end of my support from Windows side... and I wouldn''t like do that. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi
I also don''t want git. Evan On Nov 7, 2007 11:40 PM, Luis Lavena <luislavena at gmail.com> wrote:> On Nov 8, 2007 1:37 AM, Wayne E. Seguin <wayneeseguin at gmail.com> wrote: > > On Nov 7, 2007 11:22 PM, Evan Weaver <evan at cloudbur.st> wrote: > > > Sounds good. Let''s wait for a few more suggestions and then later this > > > week you can hook us up. > > > > > > What about the SVN mirror business? Would we just close the Rubyforge one? > > > > Or... switch to git. > > > > No, please no. Another OSS project going to git... and mingw-git not > production ready (and without support for git-svn or any other). > > That will mean the end of my support from Windows side... and I > wouldn''t like do that. > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > _______________________________________________ > > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-- Evan Weaver Cloudburst, LLC
We could switch back to CVS! ... better no. svn is good for me :D filipe On Wed, 7 Nov 2007, Evan Weaver wrote:> I also don''t want git. > > Evan > > On Nov 7, 2007 11:40 PM, Luis Lavena <luislavena at gmail.com> wrote: >> On Nov 8, 2007 1:37 AM, Wayne E. Seguin <wayneeseguin at gmail.com> wrote: >>> On Nov 7, 2007 11:22 PM, Evan Weaver <evan at cloudbur.st> wrote: >>>> Sounds good. Let''s wait for a few more suggestions and then later this >>>> week you can hook us up. >>>> >>>> What about the SVN mirror business? Would we just close the Rubyforge one? >>> >>> Or... switch to git. >>> >> >> No, please no. Another OSS project going to git... and mingw-git not >> production ready (and without support for git-svn or any other). >> >> That will mean the end of my support from Windows side... and I >> wouldn''t like do that. >> >> -- >> Luis Lavena >> Multimedia systems >> - >> Leaders are made, they are not born. They are made by hard effort, >> which is the price which all of us must pay to achieve any goal that >> is worthwhile. >> Vince Lombardi >> _______________________________________________ >> >> Mongrel-users mailing list >> Mongrel-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/mongrel-users >> > > > > -- > Evan Weaver > Cloudburst, LLC > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >
This devjavu hosting seems to be pretty cool. I think mongrel like ninjas, so this seems to be a good home for it. filipe On Wed, 7 Nov 2007, Evan Weaver wrote:> Sounds good. Let''s wait for a few more suggestions and then later this > week you can hook us up. > > What about the SVN mirror business? Would we just close the Rubyforge one? > > Evan > > On Nov 7, 2007 10:46 PM, Ezra Zygmuntowicz <ezmobius at gmail.com> wrote: >> >> Yeah I have a private ey namespace of devjavu so it would be an >> unlimited account. >> >> -Ezra >> >> >> >> On Nov 7, 2007, at 7:32 PM, Evan Weaver wrote: >> >>> Ezra, would that be the premium devjavu account? We already have more >>> than 5 committers. >>> >>> Evan >>> >>> On Nov 7, 2007 10:31 PM, Evan Weaver <evan at cloudbur.st> wrote: >>>> Yeah... devjavu would require migrating the SVN too which is not a >>>> big >>>> problem. I was thinking I would use svnmirror on my own server >>>> against >>>> Rubyforge to support a Trac. I already run some tracs so that''s not a >>>> big deal. >>>> >>>> But yeah... if we get a new ticket system I will migrate all the >>>> remaining open ones. But Trac is only marginally better than GForge >>>> when it comes to ticket handling :/ . >>>> >>>> Evan >>>> >>>> >>>> On Nov 7, 2007 10:26 PM, Luis Lavena <luislavena at gmail.com> wrote: >>>>> On Nov 8, 2007 12:08 AM, Evan Weaver <evan at cloudbur.st> wrote: >>>>>> Dear Mongrels, >>>>>> >>>>>> The same questions keep coming up over and over on the list, >>>>>> which is >>>>>> ok, but not really optimal. If we added a wiki to the Mongrel >>>>>> site to >>>>>> handle FAQs, what wiki should it be? >>>>>> >>>>>> Required features would be: >>>>>> >>>>>> * Spam protection >>>>>> * Doesn''t look shitty >>>>>> >>>>>> I would probably spring for Trac (and also migrate the >>>>>> bugtracker) if >>>>>> noone else has opinions, but I''m sure some of you do. >>>>>> >>>>> >>>>> Yes, me! >>>>> >>>>>> What do you think? >>>>>> >>>>> >>>>> The wiki idea is good. Maybe JuneBug [1] will be up to the task? >>>>> >>>>> The Trac idea is good, but we should migrate all the pending tickets >>>>> in rubyforge and remove the whole section because will fall in the >>>>> oblivion -- since no one will longer monitor it. >>>>> >>>>> Ezra''s suggestion is a good one, also we could get more powerful >>>>> release planing for the upcoming releases ;-) >>>>> >>>>> -- >>>>> Luis Lavena >>>>> Multimedia systems >>>>> - >>>>> Leaders are made, they are not born. They are made by hard effort, >>>>> which is the price which all of us must pay to achieve any goal that >>>>> is worthwhile. >>>>> Vince Lombardi >>>>> >>>>> _______________________________________________ >>>>> Mongrel-users mailing list >>>>> Mongrel-users at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/mongrel-users >>>>> >>>> >>>> >>>> >>>> -- >>>> Evan Weaver >>>> Cloudburst, LLC >>>> >>> >>> >>> >>> -- >>> Evan Weaver >>> Cloudburst, LLC >>> _______________________________________________ >>> Mongrel-users mailing list >>> Mongrel-users at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/mongrel-users >> >> _______________________________________________ >> Mongrel-users mailing list >> Mongrel-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/mongrel-users >> > > > > -- > Evan Weaver > Cloudburst, LLC > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >
On Nov 7, 2007 10:30 PM, Luis Lavena <luislavena at gmail.com> wrote:> On Nov 8, 2007 12:28 AM, Wayne E. Seguin <wayneeseguin at gmail.com> wrote: > > On Nov 7, 2007 10:24 PM, Ezra Zygmuntowicz <ezmobius at gmail.com> wrote: > > > > > > Evan- > > > > > > I''d be happy to donate a devjavu account with trac and svn for the > > > project if you want. > > > > I''d vote for that option. > > > > Almost forgot: we will need to store our ssh keys again I think :-P >I''ve gotten a ton out of using mongrel, so I''d be happy to give back by donating hosting as well. I''ve got an unlimited account with TextDrive, so if Ezra would like to move any part (or all) of this off his server, I''d do it too. Let me know how I can help. -- Sean Brown
On Nov 8, 2007 3:55 AM, Filipe <filipe at icewall.org> wrote:> > This devjavu hosting seems to be pretty cool. I think mongrel like > ninjas, so this seems to be a good home for it. > > filipeLoosing the Winblowz support would be very bad. +1 Ninjas!
Zed A. Shaw
2007-Nov-10 05:19 UTC
[Mongrel] Please Don''t Move Hosting (Was: Mongrel wiki?)
On Thu, 8 Nov 2007 06:55:52 -0200 (BRST) Filipe <filipe at icewall.org> wrote:> > This devjavu hosting seems to be pretty cool. I think mongrel like > ninjas, so this seems to be a good home for it.Hey guys, while I didn''t catch that you were considering moving the mongrel project off rubyforge onto devjavu, and I tend to stay out of it, I''m gonna ask that you not move svn and bug tracking off rubyforge. Being an open source project means that it''s important to host it on a system that isn''t owned by a for-profit corporation, doesn''t require paying money to maintain, and allows others to snag the code should anyone on the project try to hijack it. Rubyforge allows this since it''s run by Ruby Central, allows access to anyone for anything, and should any one person try to hijack I can ask Rich and friends to take the keys back. Not that I think you guys would do that, but stranger things have happened in open source. So I''m asking to not move the hosting, and instead just start up a wiki or FAQ system of some sort somewhere else and reference from the main site. Remember, this isn''t your project or mine, it''s the community''s. Otherwise, rock on, you''re all kicking serious ass. -- Zed A. Shaw - Hate: http://savingtheinternetwithhate.com/ - Good: http://www.zedshaw.com/ - Evil: http://yearofevil.com/
Michael Graff
2007-Nov-10 18:39 UTC
[Mongrel] Please Don''t Move Hosting (Was: Mongrel wiki?)
I can probably arrange for hosting for any open source large-scale project, either via a virtual host or a login on a server. The rules: we don''t charge you, so you can''t use banner/text paid advertising on your site. Free means free all around. Donation request links are fine, just don''t be obnoxious. More or less unlimited bandwidth, too. Whee! --Michael
Evan Weaver
2007-Nov-10 21:25 UTC
[Mongrel] Please Don''t Move Hosting (Was: Mongrel wiki?)
I don''t think we''re hurting for hosting; I think Zed is concerned about the host being controlled by only one person ultimately. Although, my opinion is, whoever controls Rubyforge controls the gems, so Rubyforge will always be the home of "real" mongrel. But it would be nice to leave the SVN in place. Evan On Nov 10, 2007 1:39 PM, Michael Graff <skan.gryphon at gmail.com> wrote:> I can probably arrange for hosting for any open source large-scale > project, either via a virtual host or a login on a server. The rules: > we don''t charge you, so you can''t use banner/text paid advertising on > your site. Free means free all around. Donation request links are > fine, just don''t be obnoxious. > > More or less unlimited bandwidth, too. Whee! > > --Michael > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-- Evan Weaver Cloudburst, LLC
Zed A. Shaw
2007-Nov-10 22:00 UTC
[Mongrel] Please Don''t Move Hosting (Was: Mongrel wiki?)
On Sat, 10 Nov 2007 16:25:44 -0500 "Evan Weaver" <evan at cloudbur.st> wrote:> I don''t think we''re hurting for hosting; I think Zed is concerned > about the host being controlled by only one person ultimately. > > Although, my opinion is, whoever controls Rubyforge controls the gems, > so Rubyforge will always be the home of "real" mongrel. But it would > be nice to leave the SVN in place.Yes, it''s not about the cost of hosting at all. Since I wrote Mongrel I can pretty much ask for hosting and people will donate it. The "whoever" that controls rubyforge are people from rubycentral who have a huge stake in not being evil(ish) and I know most of them and trust them. Nobody really knows the dude at devjavu. For example, let''s say ruby central eats it and rubyforge bites the dust. I can call David Black, Rich Kilmer, and others directly and beg them to get me a dump of everything that was there. Rich and crew probably would warn everyone things were going to get bad and ask for help or offer to give people their projects. They''d probably get money and donations from everyone who benefits from the service. Rubyforge also has a vested interest in remaining neutral in any debates or disputes about project ownership. Now, let''s take devjavu. I''ve never met the guy who runs it, don''t know much about him, and he charges money for the service. If his business implodes then he actually could consider the code sitting on his computers an asset. I don''t know how he runs his systems, where they''re hosted, what he does with them, how secure he is, or even if he''s a legit business. I''m sure he''s not an evil guy, but he''s not on the same trust level as rubyforge by a long stretch. I also don''t know if he''d remain neutral in any project ownership disputes. Another example was lighthouse. I trust Rick like crazy, but I don''t trust whether Rick''s business will be around in 1 year. If I hosted the Mongrel bug list there, I''m sure I could get the data back from Rick, but how would I resurrect the bug tracker? I wouldn''t have the source code as that''s an asset. I wouldn''t have the expertise or time to set it up. If Rick''s business went down then we''d lose a huge service. Additionally, rubyforge is a community effort. Rather than move mongrel hosting off, why not talk with the maintainers and offer to pitch in some work to get the services you want setup and running smooth. I''m sure they''d appreciate it and if not you can just setup the one wiki you want on another machine. -- Zed A. Shaw - Hate: http://savingtheinternetwithhate.com/ - Good: http://www.zedshaw.com/ - Evil: http://yearofevil.com/
Luis Lavena
2007-Nov-10 22:12 UTC
[Mongrel] Please Don''t Move Hosting (Was: Mongrel wiki?)
On Nov 10, 2007 7:00 PM, Zed A. Shaw <zedshaw at zedshaw.com> wrote:> > Yes, it''s not about the cost of hosting at all. Since I wrote Mongrel I can pretty much ask for hosting and people will donate it. The "whoever" that controls rubyforge are people from rubycentral who have a huge stake in not being evil(ish) and I know most of them and trust them. Nobody really knows the dude at devjavu. ><snipping long and worthy comments from Zed> I must have to agree with Zed on this. Even that Ezra is offering their "slice" of devjavu and even Rick offers lighthouse power to the ticket system, we would be "bounded" to external and core services that we don''t control -- and the end of the day, we will thank <your-deity-of-preference> for making these service being alive one more day. On this topic I''m a bit of paranoic: even I mostly trust open-source hosting services (like googlecode or even rubyforge) I keep the original repository locally and push changes to the mirror. So I have always a full copy of the repository, but not only because can work offline, but mostly they cannot guarantee me they will be 100% available (after all, is a free service). Maybe we are going too far from the purpose? We already have some infrastructure in place, maybe we could enhance or RFE to get more of the solution. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi
Evan Weaver
2007-Nov-10 22:59 UTC
[Mongrel] Please Don''t Move Hosting (Was: Mongrel wiki?)
Rubyforge/GForge has some rudimentary wiki service installed in new project web hosts, but I don''t know anyone who uses it. Spam protection is the main thing that concerns me about using that default. Plus it''s ugly. Maybe we could cook up an external service that pushed changes across to the Rubyforge web host. That sounds like some work, though. Evan On Nov 10, 2007 5:12 PM, Luis Lavena <luislavena at gmail.com> wrote:> On Nov 10, 2007 7:00 PM, Zed A. Shaw <zedshaw at zedshaw.com> wrote: > > > > Yes, it''s not about the cost of hosting at all. Since I wrote Mongrel I can pretty much ask for hosting and people will donate it. The "whoever" that controls rubyforge are people from rubycentral who have a huge stake in not being evil(ish) and I know most of them and trust them. Nobody really knows the dude at devjavu. > > > <snipping long and worthy comments from Zed> > > I must have to agree with Zed on this. > > Even that Ezra is offering their "slice" of devjavu and even Rick > offers lighthouse power to the ticket system, we would be "bounded" to > external and core services that we don''t control -- and the end of the > day, we will thank <your-deity-of-preference> for making these service > being alive one more day. > > On this topic I''m a bit of paranoic: even I mostly trust open-source > hosting services (like googlecode or even rubyforge) I keep the > original repository locally and push changes to the mirror. > > So I have always a full copy of the repository, but not only because > can work offline, but mostly they cannot guarantee me they will be > 100% available (after all, is a free service). > > Maybe we are going too far from the purpose? We already have some > infrastructure in place, maybe we could enhance or RFE to get more of > the solution. > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-- Evan Weaver Cloudburst, LLC
Andrei Maxim
2007-Nov-10 23:49 UTC
[Mongrel] Please Don''t Move Hosting (Was: Mongrel wiki?)
On 11/11/07, Evan Weaver <evan at cloudbur.st> wrote:> > Maybe we could cook up an external service that pushed changes across > to the Rubyforge web host. That sounds like some work, though. >... or set up a read-only SVN repository on the other site that mirrors the one on Rubyforge if we''d like to use Wiki and SVN integration. Pulling should be easier, I think. -- Andrei Maxim http://andreimaxim.ro -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20071111/10ae1e3a/attachment-0001.html
Zed A. Shaw
2007-Nov-10 23:54 UTC
[Mongrel] Please Don''t Move Hosting (Was: Mongrel wiki?)
On Sat, 10 Nov 2007 17:59:06 -0500 "Evan Weaver" <evan at cloudbur.st> wrote:> Rubyforge/GForge has some rudimentary wiki service installed in new > project web hosts, but I don''t know anyone who uses it. Spam > protection is the main thing that concerns me about using that > default. Plus it''s ugly. > > Maybe we could cook up an external service that pushed changes across > to the Rubyforge web host. That sounds like some work, though.Now I got no problem with hooking up something like a wiki or anything rubyforge don''t support somewhere else. That''s just pragmatic necessity. But, I''d talk with the rubyforge folks. It''s worth a shot. -- Zed A. Shaw - Hate: http://savingtheinternetwithhate.com/ - Good: http://www.zedshaw.com/ - Evil: http://yearofevil.com/
Evan Weaver
2007-Nov-11 03:03 UTC
[Mongrel] Please Don''t Move Hosting (Was: Mongrel wiki?)
Yeah pulling is no problem; svnsync is made for just this purpose. Evan On Nov 10, 2007 6:49 PM, Andrei Maxim <andrei at andreimaxim.ro> wrote:> > On 11/11/07, Evan Weaver <evan at cloudbur.st> wrote: > > > > > Maybe we could cook up an external service that pushed changes across > > to the Rubyforge web host. That sounds like some work, though. > > > > > ... or set up a read-only SVN repository on the other site that mirrors the > one on Rubyforge if we''d like to use Wiki and SVN integration. Pulling > should be easier, I think. > > -- > Andrei Maxim > http://andreimaxim.ro > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-- Evan Weaver Cloudburst, LLC