Anyone interested in maintaining link.module, please contact quicksketch via Drupal.org private message. There are many other commitments more important than this module I developed in the 4.7 days and haven't ever used since. This module is not yet unsupported, but without a new maintainer it may become soon. Developers with a moderate amount of experience preferred.

Comments

Manamarak’s picture

Manamarak commented

quicksketch:

I am interested in taking on this module, though I do not have a huge amount of experience, being fairly new to coding PHP.

In fact, I was hoping to work as a co-maintainer initially, I will take over the work, but wouldn't mind being able to draw on your expertise.

I have thought of some features I would like to add to the module, most notably the ability to set the title attribute of the link, as opposed to the clickable text. http://drupal.org/node/335281

My long term goal, however, would be to keep the module as simple as possible, as I believe that this is one of it's vital strengths: it adds crucial functionality whilst managing to be simple to use and implement.

I would like to hear your thoughts.

Eddie van der Walt
Manamarak

JoeMcGuire’s picture

JoeMcGuire commented

I'd be very happy to get involved with maintaining the Module.

I'm a full time PHP developer, where 90% of my time is spent on Drupal projects. I'm keen to get involved with contributing back. I have a couple of my own modules already in the planning. One of which is an FAQ field type for CCK, so I'm familiar with the the API.

I have a few ideas on how the module can go forward which I'll aim to post in the issue queue over the next couple of weeks.

Joe

quicksketch’s picture

quicksketch
he/him
commented

Thanks guys! Indeed the best way to get started is to start posting issues/patches to the Link queue. That'll help me get a gauge on your goals/approaches to the module. I've also already granted CVS access to mrfelton, who's helping out in the queue also.

quicksketch’s picture

quicksketch
he/him
commented

This module is now officially abandoned. :(

Please contact me if interested in becoming the owner of this project.

faunapolis’s picture

faunapolis commented

Sorry to re-bring the issue to live,. But, if this module is to die, is there any other CCK modules that you think could replace this module? Thanks in advance

quicksketch’s picture

quicksketch
he/him
commented

I don't think this module needs to die, and no I don't know of a replacement. It just needs a new maintainer.

coreyp_1’s picture

coreyp_1 commented

This is frustrating on so many levels. I just launched two projects that use Link heavily, and now Update Status is screaming about it.

Let me say, first of all, that I am not mad at you, quickscketch. You created a very useful module, and your initiative and support are gratefully acknowledged. I'm aggravated that I can't figure out how to help out more. I am a competent coder, but CVS completely eludes me... probably because I work primarily on Windows. I've worked on Drupal recreationally (and now professionally) for 3.5 years, but my efforts in helping with the Drupal project have been hamstrung by this.

I have created themes that integrated with the color module, created custom modules (potentially useful to the community), and done a lot of debugging... but I don't know how to translate any of it into something useful for CVS. I've followed the handbook stuff, and it looks like it was written by a Linux programmer who thinks Windows should run like Linux (no offense). It doesn't... it's a different paradigm.

I wish there was a screen cast of some sort that shows from start to finish how to work with CVS and patches with Drupal... A Hello World of sorts. This is what I can do: I can download code from Drupal, fix a bug, and explain what I did to fix it. In a pinch, I can even create a patch file, but they either don't apply cleanly because I left some obscure flag out of the command line, or I created the patch against a dev version that got updated the day before, but not before I created the patch.

And about testing patches... I can look at the patch file and see what code has been changed, but how does someone go about applying one?

Maybe I'm not setting up a testing environment correctly. Maybe I'm making this too difficult. But either way, I don't know what to do to fix it!!!!!

Sorry. I had to vent, and it didn't help that my clients got mad at me for using an "unsupported module that should be disabled" (paraphrased from Update Status) when the module is the best and only solution for the site.

I would like to help, but until someone can understand a Linux-oriented procedure and explain it to a Windows-experienced programmer, I'll have to sit on the sidelines with my hands tied.

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Fixed

First, I apologize that Update Status went crazy and started yelling. I didn't know that it would do that if a module was assigned to the Abandoned user.

As for helping and wanting a straight demo, there is a screencast linked in the first few paragraphs of http://drupal.org/patch/create. You can watch it here: http://drupal.org/node/128209. It's quite good, by fellow Lullabot Addison Berry. Note that while she uses Mac OS X (yes a *nix variant), you can use all the exact same commands if you install Cygwin (http://www.cygwin.com/setup.exe).

Of course if you want to apply a patch you can look over http://drupal.org/patch/create. Yes it's unfortunate that the documentation is "heavy", but we are programmers, and with a few hours of effort I'm sure you'll find it's not nearly so difficult as it sounds. Being a maintainer, I apply and create dozens of patches a day.

In Better News, We Have a New Maintainer!

John Fiala (jcfiala) of PingVision took the job. Thanks John! You're a hero to many people.

boobaa’s picture

boobaa
he/him
commented
Version: master » 5.x-2.5
Status: Fixed » Active

I suppose one of John's first tasks should be visiting http://drupal.org/node/74971/edit/releases and mark some (?) releases as supported to stop update status' yell.

gomez_in_the_south’s picture

gomez_in_the_south commented

I'd just like to add my thanks to quicksketch for his work on the link module until now. Also thanks to John for taking over support of the module.

preetinder’s picture

preetinder commented

Thanks quicksketch and John...

keep up the good work.

mrfelton’s picture

mrfelton commented

Good on you John. I was just too busy right now to take on the task myself but I will try and help you out as much as I can.

markus_petrux’s picture

markus_petrux commented

Just wanted to say thanks to everyone involved in this module.

Junro’s picture

Junro commented

Supporting the new mainteners!

Hi, just want to say I'm using this module with thousands nodes... it's a very unique little module and I don't know if there are others modules who could do the same thing.

jcfiala’s picture

jcfiala commented
Assigned: Unassigned » jcfiala
Status: Active » Fixed

Hey folks.

Although I've happily used the Link module in the past, I haven't had much of a chance to look over the code yet. I'm planning on diving in deep to Link module as soon as I get my current top priority, the DME, out for an official 6.x 1.0 release, which should actually be pretty soon now that Drupalcon has passed.

Taking a quick look, it seems that this module has a fairly active issue queue, so it'll take me a little time to ramp up to speed, but I know how important this module is and plan to do right by it.

Status: Fixed » Closed (fixed)

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