[drupal-devel] CCK: Looking for Volunteers

[Dries Buytaert]

On 25 Apr 2005, at 17:20, Jonathan Chaffer wrote:

> The CCK project is well underway.
> http://drupal.org/cck-status
>
> I'd like to move as rapidly as possible to a point where this project 
> can be considered for the core. This means categorizing the to-do list 
> into the items that must be done for the system to work, and the items 
> that are less vital and can be completed in a later phase. I'll be 
> doing this today. As it stands, the system is more or less 
> operational, with the caveat that the administration interface is not 
> complete. I've been focusing on the user-facing portions of the code 
> instead.
>
> At this point I'd like to issue a call for volunteers. I need people 
> to:
> - Install the code on a development system
> - Review the architecture and suggest alternative methods, as 
> applicable
> - Help me decide what to work on in what order
> - Discuss all of this on IRC or e-mail
> - Optionally, contribute code
> - Optionally, run benchmarks
> - Optionally, mock up the administration interface (Chris?)

Can you setup a site where we can test the current CCK without having 
to install it?  I could make notes as I explore everything in order to 
get a fictive task done.  I'm guessing that, with the administration 
interface not being complete, this might be premature?

I'm asking because I usually start reviewing the interface. If I start 
by looking at the code, I end up knowing too much about the changes 
that the interface and terminology become too obvious.  I will never be 
able to look at the interface like a new user would.

Looking at the TODO I'd focus on trying to mimic the current node 
system and not worry about new features (eg. custom node titles, per 
field permissions, content type duplication, etc).  I would however 
promote 'Implement basic node types as CCK types'.  For each TODO list 
item ask yourself: does the current node system this?  If yes, 
implement it.  If not, don't implement it unless it is a critical 
component.  I'd like to see a _minimalistic_ CCK.  It is the fastest 
path to core and is what we have to evaluate in various setups.

--
Dries Buytaert  ::  http://www.buytaert.net/