> We seem to have some serious friction on this list recently. I think we > should pause for a moment and reflect on our meta-level procedures.
If there was some serious friction, I missed it. All I saw was a quibble about version control for the HCoop packages, which as far as I can tell is extremely tangential to getting the Peer1 migration underway. We can switch version control systems any time. But for now, we've got CVS and for what needs to be done to get Peer1 online we don't need version control very much at all. I think we need to schedule an IRC meeting of all admins, the board, and any interested tech-minded early-adopting users for this (or next weekend at the very latest) to go over in detail what the status is, what's blocking migration, and who will do what when to remedy it, with everyone in the same place. >From what I can tell we are quite close, but I don't want things to bog down into a cycle where we have a few final issues blocking migration that are being gradually added to as fast as they are being fixed. Let's have a total feature freeze pending migration and get this show on the road. -ntk P.S. Any reason why we can't easily automatic migration of users with no domains and roll them out relatively early on? _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
