Re: [development] should tinymce get a new maintainer tinymce
Leave your office for a few hours and look what happens! I was busy planning my yearly pilgrimage to Austin for SXSW (http://groups.drupal.org/node/2708). Next thing I know, I'm maintaining TinyMCE. I wish I could say ""if nominated I will not run, if elected I will not serve, but I my dutch reformed upbringing dictates that I do some penance for voicing my opinion. I look forward to getting TinyMCE back on a track that everyone is happier with. - Kevin On 2/7/07, Boris Mann <boris@bryght.com> wrote:
On 2/7/07, Kevin Reynen <kreynen@gmail.com> wrote:
The good news...
Drupal-id.com is alive, well, has functioning email (support@drupal-id.com), and is responding to issues. Solutions to most of the unresolved issues have been at least been identified. A few have been patched. This module is no longer is crisis mode.
He's emailed a ton of folks to be the main maintainer.
Kevin, as I suggested, why don't you take the current code and make it a 5--2-0 series. Would you be OK with being the "main" maintainer.
Allie Micka, myself, and Steve McKenzie can take the 5--1-0 branch.
I've gone ahead and made Kevin the owner of the project node for now, and we can get moving on this.
-- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 Skype borismann http://www.bryght.com
This makes my head hurt! Since taking over as maintainer, I... - Posted an explanation about what's going on to the project page pointing people interested in the 4.7 features to Moxie - I cleared many of the issues from the queue - Downloaded all the suggested patches, installed and evaluated - Looked at ufku's IMCE patch to fix the IE issue and the SVN version of tinymce that has the fix Then this afternoon... I discover drupal-id updated the TinyMCE module last night. GUI button selector is back along with the .install. Location of the tinymce folder has changed back. I didn't know this was going to happen, nor do I know where this code came from or who tested it. Nothing about the changes in the Release Notes. I've been doing my best to help users with issue, get a handle on what's going on, and figure out how to move forward. I know several developers and many users jumped the tinymce ship and moved to moxie, but there are links to the tinymce project in hundreds of Drupal howtos. Anyone have suggestions on how to deal with this? - Kevin Reynen
On Feb 8, 2007, at 7:55 PM, Kevin Reynen wrote:
This makes my head hurt!
Since taking over as maintainer, I... ... Then this afternoon...
I discover drupal-id updated the TinyMCE module last night.
This is the nature of open source. Nobody owes anybody anything, we're all just out to scratch our own itches. The process works when people realize that you can help yourself in a way that helps others. In turn, you get more help and insight from others, and you'll find that they are helping themselves in a way that helps you. Spending your time and energy on a project should earn you a say, and most folks will acknowledge that. But it doesn't give you any special entitlements. If you want something done in *exactly* the way you would do it, you have to take some ownership.
I've been doing my best to help users with issue, get a handle on what's going on, and figure out how to move forward. I know several developers and many users jumped the tinymce ship and moved to moxie, but there are links to the tinymce project in hundreds of Drupal howtos.
Hopefully, by now, you realize from your own experience that this wasn't about "jumping ship". This was about respecting the project maintainer's rights to make his own decisions, while finding ways to address our own needs.
Anyone have suggestions on how to deal with this?
You can respect the project maintainer's rights to make his own decisions, while finding ways to address your own needs. If you do this in a way that helps others, you are participating in the open source process. Allie Micka pajunas interactive, inc. http://www.pajunas.com scalable web hosting and open source strategies
Allie, Let me get this straight. You get upset when a developer doesn't communicate changes... "you'll find that people weren't inherently opposed to these changes, but they were concerned by the lack of a roadmap" - Allie Micka on February 5, 2007 Now you're defending a developers right to make whatever changes he wants to the release version of popular modules without documenting what they've done and providing no support to deal with the issues this creates while someone else is trying to maintain the project? I'm not as concerned that the .js theme files have been bypassed again as I am that the people are going to quit contributing to (or even using) this if someone is going to turn the module on it's head every other month. Very little of what's on the project page or responses to issues is even accurate now. Just because this is open source doesn't mean it has to be chaos. The last email I received from drupal-id, he said he didn't have time for tinymce. He isn't even listed as having CVS access and is no longer the module's maintainer. Now there's a months worth of Drupal 5 users with a version that can't even be upgraded to this version of the module without manually running the install sql. This is EXACTLY what I was hoping to prevent by just moving drupal-id's code the direction moxie went. What are people with custom .js themes supposed to do? There's no clear way to keep that "feature". - Kevin On 2/8/07, Allie Micka <allie@pajunas.com> wrote:
On Feb 8, 2007, at 7:55 PM, Kevin Reynen wrote:
This makes my head hurt!
Since taking over as maintainer, I... ... Then this afternoon...
I discover drupal-id updated the TinyMCE module last night.
This is the nature of open source. Nobody owes anybody anything, we're all just out to scratch our own itches. The process works when people realize that you can help yourself in a way that helps others. In turn, you get more help and insight from others, and you'll find that they are helping themselves in a way that helps you.
Spending your time and energy on a project should earn you a say, and most folks will acknowledge that. But it doesn't give you any special entitlements. If you want something done in *exactly* the way you would do it, you have to take some ownership.
I've been doing my best to help users with issue, get a handle on what's going on, and figure out how to move forward. I know several developers and many users jumped the tinymce ship and moved to moxie, but there are links to the tinymce project in hundreds of Drupal howtos.
Hopefully, by now, you realize from your own experience that this wasn't about "jumping ship". This was about respecting the project maintainer's rights to make his own decisions, while finding ways to address our own needs.
Anyone have suggestions on how to deal with this?
You can respect the project maintainer's rights to make his own decisions, while finding ways to address your own needs. If you do this in a way that helps others, you are participating in the open source process.
Allie Micka pajunas interactive, inc. http://www.pajunas.com
scalable web hosting and open source strategies
On Feb 9, 2007, at 12:01 AM, Kevin Reynen wrote:
Let me get this straight. You get upset when a developer doesn't communicate changes...
"you'll find that people weren't inherently opposed to these changes, but they were concerned by the lack of a roadmap" - Allie Micka on February 5, 2007
Now you're defending a developers right to make whatever changes he wants to the release version of popular modules without documenting what they've done and providing no support to deal with the issues this creates while someone else is trying to maintain the project?
Exactly. I expressed my concerns, and then I "unforked". This permitted the maintainer to make any choice that suits him, while ensuring that there was a supported solution available for my own needs. You are welcome do similar. Thanks and good luck! Allie Micka pajunas interactive, inc. http://www.pajunas.com scalable web hosting and open source strategies
On Feb 8, 2007, at 8:55 PM, Kevin Reynen wrote:
Anyone have suggestions on how to deal with this?
You really should make a DRUPAL-5--2 branch for the new features and maintain the DRUPAL-5 branch. That way you can work avoid interfering with the drupal-id's development work.
On Feb 8, 2007, at 10:04 PM, Darren Oh wrote:
On Feb 8, 2007, at 8:55 PM, Kevin Reynen wrote:
Anyone have suggestions on how to deal with this?
You really should make a DRUPAL-5--2 branch for the new features and maintain the DRUPAL-5 branch. That way you can work avoid interfering with the drupal-id's development work.
I agree, Kevin. Merge the Moxie stuff back in to tinymce DRUPAL-5 and make a 5.x-1.0 release ASAP based on that. Move all of the new stuff to DRUPAL-5--2 branch. I think there was a pretty clear community consensus on this as a desired direction. Also, I'm sorry that your efforts to clear things up have continued to run into difficulty. Seems like it mostly has to do with a communication issue with drupal-id. It sounds like you need to have some clear communication with him about what you consider to be appropriate contribution from him, now that he passed ownership to you. You might suggest he simply use the issue queue to post patches for the DRUPAL-5--2 branch. Clearly, any co-maintainers need to share an understanding with the project owner regarding commit protocol. -- Ray Zimmerman Senior Research Associate 428-B Phillips Hall, Cornell University, Ithaca, NY 14853 phone: (607) 255-9645
participants (4)
-
Allie Micka -
Darren Oh -
Kevin Reynen -
Ray Zimmerman