Archive for the '2125' Category

Code Sprint

February 23, 2009

We just had three days straight of coding on PyVCAL. Jobias flew in from Alberta to join us in person. There was coffee and fruit. There were donuts and subs and delicious (ginger!) homemade cookies. We went out for tapas.

We got stuff done. We can connect to perforce, subversion and git. We can get basic information out of each repository. Our test infrastructure is in place and our tests will prove our progress soon. We refined out some design errors in our API. We made a big design decision that clarifies the difference between our representation of a version control system and our representation of a specific repository.

Haz made an automated checklist for our progress. Derek will implement a mock version of the API. Shazow connected us with the developer of AnyVCS. SubvertPy will relicense under the LGPL so we can use it.

PyVCAL

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.

Python Version Control Abstraction Layer

January 16, 2009

We have a Google Code project set up under the name “pysync.” It’s a start!