Post-SoC progress

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
jpetso's picture

Seems I haven't given up on Version Control API & friends by now, which one could say is a good thing. Due to my rather silent nature, there haven't been as many g.d.o posts as during the Summer of Code (namely, none until now). Nevertheless a good share of remaining issues have been resolved, and missing features have been added. Here's a short rundown of what has been achieved since part 2 of my wrap-up, which was written a month ago.

  • Backends can now provide import/export functionality for accounts in a given repository.
  • Added blocks for "Most active developers" and "Most active projects".
  • The account list is now paged and can be filtered by account status and repository.
  • Small new features that went into cvs.module have been ported to the Version Control API, namely Postgres support and an external cron script that prints out exported accounts.
  • More straightforwardness for having multiple repository registration pledges. (You know, the "I want to maintain a module, theme or translation" and "I'll put it under the GPL" ones.)
  • A small feature that allows branches and tags to be created only in specified directories.
  • RSS output that rocks.
  • More phpdoc friendly API documentation.
  • In the project node integration module, only unpublished projects are now retrieved by default.
  • (Optional) project.module specific code for only allowing project directories if they match a project type (e.g. Modules, Themes, ...) specific regexp.
  • Added a 'message' property for tag operations, as CVS seems to be the only version control system that doesn't support this.
  • The "authorization method" (which specifies if and how you can create new accounts in repositories) is now a per-repository setting instead of a global one. That means it's now finally possible to have a Drupal core repository where only admins can create new accounts, and a contrib repository that requires applications and approvals. In order to keep the code sane, I dropped the site-wide application for access to all repositories, but the admin-only mode should more than make up for this minor loss, imho.
  • A bit more caching, and tons of bug fixes.

Quite a lot, right? Looking through this list, it now finally occurs to me why I spent less time on earning money and more on getting Version Control API up to speed ;-)

Some of these changes also involved changes in the table structure, and while I had released a few beta releases, they didn't include automatic upgrade paths. That's now a thing of the past since I pushed out the first release candidate (5.x-0.9-rc1) yesterday. Starting with this one, there will be update functions in case something changes (which I believe will not be necessary for 5.x anymore).

Way to go

You might remember the list of missing functionality from the SoC wrap-up part 2, and it got a lot smaller. Most of the improvements mentioned above were part of the "Minor bugs and TODO items" bullet point, it seems those were not so minor after all :D ...anyways, those are now done, and the items left are now really the only ones that need to be done still. Right, that's a good thing.

That is... in the Project UI redesign BoF session at DrupalCon, I noticed that project.module itself also contains two (small, but still) features that need to get imported into the project integration module as well. So that leaves five missing features until we'll have covered all the existing version control related functionality. This time, it's really only those five ones (three of them carried over from my last post):

  • Release node integration. (Yeah, you know that one already.) Still not done, still critical, but rumour has it that the notorious dww has agreed to take this on. And that's a great thing, because I can now see a real chance for Version Control API being rolled out on drupal.org.
  • Commit notification mails. You might have noticed that this hasn't been a top priority for me, but as the more important stuff has been taken care of, it seems very probable that this is getting implemented soon now. Done.
  • CVS log parsing. Probably the next thing I'll tackle, assuming I can obtain a decent log file for testing this stuff. Done.
  • Port the "Developers" page from project.module. There might be changes to this page anyways, but for now I find it most important to get a plain port of everything and worry about user interface improvements later on. Together with this feature, I'm pretty sure that this time I'll not get around implementing a commit statistics API function, which is the real meat of this feature. Done, and also the user page integration that I also missed at first.
  • Restrict project creation for users that don't have a version control account. Which will be optional, of course, controlled by some checkbox in the settings. Done. For better usability on project.module, there's also this additional patch.

When all of these are there, we're going to have a 1.0 release. Nice, eh? But wait, it's even getting better!

World news, world news

Goodness #1. Well you probably noticed already, but Derek stated his intentions to deprecate cvs.module starting with 6.x, and having Version Control API plus the CVS backend as the official replacement. Which is teh awesome! w00t! (Also mentioned in the Project* roadmap for Drupal 6.)

Of course, this means that I can't wait too long with the Drupal 6 port of Version Control API & friends, so this is going to be one final considerable effort until we're, er, "officially done". (?) But I believe some more effort in the short term will pay off for drupal.org, Version Control API and everyone else.

Goodness #2. In my continued effort to abuse official sponsoring for my own personal interests, I've been able to attain a university practical where I will implement a Subversion backend plus some other, more high-level (workflow-ng powered) commit subscription stuff. Coached by Univ.Ass. Amin Andjomshoaa. You can also spell him without the "d". So, good stuff is coming!

Best DrupalCon ever (tm)

Yes, I've been to Barcelona too. It's a unique experience somehow, exciting and a bit scary at the same time. (Of course, the excitement clearly prevails.) Lots of interesting talks, a two-part BoF, and most of all a number of new people that I encountered there. You know who you are! The only drawback was that neither Derek nor Andy were able to get there, but you can't have everything. I came home yesterday, and am still trying to get back to normal life :)

...and on a totally unrelated note...

Maybe I should register my blog with Planet Drupal, but as I haven't yet done so and still need to get the news out:

Filefield 2.0 has been released! Whoo! Like, er, ... "Filefield 2 - upload your files with style."
Or something.

...you know, I should really get a life now. See you!

Comments

Subversion time frame

aclight's picture

Goodness #2. In my continued effort to abuse official sponsoring for my own personal interests, I've been able to attain a university practical where I will implement a Subversion backend plus some other, more high-level (workflow-ng powered) commit subscription stuff. Coached by Univ.Ass. Amin Andjomshoaa. You can also spell him without the "d". So, good stuff is coming!

I'm glad to hear you got permission to do this. Do you know roughly what your time frame for this will be? Just curious.

Re: Subversion time frame

jpetso's picture

I was planning to start this week and get it working during October. No idea how time intensive my other courses will be, so I can't really provide a more detailed estimate.

Any update?

aclight's picture

There has been some intense discussion going on in http://drupal.org/node/187019 about switching to SVN. I was wondering if you could update us on the progress you're making on a subversion backend.

Also, when you get it working, count me in as a beta tester.

Subversion

Jax's picture

I really would be willing to test this. Will you also be posting about that effort? Or is there a separate group? Or is there already a new project on d.o for this specifically?

Re: Subversion

jpetso's picture
  1. Cool, a tester! That's very much appreciated, thanks.
  2. Yes, I'll be posting about this effort.
  3. There's the "Issue tracking and software releases" group, everything will at least go there. I'm not sure how much I should still involve the SoC 2007 group as the Summer of Code is already over.
  4. No new project on drupal.org yet. There will be a project when there is code, but I'll be posting about this anyways when this happens.

So, no reason to be afraid of a lack of information :)

Subversion testing...

marquardt's picture

...sign me in as another tester for your subversion integration if it becomes available;-)

Christian.

Issue tracking and software releases

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week