Hi,

I'm currently working on porting Phone CCK on Drupal 7 because my site will migrate soon to Drupal 7 and it requires Phone CCK module. I'm interested to be a co-maintainer of your module for D7. Hope to hear from you soon. Thanks.

Regards,
Roland

Comments

thierry_gd’s picture

thierry_gd commented
Status: Active » Closed (fixed)

At the moment, I 'm not taking any co-maintainer.

arpeggio’s picture

arpeggio commented

Hi thierry_gd,

The Phone module I developed is for Drupal 7 with some improvements (like microformat and RDFA support, themeable phone field) and code optimizations. Currently the module doesn't support or pledging to support Drupal 7. Soon Drupal 7 will be released and people who will migrate to Drupal 7 and are using your module will look for a Drupal 7 support. Is it ok if I ask for the reason why you're not taking any co-maintainer?

Thanks,
Roland

kbk’s picture

kbk commented
Status: Closed (fixed) » Active

I would be interested to hear about plans for moving this module to Drupal 7.

Best,
Kyle

thierry_gd’s picture

thierry_gd commented
Status: Active » Closed (fixed)

Will work on the support of Drupal 7 in the next months

hgurol’s picture

hgurol commented
Priority: Normal » Major
Status: Closed (fixed) » Active

Any progress with the d7 upgrade? Its been 6 months since we have heard from you about it.

Thanks...

aren cambre’s picture

aren cambre commented

#902570: Drupal 7 port
#1012880: Is this module supported?

thierry_gd’s picture

thierry_gd commented

Upgrade planned in the next months

BenK’s picture

BenK commented

Subscribing

hgurol’s picture

hgurol commented

any progress with the upgrade?

dmenefee’s picture

dmenefee commented

Also interested in D7 upgrade. We can't use this module if it doesn't have a clear upgrade path.

marcusx’s picture

marcusx commented

Subscribing. Any progress on that? Can someone post a patch who has already worked on a D7 version? @arpeggio is your own module for D7 working? Maybe you can post it in your new sandbox

Thanks!
Marcus

arpeggio’s picture

arpeggio commented

Yes, I do have my own working version of phone field (very different implementation compared to Phone CCK) and I am using it now in my Drupal 7 site. However, I suggest to wait for this Phone CCK module to complete its own D7 version, we will just create a duplicate work if we will post another same phone field project.

hgurol’s picture

hgurol commented

@arpeggio

As you and most of us already knows; this module is pretty much un-maintained.

As for the project owner; his attitude is even a lot worse than the state of this module. (Obviously) He doesnt have the time to support and maintain his modules, yet he is constantly refusing to have a co-maintainer. He doesnt respond to issue queues for months, until some d.o. admin questions whats going on and he feels the threat that he might lose his power. What a pathetic guy...

How come you can suggest to wait this module to complete its own D7 version?!!

Lets do something...

kbk’s picture

kbk commented

31% open-issues and a last commit at 11 weeks ago aren't terrible - check out the data module with its 63% open-issues and a sitting, critical bug report. That said, a lot more people depend on this module. Could someone just port the code and upload it to this queue?

hgurol’s picture

hgurol commented

@kbk
I don't know the story about data module but I do know about this module's story. If you read a couple of issues related to this module's maintenance status and about its D7 port, and match it with the commit history, it will tell you A LOT MORE then the statistics you are referring to...

arpeggio’s picture

arpeggio commented

How come you can suggest to wait this module to complete its own D7 version?!!

We wouldn't want to step on toes of Phone (CCK)'s maintainer.

Lets do something...

Have someone tried to contact thierry_gd? Obviously the maintainer is very busy and by contacting him might get his attention to spare extra time to resolve the issues... or just a hunch maybe someone might want to sponsor the D7 porting of Phone and the maintainer might give his full time to resolve this issue.

i46’s picture

i46 commented

Take it easy guys, give thierry a break, he could be so busy or has many other things to do.

I know we're looking for D7 module migration but Since we're looking for such useful module like this one, I've found another one has D7 support please check the link

http://drupal.org/project/cck_phone

They differ somehow but I would rather use the module I've mentioned because it already has a D7 dev version and by the way the module developer is looking for a co-maintainer if any of you is interested.

hopefully by next month "thierry" will surprise us with a D7 version for this awesome module

cheers

1kenthomas’s picture

1kenthomas commented

This is a key module and obviously needed for D7. Months have been passing, and D7 lags in significant ways due to lack of compatible modules.

Duplication of modules and efforts is often a bad thing. It gets less done, and sows confusion -- which of three phone modules, should I use today, and how am I to know?

As the Drupal project and community grows, it desperately needs to address these issues to remain viable and not appear an amateur project or a management and implementation nightmare for institutions.

In this case, I recommend co-operation or fork. Anyone may be busy, but the community needs to know what's going on, and what's going to happen.

And surely, together, the three major parties in this could get us somewhere very useful. "Merge!"

alan d.’s picture

alan d. commented

Sorry for butting in, I found this thread from an unrelated search.

For those that have done the hard work and ported to Drupal 7, why not post your work into the queue and jump start things.

Some maintainers just do not play well with others and want the "control". As such, posting a completed port as a zip could allow them to cut n' paste the code into "their" version and get the changes committed. They get the credit but you get the module ported, maybe a mention in the readme or project page. I've ported a few modules this way and rewritten another couple of modules, without any access to the project, all done via the issue queues.

End result, better up to date modules and everyone is happy :)

jelenex’s picture

jelenex commented

@Alan D. -- thanks for those wise words :)
Made me realize that this is an opportunity to learn something about Field API coding, so I went and ported this module to Drupal 7, see: #1156850: Port Phone (CCK) to D7
It took me several hours and it was fun..

aren cambre’s picture

aren cambre commented
Status: Active » Fixed

It's pretty clear the maintainer doesn't want a co-maintainer. #1156850: Port Phone (CCK) to D7 addresses the remainder of this issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.