[darcs-devel] darcs and darcs hub (Re: obliterated patches)
Simon Michael
simon at joyful.com
Tue Mar 17 01:20:12 UTC 2015
On 3/15/15 11:44 PM, Ganesh Sittampalam wrote:
> On 16/03/2015 00:07, Ben Franksen wrote:
>
>> While this sounds like a good idea, I have doubts that moving to darcshub
>> would allow us to keep using the tools we do now. Would using darcshub mean
>> we no longer do 'darcs send' but instead use the github model of pull-
>> requests?
Good questions Ben. Back then, the darcs dev process seemed to me to be
not working, I for one had a hard time getting it to work or explaining
it to any new contributor. But things seem to have improved since - I
see at least a few of you regular devs being rather productive with the
current setup. I see the advantages to keeping things email-centric too.
So I'm not trying to convince anyone to change their process. But I'm
always interested in ways to remove friction and increase darcs dev
efficiency.
> We might need to do some custom work there, if we can't do it in a
> generic way. I think the darcsden issue tracker is also a bit more
> primitive than the roundup one, so it might need a bit of general work.
A lot more primitive. It lacks email notification, eg. Of course
sometimes simpler is better! I once was darcs roundup maintainer and
that thing took a lot of care and feeding.
>> I guess this is a chicken-and-egg sort of problem. I fear there is little
>> incentive for an individual developer to use darcshub until we move the
>> repos there committed to it as our development platform (and integrated it
>> into our workflow).
More information about the darcs-devel
mailing list