[drupal-devel] CCK: Looking for Volunteers
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?) If you can help with at least the first four, please let me know. -- Jonathan Chaffer Applications Developer, structure:interactive (616) 364-7423 http://www.structureinteractive.com/
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/
On Apr 26, 2005, at 2:06 AM, Dries Buytaert wrote:
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.
This is a very good point. The interface is far from ready for review... it's just a patchwork there to get things bootstrapped. I will set up a test site when there's something to test; right now I'm looking for programmer perspectives until someone steps up with UI ideas/guidelines.
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.
The reason "Implement basic node types as CCK types" has a low priority is that it has a lot of upgrade path implications. Certainly it is already possible to create doppelgängers for most of these node types. That line item means deprecating the old ones, which is more significant. Well, the truly minimalist version would be a system where one can make new story-style node types, but cannot manipulate fields at all. I can strip the system down to this pretty easily, and get to a usable UI for that. The back end would then be in place for extension to more interesting content types. This would hardly scratch the surface of what the system will enable, but may have nice ramifications for, say, the new event module. Opinions, anyone? Is it worth my effort to create such a CCK-light for intermediate review?
Opinions, anyone? Is it worth my effort to create such a CCK-light for intermediate review?
Considering that flexinode does this plus 10x more, I don't think anyone will get so excited by it. Just my .02
True. But IMO we should state: "CCk lite will do 10x less then flexinode, but will do that with 10x better technology and offer 10x better usability." If that is the case -a CCK lite that has very few features, but is a *very* solid foundation for future expansion- I would say: go for it: its a huge improvement for us, and thus will be a huge improvement for the users in future. Ber --
Op 26-apr-05 om 8:06 heeft Dries Buytaert het volgende geschreven:
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?
Jonathan, if you are in need of a website for this purpose please contact me.. I can provide you a solid and free to use website.. Steef.
I'm all about this. I'm really excited about this project and see as something of a holy grail for Drupal. That said, I need some assurances about my involvement in this so that I can maximize my utility for the community and we can get a lot done. I know Dries has said that we should basically create a "CCK-lite" to fast-track it to core, but it concerns me that we might miss a great opportunity here to really pioneer a space that *no other* CMS seems to offer, at least well. I have some big ideas about this and I just want to know... should I expect to be shot down all the time or can I be free to explore new terrain (with the understanding that we have to make incremental changes)? Chris On 4/25/05, Jonathan Chaffer <jchaffer@structureinteractive.com> wrote:
The CCK project is well underway. http://drupal.org/cck-status
- Optionally, mock up the administration interface (Chris?)
If you can help with at least the first four, please let me know. --
Jonathan Chaffer Applications Developer, structure:interactive (616) 364-7423 http://www.structureinteractive.com/
participants (6)
-
Ber Kessels -
Chris Messina -
Dries Buytaert -
Jonathan Chaffer -
Moshe Weitzman -
Stefan Nagtegaal