I'm sure that a developer with a module ready will not back away once
he sees you require him to simply use a proper release rather than a
dev release. I mean to think this would make the entry level higher
seems a little of an over statement.<br>
<br>
Why does naming your releases suddenly make it a commitment to users or
anything major and against open source? It's ready when it's ready, and
it's ready when it's released. Try to line up some clear arguments
against enforcing proper releases. Garbage code can be in a dev or in a release, at least garbage in a release can tell us which release to avoid.<br><br>Enforcing releases is neither cruel to developers, doesn't hurt the open source spirit, doesn't dictate any new requirements on developers as even current releases have no restrictions whatsoever.<br>
<br>What do releases do? They make update module work better, they make user's lives easier cause they don't have to wonder which "dev" release they're using without going to check on file dates and so forth, they make things less chaotic. Releases don't mean a developer is guaranteeing anything or losing any flexibility. I see nothing bad in enforcing them at all.<br>
<br><div class="gmail_quote">On Feb 18, 2008 4:39 PM, Earnie Boyd <<a href="mailto:earnie@users.sourceforge.net">earnie@users.sourceforge.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Quoting Ivan Sergio Borgonovo <<a href="mailto:mail@webthatworks.it">mail@webthatworks.it</a>>:<br><br>><br>> I think it is in the right of drupal infrastructure team to impose<br>> minimum requirement so that your module is hosted and advertised on<br>
> drupal infrastructure and associated with drupal project.<br>><br><br></div>Nope. Drupal and therefore its contributed modules uses the GPL<br>license which guarantees that I can do what ever with it including<br>
hosting it else where.<br><div class="Ih2E3d"><br>> drupal project is free to impose or not impose any rule.<br><br></div>Not if the rule violates the license.<br><div class="Ih2E3d"><br>> They do... and you'll have less developed modules.<br>
> They don't... and the the quality of modules will be lower.<br>> All this reflects on the image and technical merits of drupal project<br>> as a whole.<br>><br><br></div>Maybe. Or perhaps it would less favorless on the project if Drupal<br>
decided not to host contributed modules at all. There is a learning<br>curve and there are suggested procedures with the contributed module<br>conventions. Enforcing them is a community effort and if you find a<br>module that doesn't align with the suggested procedures you can open an<br>
issue with the project.<br><div class="Ih2E3d"><br>> It doesn't look scandalous.<br>><br><br></div>Yes it does because what you propose violates the license.<br><br>Earnie -- <a href="http://for-my-kids.com/" target="_blank">http://for-my-kids.com/</a><br>
-- <a href="http://give-me-an-offer.com/" target="_blank">http://give-me-an-offer.com/</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Ashraf Amayreh<br><a href="http://blogs.aamayreh.org">http://blogs.aamayreh.org</a>