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:
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-
I’d be happy to donate a devjavu account with trac and svn for the
project if you want.
Cheers-
-Ezra
On Nov 8, 2007 12:08 AM, Evan W. [email protected] wrote:
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 
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 8, 2007 12:28 AM, Wayne E. Seguin [email protected] wrote:
On Nov 7, 2007 10:24 PM, Ezra Z. [email protected] wrote:
Evan-
I'd be happy to donate a devjavu account with trac and svn for theproject if you want.
I’d vote for that option.
Almost forgot: we will need to store our ssh keys again I think 
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 Z. [email protected] wrote:
Evan-
I'd be happy to donate a devjavu account with trac and svn for theproject if you want.
I’d vote for that option.
~Wayne
Ezra, would that be the premium devjavu account? We already have more
than 5 committers.
Evan
On Nov 7, 2007 10:31 PM, Evan W. [email protected] 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
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/
~Wayne
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 11/8/07, Wayne E. Seguin [email protected] 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 
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
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
Yeah I have a private ey namespace of devjavu so it would be an
unlimited account.
-Ezra
On Nov 7, 2007 11:22 PM, Evan W. [email protected] 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 [email protected] wrote:
On Nov 7, 2007 11:22 PM, Evan W. [email protected] 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.
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
We could switch back to CVS!
… better no. svn is good for me 
filipe
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 Nov 8, 2007 3:55 AM, Filipe [email protected] wrote:
This devjavu hosting seems to be pretty cool. I think mongrel like
ninjas, so this seems to be a good home for it.filipe
Loosing the Winblowz support would be very bad.
+1 Ninjas!
On Nov 7, 2007 10:30 PM, Luis L. [email protected] wrote:
Almost forgot: we will need to store our ssh keys again I think
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 B.
On Thu, 8 Nov 2007 06:55:52 -0200 (BRST)
Filipe [email protected] 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
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
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs