I think it's easy and tempting but ultimately counter-productive to focus on who's right or really gets it or works in the real world. If it were a simple, one-sided issue, it wouldn't be a problem. Really, if you remove the specifics, it's yet another debate about what Drupal should or should not include. This seems natural and inevitable: the many flavors of *nix exemplify, in my mind, that even in the OSS world different people have different needs and want their needs prioritized first (security, usability, stability, maintainability, etc). It also seems pretty difficult to expect everyone to agree on what the community's needs are, let alone what the order is. (And hey, the founding members of the community have been pretty amazingly successful at meeting most needs through the modular design.)<br>
<br>So while we could say 'fork it', walk away, or continue to have these passionate but inherently divisive discussions on a case-by-case basis; we could also recognize our common interests and gains by working together and focus on finding an inclusive solution. That doesn't have to mean compromise, it's not always a binary world. Globally speaking, I say we concentrate all this energy into discovering creative solutions.<br>
<br>Warm Regards,<br>Tim<br><br><div class="gmail_quote">On Mon, May 25, 2009 at 11:25 AM, Naheem Zaffar <span dir="ltr"><<a href="mailto:naheemzaffar@gmail.com">naheemzaffar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think many people will be happy with a(n easily customiseable/extendable) tag editor in core - even those who want a full fledged wysiwyg, if their only other option is no editor in core at all.<br><br>I myself prefer a simple tag editor too - it also has this "ability" to strip out all the extra markup when copying and pasting from word...<br>
<br>Ofcourse most developers, if asked for an opinion will choose the editor they like and personally prefer to be the one that is included in core, but that cannot happen, so what is probably needed is someone to lead the effort. Someone who has buy in with the developers to decide "This is the editor that we want in. Either it gets in or nothing" and after that point, I suspect most of the bike shedding will be less common and people may try to work on the actual issues to get that to happen.<br>
</blockquote></div><br><br clear="all"><br>-- <br><br>Tim Loudon<br>t: 781.686.6096<br>e: <a href="mailto:tloud365@gmail.com">tloud365@gmail.com</a><br>