John Hampton wrote: > I have semi-officially taken over maintenance for the GitPlugin.
Hey, that's great! > Part of my reason for this is that I have an irrational hatred for > single file plugins. Don't ask for the reasons, cus they aren't really > good. Suffice to say, I don't like them and I think they should be used > as little as possible I understand the feeling, mostly because I have the same feelings for eggs, though less intense it seems ;-) > I think this is better because: > a) easy_install is fairly easy Sure, easy_install is... well, easy, but no_install_at_all is even easier. > c) if one actually enables the full tracext.* namespace, then they > don't inadvertently enable plugins that they didn't want but didn't know > were installed. I would rather discourage such practice. > This brings up the question of "enforcement". In addition to the > plugins already on trac-hacks.org that Tim mentioned, the > ActiveDirectoryAuthPlugin also uses the tracext.* namespace. > > So, what are the rules/requirements/etc for using tracext.*? I realize now, after re-reading my original post, that my proposal was confusing, probably also due to the disproportionate length of the post compared to the simplicity of the proposal. So let me try to reformulate. There are three very useful, but optional features packaged with Trac. Activating and updating them is more difficult and error prone than strictly necessary. My goal was simply to move them from one folder (sample-plugins) to another (tracext), and to mark that folder as a namespace. That was all. The fact that they are currently packaged as single-file plugins is not really relevant. All I wanted is that they can be enabled with a single line in trac.ini, or through the plugin admin panel. I proposed "tracext" as an analogy to "hgext", but I realize that this brought more confusion, and suggesting that it should be a namespace added even more. And the "quality" criteria I mentioned were only intended to explain why these three files should be moved from "sample-plugins" and not the others. So maybe at this point I should retract the "tracext" namespace, and instead suggest we move them to a new "tracopt" top-level *package*, or a "trac.opt" package whose components would be disabled by default. This will avoid any conflicts with external plugins while still reaching my goal. Yes, that sounds like the simplest solution. -- Remy
signature.asc
Description: OpenPGP digital signature
