I'd like to back port this to D6 if no one is offended

This task deserves more priority. I have been wanting to move to D7 for a while just to mess with this module. I have used a very broken, old version of this module for D6, but it was very bare. If you just look through the issues, I think you could still find that version.

My site still uses achievements, too, but it is now my own custom module (same structure, site-specific features): http://www.getlives.com

I would strongly recommend back-porting the D7 module. It seems far greater than my crappy module. :)

Won't fixing. Core has its own way of encouraging forward movement (no backwards compatibility), and I have mine: supporting only the current version of core. But, yes, if you look through the closed issue queue, there's a pre-1.0 version of a Drupal 6 module attached to an issue somewhere but, naturally, it's not something I'm supporting. If the OP is considering back porting this, I'd suggest doing so in a Drupal.org sandbox and I'd be willing to link to it as an unsupported module from the front page of the project.

If you won't allow it as a supported module, could he (or anyone else) create a new module from it and support it themselves? I think it is worth bringing in a second maintainer for this module for supporting D6. You could just say on the front page that the 6.x version is not the same module and is maintained by another person.

Hi,

I would like to help with a D6 port of the D7 version.
We still have some D6 pages and would will need an Achievements system, so it would be perfect to port this one to D6.

Since multiple people are coming forward to port as well as support the 6.x version, is there a reason not allowing co-maintainers. We understand appreciate your philosophy Morbus IFF, but if someone else is porting and maintaining this what is the issue? There are quite a few modules on d.o where such dual maintainers are being available.

Even if you don't like the idea, is there any harm to keep this thread active so those want to join this effort and continue to collaborate?

@ajayg, from comment #2: "If the OP is considering back porting this, I'd suggest doing so in a Drupal.org
sandbox and I'd be willing to link to it as an unsupported module from the front page of the project."

@Morbus Iff , As with any other drupal modules, I am sure the 6.x port will have more issues, patches and everything that goes with it. A link to sandbox looses all the collaboration support that we can have it here on d.o. Also a released module only, is considered by drupal's security team.

Your point of view is understandable if you had to support this. But if that is done by community , I still don't understand your philosophy. More so because you are quite a senior member here and must have watched this is how several other modules evolved.

If I was a developer, I would be happy to see there is a community getting evolved around a module, because a significant number of modules die because there is no uptick in deployment for those and hence no community.

@ajayg: If you like, the simplest explanation is this: I'm a dick. I'm very protective of my code, and I don't really trust anyone else with providing the same level of support, quality, or obsessiveness to detail. I never want to get into a situation where "my" issue queue is filled up with 50 bugs ("OMG, it has a ton of bugs! I'm not gonna use it!") on a version of code that has my name on it ("well, it does say Morbus on the project page and in the README..."), has nothing to do with me, and which I'm opposed to on a philosophical level, "just" to make the community happy. I don't care about download or usage counts.

As a developer, if I saw in my issue queue five or six duplicate issues all pining for the same thing, and not a single one showing any proffered effort past clicking "Save", it doesn't inspire me with confidence on the eventual quality of the result or ongoing support.

@Morbus Iff, first of all I don't think you are dick.

But I do see your protectiveness of code and passion for support, quality and obsessiveness to details. And I think drupal needs more people like you.
I could have easily suggested just fork the code, start a new project as others have done and the folks requesting 6.x can just move there.
Instead, I am suggesting, we can address some of your concerns different way. For example, by making it clear in README 6.x is supported by xyz, not you. Give it a try and let a new person learn from your quality of code. But more importantly rub some of your passion on others to make them better contributors to d.o.

If that does not work to your liking, you can always unpublish 6.x branch. Not a major harm done for trying out a few weeks.

You can be proud of who Morbus Iff is now or you can be proud of helping create 2-3 more Morbus Iffs in the future.

Your choice.

I already made my choice long ago. You're the one belating the point ;)

EDIT: To belate further: no one has come forth with any code or proof that they're willing to put forth the effort. I'm not just going to open up maintainership and a branch and suddenly expect brilliance to appear. There's been absolutely no effort besides "Morbus, do this!" and "Morbus, I might want to do this!". That doesn't encourage me in the least, and it certainly doesn't do a damn thing to ease any of my stated concerns above. "If You Open It Up, They Will Come" is not a mantra that has ever really worked. I tend to live by "The Internet (Works Around Roadblocks|Policies Itself)", "Hackers Make it Happen", and "Ask for Forgiveness, not Permission". I've seen none of that here.

Also: What's your 360, PS3, or Steam gamer tag?

I was not aware this was discussed before and apologize for taking your time again. If no one had come forward as they say here then I should not say anything further.

Sorry I don't understand what you mean by 360, PS3, or Steam gamer tag.