+1, I think this would also help me (and possibly Leon Smith) finishing the polish bytestring builder. I'm pretty sure that having an issue tracker and an overview of the state of the different forks would have avoided the merge hickups of the builder last September. 2013/2/12 Johan Tibell :

On Mon, Feb 11, 2013 at 8:15 PM, Bryan O'Sullivan wrote:

...

Hi, Duncan -

The subject says it all. I'd like to contribute some patches to bytestring, but darcs is a big wall at this point, and the package has no bug tracker. I'd like to move it under http://github.com/haskell, a place that has served several of our core packages well.

I know you're fond of darcs, but it's well established by experience that we'll get many more contributions (both patches and problem reports) on github.

So... pretty pretty please.

+1

_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

On 12 February 2013 18:34, Milan Straka wrote:

Hi all,

...

-----Original message----- From: Bryan O'Sullivan Sent: 11 Feb 2013, 20:15

Hi, Duncan -

The subject says it all. I'd like to contribute some patches to bytestring, but darcs is a big wall at this point, and the package has no bug tracker. I'd like to move it under http://github.com/haskell, a place that has served several of our core packages well.

I know you're fond of darcs, but it's well established by experience that we'll get many more contributions (both patches and problem reports) on github.

+1 here.

For containers, this was a good step -- we got several contributions since moving to github. I believe many people are more familiar with github than darcs.

Isn't this an apples vs oranges comparison though? ;-)

Cheers, Milan

_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com

On Tue, Feb 12, 2013 at 10:34 AM, Milan Straka wrote:

So for me it is github vs darcs at this time.

Of course, one could implement all these features and then it would be github vs. darcs + our_thumping_feature_providing_whatever :)

We're not capable. Github has dozens and dozens of full-time engineers actively working on improving their service and keeping it running. Not only is the user experience so much better than the alternatives, they have a large team dedicated to keeping the infrastructure running. +1 from me for moving as much stuff to Github as possible, which IMO is so awesome that I'm willing to give them money every month twice over (once for myself and once for the Snap Framework organization). G -- Gregory Collins

On Tue, Feb 12, 2013 at 11:12 AM, Ian Lynagh wrote:

Have you got any evidence for that?

Certainly - look at packages such as network, containers, and unordered-containers on github.

On 12/02/13 19:12, Ian Lynagh wrote:

On Mon, Feb 11, 2013 at 08:15:51PM -0800, Bryan O'Sullivan wrote:

...

I know you're fond of darcs, but it's well established by experience that we'll get many more contributions (both patches and problem reports) on github.

Have you got any evidence for that?

I've just skimmed the "RFC: migrating to git" thread on glasgow-haskell-users@ in Jan 2011, and a handful of people gave some sort of indication that they might contribute (or contribute more) if GHC and its libraries switched to git. However, looking for them in the git commit logs (which admittedly isn't necessarily going to find all contributions from them, but it's the best I can easily do) for the almost-2-years since we migrated finds very few patches from them:

To be fair, GHC isn't really using github, we're using Trac. The original assertion was that github would make it easier to contribute to bytestring, which doesn't have a Trac. So no bug tracker or wiki or source code browser, and no way to keep track of contributions. It's a no brainer, if you ask me. Switching to git is a small price to pay (and git does get the job done, like it not). When GHC switched to git it was not primarily to increase the rate of contributions, although we hoped that would happen too. It was to make branching and merging easier, and I think there's ample evidence of that - we used to have approximately zero active branches, and now we have several. Cheers, Simon

On Fri, Feb 15, 2013 at 9:41 AM, Duncan Coutts

wrote:

Yes.

OK - thank you for being so accommodating on this. I know you're not a git fan (nor am I). I'll import the darcs repo and follow up with a URL later.

On Fri, Feb 15, 2013 at 10:13 AM, Johan Tibell wrote:

Will you leave the bug database (if there's anything in there) in Trac or move it over?

If there's anything to move, I'll move them.

Out of curiousity, how has the bytestring-github migration progressed? On Sun, Feb 17, 2013 at 7:45 AM, Ben Millwood wrote:

On Fri, Feb 15, 2013 at 05:41:47PM +0000, Duncan Coutts wrote:

...

On Mon, 2013-02-11 at 20:15 -0800, Bryan O'Sullivan wrote:

...

Hi, Duncan -

The subject says it all. I'd like to contribute some patches to bytestring, but darcs is a big wall at this point, and the package has no bug tracker.

Ah but that's because it has no bugs ;-)

(It actually does have a bug tracker, it's a component in the ghc trac. It's true that it doesn't get used much, but then there have been very few bugs in recent years.)

Crucially, it's not linked from the Hackage page; when I wanted to report a concern with ByteString I e-mailed the addresses in the bug-reports field and received no response.

http://hackage.haskell.org/**package/bytestringhttp://hackage.haskell.org/package/bytestring

It wasn't terribly important, something about hGetSome being added in a minor version, but regardless the impression that I got was that there was nobody paying attention. Moving to Github would fix that but so would just updating the bug-reports field.

(Nevertheless, I'm generally in favour of things moving to github since it reduces the number of user interfaces I have to think about, and reduces how much I am punished for still not working out how to use darcs.)

Ben

______________________________**_________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/**mailman/listinfo/librarieshttp://www.haskell.org/mailman/listinfo/libraries

BTW it would be nice to make this repo official by releasing a point release to hackage which lists the new repo in the cabal file. Bas On 7 March 2013 14:00, Gregory Collins wrote:

We've gotten one pull request for bytestring there, and speaking for myself, the really nice github code review (as well as the fact that I'm subscribed to github.com/haskell notifications) has meant that we've gotten at least one new pair of eyeballs looking at patches.

On Thu, Mar 7, 2013 at 12:19 PM, Leon Smith wrote:

...

Out of curiousity, how has the bytestring-github migration progressed?

On Sun, Feb 17, 2013 at 7:45 AM, Ben Millwood wrote:

...

On Fri, Feb 15, 2013 at 05:41:47PM +0000, Duncan Coutts wrote:

...

On Mon, 2013-02-11 at 20:15 -0800, Bryan O'Sullivan wrote:

...

Hi, Duncan -

The subject says it all. I'd like to contribute some patches to bytestring, but darcs is a big wall at this point, and the package has no bug tracker.

Ah but that's because it has no bugs ;-)

(It actually does have a bug tracker, it's a component in the ghc trac. It's true that it doesn't get used much, but then there have been very few bugs in recent years.)

Crucially, it's not linked from the Hackage page; when I wanted to report a concern with ByteString I e-mailed the addresses in the bug-reports field and received no response.

http://hackage.haskell.org/package/bytestring

It wasn't terribly important, something about hGetSome being added in a minor version, but regardless the impression that I got was that there was nobody paying attention. Moving to Github would fix that but so would just updating the bug-reports field.

(Nevertheless, I'm generally in favour of things moving to github since it reduces the number of user interfaces I have to think about, and reduces how much I am punished for still not working out how to use darcs.)

Ben

_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

-- Gregory Collins

_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries