On Jun 10, 2016 10:23 AM, "James Carman" <ja...@carmanconsulting.com> wrote: > > On Fri, Jun 10, 2016 at 1:05 PM Gary Gregory <garydgreg...@gmail.com> wrote: > > > > > I think mailing the list for each component is nice. It seems polite, less > > overbearing and less brute-force; IOW more community oriented. The VOTE is > > nice because it gives folks a few days to voice and record their objection > > (I do not plan on objecting ;-). You could [POLL] the list with a "what > > components should move" message and then have a single [VOTE]. > > > > > If none of us object to the components moving if they see fit, then let's > just say that and avoid the formality. Sure, a nice heads-up from the > component saying "foo is getting ready to move to Git", but they shouldn't > really need to ask permission if we're all okay with it.
I'm sorry to go on about this because I do see Commons as a better place with Git but... > they shouldn't > really need to ask permission if we're > all okay with it. Isn't a VOTE, lazy perhaps or POLL the simplest way to find out "if we're all OK with it"? A LAZY VOTE seems like right tool to me. Gary > > > > This is an important change in workflow and I am not sure our release > > instruction page is 100% up to date for Git, that needs to happen ASAP, > > perhaps _before_ more polling, voting, and migrations take place. > > > > > If it was good enough for all that have moved thus far, then it's good > enough for the future ones, I'd think. > > > > Also as an RM, you'll still need to deal with SVN (the site), so this is > > not a panacea for whatever ill some folks have toward SVN. > > > > > Yep, understood.
