Does anyone know where things stand with regard to further CCK development these days? It seems that JonBob has gone pretty quiet in recent months (in the issue queue at least). Thanks, Ray
Ray Zimmerman wrote:
Does anyone know where things stand with regard to further CCK development these days? It seems that JonBob has gone pretty quiet in recent months (in the issue queue at least).
chx, webchick, Jaza, Eaton, mathieu, and myself have all taken turns working on this. (And of course, all the people that have helped out previously.) JonBob has made commits to the contributions version as recently as 3 days ago. http://drupal.org/node/62340 is what needs review. -- Neil Drumm http://delocalizedham.com/
On Aug 3, 2006, at 10:45 PM, Neil Drumm wrote:
Ray Zimmerman wrote:
Does anyone know where things stand with regard to further CCK development these days? It seems that JonBob has gone pretty quiet in recent months (in the issue queue at least).
chx, webchick, Jaza, Eaton, mathieu, and myself have all taken turns working on this. (And of course, all the people that have helped out previously.) JonBob has made commits to the contributions version as recently as 3 days ago.
http://drupal.org/node/62340 is what needs review.
Right, I was aware of all of this. I was referring more to the development of the contrib module for 4.7 (things like [1], [2], [3], [4]). It's just that over the past several months I've noticed a number of threads where it appeared folks were waiting for JonBob's blessing to move forward and I never saw his response. Maybe he's communicated with them on IRC or something. Anyway, sounds like the attention at the moment may be more focused on getting core ready for CCK than on enhancing the 4.7 contrib module. Just trying to get a handle on where things are headed ... Ray [1] http://drupal.org/node/60384 [2] http://drupal.org/node/69472 [3] http://drupal.org/node/50062 [4] http://drupal.org/node/60756
Ray Zimmerman wrote:
On Aug 3, 2006, at 10:45 PM, Neil Drumm wrote:
Ray Zimmerman wrote:
Does anyone know where things stand with regard to further CCK development these days? It seems that JonBob has gone pretty quiet in recent months (in the issue queue at least).
chx, webchick, Jaza, Eaton, mathieu, and myself have all taken turns working on this. (And of course, all the people that have helped out previously.) JonBob has made commits to the contributions version as recently as 3 days ago.
http://drupal.org/node/62340 is what needs review.
Right, I was aware of all of this. I was referring more to the development of the contrib module for 4.7 (things like [1], [2], [3], [4]). It's just that over the past several months I've noticed a number of threads where it appeared folks were waiting for JonBob's blessing to move forward and I never saw his response. Maybe he's communicated with them on IRC or something.
I am kind of in the same boat. For a project of mine I need to decide whether to go with cck or to write my own node module. I would prefer to go with cck as I see a bigger benefit to Drupal as a whole, but if development does not seem to be viable, I might have to ditch the plan. Cheers, Gerhard
I'm currently working on a node module where I used CCK to hold the data. The advantages have been significantly less coding, no schema to upgrade, and the ability to modify my node type from the GUI (a very nice feature during development). The disadvantages have been a lack of import/export ability (more on this below), and a lack of call backs (e.g. during the view stage). I've been working on a set of patches to add an import/export api to CCK. It has been difficult because all the logic for saving/updating types and fields is tightly coupled to the form submission code. I would be happy to share these patches with others if they think they can help. Otherwise, I'll just keep plugging away. -Mark
I am kind of in the same boat. For a project of mine I need to decide whether to go with cck or to write my own node module.
I would prefer to go with cck as I see a bigger benefit to Drupal as a whole, but if development does not seem to be viable, I might have to ditch the plan.
Cheers, Gerhard
On 8/4/06, Mark Fredrickson <mark.m.fredrickson@gmail.com> wrote:
I've been working on a set of patches to add an import/export api to CCK. It has been difficult because all the logic for saving/updating types and fields is tightly coupled to the form submission code. I would be happy to share these patches with others if they think they can help. Otherwise, I'll just keep plugging away.
Speak to jaza (jeremy epstein) about this. he is working on a import / export api for drupal (summer of code project). I was actually just speaking to him about cck import / export today =)
On Aug 4, 2006, at 6:50 AM, Gerhard Killesreiter wrote:
Ray Zimmerman wrote:
On Aug 3, 2006, at 10:45 PM, Neil Drumm wrote:
Ray Zimmerman wrote:
Does anyone know where things stand with regard to further CCK development these days? It seems that JonBob has gone pretty quiet in recent months (in the issue queue at least).
chx, webchick, Jaza, Eaton, mathieu, and myself have all taken turns working on this. (And of course, all the people that have helped out previously.) JonBob has made commits to the contributions version as recently as 3 days ago.
http://drupal.org/node/62340 is what needs review. Right, I was aware of all of this. I was referring more to the development of the contrib module for 4.7 (things like [1], [2], [3], [4]). It's just that over the past several months I've noticed a number of threads where it appeared folks were waiting for JonBob's blessing to move forward and I never saw his response. Maybe he's communicated with them on IRC or something.
I am kind of in the same boat. For a project of mine I need to decide whether to go with cck or to write my own node module.
I would prefer to go with cck as I see a bigger benefit to Drupal as a whole, but if development does not seem to be viable, I might have to ditch the plan.
I think a lot of people would be very interested to know if CCK is not viable/tanking/going by the wayside, etc. It is being pretty heavily promoted on drupal.org and elsewhere (me included) for the obvious advantages it offers. But if there are serious roadblocks to its future development, I see a situation developing where a lot of people might have upgrade nightmares or rapidly obsolete applications. I'm very happy to be labeled an alarmist if there is no issue, but reading Gerhard's comments here, I can't help but be concerned. evan
On 4-Aug-06, at 9:33 AM, Evan Leeson wrote:
On Aug 4, 2006, at 6:50 AM, Gerhard Killesreiter wrote:
Ray Zimmerman wrote:
On Aug 3, 2006, at 10:45 PM, Neil Drumm wrote:
Ray Zimmerman wrote:
Does anyone know where things stand with regard to further CCK development these days? It seems that JonBob has gone pretty quiet in recent months (in the issue queue at least).
chx, webchick, Jaza, Eaton, mathieu, and myself have all taken turns working on this. (And of course, all the people that have helped out previously.) JonBob has made commits to the contributions version as recently as 3 days ago.
http://drupal.org/node/62340 is what needs review. Right, I was aware of all of this. I was referring more to the development of the contrib module for 4.7 (things like [1], [2], [3], [4]). It's just that over the past several months I've noticed a number of threads where it appeared folks were waiting for JonBob's blessing to move forward and I never saw his response. Maybe he's communicated with them on IRC or something.
I am kind of in the same boat. For a project of mine I need to decide whether to go with cck or to write my own node module.
I would prefer to go with cck as I see a bigger benefit to Drupal as a whole, but if development does not seem to be viable, I might have to ditch the plan.
I think a lot of people would be very interested to know if CCK is not viable/tanking/going by the wayside, etc. It is being pretty heavily promoted on drupal.org and elsewhere (me included) for the obvious advantages it offers. But if there are serious roadblocks to its future development, I see a situation developing where a lot of people might have upgrade nightmares or rapidly obsolete applications.
I'm very happy to be labeled an alarmist if there is no issue, but reading Gerhard's comments here, I can't help but be concerned.
As with EVERYTHING on Drupal.org....do your homework. Look at commits, look at issue queue, etc. Oh, and of course, for all those "panicking" -- you are, of course, contributing in some way to CCK? Documentation, tutorials, development, funding? If anyone has specific items they want to see, a bounty might be appropriate. If JonBob doesn't have the time to be the one gateway through which all development passes, I suggest speaking with him about nominating a second maintainer. -- Boris
On Aug 4, 2006, at 9:44 AM, Boris Mann wrote:
Oh, and of course, for all those "panicking" -- you are, of course, contributing in some way to CCK?
yes. a few months ago i had a burst of interest in CCK, and dove in to start making it better. i submitted a modest # of patches to the issue queue. at the time, i asked JonBob if he'd be willing to grant me commit access so i could get my fixes in and help review other patches, and he graciously declined my offer. ;) most of my patches are still languishing there, uncommitted. :(
If JonBob doesn't have the time to be the one gateway through which all development passes, I suggest speaking with him about nominating a second maintainer.
+1. i'm in gerhard's situation. i have a huge new project on the horizon that i was planning to rely on CCK for. given the time frame, it'll probably have to be 4.7, not waiting until 4.8/5.0. if i have to maintain my own working version of CCK just for this, that'd be a huge pain in the ass and a real shame for everyone. if killes and me are both poised to abandon the (otherwise obvious) choice of using CCK for these new projects, something is clearly wrong. sadly, both of us are awfully busy ;) so i don't think either of us are in a position to be a full-time 4.7 CCK maintainer. but, i'm pretty sure we could help out if given the chance. ;) -derek (dww)
On Aug 4, 2006, at 3:17 PM, Derek Wright wrote:
On Aug 4, 2006, at 9:44 AM, Boris Mann wrote:
Oh, and of course, for all those "panicking" -- you are, of course, contributing in some way to CCK?
yes. a few months ago i had a burst of interest in CCK, and dove in to start making it better. i submitted a modest # of patches to the issue queue. at the time, i asked JonBob if he'd be willing to grant me commit access so i could get my fixes in and help review other patches, and he graciously declined my offer. ;) most of my patches are still languishing there, uncommitted. :(
If JonBob doesn't have the time to be the one gateway through which all development passes, I suggest speaking with him about nominating a second maintainer.
+1. i'm in gerhard's situation. i have a huge new project on the horizon that i was planning to rely on CCK for. given the time frame, it'll probably have to be 4.7, not waiting until 4.8/5.0. if i have to maintain my own working version of CCK just for this, that'd be a huge pain in the ass and a real shame for everyone.
if killes and me are both poised to abandon the (otherwise obvious) choice of using CCK for these new projects, something is clearly wrong. sadly, both of us are awfully busy ;) so i don't think either of us are in a position to be a full-time 4.7 CCK maintainer. but, i'm pretty sure we could help out if given the chance. ;)
This is exactly the kind of thing that prompted my initial e-mail. I just poked JonBob with an e-mail about this thread. Hopefully, we'll hear something straight from the horse's mouth soon. Ray
On Fri, 2006-08-04 at 12:17 -0700, Derek Wright wrote:
On Aug 4, 2006, at 9:44 AM, Boris Mann wrote:
Oh, and of course, for all those "panicking" -- you are, of course, contributing in some way to CCK?
yes. a few months ago i had a burst of interest in CCK, and dove in to start making it better. i submitted a modest # of patches to the issue queue. at the time, i asked JonBob if he'd be willing to grant me commit access so i could get my fixes in and help review other patches, and he graciously declined my offer. ;) most of my patches are still languishing there, uncommitted. :(
If JonBob doesn't have the time to be the one gateway through which all development passes, I suggest speaking with him about nominating a second maintainer.
+1. i'm in gerhard's situation. i have a huge new project on the horizon that i was planning to rely on CCK for. given the time frame, it'll probably have to be 4.7, not waiting until 4.8/5.0. if i have to maintain my own working version of CCK just for this, that'd be a huge pain in the ass and a real shame for everyone.
if killes and me are both poised to abandon the (otherwise obvious) choice of using CCK for these new projects, something is clearly wrong. sadly, both of us are awfully busy ;) so i don't think either of us are in a position to be a full-time 4.7 CCK maintainer. but, i'm pretty sure we could help out if given the chance. ;)
-derek (dww)
JonBob is around for reviewing and commiting I hear.... so bug him ;)... I depend on cck for several sites and will be doing more work on it as time goes by. If JonBob wants to hold commit rights there is nothing stopping the people using cck + drupal 4.7 from using an alternative repository to keep features up to date. I maintain my own bzr tree of cck, and merge in CVS regularly. CCK does work with 4.7, but as with everything requires elbow grease. :) I'm more concerned about the development that will be required to make CCK compatible with 4.8/5.0 after the pave the way for cck patch hit core.
On 04 Aug 2006, at 15:50, Gerhard Killesreiter wrote:
Right, I was aware of all of this. I was referring more to the development of the contrib module for 4.7 (things like [1], [2], [3], [4]). It's just that over the past several months I've noticed a number of threads where it appeared folks were waiting for JonBob's blessing to move forward and I never saw his response. Maybe he's communicated with them on IRC or something.
I am kind of in the same boat. For a project of mine I need to decide whether to go with cck or to write my own node module. I would prefer to go with cck as I see a bigger benefit to Drupal as a whole, but if development does not seem to be viable, I might have to ditch the plan.
It is a fact that every day more and more people are relying on CCK, or want to rely on the CCK but don't feel comfortable to. That's exactly why I'd like to move CCK to Drupal core: http://buytaert.net/ custom-content-types. One step at a time, using incremental patches. :-) If more people would be willing to help with this, we could have a functional CCK in Drupal core. It would be stable, reliable and future proof. It would make live easier for many people. Ask yourself: do you want to be able to use and rely on CCK in the next Drupal version? If the answer is 'yes', and if the CCK is valuable to you, help get it into core. It doesn't get any more complex than that. Next, ask yourself: what is it worth to me to have CCK in Drupal core? What would be the impact on my work and projects, and at the Drupal community at large? What would be the indirect impact on my work if this helps Drupal grow? Is it worth a couple hours of your time? -- Dries Buytaert :: http://www.buytaert.net/
On 5 Aug 2006, at 11:36, Dries Buytaert wrote:
If more people would be willing to help with this, we could have a functional CCK in Drupal core. It would be stable, reliable and future proof. It would make live easier for many people.
Ask yourself: do you want to be able to use and rely on CCK in the next Drupal version? If the answer is 'yes', and if the CCK is valuable to you, help get it into core. It doesn't get any more complex than that.
Next, ask yourself: what is it worth to me to have CCK in Drupal core? What would be the impact on my work and projects, and at the Drupal community at large? What would be the indirect impact on my work if this helps Drupal grow? Is it worth a couple hours of your time?
-- Dries Buytaert :: http://www.buytaert.net/
CCK would be very valuable to me, but I don't have the coding skills to contribute. Is money an issue for the developers? It's the only way I can contribute other than with testing. What would it take to get this in core? Mark http://drupal.org/user/62940
Op zondag 6 augustus 2006 12:35, schreef Mark Hope:
CCK would be very valuable to me, but I don't have the coding skills to contribute. Is money an issue for the developers? It's the only way I can contribute other than with testing.
Don't underestimate the need for testing. It is currently the only way to make something get into core. If there is a particular issue you want to see solved, the best idea is to hire a drupal developer drupal.org/services, who can develop or solve that issue.
What would it take to get this in core?
Testing. Starting with the first step towards CCK: http://drupal.org/node/62340
Hi, all. It goes without saying that I feel horrible about my lack of involvement with the project of late. I know that people have been depending on my work, and I haven't been able to provide it. I've been a bit confused about the direction of my professional life, and it has had a big impact on my motivation to do programming in my spare time. But that's a separate discussion... I've resolved to give up some control in many areas of my life for my own health, and this is one of them. I asked tavon to do maintenance on the 4.7 branch of CCK, which helps a bit; I want to expand that with more committers now. At the moment I want people who are willing to review and commit bug fixes and hold off on the feature requests. Let me know if you're interested. I'm thrilled that features of the CCK project are making their way into core. Thanks to Karoly and Neil especially in making this happen. There is now a big conflict between the contributed system and the core functions, though, that I need help in reconciling. It's not even possible to update a HEAD install right now if CCK is installed due to DB conflicts. I don't know where to go on this one. Finally, a few bigger features I've been working on that there is no viable code for yet: Configurable titles. We need a way for any combination of fields to be used as the title of a node. This helps to address the node reference problem of non-unique node titles, as well. Mostly I can't come up with a decent UI for this. Validators. There is a pending patch for adding regexes to validate input. I'd really much rather get a general system in place, so that validation methods can be added on to a field flexibly, similar to how widgets are associated with fields now. This would allow us to add, say, an e-mail address validator to a text field, obviating the need for a whole separate e-mail address field type. Formatters. In a similar vein, I'd like the presentation of data to be decoupled from the field type modules, so that they can be defined flexibly in additional modules. This is the other half of the e-mail address example; allowing for the address to be automatically linked. When this is implemented it can also be exposed to Views as the list of ways to display a field. Tests. We are toying with test-driven development at my workplace, and I've been working with tavon on applying this to the CCK development. The biggest hurdle with accomplishing this with simpletest is getting the database back to a known state during the setup/teardown. I'm interested in any views on this topic. Thanks for everyone's patience with me. I consider you all to be great friends, and apologize once again for being out of touch. -- Jonathan Chaffer Algorithm Alchemist, Structure Interactive (616) 364-7423 http://www.structureinteractive.com/
On Mon, 2006-08-07 at 05:22 -0400, Jonathan Chaffer wrote:
Hi, all.
It goes without saying that I feel horrible about my lack of involvement with the project of late. I know that people have been depending on my work, and I haven't been able to provide it. I've been a bit confused about the direction of my professional life, and it has had a big impact on my motivation to do programming in my spare time. But that's a separate discussion...
I've resolved to give up some control in many areas of my life for my own health, and this is one of them. I asked tavon to do maintenance on the 4.7 branch of CCK, which helps a bit; I want to expand that with more committers now. At the moment I want people who are willing to review and commit bug fixes and hold off on the feature requests. Let me know if you're interested.
I'm thrilled that features of the CCK project are making their way into core. Thanks to Karoly and Neil especially in making this happen. There is now a big conflict between the contributed system and the core functions, though, that I need help in reconciling. It's not even possible to update a HEAD install right now if CCK is installed due to DB conflicts. I don't know where to go on this one.
Finally, a few bigger features I've been working on that there is no viable code for yet:
Configurable titles. We need a way for any combination of fields to be used as the title of a node. This helps to address the node reference problem of non-unique node titles, as well. Mostly I can't come up with a decent UI for this.
Validators. There is a pending patch for adding regexes to validate input. I'd really much rather get a general system in place, so that validation methods can be added on to a field flexibly, similar to how widgets are associated with fields now. This would allow us to add, say, an e-mail address validator to a text field, obviating the need for a whole separate e-mail address field type.
Formatters. In a similar vein, I'd like the presentation of data to be decoupled from the field type modules, so that they can be defined flexibly in additional modules. This is the other half of the e-mail address example; allowing for the address to be automatically linked. When this is implemented it can also be exposed to Views as the list of ways to display a field.
Tests. We are toying with test-driven development at my workplace, and I've been working with tavon on applying this to the CCK development. The biggest hurdle with accomplishing this with simpletest is getting the database back to a known state during the setup/teardown. I'm interested in any views on this topic.
Thanks for everyone's patience with me. I consider you all to be great friends, and apologize once again for being out of touch.
Hurray JonBob. If you can set the roadmap. I'm still happy to help. You have the most solid overall vision of what cck should be at this juncture. I can help with any part you need. CCK is central to much of what I want to do with drupal. Good documentation for where the development should go, and setting up tasks on the project will help me focus my energy where need be. My filesystem work should be coming to a near close this weekend so I will have cycles open to work on starting next week. .darrel.
participants (13)
-
Adrian Rossouw -
Boris Mann -
Bèr Kessels -
Darrel O'Pry -
Derek Wright -
Dries Buytaert -
Evan Leeson -
Gerhard Killesreiter -
Jonathan Chaffer -
Mark Fredrickson -
Mark Hope -
Neil Drumm -
Ray Zimmerman