January 30, 2009

We wanted the name PyVCS for our project. It turned out it was already claimed on Google Code for a version control system written in Python. In a hurry, we picked up the PySync project on Google Code and tied ourselves to it with mailing lists and permissions.

It turns out that PySync is the name of an existing Python project that actually has something to do with syncing, unlike our project. PySync is also taken on PyPI, the Python Package Index.

So, after a quick discussion with Veronica and James, I reserved PyVCAL on PyPI, for Python Version Control Abstraction Layer, which has the advantage of describing what we want to build.


If all goes well, by the end of today, we’ll have broken ground with some prototype git code from James and some throwaway code from Veronica and I. Why prototype throwaway code? Two reasons come to mind: First, we want to have a bit of “just do it” spirit. We’re nearing the end of January, after all. Second, we want to familiarize ourselves with the Google Code code review tool and also a Subversion branch-and-merge workflow. I think of this as an investment that will pay off quickly.


One Response to “PyVCAL”

  1. Rory Says:

    A little “just do it” spirit is always a good thing, especially for Nike’s marketing department. I would have preferred ‘git ‘er done’ though.

Comments are closed.

%d bloggers like this: