Multiple duplicated modules

fwiw these modules are:

http://drupal.org/project/img_filter > dupe of inline.module
http://drupal.org/project/messenger > dupe of private message
http://drupal.org/project/ip_locator > several modules like this, one is http://drupal.org/project/ip2nation another: http://drupal.org/node/45806
http://drupal.org/project/piclens_lite

For examples of the several issues filed against these modules for duplication and the maintainer's response see:
http://drupal.org/node/251133
http://drupal.org/node/151723

My suggestion with what to do with the modules are to remove or at minimum unpublish them if unsuspecting users download them and find bugs and report them the dup dev can't roll a new release out any way.

Avoid the confusion and force them to stop watering down already existing modules, is my opinion.

The dev who is duplicating modules should work to make the already existing modules better if he/she wants to better the community.

Ok, this all moved really fast. I started the discussion on IRC and it just went nuts. I think we need to stop and think about this. It's not as simple as banning a spammer. Removing his CVS access creates problems as well as solving them.

First, we need to vrencianz in on this discussion. If we can come to an agreement on removing what dupes we can and that he won't create more, then I think we should restore his access to care for the rest. Looking at the modules list, but not having used these modules, this is my opinion:

img_filter and ip_locator don't look like they would be a hardship for the users to replace with the modules they are duplicating but they have been around for a while. My main concern is with img_filter and the fact that filter code in content is hard to replace.

messenger has been around nearly a year and that has content storage. Losing that module could significantly impact users unless there is some conversion path to privatemsg. If there isn't, and no one is willing to write one, that module needs to stay for the sake of the users. I would like to see an explanation of how it differs from privatemsg on the project page, though.

piclens_lite, which started this firestorm, though, is brand new. I see no reason not to unpublish this module.

In summary, messanger at least and possibly img_filter need caring for. For that, vrencianz needs cvs access. I suggest we change this to a warning and allow him to keep the access for now on the condition that he adds clear explanations to whatever project pages remain and does not duplicate any new modules.

Michelle

Before disabling a contributing user's cvs, I think it's important to weigh the impact that will have on existing users of those modules.

Basically, if you are terminating the main source of unpaid volunteer work by the core maintainer on multiple modules, you need to take into account the negative impact that will have on people using those modules.

Is it enough to say "use module x instead"? How does that affect the image of Drupal, in terms of user-friendliness, or the general stability of the module base? I think this is an important consideration.

When you discontinue a user, you're also discontinuing every module they maintain, with no recourse for support or patches after that point. This isn't a decision to make lightly.

Edit: I see Michelle has brought up some similar points :)

1) ip_locator: please take look to the drupal cvs logs. This project was created before other modules but, becouse of a strange reason, I had no access to it.
2) messenger: 'im' was the project that inspired me not privatemsg. 'im' wasn't maintained and I decided to make my own.
3) img_filter and inline (has no drupal 6 version) are incomparable at this moment. Inline is great but it cannot control images positions and it has no thumbnails.
4) the module which caused this problem: piclens lite: one week delay as I know. I finished coding it and when wanted to create a project, exists. oops. Img package worked with it. Rollback it? No. That's it. My fault. Even of this I think that this module is good. Competition is good.

I have a site family (http://para.ro) hosted for no money but my money and these modules and my time. I never made money from Drupal except two years ago when helped a guy to install few sites. I reject Drupal related jobs because I have a job (I am programmer, but c++, database, c#).

What a hack I did so wrong to open a thread like this?

(my English is not good as you observed)

Before you drop me out think that I am a good maintaner and care of my users (see my issues). Do you want to drop maintained projects and keep a lot of unmaintaned modules. It is not fair.

1. http://drupal.org/node/45806 was added to CVS in 2006, 18 months before ip_locator
2. The reason given for CVS account disabling wasn't plagiarism, it was reckless duplication. Also there are mechanisms in place to take over maintainership of abandoned modules
3. this module started as a direct fork of inline, and attempts by inline's maintainer to work with you when it was started were ignored.
4. I'm not sure what you're trying to say with that one.

No one has an issue about whether you make money from Drupal or not, the issues I've read for your modules have consisted of rude and repeated shutting down of genuine questions about duplication.

See the cvs logs man, not the drupal project. you'llsee an ip_locator module created there 2,5 years ago. The ip locator has its own database which is a big advantage.
The inline's developer never contacted me.

The inline's developer never contacted me.

Sun contacted you here: http://drupal.org/node/150624 Addtionally I personally opened a duplicate issue here: http://drupal.org/node/153636 because as with so many others you'd closed the first one and I didn't see it at first.

As for cvs logs, please compare: ip_locator and IP to country. If this was just one module I don't think we'd be having this discussion, but all four of your projects are like this.

Well. Nobody told me that he is a maintainer. The developer was Bruno(I think).
For ip_locator see http://drupal.org/node/50010 and http://drupal.org/node/34959 October 23, 2005!

Search this Drupal site for messenger, ip_locator, localities, lexicon, mail_validator. You'll have surprises.
These modules wasn't hosted here.

Could you access the cvs raw logs?

I sleep very well every day but today cannot but I realosed that you are joking.

1) IP2Nation. Has no activity on it Filter issues by all-all-all. Nothing. It seams that this is a perfect module. After installation it just works. No support requests and or bug reports. Great! hahahahahah.
2) Private message has no Drupal 6.x version. No comment.
3) Inline has no 6.x version. What a surprise! I started the img development from its code. There is something wron?

/**
  A Drupal (http://Drupal.org) image display module.

  Copyright (C) Vrencian Zoltan http://project.para.ro.
  
  Older versions of the advanced mode was taken from the inline module (http://drupal.org/project/inline)

  This program is free software; you can redistribute it and/or
  modify it under the terms of the GNU General Public License
  as published by the Free Software Foundation; either version 2
  of the License, or (at your option) any later version.

  This program is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License for more details.

  You should have received a copy of the GNU General Public License
  along with this program; if not, write to the Free Software
  Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
*/

It is GPL. Or you want me out from here because I modified a GPL application, made it much more better? I don't think so.

Till now it is a joke. ... or not?Is this some kind of discrimination? http://en.wikipedia.org/wiki/Discrimination

You want me out with no reason because of I am from Romania?

If it is a mistake I wait appologise.

The issue comes down to abiding by the simple Joining forces with others guideline for CVS account holders, which is linked multiple times from http://drupal.org/node/59 which you are required to read and adhere to in order to obtain a CVS account in the first place.

The proper way to deal with a situation where you need a module and it currently is unmaintained, languishing, or has not yet been ported to the proper Drupal version, is to post an issue in the module's queue stating your offer to help maintain it (ideally, accompanied by a patch that solves the problem for you, as a show that you are serious about helping). A search on drupal.org for "maintainership" reveals countless issues where this has been done successfully by other people.

An issue in the appropriate queue is:
a) public
b) timestamped
c) a direct line of communication to a (responsible) maintainer
d) an easy, documented way for the CVS team to confirm absence of a maintainer and make it a no-brainer for transferring the project to you

Forking projects is bad because:
a) Users are confused about which project to use.
b) The earlier created project will have tons more users than your newly created one, and they are now stranded on something that's unmaintained.
c) It's against the rules that you agreed to when you applied for a CVS account.

I don't see active discrimination here. I see a bit of a sledgehammer approach in enforcing our rules, and I see defensiveness and aggressiveness on your part (and implying we're racist while you're at it), which is only exacerbating the situation. Your best option would be to follow the established protocols and take over maintainership of these abandoned projects, assuming you have not burnt so many bridges that your privileges won't be restored at this point.

One thing I will point out however is the above steps for taking over an abandoned module don't seem to be documented anywhere in the CVS handbook, nor on node/59, although they are common knowledge to anyone who hangs out on the devel list or in #drupal. http://drupal.org/node/248145 looks like it's still in flux. So we should get on that ASAP to avoid another one of these situations.

Fixing the title because this hasn't anything even remotely to do with discrimination.

@webchick - If people have objections, they sure are being quiet about it. I'll just go ahead and add the page tonight.

Michelle

@vrencianz
It's nothing to do with Romania. I'm sure it's very nice this time of year.

When I posted my question about duplication I wasn't intending to set you up against all this. But looking at the history of some (not all) of your other modules now, it does seem that you do duplicate a lot.

That in itself would just be annoying, but possible to ignore. But your inability or refusals to explain why the forks are needed is confusing, and your shutting down of the support requests is frequently rude.

I just wanted piclens_lite to be merged, retired, or at least described better to avoid the obvious clutter its existence causes. Your'e the one who asked for someone else to remove it if it didn't fit well on the Drupal repository.

If co-operation was possible in that thread, this may not have become an issue to other folk. But looking at all your similar examples of this behavior, I do see the problem the CVS maintainers have to deal with. I also see a problem with cutting access to the older modules you mention. I have no idea how unique or useful they are.
I don't think it's a great idea to cut anyone off from the things that they are doing well, so I wish we could separate the issues of duplication from the rest of your work. I will assume your other contributions are just fine..

if you could see why so many folk think that your contributions are clutter, and if you learned from this, apologised, followed the rules, and could say it wouldn't happen again, I'd support just removing the 'duplicate' projects and restoring access.

However, as it seems you can't see what the problem with what you are doing is, and find it easier to call everyone racist, I expect that won't be happening.

As the maintainer of the piclens module, my 2 cents in the discussion. I'm mostly dissapointed about the piclens_lite module when I look at the commitment for my own module:

• I first saw piclens 2 months ago at the DrupalCon in Boston thinking it was a cool new flickr plugin
• I finally found out 3 weeks ago by accident this was the piclens browser plugin and there was a webmaster option
• So excited I had my first working version after 2 hours, but after two days I realized that MediaRSS was not invented by PicLens, but Yahoo! and mediarss community to enchance rss content feeds
• I decided not to release an official version for different reasons: piclens lite/flash browser issues, drupal image modules support etc, waiting for patches, bug reports etc (thanks dman and others!)
• But most of all: after 3 weeks of development, I'm thinking to release a separate project called MediaRSS API (and a patch for rss feeds for D7 as I think this is reasonable for core to support this kind of feeds) with hooks support and piclens module depending on this. This seems very logical to me, because it would be stupid to support mediarss feeds for like say the audio module in my piclens module. That would be, well, utterly stupid. (note, I was going to send out a mail via the contact form to all my issue and patch contributers to have their opinion in another issue)

Anyway, I'm not here to judge. It's the second time I see a contrib module pop up a few weeks after I added my mine (cf blockclone vs multiblock), just wanted to express my confusion also as I'm not sure which next steps I should take now (release piclens / mediarss etc ...)

I like the direction of generic media RSS support ... vrencianz's work with of 'attached files' being a feed for a page would even be a good addition to that. that's for a different thread.

What I see here however is an example of the attitude that works. No hubris, no ego, just looking forward.

- Here's how I've done it, there may be better approaches, please join in.
- I'm open to suggestions for improvement
- If there's a better approach, lets go with that, even if it means retiring what I've done so far.

VS

- I want a small difference from the existing work, so I'll make an entirely different version.
- Anyone who even questions my approach is wrong.
- Duplication of effort, splitting the community and multiple similar search results are good because (my) choice is good.

No discrimination, say?

Why I am the very first Drupal developer expelled because of 'duplicated projects' then?

Why Ubercart and e-commerce developers had no thi sproblem.
What about thickbox, lighbox, craqbox developers?
Jquery tabs, jstools?
............................................

I have right to refuse using a module and/or collaboration with a developer whom code I don't like. Not only me, you have this right. Anyone has this right. No explanations.

Your explanations are very poor, but long. I cannot see a real reason there. The module which started this discussion if 96 lines long.

Let me guess: It is because you have lost your inline sponsors because of me? You'll lost other sponsors because of my modules? Let me understand.

The existing PickLens module integrates the image gallery (I like and use it) only. This what it do in the Piclens.module.

After that:

* mediarssapi_feed_url($url, $title);
  This function adds the rss feed with the $url to your own menu callback providing the feed
  into the head of your document. $title is optional.

* mediarssapi_format_item($item);
  This function formats one item (image, video) into a valid xml structure for the piclens feed.
  $item is an array with following properties:
  - title : title image or video
  - link : direct link to content
  - thumbnail : thumbnail url image or video
  - content : content url of image or video  

* mediarssapi_rss($items);
  This function outputs the feed. $items is a string formatted xml list of $items.

* mediarssapi_piclens_lite_javascript()
  This function adds the javascript for the PicLens Lite into the head of your document.

* mediarssapi_piclens_lite_link($drupal_set_message)
  This function returns a link to start the PicLens Lite slideshow.
  If $drupal_set_message = TRUE, the link will be inserted as a drupal message, otherwhise
  the link is simply returned. Inside this function theme('piclens_lite_html_link'); is called
  to return the html. You can override the theming with phptemplate_piclens_lite_html_link() off course. 

Do you want me to use these stuff instead of defining a hook and eventually output a link to the slideshow everywhere I want (not just a button)? I don't think so.

Do yon want to enforce me to use and or maintain, continue development of this module, inline, ip2nation (hahaha) private messages or any existent and didn't maintained modules hosted by Drupal?

Tell me exactly what do you want, don't close my CVS account without a good explanation. Again. Your explanations are poor and has no content, just general philosophy.

Reasons? See #12.
You are breaking the rules of Drupal module creation and maintainance.

You are unable to see that. So now, instead of thinking that this punishment was a bit harsh, (I didn't think you deserved it from just the one mistake) ... I now agree that if you won't follow the rules, you shouldn't play the game.
Not much is wanted of you, but following the rules of participation is required. And, I guess, being enforced.

Sometimes general philosophy can be a good reason. Most OSS projects started with just a 'general philosophy'. And sometimes had to make up the rules later to deal with troubles.

As General Philosophy goes, "Don't be a dick" is a good one to start with.

Singing about discrimination and other strange accusations is silly when most of us don't even know or care where you come from or what you look like. It's your behaviour that's got you into strife here ... not your hometown.

I thought that if you could understand the problem, take some advice, and pull your head in, this could be possible to be settled. Why not co-operate? We can't make you co-operate ... but that is what the rest of us are here for and what the repository is about.
You say really don't want to join forces... OK, so this is a message to buzz off then I guess.

The CVS account application page explains clearly what is expected. Webchick has already linked to http://drupal.org/node/243204 and http://drupal.org/node/59, but it appears you've ignored her post and instead decided to accuse the volunteers on this site of discrimination and profiteering. Here's the relevant sections for convenience from #59

If your motivation message resembles one of these then please, think before applying.
[..snip..]

# Module 'Foo' no longer appears maintained so I have written a new version I would like to contribute. Realistically this forms duplication and Drupal.Org tries to avoid this where possible (see the previous link for why this is so). The best way forward in this situation is to provide feedback to the module with patches rather than strike out afresh. If the module appears abandoned and patches sit by without review of commit, use the Webmasters to ask to take over an orphaned module.

# Module 'Foo' is just too complex so I have written a much simpler version. This is just straight duplication of functionality and applications like this will almost certainly be declined. It is worth remembering that many modules start out simple also and, over time, grow into more complex systems. If you have the know how to write a "simple version" from scratch rather than work out how a complex module works then maybe your effort would be better spent making the existing complex module easier to use (improve it's UI, write documentation, etc).

There are many duplicate modules hosted on Drupal.org, either by accident or design, but developers of those modules are usually open to discussion of ways to consolidate them or work together, or alternatively explain their reasons for creating a different module. Up to now I've not been aware of anyone who has simply shut down discussion and then made accusations of discrimination and profiteering instead, so rather than another post doing this, I would consider re-reading your offhand and dismissive responses to other developers where this has been raised with you before.

If you think other developers who contribute duplicate modules are treated differently please see the discussion here for an example and note how it was resolved: http://drupal.org/node/243204 (an explanation was given and the project node was unpublished by the developer).

Well, I am not shure how to understand this kind of discussion.

For my part, the IMG_Filter seems to work better - for me - then what I saw from other parts - and it works in version 6.

What is the news from those other modules ?

Is there any "guarantee" - what so ever - that the other modules make it to the next Drupal version ?

I do not care how many similar modules are out there, what I do care as a user, is
that things need to be discussed openly, BEFORE someone shuts down any access or follow up
oportunities to either users or developpers.

A suggestion: Drupal has a fine feature with "taxonomies", which should allow to easily classify
modules so that every effort could easily be found and compared - why is this not implemented
in a better way in the modules area ?

About the way this was handled

It is not the fair way anybody deserves to be treated,
if he does something "diffferent" or "better" in his mind.

By the way, nature itself has many facets of similar, often confusingly similar
developments, and that is what makes development and survival possible at first place.

The anacronic, nasty attitude that was shown here seems to be a joke, but I am afraid it is not.

As a user I would have preferred a discussion and the option to be warned, but not to be
depending from a "gang" that unilaterally "cuts off" and imposes measures on others.

The image of Drupal had in the past some problems with people who responded to support
requests in an arrogant manner similar to "You dont like what You see, make something Yourself"

In this occasion, no concern about users was seen, before action was taken.

Those who did that, should be ashamed ...

To the guy who ventured into developping and presenting his versions and ideas,
"Thank You very much for the effort".

On my part, I will take a time, look and decide wether Drupal is still
what I want my sites depend on.

Sorry if this seems and sounds harsh, but I did not expect this kind of
attitude possible at all within this community.

Roland Becker
Costa Rica

Personally, I would agree that this quick close-down seemed a bit drastic without entering into a dialog and warning process. This wasn't what I would have recommended.

however

I now see the various CVS maintainers are aware of a much longer history of very similar bahaviour from this user.
This one (linked by catch above) seems a representative example :-)
They've also seen a few of the other split issue discussions that went bad - several linked from here.
Altogether it's a bit of a concern.

On top of that, the attitude, the blank refusal to co-operate, or even acknowledge the issues and look for a compromise is looking like the real problem here.
He declares there's no way he'll co-operate with the community, and doesn't care about duplications and the confusions it causes. He doesn't acknowlege the rules he was directed to look at ... And he issued a challenge to remove his module. Not that I had anything to do with bringing this hostile behavior to the admins attentions, FTR.

And the accusations he's been throwing back in this thread are just childish.

I do wish there was a compromise, as I don't like to see the genuine input he's had be dismissed ... but it does require him to at least understand what the problem is. Surely this 'punishment' should bring this bad behaviour to his attention.

Based on what I've read, discussions did take place with this individual before the CVS access was removed. If you can call them discussions. Discussions aren't usually one sided.

Other developers did try to engage this individual in discussion using this persons issue query on the modules they were concerned about. Other developers did try to inform this individual that his efforts could be better used and rather then working with those developers and working toward a compromise, this indvidual ignored, argued and continued in the manner of disregard toward the objections, inquires that were being brought to his attention.

Those bringing this to this indviduals attention were told (by him) to ignore him and his projects which isn't a compromise or even a try on this persons part to understand the positions of those trying to open a line of communication with him.

If the initial discussions weren't getting through to this person then, I don't see where yet another discussion would. The drupal.org account wasn't blocked and he still has every opportunity to discuss and comply. To comply he would have to show that he understands rather then choose to be a victim in this case.

In my book there is a major difference between complying and commitment. Many developers of Drupal and drupal modules are committed to what they do and the way they want to see the community grow and expand and others are compliant because they understand that the rules are the rules and they do it because they feel they must.

In workplace safety (my field of work) we distinguish compliance vs. commitment as:
compliance = you work safe because people are looking over your shoulder and expect you to work safe
commitment = you work safe because you believe it betters the work place

While both of the above will force people to work safe trust that those who just comply will not work safe if someone is not looking over their shoulder and run a greater risk of getting hurt on the job. Those who are committed to working safe lessen their risk because they put working safe as a priority in everything they do on the job.

I think the problem laid in front of the community with this situation is vrencianz doesn't seem to want to comply or commit.

On a positive note

I'm all for this vrencianz to become a bigger part of the community with his developing. I see where vrencianz is a good maintainer of what he is doing, I assume he's working within the drupal coding standards as I've read no complaints about the way he codes his modules. I really think that he could push some of the already existing module forward which will benefit all users of the community.

Pushing them forward doesn't constitute forking between versions, Modules could be ported forward for Drupal 6 that weren't already and changes made at that time if he and other mainatiners saw fit. vrencianz can also choose the path of expanding on existing modules by creating addon's to the contribs if necessary.

If there are modules he's working on that don't have a maintainer now, he can certainly apply for co maintainership/maintainership and bring these modules forward in a way that suits himself and the community at large that are either already using these modules or that in the future choose to use these modules.

What's the problem?

http://drupal.org/project/img_filter
http://drupal.org/project/messenger
http://drupal.org/project/ip_locator

I've tried these modules out and I found that the ones you are closing down is much better to my Drupal 6 setup comparing to the other ones. Closing them down seems stupid. There are lot's of duplicates on other stuff!

So, even if you closes these down I'll still continue to use them because I want good functionality and don't bother the politics!!!

Regards,

/Thomas

double - post.
Looks like this post was stuck in the inter-tubes for a few hours. That's been happening to me a bit recently :-[

I published this on the banned authors website
because I beleave that he may have enough
reasons to not come back to the Drupal site after
what has been done to his effort and commitment.
------------------------------------------------------------------

Hi vrencianz,

I FEEL SORRY FOR THE TYPE OF ATTITUDE THESE FEW PEOPLE SHOWED TO YOU.

I also hope that someone of the original crew takes an moment an corrects this development ASAP (as soon as possible).

For my personal experience, I agree that IMG FILTER for Drupal6 is very good and I prefer it to others on the case of use I have.

To ban someone just for presenting different options, variations etc. is in my opinion noty very intelligent - not for the community and not to the project that all try to contribute.

Sorry for what has happened to You.

Please send me a private mail.
I would eventually need some help in ongoing projects.

Best regards, all good wishes and THANK YOU
for Your effort and commitment.

Roland
Costa Rica

@scriptnews - Please don't spread FUD. He hasn't been banned. He's had his CVS access suspended for breaking the rules of said account. No one has mentioned banning him and that's not even up for consideration AFAIK.

@all - Ignoring the tone for the moment, it sounds like his existing modules have some user support and removing them could cause backlash. I suggest we leave them be rather than disrupting the existing users. A note should be added to all the project pages to inform new users of the duplication and attempt to explain the differences to ease the confusion. At this point, I would rather see the maintainer's access restored so he can continue to care for the modules rather than have them be abandoned/unpublished. But it should be with the understanding that he creates no new modules that duplicate existing ones so this problem doesn't continue.

Michelle

As a new Drupal user (a few weeks now) I'm totally Flabbergasted with this...

My recently created Drupal 6.x site reported a problem with the img_filter module, which on further investigation appeared somewhat alarming: 'module no longer maintained'. Wow!

Checking the module on the Drupal site showed that this is due to some site maintainer discussion... Whatever the underlying motivation, I think it's a bad thing that sites that use Drupal 6.x with one of the affected modules now have a problem. Should I now change my site to use another module? Wait, there is no real alternative to img_filter. What to do then? :-( Hopefully a more constructive solution is found for this discussion soon (one that does not affect Drupal users).

One might easily conclude from this that Drupal 6 is not yet ready for use and revert to Drupal 5 for a few years (?) or so.

I have no clue who caused precisely what misunderstanding here - it seems I´m not the only one - but if it starts affecting sites using the respective modules I´m wondering whether that politics is supposed to affect existing installations with error messages just because someone did something in some inappropriate manner . . . well, just my humble saturday night remark . . might be helpful to lean back for a moment, have a weekend stroll in the sunshine and reconsider what is the best approach to solve this matter.

enjoy ur weekend!

Hi All,

If these modules are now effectively finished (rightly or wrongly), and we're being told to use existing modules.. Can someone point out to those of us that have Drupal 6 running which module(s) we should move to using instead in order to have the same (or better!) functionality? (I really don't want to swap to something else and then find that it is also closed down!)

I ask as the Inline module Catch refers to is not available for D6.x

Thanks

Any chance to continue with IMG_FILTER? It was really stupid thing to mark this as duplicate :-( I have the same question like Waywisher.

Ok, this is a mess. I have re-enabled cvs access for vrencianz until this can be settled. I can't guarantee it will stay that way as I'm not the final authority on it but, as I'm the one that started this mess, I decided to act. This all started out of concern for the users so following a path that ends up hurting the users makes no sense. We need to discuss what is to happen with both vrencianz and these modules and come to some sort of solution that works for everyone. Until then, he needs access to maintain his modules so we don't leave the users out in the cold.

Michelle

+1 for the img module. Thx to the dev for adding useful functionality and needed updates to inline, and then graciously offering it back to the community. What's up with inline module? Why didn't it integrate these features or update to D6? If a dev wants to fork a GPLed module and make it better and keep it upgraded so that it actually works with the current version of Drupal, why isn't that legit?

While I agree with the Drupal dogma that it's always better to join a similar existing project (if it exists), there are situations that can make this near impossible, especially when an existing maintainer ultimately has control of a project.

For example, I had a assigment that required I add *a lot* of functionality to the Inline module. I believe it covers everything added by the inline fork discussed here and more. I offered it back to the Inline project here:

#163806: Enhanced version of Inline using hook_filter, CCK Imagefield/Filefield, Thickbox, parameters, etc.

I put up a demo (which I've take down since), had others testing it, and currently have it up on production sites. However, after much discussion on that thread (and other threads), it became clear that it didn't mesh with the maintainers "vision" of how he would like the module (and API) to progress in several areas. (As well as not coming in several bite size chunks, which I had no time for due to deadlines.)

So what is a developer to do at that point? Well, I just said screw it :) I'll just maintain my own module privately, port it to 6 and be happy. That's because I knew of the Drupal duplication rules, and wasn't prepared to spend months of debate trying to convince a maintainer to look at things differently based on my experience implementing all the new features.

I think in cases like this the community *can* loose out. Other modules *could* potentially leapfrog existing ones because of situations like this.

Which brings me to my point... and one that I know has been discussed a lot lately as the module submissions continue to grow.

If it were up to me, I would allow more liberal module/project creation and add *registered user* ratings for a variety of criteria that's *weighted* by the voting users registration date at Drupal.org and their Karma score (yes, another addition).

I understand the notion of "user confusion" with competing projects, but in the end the strong projects will always rise to the top.

Hi Michelle

Please let me know what FUD is.

I used the word "banned" not because he eventually has lost access to the Drupal site, but because he has no more access to his development.

There was also the inappropiate use of the word "punished" by one of the people who did this.

Mistakes may happen and ofcause I am shure You did not mean this outcome.

Thank You for all Your effort and good will.

Hopefully this issue gets fixed.

Best Regards

Roland
Costa Rica

Dear Michelle

Whoever started this mess (as you correctly name it) has done a bad service to the community!
Because Drupal is not only about developers and maintainers but much more about USERS. Users that are NOT interested in dwelling into PhP and programming but making USE of Drupal for their online web presence.
I have to agree that some sort of discipline must exist in the ways of Drupal but let's not forget that DIVERSITY was, is and will be the key to better development and SURVIVAL of this beautiful CMS.
As a user I am more than HAPPY to browse through hundreds of modules to check what each of them has to offer. I am not "confused" by their number but by their LACK of proper, "for DUMMIES" kind of DOCUMENTATION. Module developers tend to forget that not everyone of those using Drupal has the ability, the TIME or the interest to dive into its "intestines".
I love Drupal for its SIMPLICITY (the fact that has so much to offer is a plus) and I love modules that are as neat and WELL functioning as Img Package ( why, oh why do I need 10 modules to do the simple job of inserting some pics into any of my nodes???). If Img Package is a fork than, BY ALL MEANS, I approve forking. The guy did indeed a BETTER job, a SMARTER job, a WORKING module where others do not even exist as of yet!!!. You or others suggest it is a duplicate. Please translate the word...hehehe.
What is NOT duplicate in this world? Accidentally, the Img Package developer did a better and a safer job with this module be it a duplicate a fork or whatever you wish to name it...the module rocks! Where are the others??? Drupal 6 is out for ages and I see none of the real useful modules being ported. As I mentioned, what would I use to post pictures in my nodes? IMCE-not ready, Image-not ready and so on.
Let them that can DO IT, do it. That is what community and Open Source is all about.
Talking about "politics": why don't you use moderators to check the ORIGINALITY of whatever new module is submitted to this site??? You discover AFTER 2 years that some module "might" be a duplicate??? And start ALL THIS nonsense instead of being happy that we have AT LEAST one module ready for Drupal 6 that will allow us to post pics (and even better, to browse them with Lightbox?)

Where are ALL the others , so much needed small modules for Drupal 6???
Where is "Legal" for instance??? A kid could do it in a weekend, yet the "OWNER" of the module is nowhere to be found!!! How about someone else to get the job done? I DO NOT CARE if it is a fork!
I want the module NOW...this is the mentality of ALL users. We can care less for all of your tribulations about ownership, maintainership so on. Yes, clutter is BAD but not having the FUNCTIONS in good time is WORSE. I could write you pages of all frustrations I get trying to learn how to use one or another of the POOR documented modules. As if we are supposed to understand or care about the super-duper lingo. Do you have any idea how many of the posted modules and themes are POORLY coded???
Let's face it: we need competition and better coded modules, variations are just GREAT!
I tend to believe that some folks here have very strict Copyrights policies on their personal websites :)

Dear Michelle, please try to understand that pride and prejudice come with an expense that not everybody can afford. I wish you and all drupal.org moderators: "A splendid Sunday!!!"

Sincerely yours
fulga

+1 #27

This is a joke made by someone maybe even don't know what is Drupal 6.

I built websites with Drupal 6 when it was RC1 with some custom modules. I was waiting for an image processing module until I found img_filter. It's neat. It only does one job - processing images, and does it the best. "Modules" should be like this. Those pretending to do everything should be killed.

Users:

Thank you all for supporting these 'duplicated' modules. I have no words.

Maintainers:

Thanks. ... but I'm afraid that this nightmare is far away to be over.

This issue has turned into a trainwreck. I see no point in keeping it open.

Michelle

As shown by #253416: Buy Lorem Ipsum, #31 apparantly wasn't succesful. A pity.