February 2006 - Development - lists.drupal.org

using #downloads for quality of modules
by ae2005 21 Feb '06

21 Feb '06

one quick proxy for measuring quality of modules could be number of downloads, like the list kieran posted. presumably the most downloaded ones are relatively stable, due to research and filtering done by individuals first. i do think it'd be great to keep a list of top downloads in a very easy to find place on the site. ae

16 28

updating creative commons module
by Moshe Weitzman 21 Feb '06

21 Feb '06

I have been unable to get a reply from the maintainer of the creative commons module - http://drupal.org/node/17497. Does anyone know how to contact him (digibike), or does anyone want to just go ahead and upgrade it? You can probably assume ownership of the module too since it appears abandoned. I need it for an upcoming project. -moshe

2 1

Removing criticals: day two
by Karoly Negyesi 21 Feb '06

21 Feb '06

Hi! We are making big, big progress. We have closed / reclassified lots of critical bugs and even patched some, and we saw them committed. Can we do another ten today? Let's try! I already assigned one to myself, maybe I will have time for another, most likely the contact one which I think is obsoleted by the form choice checker. Keep on the good job folks! Thanks Karoly Negyesi

2 1

Re: new install hook examples, .install files
by Chad Phillips -- Apartment Lines 21 Feb '06

21 Feb '06

> > Please re-open this issue and submit any improvements while the > deficiencies are still fresh in your mind: > http://drupal.org/node/48722 > > Thanks, > andrew done, and a patch is submitted which corrects said deficiencies. can you please review and commit?

2 1

new install hook examples, .install files
by Chad Phillips -- Apartment Lines 21 Feb '06

21 Feb '06

i spent a few hours getting my HEAD modules using the new core install hook. i found the developer docs to be just a bit confusing, but was able to get things right after a bit. anybody who's interested in looking at some working examples, see eventrepeat.install or signup.install in HEAD contrib. since the hook is called from a full bootstrap, you can actually do a heck of a lot more than just install tables--in my case i also displayed some user messages regarding the status of the module installation, and in eventrepeat's case, i invoked eventrepeat_cron() to autopopulate a table w/ current date information. i'm loving this change! :) chad

2 1

RE: [development] no 4-7-0 branch for core yet?
by Walt Daniels 21 Feb '06

21 Feb '06

Typo 5.12+ not 5.13+ > -----Original Message----- > From: Walt Daniels [mailto:wdlists@optonline.net] > Sent: Monday, February 20, 2006 4:51 PM > To: 'development(a)drupal.org' > Subject: RE: [development] no 4-7-0 branch for core yet? > > See http://drupal.org/node/43735#comment-92865 , dependent on > 5.13+ release. > > > -----Original Message----- > > From: development-bounces(a)drupal.org > > [mailto:development-bounces@drupal.org] On Behalf Of Tim Altman > > Sent: Monday, February 20, 2006 4:40 PM > > To: development(a)drupal.org > > Subject: Re: [development] no 4-7-0 branch for core yet? > > > > On Mon, 20 Feb 2006 22:15:05 +0100, Walt Daniels > > <wdlists(a)optonline.net> > > wrote: > > > > > Agree!!!! > > > Even after 4.7 drops, the contribs that I depend on won't > > be ready for > > > at least a while. Currently they are very badly marked as > to which > > > version they work with. The release policy must take the > > contribs into > > > account. You can't turn the releases unless the contribs > > can keep up. > > > > > > There are lots of remarks about things that work with PHP 4 > > or 5, but > > > none about things that work with MySQL 4 or 5. Dreamhost > > just went to > > > MySQL5 and I am stuck badly. So changes in these two > which have no > > > reason to folllow the Drupal schedule have to be factored into > > > possible Drupal schedules. I have a tight deadline of > > getting off my > > > current ISP (which dies March 29) and onto Dreamhost. > > Drupal 4.6 does > > > not work with MySQL 5 and 4.7 + its contribs is not likely > > to be ready > > > for production. > > > > I'm using 4.6.5 on Dreamhost without problems (that I know of).... > > Care to elaborate? > > > > -- > > Tim Altman

2 2

Drupal.org upgrade
by Dries Buytaert 20 Feb '06

20 Feb '06

If you want to help with the Drupal.org upgrade, here is what you can do: 1. Help categorize projects. See http://dev.bryght.com/t/wiki/ DrupalProjectCategories, and the discussion on development(a)drupal.org. 2. Go to http://scratch.drupal.org/ and test, test, test. Report problems using the issue tracker. (Example 1: the user profile pages are broken due to a bug in CVS HEAD. Just take a look. Clearly a show-stopper.) (Example 2: double-check whether the Drupal.org theme has been updated to comply with recent CSS changes.) 3. Look into optimizing the forum listings; ?q=forum is one of the slower pages. 4. Look into optimizing the cvslog module: ?q=cvs is one of the slower pages. 5. Follow-up and work on infrastructure issues: http://drupal.org/ project/issues/drupal_org_maintenance. You can also help with: 1. Project module development. 2. Improving the code checker script. 3. Importing CVS repositories in cvslog module. -- Dries Buytaert :: http://www.buytaert.net/

5 10

RE: [development] no 4-7-0 branch for core yet?
by Boerland, Bert 20 Feb '06

20 Feb '06

-----Original Message----- From: development-bounces(a)drupal.org > A time based release cycle has merits. timeboxing can -needless to say: when done correctly- be a very good way of running a project where needed functionality and available manpower outnumber the due date. it might be that with the grow of the Drupal community and installed base the first two constraints are indeed less scarce resources. switching from the current ("done when its done") way to a "done when its time way", just because the current progress is not up to the expectations of the larger part of the community, might be an unwise decision. note, i am in favor of having two releases per year, it makes the progress predictable, customers do understand the upgrade costs and lifecycle management (support of older versions) can be taken care of in a good way. however, before switching to this development model (only one can decide) everybody needs to understand the impact of it. before people start to complain, best to read http://en.wikipedia.org/wiki/DSDM#Prerequisites_for_using_DSDM

5 4

is 4.7 too complicated to fix? why not raise funds?
by qomo 20 Feb '06

20 Feb '06

On Mon, 2006-02-20 at 11:35 -0800, qomo wrote: > a question and some suggestions: > > 1) if we use timed release, and today were the release date, what would > we release? (I assume not CVS, since its bugginess changes daily.) > Would we release 4.7.0b4? If that's true, why not release 4.7.0b4 and > call it 4.7? > 2) I think it'd be good to call the next release 5.0. I think this is > less confusing to the user because 4.6 and 4.7 are so different, so much > more than 4.5 and 4.6 > 3) If Dries wants to have something the user can see, I'd say then just > make the new theme. For example, take the terrific new theme called > fancy, put some pretty colors on it, and a nice logo. Whola, a new > default theme. > 4) I wonder if the 4.7 release is being held up by lack of developer > time to work on bugs, or by a very complicated structure that's making > it too hard to get the bugs out. If it's the former, then we have a > serious problem. If it's the former, I'd suggest (coming from a business > perspective) that we > (a) identify the show-stopper bugs > (b) estimate how many hours it would take to fix them > (c) multiply that number by a developer's hourly rate > (d) put a big button on top of drupal.org asking for donations. > > e.g. > (a) there are 3 show stopper bugs > (b) 16 hours each > (c) 48 * 100 = $4800 > (d) put on a big button on top of home page saying if each person > donates 10 to 30 dollars, we would only need 240 people to donate. > that's less than 10% of people browsing the site at this very minute. > > sorry, I'm not a developer, so this idea may be based on ignorance. > but as someone who is not a developer, I now think it's less confusing > to call the next release 5.0 because of all the new powerful features > being added (and will be added due to the power of form api) than to > call it 4.7. > > Ann >

1 0

Re: [infrastructure] [task] Spreadsheet of Drupal 4.6 modules and their terms in categories
by Dries Buytaert 20 Feb '06

20 Feb '06

> I still want to go through and make sure that at least the 25 > modules in the taxonomy garden have the term category. I finished the parser and tested it on scratch.drupal.org with the latest spreadsheet taken from http://drupal.org/node/50091. You can see the result at http://scratch.drupal.org/project/Modules. (Whenever the spreadsheet is updated, I'll do a fresh import.) Please take some time to test it out. If you have suggestions for user interface improvements, please post these to the project module's issue tracker (http://drupal.org/project/project) Thanks! -- Dries Buytaert :: http://www.buytaert.net/

4 4