On Sun, Feb 22, 2009 at 8:25 AM, Bernhard Schussek <[email protected]> wrote: > > Hi Tom, > > While I agree with you on this point, I don't agree that choosing > plugin prefixes unique to your company are the solution. As I said > before, plugins are a community effort and thus should be community > driven. If other developers join your team, why should they develop a > plugin that is published in the name of your company? Such an attitude > only weakens collaboration.
This is a valid point, but in the real world other developers are not exactly breaking my door down asking permission to contribute to any of my plugins. Most of the time a few "burning souls" do most of the work on any given project. If I was seeing strong interest in contributing in a major way to a plugin I'd initiated, and the catch was that they wanted the plugin to have an 'sf' prefix, I'd probably say yes. The prefixes also serve to keep the sf namespace clean for new core plugins and they prevent me from getting stuck if somebody *else* abandons a project which is camping on the "right" name for something I want to do. > A different and better approach would be to honor these companies on > the page of the plugin. Just as the authors are presented right now, > the companies could be presented together with a short description and > a link to the company website. That's a good idea. > If, at last, your plugin is just a way of showcasing your company and > you do not want other developers to join the team, you really should > not publish it on the symfony homepage. However your motivations, it > will always be a risk for others to use plugins maintained by one > single company only. As soon as the company moves to other goals or > has no time to fix bugs or develop new features, plugin development > will be condemned to stagnate. Worst of all, the community will not > even be able to fix this. Well, no, this is what open source licenses are for. Anybody can pick up any MIT-licensed plugin and fork it tomorrow morning, if need be. And that has happened in the past in other open source projects when the original developers lost interest. > If the latter is the case for you, I suggest that you remove your > plugins from the official plugins page and set up a custom plugin page > on the website of your company. This will be much more effective to > demonstrate your company's activities. Other developers using your > plugin, though, will clearly know that they now are dependent on you. The "official plugins page" has always had facilities to link to a home page somewhere else, a repository somewhere else, and a ticketing system somewhere else. This has always sent the message that it's perfectly okay to list third party Symfony plugins in the official directory. And it should be, because making people aware of Symfony resources is in the interest of the Symfony project as a whole. -- Tom Boutell www.punkave.com www.boutell.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
