Issue tracking and software releases
This group is a place for developers who are interested in how Drupal manages issue tracking, software releases, integration with CVS and other revision control systems, and related areas of functionality. Currently, the project module and casetracker module are the main modules in this space.
Suggestions for improving the d.o issue queue (especially for core)
This page is a place to gather suggestions to improve the drupal.org issue queue (provided by the Project issue tracking module), especially as relates to the core issue queue (by far the largest and most active queue on the site). Please add to the list, or edit items to provide a link to the corresponding issue (feature request, whatever) in the project issue queue.
Note: Requests to add or rename issue status values belong in the drupal.org webmaster issue queue (component == 'Site organization') since those are just admin settings on d.o, not hard-coded into project_issue.module.
Issues to consider for multiple project branches
One part of my GSoC is to add support (of some sort) to VersionControl API for having multiple branches within a project (like a drupal.org project) with different user permissions. The idea is to allow a more DVCS-like workflow, where people can work independently on their own branch and then request an admin user to pull their changes into the master repository. I won't be starting this for a few weeks, but I wanted to get a discussion going about what it should look like.
How to handle Git (or other VCS) allowed branch/tag names?
I'm working on the Git hooks (specifically the 'update' hook right now) and am trying to figure out what sorts of things we would want in a pre-commit (or pre-push, in the case of DVCSs) hook.
What I have now
For now, I have only been checking whether the user attempting to push has an account with the given repository. Combined with the "admin must approve accounts" setting on repositories, this seems good enough to be useful.
Agile Process Planning Poker Module
Planning poker is fun, but if you're on a distributed team how do you play?
There are online tools to do this, but I'd like a simple way to do this in Drupal. Some thoughts:
- If all your issues are stored in Drupal then you could play poker with a node that consists of a nodereference field and a number field and then display the results of those node submissions. This feels like a sledgehammer solution.
Git and Drupal Core workflow
This are just some random ideas about how we could organize drupal core development when/if it would be powered by git.
Every (core) dev can request a personal git repo for drupal development. Here he can push his stuff too, in a special layout.
The branches are named after issues the dev is assigned to. The base for them is the current HEAD (it's left to the dev pulling it in before starting his work!). Then the dev develops his patch. Whenever needed, he pulls the current HEAD in. When he's done with his patch, he uses a special tag name, and the magic starts:
Version Control API and family changes
Overview
This project objective is provide all tools to make it easy a possible drupal.org migration to another Version Control System(aka VCS). By the way, after this, drupal VCS's interaction will be improved, so it provides more flexibility to use it as project managment system for development.
This propose started like a jpetso propose.
Introduction
Some drupal.org developer tools, like the auto-releasing module versions feature, are CVS dependent, which is one of the reasons why drupal project is using CVS now.
Drupal developers are used to recognize others work, so it would be really natural to use a Distribututed Version Control System(aka DVCS) where this concept is implicit(authors and commiters can differ).
On GSoC 2007, Jakob Petsovits developed Version Control API, making it possible to integrate various VCS backends in drupal.
I'm really interested on VCS's, and specially dreaming about commiting to drupal with git(that's why I wrote a guide for maintainers).
Now, there are some details that make Jakob solution not production ready, so I want to take it all to this state.
Version Control API in Drupal 6 and beyond
It's been a long time since I last posted an update on the state of the Version Control API, assuming we disregard short teasers on Planet Drupal. Since this last article, Version Control API nearly died during my attempts to wholly restructure the data model for practically everything involving commits, branches & tags (now unified as "labels") and repository items (= files and directories). Luckily, the story has come to a good end. Well, "end"? Depends.
Senior Drupal Developer, work from anywhere! | D202
D202 is a full service web development shop headquartered in New York. We build beautiful content managed websites with a focus on online communities and social networks. Our team is distributed, with members from across the world. Our portfolio includes sites like www.data.org, www.roushfenway.com, www.jewishideas.org and more, and we're steadily growing.
D202 is looking for a Senior Drupal Developer who will be responsible for engineering features and functionality across multiple Drupal-based projects.
Location: You can live anywhere in the world
Project issue tracking 5.x-2.3 release roadmap
It's time to fix the last of the bugs before we create a new branch and start committing D6 porting patches for project*. That means we need a 5.x-2.3 release of Project issue tracking. Here's the working list of issues to resolve before we can tag/release the next version.
Private client issue tracker using Project + OG modules
This is a site building recipe to build a private issue tracking system. It is still pretty experimental.
cvs contrib procedure
When I gained cvs access, I read the drupal book pages on cvs and also merlinofchaos blog, and polled irc drupal-support.
What I came up with was that there are 2 ways of maintaining releases for contributed modules.
1) Always have the latest code in head, and only release a branch when the new version of drupal comes out. For example when working with module and it is for drupal5 the code is found under HEAD, when the module is upgraded for drupal6, create a branch DRUPAL-5 for the drupal5 module.
Subscriptions vs. Notifications vs. Project issue's mail.inc
Here are some notes that I took while comparing these system, based on a couple hours of poking around and reading code. Anyone feel free to jump in here and correct me on any of this stuff, especially if you've actually /used/ either of these modules before. :P
Parsing .info files for dependencies
Idea came up on this issue (twice) http://drupal.org/node/265450
This information would be useful for a couple of reasons:
Showing dependencies automatically on project pages - some maintainers are kind enough to list them in the description, but what's in the .info file is the best bet.
Showing related modules - modules like token, views, voting API could show dependent modules, modules with dependencies could show other modules with the same dependencies (cck, jQuery UI).
Project module 5.x-1.3 release roadmap
The following issues are all (at the time I'm writing this) either RTBC or CNR
- project* namespace bugs in $node (http://drupal.org/node/98278)
- Code style fixes on 5.x (http://drupal.org/node/324639)
Prevent/limit project_usage abuse (http://drupal.org/node/168009)Make usage statistics visible (http://drupal.org/node/165380)-- Fixed on 2008-10-23project_page_overview() should use {project_release_supported_versions} (http://drupal.org/node/235037)
Project issue 5.x-2.2 release punch list
Note: Project issue 5.x-2.2 has been released. See http://drupal.org/node/249127.
Here's a list of issues to finish up for the upcoming 5.x-2.2 release of project issue:
Russian Translation: http://drupal.org/node/221640-- Fixed 2008-04-13Unaccessible project titles and uris visible: http://drupal.org/node/233785-- Postponed from this release pending further discussion of the implementationAdvanced search only matches an exact phrase: http://drupal.org/node/235097-- Fixed 2008-04-13
Case Tracker, Services and Timesheets
I like <href="/project/casetracker">Case Tracker because it is Drupal. It has some weirdities, but otherwise it's a good baseline and I've extended it pretty easily with cck and views and it's really starting to hum. So I thought it was time to share where I'm at with Case Tracker.
I tried Organic Groups integration with Case Tracker in an earlier trial (my current support site is the 4th and final attempt). I have a client node-type and I use the CCK node reference module to link projects to clients. I then have half a module worth of glue code to improve navigation and usability.
Project* SoC project
Hi everyone!
My name is Markus Schanta, I'm a 21 year old Computer Science student from Vienna, Austria and I would love to participate in the 2008 SoC and do some work on the project* modules.
The project* modules provide project management for Drupal sites. Generally projects are assumed to represent software that has source code, releases, and so on. The project* collection of modules (Project, Project issue tracking, and CVS integration) is the largest set of code running on drupal.org besides Drupal core.
A new theme upload system for Drupal.org
Added to official ideas list at http://drupal.org/node/234735
(draft project outline).
Contributing a theme to Drupal.org currently requires a CVS account. This isn't good for getting new designers and themers involved. So this project would involve creating a UI so that themes can be uploaded via a browser, yet still have a project page and versions. Some developers are likely to want to continue managing their themes directly from CVS of course.
Roadmap for project* views-i-fication
Here's the more detailed plan for views-i-fying the project and project issue tracking modules.
NOTE: As of April 10, 2008, the current timeline for adding views integration is to quickly finish the basic Views 1 functionality for the project issue module in Refactor project issue to use views, commit that code, and then begin the port of project* to Drupal 6. During that port, Views 2 integration will be added and Views 2 will be required for the Drupal 6 version of project*.
March 7, 2008: DrupalCon Code Sprint Plans
dww, hunmonk, and I will be meeting at MIT for the DrupalCon 2008 Boston code sprint around 10:00am today. If any of you are interested in helping out and are in town, feel free to join us-we'd love to have additional help. If you aren't in Boston right now, drop in the #drupal-project channel on irc.freenode.net and talk to us there.
I wanted to write down our current plan (as I understand it) for the day to help us organize assistance better. The items below are those that we want to tackle, roughly in this order.
