I guess I'd better weigh in as a darcs developer here (though speaking for myself only). Generally, I like to encourage Darcs users to give Git a chance and explore GitHub so they understand first hand what they might be missing out on if they do not already.
I don't mean to chase people away, of course! Naturally, my encouraging people to use Git conflicts with my desire for Darcs to have a supporting base for the Darcs agenda of building a better version control system. The reason is simply that a feeling that it would irresponsible for me to let my desire override your best interests. If the Git model works better for you, or if Darcs cannot yet scale to your team size, or if GitHub enhances collaboration in a way that a version control system cannot on its own, or if you simply feel that the network effects of everybody else being on GitHub are too important to pass up; by all means, switch.
I wouldn't want people to be using Darcs either out of Haskell brand loyalty (we are way beyond/before that), or out of unfamiliarity with Git. Basically, the kind of users I would want us to have are those that know what they are getting into, that know Darcs both for its simplicity and its flaws.
Finally, about Darcs Bridge:
> One option might be to use wxHaskell as a test case for darcs-bridge, in which case we could allow commits to darcs or Github, but I'll leave it to Eric to decide whether darcs bridge is ready for such a use case.
It's worth considering for the future. I think right now you're best off focusing on one and then maybe re-enabling the bridge later on.
Anyway, by all means, do give it a try! You can always come back later.
PS. Darcs users should know that git add -p somewhat approximates darcs interactive record; often it's all that people miss
Eric Kow <http://erickow.com>