Re: [development] sandboxing releases
I would like to plead -again- to open up the sandboxen for such modules, projects and ideas.
i personally don't object to this. however, please (re)read my last reply on the previous sandbox thread, for some concrete suggestions on why contributions/modules was a better alternative than contributions/sandbox/ber, even if you don't maintain (or even create) official project nodes for any of them: http://lists.drupal.org/archives/development/2006-12/msg00193.html cheers, -derek
Op maandag 26 februari 2007 09:31, schreef Derek Wright:
i personally don't object to this. however, please (re)read my last reply on the previous sandbox thread, for some concrete suggestions on why contributions/modules was a better alternative than contributions/sandbox/ber, even if you don't maintain (or even create) official project nodes for any of them:
http://lists.drupal.org/archives/development/2006-12/msg00193.html
Thanks. I never got as far as that message, the thread was huge :) It makes a lot of sense to me, and it sounds like a fair deal to simply commit all my 'in progress' or 'schetchy' works to the main contrib repository indeed. I think it also would make sense if everyone started doing it. Bèr -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: www.sympal.nl
Bèr Kessels wrote:
It makes a lot of sense to me, and it sounds like a fair deal to simply commit all my 'in progress' or 'schetchy' works to the main contrib repository indeed. I think it also would make sense if everyone started doing it.
I *do* agree with adding these useful modules to contrib. I've often found myself in the position of having somethign useful but not something i wish to maintain. The problem remaining in my opinion is discovery. The cvs folder names are a bit ambigious to say the least. The project nodes really help outline the functionality and differentiation from the other modules. Would it be possible to make some sort of development only project node? In my eyes this is a project node with only the "HEAD" branch and maybe these could be filtered from the project list on d.o unless specifically unfiltered. That way we can discourage or prevent normal passer by users form discovering the modules and installing them while still providing some information and context for interested developers looking to extend or maybe even adopt said module to provide proper support. -- Michael Favia michael@favias.org tel. 512.585.5650 http://michael.favias.org
Op maandag 26 februari 2007 16:26, schreef Michael Favia:
The cvs folder names are a bit ambigious to say the least. The project nodes really help outline the functionality and differentiation from the other modules.
People who know how to do CVS checkouts, also know how to search (grep/spotight/locate/beagle etc) them. IMO 'the people who may need it, will know where to find it'.
Would it be possible to make some sort of development only project node? In my eyes this is a project node with only the "HEAD" branch and maybe these could be filtered from the project list on d.o unless specifically unfiltered.
It is already possible to create project nodes, with no releases. Even with the issues siwtched off. Or with only nighly snapshot releases. Or any combination. So I would say that the contribs are safe enough to stick your work with a 'discovery node' attached to it. Bèr -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: www.sympal.nl
Bèr Kessels wrote:
So I would say that the contribs are safe enough to stick your work with a 'discovery node' attached to it.
That is all i was suggesting. a little structured information goes along way. I can presently grep through the projects but i get a lot of false positives too. We have some good tools for searching and categorization on d.o and i was just suggesting that we utilize them for such modules without releases. I was also suggesting no displaying those modules (un released) *by default* to prevent the less informed public from hamstringing themselves. But if you think they can handle it then i have no objection. thx. -- Michael Favia michael@favias.org tel. 512.585.5650 http://michael.favias.org
participants (3)
-
Bèr Kessels -
Derek Wright -
Michael Favia