On Mon, Jun 4, 2012 at 2:38 PM, Rich Freeman <firstname.lastname@example.org> wrote:
> On Mon, Jun 4, 2012 at 2:48 AM, Dirkjan Ochtman <email@example.com> wrote:
>> IMO we should try to be cutting down barriers from the git migration,
>> not throwing up more. The process has taken long enough already; the
>> desire to control everything about the migration is part of why it's
>> taken so long.
> Fair enough.
> We should also be asking ourselves what happens if something goes
> really wrong and there are no commits for a whole two days. I think
> the answer is, not much. As long as there are a few devs who can tend
> to security issues or whatever I don't see it as an issue if we have
> the odd glitch.
That's what I was thinking, too. :)
> We do need to get the docs up so that we're at least somewhat
> harmonized on conventions (authors vs committers, and so on). Let's
> not burn the first person to make a mistake at the stake either...
Yeah, some initial tutorial of how to get going would probably help a
lot. For everything else, there's IRC (and hopefully most of what's
discussed there would soon find it's way into the HOWTO doc).