------art_33805_18639873.1151192641705
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Folks,

I started this thread... please let me take a shot at summarizing people's
points:

   - Rewriting GForge in Ruby for RubyForge is a waste of time and a
   religious persuit because it splits the development of an existing, well
   supported product in two and that's not good for a bunch of well stated
   reasons.
   - There are things that are less than optimal about GForge, it'd be
   nice if these things could be added:
      - Publishing gems is not as streamlined as it could be
      - It'd be nice to have source browsing
      - Certain other features from Trac would be nice
      - (my personal comments) It's clunky to run surveys and there's
      no built-in chat and there's no iCal integration (e.g., when did
      we release stuff, what's upcoming to do on my calendar, etc.)
      - Put your code where your mouth is (I plan to, but I wanted to
   understand from others what the upsides and downsides were)
   - Did I miss something?

So...

Please send me a list of things people want to add to RubyForge.  I'll do
the following:

   - Aggregate the input items so there's a list of what people want
   - Look at the GForge schema to see how hard it would be to put a Rails
   app (or a series of Rails apps) on the 'side' of GForge so that if we add,
   for example, Ruport based reporting or Trac-style issue tracking, how hard
   the actual process of integrating that with a GForge single sign-on would be
   and also what the additional burden would be on Tom and Richard.
   - On Friday, I'll publish the "top 10 list" and the "how hard it would
   be to add these features beside GForge" lists.

So, you all, please send me your wish list publicly or privately.

Thanks,

David

On 6/24/06, Julian 'Julik' Tarkhanov <listbox / julik.nl> wrote:
>
>
> On 24-jun-2006, at 23:06, Ryan Davis wrote:
> >
> > Or you could quit being a drama-queen and be a bit more realistic.
> It was not my intention to insult anybody. A very odd response, if I
> might say so.
>
> > Not counting login it takes exactly 1 form to create a new release
> > including uploading the file.
> Shall the file be one. If they are many though... (and a normal
> release usually has at least two)
> >
> >> Currently there are like 3 different Rake tasks for publishing
> >> gems (all of them UNOFFICIAL) and I had problems with all of these.
> >
> > That has little (if anything) to do with rubyforge itself.
>
> Uhm... Let's say that I don't agree but as you are in the mood of
> name calling I will just shut up.
>
> --
> Julian 'Julik' Tarkhanov
> please send all personal mail to
> me at julik.nl
>
>
>
>


-- 
--------
David Pollak's Ruby Playground
http://dppruby.com

------art_33805_18639873.1151192641705--