Soliciting feature requests / review

Wrong project?

Is this project still on going? I may want to test the module. I'm surprised there hasn't been more takers.

You can check the module info and code at:
http://wiki.audean.com/doku.php

Download is at:
http://wiki.audean.com/helpdesk/helpdesk.tar

Code reference is at:
http://wiki.audean.com/helpdesk/doc/index.html

The status of the (slow) progress is at:
http://wiki.audean.com/doku.php?id=hd:progress

Be aware that:
- although it is now marginally usable for tests (can create/update/delete elements), it is still far from being usable in production
- it is currently 4.6 only
- I have other, more urgent code that's going to be ready sooner, much like the taxonews module that appeared someday while working on helpdesk.

Of course, if you wish to take part in the project, or add comments/feature requests, you're much welcome :-)

Frederic

Hi Frederick,

I finally got around to reading your response. I'd like to join in and help, but I too am finding myself bogged down in a number of other projects (all work-related and non-drupal). I'll try to take a look at what you have so far when I get a chance. I'm not much of a coder, but sometimes do tinker enough to be helpful. I'm surprised we're not seeing more people wanting to join in on this project as we've seen enough requests in the past.

Hi,

I've not worked a lot on it since then: spent more time on other modules:

• Glossary2 (G2)
• Taxonews
• and a private module for our company

...and I didn't have a CVS account available anyway.

Now that I have CVS access, I'm committing the current version so that anyone can dabble with the code more conveniently than with the wiki, which is more suited for documentation than for coding support. Feel free to create issues on it for new features, bugs, or help.

Note that the code is still very incomplete.

I'm working on it tonight.

This is my work for now:

http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/deekayen/modu...

I filtered out a lot of what I thought were worthless comments, formatted it to be more along the lines of Drupal scripting guidelines, and started the forms API conversion for Drupal 4.7. If I had known how broken it all was before I started, I might not have even done that much.

Well, as I said in an earlier comment: "Note that the code is still very incomplete."

Not that, as per the issue subject, this was a question about features expected, and comments on the existing feature selection, five months ago, not about the code itself. I'm not even sure your working from the current code base is a good idea.

This was my first attempt at creating a module, and it obviously didn't work out well: should I be starting it now that I understand Drupal better, I would obviously do it with much the same functionality, but coded quite differently. Indeed, as I still have the need for this module, I'll be working on it again rather soon, but I don't expect to use more than fragments from this version.

If you're in need of this type of functionality, I'd rather suggest we discuss the feature set and restart from scratch. What do you think of it ?

Man I hope you fellows get some traction with this as I am very very interested. I can commit to checking docs and testing....FWIW...

Thanks for your offer: check the docs on the wiki (info earlier on this thread). Feel free to suggest changes: as I wrote recently, the code will probalb be redone anyway, but the features should stay as currently specified.

Cool deal. I will go through the Wiki. One thing to think of is trying to be as ITIL compliant as possible. ITIL is the best practicce at this point for ITmanagement, but that is another discussion. I'll post more after I get through the Wiki..

This project is unmaintained, so I'm closing this to get it out of my open issues list.

fgm says it's not unmaintained.