<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On Feb 6, 2007, at 2:31 PM, Kevin Reynen wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">HerI see few potential outcomes from this course of action...</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">1) drupal-id.com gets pissed and removes me from the project, but</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">doesn't address any of the other issues leaving things where they were</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">yesterday</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">2) drupal-id.com finally realizes there is a problem with their email</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">system, starts to respond and address user issues/concerns</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">3) drupal-id.com continues to do nothing, is removed as the</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">maintainer, and everyone interested has a rational discussion about</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">how best to move forward</DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>These three options are a no-win. This is not some power struggle and nobody is going to walk away with a prize. While it's somewhat of a privilege to be the maintainer of a highly-used module, it's also a huge pain and a thankless job.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The main issue here is that the cost/benefit for maintainership was too much for the original maintainer. Upon stepping down, nobody but Drupal-Id picked up the work effort. The good news is that he/she/they put forth some development effort, the bad news is that this came without community involvement, and therefore, the community needs where not adequately addressed.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The TinyMCE module is important to our business and our clients. Despite this, I'm embarrassed to say that I haven't taken any part in working the issue queue or otherwise participating in the care and feeding of this module. Now it has reached a critical situation, and many of us have been forced to act reactively rather than proactively.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I don't have the time and necessity to spend on theoretical changes (apparently, few do), but the lack of an upgrade path is the key matter of importance. Now, it's useful to fewer people, and making this seem like a contentious or competitive situation makes people feel even more disinclined to get involved. It's like "opposite day" in open source land.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>So now, I have enough motivation to make the time to maintain a 4.7-compatible "unfork" at <A href="http://drupal.org/project/moxie">http://drupal.org/project/moxie</A> . Boris and Steve McKenzie have agreed to help address some TinyMCE issues there, and we will work on it there for as long as is necessary.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>If, on top of clearing issues and meeting the community's short-term needs, someone *still* has time to expend on these feature changes, then great! We may have found a "real" maintainer this time around :P</DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Meanwhile, I am trying to clear as many issues from the TinyMCE queue</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">as possible.<SPAN class="Apple-converted-space"> </SPAN>Suggestions about leaving the 4.7 feature requests open</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">or pointing those users to the Moxie "unfork" and closing the issue?</DIV> </BLOCKQUOTE></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>As long as Drupal-Id is continues committing to the tinymce project, we have no right to remove maintainership, even if we disagree with his/her/their decisions.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I really appreciate that you want to help clearing out the issue queue - that's the most important thing we can be doing now. We're creating a clean-up rallying point around moxie, and it would be great if you could direct issues there. For everyone else who feels like they need a little give/take karma on TinyMCE, please lend a hand in this!</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Doing it this way lets us dispense with this frustrating discussion. Everybody gets what they need in the short-term, bugs get fixed in a maintained branch, nobody's getting publicly flogged for their development choices, and we can all get back to work. Later, we can revisit a merge when/if one module is bug-free and can address the needs of both user sets.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR><DIV><DIV>Allie Micka</DIV><DIV>pajunas interactive, inc.</DIV><DIV><A href="http://www.pajunas.com">http://www.pajunas.com</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>scalable web hosting and open source strategies</DIV></DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>P.S. I don't disagree with the motivations for some of these changes, From here, it seems that it would be easier to add the js-files-as-editable from the 4.7 interface rather than starting from scratch. (by writing them to the files directory rather than putting them in a db table). Keeping what's useful and blending in your requirements.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Courier New" size="3" style="font: 12.0px Courier New"></FONT></P> </DIV><BR></BODY></HTML>