I would like to see Drupal shops start setting up API sites for their modules and start filing issues to solve what comes up when you have lots of code mixed in one site. We need: * Another column to add a concept of project * Integrate with update status to get the right system for each module * Add navigation so users know where they are in the site * How should searching be handled? * Report documentation coverage to the module page on Drupal.org. I'll be working on API module at the DC code sprint as one of my many projects. Find me if you want to help. -Neil On Thu, Mar 5, 2009 at 8:06 AM, Aaron Winborn <winborn@advomatic.com> wrote:
api-contrib.drupal.org would be nice... :D
----- Original Message ----- From: "Gábor Hojtsy" <gabor@hojtsy.hu> To: development@drupal.org Sent: Thursday, March 5, 2009 7:57:50 AM GMT -05:00 US/Canada Eastern Subject: Re: [development] How to port modules? was: Drupal 7 "When it's Ready"
On Thu, Mar 5, 2009 at 10:08 AM, Ivan Sergio Borgonovo <mail@webthatworks.it> wrote:
I was just planning to write my own tool at least to spot changes in signatures.
Already done. In terms of docs, it is implemented on api.drupal.org, in terms of module upgrade mistake checking, it is implemented in coder.module.
Gábor
-- Neil Drumm http://delocalizedham.com