On 5/4/10 10:06 PM, Will Coleda wrote:
My issues with git have primarily been with git-svn; There are things
you can do with git that you cannot do with git-svn. My largest pain
point with git has been here. Now I know. My pain with straight git on
partcl& rakudo has been very much lower, and even that has been
mitigated by the other parrot developers who use git and have been
extremely helpful.
That I believe too. They really are fundamentally different ways of
thinking about development, so it's not entirely surprising the tools
don't mesh well.
I've already asked the OSUOSL folks for help here - they seemed eager
to help us setup a trac/git demo instance; I've got cotto cc'd on the
ticket. (See today's parrotsketch for more on this.)
Excellent, thanks!
ANR:
> > I also get the impression that the git advocates would like an
answer soon,
> > so the end of June may be too long anyway.
This supposes that there is someone to give "them" an answer. Just to
be clear, them is us.
Actually, what I was thinking is that while I'm quite happy to leave it
at "maybe someday", I sense that for some people this is a question with
more urgency. It was an intentionally passive sentence (no agents
implied), not poor writing.
I don't expect this decision to come from any individual on the board,
or even the board as a collective, but to probably come from a
supermajority of the members. This discussion has been framed, for
good or ill, as a "convince allison" discussion for some time. I'm
pretty sure that that is not a healthy direction for us to go in.
We're seeking consensus, which is pretty much the way we always run. We
respect each other's opinions, and that is a very healthy thing.
I count around 5 people advocating for git, a large number of neutrals,
and a dwindling number opposed to the change.
I'm asking for people to raise their objections now, because if it turns
out I'm the *only* one still opposed to the change, I'll yield (since,
as I said in the IRC discussion, most of my objections center around
protecting others in the project). I'll still be a hard-ass about
migration plans, this is not a change to be made lightly.
Allison
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
