[#25936] [Bug:1.9] [rubygems] $LOAD_PATH includes bin directory — Nobuyoshi Nakada <nobu@...>

Hi,

10 messages 2009/10/05

[#25943] Disabling tainting — Tony Arcieri <tony@...>

Would it make sense to have a flag passed to the interpreter on startup that

16 messages 2009/10/05

[#26028] [Bug #2189] Math.atanh(1) & Math.atanh(-1) should not raise an error — Marc-Andre Lafortune <redmine@...>

Bug #2189: Math.atanh(1) & Math.atanh(-1) should not raise an error

14 messages 2009/10/10

[#26222] [Bug #2250] IO::for_fd() objects' finalization dangerously closes underlying fds — Mike Pomraning <redmine@...>

Bug #2250: IO::for_fd() objects' finalization dangerously closes underlying fds

11 messages 2009/10/22

[#26244] [Bug #2258] Kernel#require inside rb_require() inside rb_protect() inside SysV context fails — Suraj Kurapati <redmine@...>

Bug #2258: Kernel#require inside rb_require() inside rb_protect() inside SysV context fails

24 messages 2009/10/22

[#26361] [Feature #2294] [PATCH] ruby_bind_stack() to embed Ruby in coroutine — Suraj Kurapati <redmine@...>

Feature #2294: [PATCH] ruby_bind_stack() to embed Ruby in coroutine

42 messages 2009/10/27

[#26371] [Bug #2295] segmentation faults — tomer doron <redmine@...>

Bug #2295: segmentation faults

16 messages 2009/10/27

[ruby-core:26351] Re: RubyForge and RubyGems and GemCutter...

From: Luis Lavena <luislavena@...>
Date: 2009-10-27 02:29:51 UTC
List: ruby-core #26351
On Mon, Oct 26, 2009 at 9:27 PM, Richard Kilmer <rich@infoether.com> wrote:
> Hi all -
>

Hello Richard,

> [...]
>
>
> As part of this transition, RubyForge is going to be slowly stood down. t
> won't simply be turned off, of course; we could see it staying in read-only
> mode for quite a while. ut that's where things are headed. he community
> hub functions of RubyForge will not go away. ommunity features that
> RubyForge uniquely provides (or should provide) will be added to the source
> base of the app that GemCutter started with and will be maintained on
> github.
>

As I understand this: files packages and releases will disappear.
Mailing lists will require be moved, etc.

This is what defines "community features", right?

I've commented on that thread that not everything hosted at RubyForge
is a gem, and because of that doesn't fit into "RubyGems" domain.

Also, there are projects that still uses CVS as repository, not to
mention subversion which will need to transition to a DVCS to survive
the read-only mode of RubyForge.

> This is a change; but it's one that we at Ruby Central feel is important.
> e want to provide the community with what it needs. ith services that
> Github, the new SourceForge and Google Code provide we feel that source
> management, mailing lists and bug tracking are being better provided by
> others. e want to focus on community features. e will be developing
> those quickly and that will all hub at RubyGems.org.

But now is not clear what is community features anymore, since GitHub
provides issue tracking, code hosting and collaboration and page
hosting, Google Groups provides mailing lists and rdoc.info can
provide up to date documentation.

What would be the community features be created then?

Please don't take my comment as wrong, but as maintainer of
RubyInstaller and developer of other projects I'm concern that the
segmentation will hurt more than help.

Right now is hard to get contributors and people find the
documentation, downloads and tools, with the switch of RubyForge will
make things even harder.

Regards,
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup駻y

In This Thread

Prev Next