#138: when we switch from svn.perl.org to trac, consider using git
---------------------------------+------------------------------------------
Reporter: Infinoid | Owner:
Type: feature | Status: closed
Priority: normal | Milestone:
Component: website | Version:
Severity: medium | Resolution: wontfix
Keywords: git svn trac plugin | Lang:
Patch: | Platform:
---------------------------------+------------------------------------------
Comment(by allison):
We certainly won't be moving to git or another alternative source control
system before 1.0. That kind of tool change is too disruptive to developer
productivity. And, the developers that do prefer git can already use it
through git-svn. (perl.org has been running a git mirror or the parrot
repository for months now, but AFAIK no one is using it.)
I imagine we will talk about infrastructure changes periodically, as new
tools become available. So, I'll give my perspective on git for those
future conversations. I don't see git as a good fit for the Parrot
development model. The whole point of git is that there is no centralized
repository. Instead, each developer has their own repository, and they
trade changes back and forth. It was designed for the Linux kernel
development model, where anyone can do work, but ultimately Linus decides
what does or doesn't go into a release. The canonical source for cutting a
release of the kernel is Linus' git repository.
In Parrot, we've taken a completely opposite approach. We've intentionally
worked to remove "single points of failure", where any one part of the
development process can be entirely blocked on one person. (For example we
have multiple release managers in rotation, to share the load, and so any
one of them can take over a particular release if needed.) And, from a
personal perspective, Linus is full-time funded to work on the Linux
kernel and can afford to spend all his time reviewing every change before
it touches the "main" repository. I'm not. I'm quite glad that we have a
whole group of experienced committers who review and apply patches, and
who watch the commit logs and vet changes. That's the Parrot way.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/138#comment:11>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
