I was browsing dsource.org for some libraries, that I need and every single
project, that I looked at was either completely abandoned or stuck with the
ancient D1.
Is there at least one sane project in there or is dsource.org an ancient
fossil for museum display?
Sorry for my frustration.

-- 
Bye,
Gor Gyolchanyan.

On Mon, 14 May 2012 10:06:12 -0400, Gor Gyolchanyan <gor.f.gyolchanyan@gmail.com> wrote:

> I was browsing dsource.org for some libraries, that I need and every single
> project, that I looked at was either completely abandoned or stuck with the
> ancient D1.
> Is there at least one sane project in there or is dsource.org an ancient
> fossil for museum display?
> Sorry for my frustration.

There are several.  The problem is finding them amongst all the tumbleweeds.

I plan to move my lib (dcollections) to github as soon as I have some spare time that I wouldn't want to spend doing something else (i.e. low on the priority list).

-Steve

>> ancient D1.

druntime has assembler code, assembler is more ancient than D1, druntime belongs to D2, so D2 is more ancient than D1. Whoops! It's a time paradox!

"Gor Gyolchanyan" <gor.f.gyolchanyan@gmail.com> wrote in message news:mailman.722.1337004471.24740.digitalmars-d@puremagic.com...
>I was browsing dsource.org for some libraries, that I need and every single
> project, that I looked at was either completely abandoned or stuck with
> the
> ancient D1.
> Is there at least one sane project in there or is dsource.org an ancient
> fossil for museum display?
> Sorry for my frustration.
>

I still use it for issue tracking and [zero-traffic] message boards for my stuff:

http://www.dsource.org/projects/semitwist http://www.dsource.org/projects/goldie http://www.dsource.org/projects/haxed

And for that last one, HaxeD, I also use it as the main project homepage.

Plus, Tango and the Orange serialization lib are still on DSource:

http://www.dsource.org/projects/tango http://www.dsource.org/projects/orange

That's just off the top of my head, there's probably other stuff, too.

It would be nice to make a replacement to dsource. There's a fair few problems with it. For one, people prefer hosting their source on Github or Bitbucket or such, it's silly to try and get people to use your own source control hosting instead of just pointing to one of those. Another would be to integrate package manager stuff when one is available. And, most importantly, to prioritize active projects and focus out dead projects automatically.

I was thinking of writing one, but not sure if it's really worth it (and have a couple projects/libraries that need to be written first).

"Kapps" <opantm2+spam@gmail.com> wrote in message news:gvuqhcqczjqmdtpsagrj@forum.dlang.org...
> It would be nice to make a replacement to dsource. There's a fair few problems with it. For one, people prefer hosting their source on Github or Bitbucket or such, it's silly to try and get people to use your own source control hosting instead of just pointing to one of those.

I firmly believe that GitHub/BitBucket/etc-style features need to be standard *protocols*, not features bundled inseparably to project hosting. What the hell is this, 1980 all over again where data is routinely tied inseparably to the software it originated from?

It makes *no* sense for GitHub/BitBucket to be designed so that:

1. Forking/Pull requests/etc are all isolated from other project hosting providers (It's *DISTRIBUTED* fucking version control, for christsakes!), and

2. Interfaces [very, very VERY sloooow and half-broken ones] are tied to the project hosting site/software.

It's like that twitface shit all over again (ie, all that "walled-off sub-internets" bullshit), or those god-awful "web photo-viewer" programs, but with programmers - exactly the people who *should know better*. This is 2012, there's *no* excuse for software design blunders that were already going out of date 30 fucking years ago.

Of course, such anachronisms will never be reverted so long as the "cell and internet generation" is still around...

> Another would be to integrate package manager stuff when one is available. And, most importantly, to prioritize active projects and focus out dead projects automatically.
>

I agree, such things would be nice. There also needs to be proper use of HTTPS for logins/sessions, and automated creation of new projects.

On 5/14/2012 11:06 PM, Gor Gyolchanyan wrote:
> I was browsing dsource.org <http://dsource.org> for some libraries, that
> I need and every single project, that I looked at was either completely
> abandoned or stuck with the ancient D1.
> Is there at least one sane project in there or is dsource.org
> <http://dsource.org> an ancient fossil for museum display?
> Sorry for my frustration.
>
> --
> Bye,
> Gor Gyolchanyan.

Derelict 2 is still alive and kicking there. Plus, the Derelict forum there is where I support both Derelict 2 & 3.

On 2012-05-15 08:32, Mike Parker wrote:

> Derelict 2 is still alive and kicking there. Plus, the Derelict forum
> there is where I support both Derelict 2 & 3.

The forum for Derelict is basically the only one which is active.

-- 
/Jacob Carlborg

Derelict 3 is under development and is on github, so Derelict is not gonna
be on dsource.org for too long,
A plethora of dead projects on dsource.org is a good way to scare away
newcomers, i think.

On Tue, May 15, 2012 at 1:42 PM, Jacob Carlborg <doob@me.com> wrote:

> On 2012-05-15 08:32, Mike Parker wrote:
>
>  Derelict 2 is still alive and kicking there. Plus, the Derelict forum
>> there is where I support both Derelict 2 & 3.
>>
>
> The forum for Derelict is basically the only one which is active.
>
> --
> /Jacob Carlborg
>



-- 
Bye,
Gor Gyolchanyan.

On 15.05.2012 14:04, Gor Gyolchanyan wrote:
> Derelict 3 is under development and is on github, so Derelict is not
> gonna be on dsource.org <http://dsource.org> for too long,
> A plethora of dead projects on dsource.org <http://dsource.org> is a
> good way to scare away newcomers, i think.
>

I think that a global purge can save it. Just archive/move away all of projects not updated for more then 1 year into some sort of Archive section. In case of misfire author can just contact admin and get his project reinstated.


-- 
Dmitry Olshansky