This module needs a co-maintainer

This module doesn't appear to be maintained - from what I can see Moxide hasn't been replying to issues for the past few months or so, although they have made a few commits this year.

According to the drupal policy on "Dealing with abandoned projects" (http://drupal.org/node/251466), I think it would now be reasonable to move it to the webmasters' queue (drupal.org Webmasters).

Before I do this, would any of the people who have been doing patches be interested in taking over the module or becoming a co-maintainer on it?

I have alerted kdebischop, magico and fall_Out to this post, as they have all worked on patches to the module.

Hello,

First, I wish to apologize for my lack of communication during the past months. I have been elected as the mayor of my village, and this new "job" is awfully time consuming.

I will be glad to pass the maintainship of this project.

Regards.

I would be happy to take over this project, because I have already been working on it.

But I have a problem: I don't have too much experience about managing projects, so I will be happy to take over if at least there is one more person (more experienced than me) to help me manage this.

Thanks Moxide, for letting us know the situation; and congratulations at being elected Mayor :-)

fall_Out: thanks for offering your help. What sort of experience do you feel you're lacking? I know there are various places you can find help, such as the docs (http://drupal.org/handbook/cvs) and irc.drupal.org.
Perhaps you could take it on the project and put a note up on the project page (in bold face) saying that the project needs a co-maintainer?

If you don't feel as though you can take it on yourself, would you be willing to put up the note, Moxide?

I would consider offering what expertise I have: I haven't any experience managing projects on drupal.org, but I do know CVS reasonably well (though I still need to learn about branches). I am confident I could learn the skills by reading the docs.

However it would be premature of me to offer, as I haven't actually tried wymeditor yet! I was looking for the ideal editor module, and this one seemed quite a promising candidate, apart from the fact that it was looking a little unmaintained. This is why I posted to this thread. Now that there is more of a possibility of the project being maintained, I will take a closer look.

The other question in my mind is how fast progress is being made on the WYSIWYG project (http://drupal.org/project/wysiwyg), which is attracting the interest of some core developers (see http://groups.drupal.org/wysiwyg).

Hello,

I've added a note in the project's page.

Do we wait a few days before deciding who will be the maintainer ?

Hi,

I request the CVS account, I am waiting for a response...

When I have an answer to the cvs account, i announce!

CVS account approved and project transferred. Note, Moxide, you still have CVS write access to the project.

Thanks so much, fall_0ut, for your boldness to try to maintain this indeed promissing looking project! While reading this thread I thought I'd be interested to learn how to (co-)maintain such a project and learn about developing modules... So I would, in a way, be interested in co-maintaining. Having said that I do have to back off right away since I most-likely (99%) will not have the time as I'm behind with studies already and have two other time consuming projects waiting to be finished... (actually, two drupal sites). Pitty. I will second-think this, though, as soon as I can see shore with studies and come back. In the mean-time, if there is something you don't depend on fast responce or even positive responce at all do tell me and I will see what I can do (I could spare 1-2h/w incl. familiarization). Being enthusiastic about doing something means 50% completion, doesn't it ;)

It would be nice anyway to keep us updated how you settle in and, when you have an overview, how chances of a D6 port are. Maybe it might even be a good idea to go the whole hog and aim at D6 first prio and give packporting to D5 second priorities? After all someone running D5 allready wouldn't integrate such a new aproach into production sites. And people starting from scratch would most likely start with D6 since most modules are only a couple of weeks from stable as far as I see it.

Thanks again and cheers.

Btw. I came from WYSIWYG project and am looking for "in-place" editing solutions for a while and would really love to see these two features go hand in hand and maybe even that far as to give users/visitors a choise of editors (restricted to maybe in-place vs. separate). I did read something about in-place editing will be in the next drupal version, but I cannot find anything right now.

Edit: Idea to put D6 branch first

Edit 2: In case you haven't read it allready, here is from WYSIWYG project's site:

Think of inline editing. Imagine in-place editing of nodes, blocks and comments. You're correct, some of these thoughts already exist in various modules. (...) Last but not least, this project tries to reduce the amount of new wysiwyg-/ajax-related projects and is therefore all open for any (including experimental) code. Some sub-modules of this project will probably depend on the fabulous Javascript Tools. WYSIWYG editor (co-)maintainers and coders are encouraged to open and participate in issues and discussions, contribute code of their modules, as well as enhancing requirements of the wysiwyg API.
(...)
Consider joining the Wysiwyg group.

Thanks from me too fall_Out! And fast work in getting the 0.5a version of wymeditor into a branch!

Hi everyone,

Could someone apply to be co-maintainer of this project with a specific task: be good communicating in english.

This project needs someone to write the INSTALL.txt, README.txt, validate the text used on the releases, project information text and release information text.

I think that it would be very, very, very helpful for fall_0ut!!!

How do you mean validate? I just noticed the project description has changed (to the better!). I wouldn't mind to proof-read it if that's what your after (even though I'm not native to english I'm fairly comfortable with it). I could offer to send (whom to?) a text file with my suggested version if there is no native volunteer. I would have to pass on INSTALL and README right now, though.

Cheers

Yes, thats the idea: proof-read. It should be sent to fall_0ut, because he's the one in charge :)

I just created an og for wymeditor for this modules development's comunication so we don't overflood this issue system. It's been listed for aproval. Since I rushed through the creating process I hope everything is good. It's been set-up as an open group so memberships are welcome (as is contribution to this module :) ) and feel free to use it if it helps.

Cheers.

Good idea in create the group..

I'm trying to figure out what's going on here. It seems like og needs approval still, so there's no comment there. And I can't seem to figure out the plan here.

So I come back to my original question: I have a functional patch that ports the newest version of wymeditor to d6. It works, I have it deployed on 2 sites. It needs more work, which I'm willing to participate in if people want to work with my patch as a starting point. So is there any interest in using this working patch?

Or is there some other work in progress that I might be able to help with?

Are you still looking for a co-maintainer?

Hi,
Please post the patch.

If you are interested in co-maintainer please send me a mail, to talk about it.

Cheers.

With 5x-2.0 it was created a new branch that completely breaks with former branches adding new features and approaches to the module integration.

I think, that the first step would be, that people interested in this module should install this and try to understand these new features. Fall_0ut is working in upgrade this same branch to D6, and then both will be maintained.

Some new features also depend on some changes on the official WYMeditor, and some work is also being done there to accomplish the required behavior. Soon (next week) we'll have a D6 version.

I tried contacting you but got no response. Since you've accepted some patches, I know you are online. Did my message on your contact page not get through?

I'm really not sure what your plans are for this module. But I am interested in helping.

I am interested in helping. I'm going to be actively helping the WYM team develop the new 0.6 branch over the coming months. I, too, have not had experience as a module maintainer, but I have a ton of WYM experience, mainly for www.vocalo.org

Please join the Wysiwyg API project.

The API has been completely rewritten, now supporting any client-side editor and editor version. Support for TinyMCE 2.x, TinyMCE 3.x, and (rudimentary for) FCKeditor 2.6 has been added.

If you do not want join forces, I say "meh!", but I'll still analyze and probably fork the input format handling you added into this module for Wysiwyg API (if that works).

That said: http://drupal.org/node/253600#comment-1045008 ;)

I guess, someone of you should have the fu to create a new include file and JavaScript integration file for Wysiwyg API in almost no time. I already looked at it myself, but found it too weird at first sight, so I did not proceed. I'd be happy to review + commit a patch that adds WYMeditor support to Wysiwyg API!