[development] CCK status?

[Darrel O'Pry]

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.