Jump to page: 1 2
Thread overview
GitHub or dsource?
Jul 07, 2011
Mike James
Jul 07, 2011
Vladimir Panteleev
Jul 07, 2011
Trass3r
Jul 07, 2011
Mirko Pilger
Oct 09, 2011
Bernard Helyer
Jul 08, 2011
Graham Fawcett
Jul 07, 2011
Nick Sabalausky
Jul 20, 2011
David Nadlinger
Jul 21, 2011
Nick Sabalausky
Jul 07, 2011
Walter Bright
July 07, 2011
What's the latest thinking on the best repository for open-source D code... GitHub or dsource?

-=mike=-


July 07, 2011
On Thu, 07 Jul 2011 20:13:53 +0300, Mike James <foo@bar.com> wrote:

> What's the latest thinking on the best repository for open-source D code...
> GitHub or dsource?

Reasons for using GitHub:

* Makes collaboration easier (forking / pull requests)
* Instant project creation
* Better uptime, I think

Reasons for using DSource:

* Your project is published among other D projects on DSource
* Has per-project forums
* Also supports Subversion and Mercurial

-- 
Best regards,
 Vladimir                            mailto:vladimir@thecybershadow.net
July 07, 2011
At least for code hosting you should use github.
July 07, 2011
google code is a good choice if you prefer mercurial.

http://code.google.com/projecthosting/
July 07, 2011
On Thu, 07 Jul 2011 13:13:53 -0400, Mike James <foo@bar.com> wrote:

> What's the latest thinking on the best repository for open-source D code...
> GitHub or dsource?

Github provides much better collaborative source control.  However, dsource provides a bug tracking system linked to your source code.  I guess github does too, but I haven't used it.  I like the Trac interface and features, so I'm more comfortable with dsource.

In all, I think Trac (included in dsource) tips the scales for dsource, but the one thing that really *really* tips the scales in favor of github is that your project isn't lost in a graveyard of abandoned projects.  That aspect of dsource really needs fixing.  If I were to choose a new place for a project, I'd probably choose github, and see how the issue tracker works out.

-Steve
July 07, 2011
"Mike James" <foo@bar.com> wrote in message news:iv4pp8$2td5$1@digitalmars.com...
> What's the latest thinking on the best repository for open-source D code... GitHub or dsource?
>

Unless you want to use mercurial, I'd say GitHub has the advantage of handling forks and collaboration much better. But DSource is better for forums and issue tracking. So I would just use both - code hosting at github and forums/issue-tracking at dsource. Wiki could probably go either way, but I havent really used GitHub's wiki system for anything more than one page, so I don't know.


July 07, 2011
On 7/7/2011 10:13 AM, Mike James wrote:
> What's the latest thinking on the best repository for open-source D code...
> GitHub or dsource?

Whatever the technical merits of one or the other, when the dmd/phobos sources switched to github the level of participation by collaborators on improving the source increased probably by a factor of 10.
July 08, 2011
On Thu, 07 Jul 2011 14:09:12 -0400, Steven Schveighoffer wrote:

> On Thu, 07 Jul 2011 13:13:53 -0400, Mike James <foo@bar.com> wrote:
> 
>> What's the latest thinking on the best repository for open-source D
>> code...
>> GitHub or dsource?
> 
> Github provides much better collaborative source control.  However, dsource provides a bug tracking system linked to your source code.  I guess github does too, but I haven't used it.  I like the Trac interface and features, so I'm more comfortable with dsource.
> 
> In all, I think Trac (included in dsource) tips the scales for dsource, but the one thing that really *really* tips the scales in favor of github is that your project isn't lost in a graveyard of abandoned projects. That aspect of dsource really needs fixing.  If I were to choose a new place for a project, I'd probably choose github, and see how the issue tracker works out.

Trac has a plugin for Git. It would be possible to maintain a local clone on dsource (for example) of a Github-hosted project, and use Trac as your "project frontend." You'd need a cronjob or something to git-pull changes from the Github site.

Graham
July 20, 2011
On 7/7/11 8:19 PM, Nick Sabalausky wrote:
> […]But DSource is better for
> forums and issue tracking. So I would just use both - code hosting at github
> and forums/issue-tracking at dsource.

I doubt that DSource is really the better option for issue tracking. First, GitHub rolled out »Issues 2.0« a few months ago, which now has support for assigning bugs, milestones, etc. I personally haven't used it for a large project yet, but Ruby on Rails switched to it (they previously used Lighthouse), so I suppose it is quite fit for the purpose.

Second, at least for QtD, there is a massive problem with using the DSource Trac instance: Spam. I don't know if this affects other projects as well, and you might not actually notice it that much because we usually hard-delete spammy tickets/changes via the admin panel, but it is definitely annoying.

David
July 21, 2011
"David Nadlinger" <see@klickverbot.at> wrote in message news:j068tj$4fv$1@digitalmars.com...
> On 7/7/11 8:19 PM, Nick Sabalausky wrote:
>> [.]But DSource is better for
>> forums and issue tracking. So I would just use both - code hosting at
>> github
>> and forums/issue-tracking at dsource.
>
> I doubt that DSource is really the better option for issue tracking. First, GitHub rolled out »Issues 2.0« a few months ago, which now has support for assigning bugs, milestones, etc. I personally haven't used it for a large project yet, but Ruby on Rails switched to it (they previously used Lighthouse), so I suppose it is quite fit for the purpose.
>
> Second, at least for QtD, there is a massive problem with using the DSource Trac instance: Spam. I don't know if this affects other projects as well, and you might not actually notice it that much because we usually hard-delete spammy tickets/changes via the admin panel, but it is definitely annoying.
>

I might have been thinking of BitBucket. BitBucket's issue system is horrid.


« First   ‹ Prev
1 2