June 2006 - Development - lists.drupal.org

Re: [development] cron vs poormans cron [was download statistics for core]
by Kobus Myburgh 03 Jun '06

03 Jun '06

> This makes me think that there are really two types of scheduled tasks > in Drupal; those that need to happen even if the site is inactive > (sending a mail queue), and those that only need to happen if people are > visiting the site. Poormans cron does a great job of the latter, but > can't guarantee the former on a low-traffic site. An elaborate but > ... Not even I have such a low traffic site that poormanscron doesn't work. I currently have two sites sending out mailing lists with poormanscron, and they are relatively small user bases (59 and 230 users respectively, currently 61 and 1022 nodes respectively) and the recipients get the mailinst lists just fine, albeit sometimes a few minutes later than anticipated, but does that really matter? Kobus

1 0

hook_depend()
by Doq Doques 03 Jun '06

03 Jun '06

Hi. What about implementing hook_depend(). I mean module that depends on some module (e.g. taxonomy) must define function modulename_depend() { return array('taxonomy'); } Then if user has no taxonomy module turned on - he/she will be asked to do so or not. If not - he/she will be told that modulename can't be installed. Also when user disables taxonomy module then he/she will be told that modulename depends on taxonomy module and so modulename will be also turned off.

9 13

New Drupal powered site soon
by Bertrand Mansion 02 Jun '06

02 Jun '06

Hi, This site : http://www.cg94.fr will soon be Drupal 4.7 powered (in two weeks). My customer 'Le Conseil général du Val-de-Marne' [1] wishes to make a donation, I now have the money for it. Could the people in the community responsible for money stuff contact me privately to arrange this ? Thanks in advance. [1] http://en.wikipedia.org/wiki/Val-de-Marne -- Bertrand Mansion Mamasam Tel : +33 1 48 89 88 26 http://www.mamasam.com Creative Internet Solutions

1 0

rather useful data
by Dries Buytaert 02 Jun '06

02 Jun '06

Would love to have similar Drupal video's: http://www.betterdesktop.org/wiki/index.php?title=Data -- Dries Buytaert :: http://www.buytaert.net/

2 1

Drupal 4.6.8 and 4.7.2
by Gerhard Killesreiter 02 Jun '06

02 Jun '06

are now available. Cheers, Gerhard

1 0

Anyone seen vauxia?
by Dan Robinson 01 Jun '06

01 Jun '06

We've been working with her send, premium and guestpass modules. We've found a bunch of bugs, submitted some patches and have tried pinging her to see if she's still maintaining these. Anyone seen her around? Thanks, Dan

5 8

tango icons no longer "allowed" in contribs.
by Bèr Kessels 01 Jun '06

01 Jun '06

Hello fellow developers and themers. First of all, I hope we can all hold our breath, and fingers and not start another thread out of this. You might not agree, but leave that for other times and places. Thank you ;) Tango icons use Creative commons (CC) as their licence. Whether or not CC is compatible, transformable, integratable or anything else is not the point here. The result is that you cannot use tango icons in contribs, as was our policy for a while. If you have a project using tango (or any CC icons or work, in fact) make sure you either replace them with your own work or one of the various nice GPL icons around. Make sure you do this an all branches (releases). If you find modules that still use tango icons, or any other incompatible licence, please contact the owner, or leave an issue in the queue for that project. Dries -and the other contrib maintainers- want to keep contribs Pure GPL. This is for simpicity. « We're not lawyers, so let's try not to make up our own rules, or mix licenses without knowing what we are doing. » -- Dries With regards, Bèr

1 0

RE: [infrastructure] Re: [development] Drupal 4.5 unsupported
by Steven Peck 01 Jun '06

01 Jun '06

> -----Original Message----- > From: development-bounces(a)drupal.org > [mailto:development-bounces@drupal.org] On Behalf Of Larry Garfield > Sent: Tuesday, May 30, 2006 10:48 AM > To: development(a)drupal.org > Subject: Re: [infrastructure] Re: [development] Drupal 4.5 unsupported > > On Tue, May 30, 2006 8:59 am, Khalid B said: > > On 5/30/06, blogdiva(a)culturekitchen.com > <blogdiva(a)culturekitchen.com> > > wrote: > >> That's an awesome question. I'd like to hear from > developers and the > >> people in the marketing team. The question is at the core of what I > >> feel Drupal is overlooking at the moment --code freezes. > > > > Code freezes do happen. Once we have a release, its API > does not change > > (may be a tiny bit occasionally, but not normally). > > > > What we do not freeze is APIs between releases. How can we > move forward > > from 4.7 to 6.6 with the API remaining the same? Where would the new > > stuff go? Are you advocating we keep APIs forever? > > > > Read my comment here on where the energy should be focussed > (migration > > tools, > > transitional releases, and compatibility layers). > > > > http://baheyeldin.com/node/617 > > Honestly, I think part of the issue with the "stable API" > question is that > Drupal uses version numbers differently from many projects. > The de facto > standard for version numbers for most projects is > Major.Minor.Bug / x.y.z. > > Z increases only fix bugs. > Y increases add features, but don't break backward > compatibility with 3rd > party code. > X increases, all bets are off. > > Witness, for instance, KDE, which has evolved and improved > dramatically in > the 3.y.z cycle, but code for 3.0.0 still (generally) works > in 3.5.1. For > the upcoming 4.0, howver, there are no "sacred cows" and > everything will > need to be updated. > > For Drupal, Y increases, all bets are off. We technically > don't have Y > releases, just Z and X, but we use both of the first two > numbers for the X > releases. That throws a lot of people off. It actually > surprised me a > great deal, although fortunately it didn't affect my plans > significantly. > > Whatever else we do, we should probably make that clearer > right up front. > It's not inherently a bad development model, just an > unconventional one > that needs to be made clearer. > > --Larry Garfield > How much more clear can I make this? http://drupal.org/handbook/version-info The alias is recent but it has been at the top level of the handbook now for about a year. Should we link it in the Project download page for Drupal? There are other projects that use different from KDE versioning release scheme's as well. Drupal's been consistent for the 3 years I've used it with it's versioning information and method. The versioning scheme has not changed at all. -sp

12 19

GPL policy: request for clarification
by Nedjo Rogers 01 Jun '06

01 Jun '06

The GPL appears to allow us to combine GPL and "compatible" code in a single GPL-licensed package. Can we include such code in drupal.org CVS? This is a pressing issue because there is considerable interest in using external GPL-compatible but non-GPL Javascript libraries (Prototype, jQuery), at least in contrib and possibly as candidates for core. Our CVS policy states "All code must be licensed under GNU/GPL" (contributions README.txt). The practice has been to interpret this as meaning that open source libraries with "MIT" or similar licenses may not be included in Drupal CVS. However, the Free Software Project has designated a number of licenses, including the "MIT" license, as "compatible" with the GPL, because they impose no restrictions that conflict with the GPL, see http://www.gnu.org/philosophy/license-list.html#GPLCompatibleLicenses. The GPL FAQ specifically states, http://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean, that the GPL permits you to "combine code released under the other [compatible] license with code released under the GNU GPL in one larger program" privided that "such a combination ... is released under the GNU GPL". In other words, apparently, we can GPL the combination of GPL code and code with compatible licenses. So, it appears, we should be free to include "MIT" and other compatible-licensed code in our CVS and releases, provided we make it clear we are thus GPL-ing the combination. So, can we go ahead and put such combinations in CVS? Can we consider/propose them for core?

9 11

Re: [Drupal feature] Personal Contact SELECTED BY DEFAULT, even MANDATED
by Steve Dondley 01 Jun '06

01 Jun '06

I helped write a patch that already addresses this and it has been committed to the head: http://drupal.org/node/41352 On 6/1/06, pwolanin <development(a)drupal.org> wrote: > Issue status update for > http://drupal.org/node/66648 > Post a follow up: > http://drupal.org/project/comments/add/66648 > > Project: Drupal > Version: cvs > Component: contact.module > Category: feature requests > Priority: normal > Assigned to: Anonymous > Reported by: iandickson > Updated by: pwolanin > Status: active > > Yes, I agree. I think people joining a site are already opting in, so > it makes more sense to have this on by default. I'd almost categorize > this as a bug and push for inclusion in 4.7.2... > > > > > pwolanin > > > > Previous comments: > ------------------------------------------------------------------------ > > Thu, 01 Jun 2006 06:55:01 +0000 : iandickson > > In community projects it is often the case that members are not really > up for reading everything carefully. Upshot - they miss the box and > wonder why no one contacts them..., so I'd like to be able to set > Personal Contact ON by Default. (User can disable if they wish). > > > I'd also like an option to MANDATE it so it can't be disabled by user, > (People get annoyed if they can't contact a provocative poster). > > > Note - I went looking for this and found threads in which people who > needed this function had posted mod hacks to do it. Which I won't use - > too hairy - but shows how important it is. > > > General Comment - this is a Usability Issue - a key role of Admin > should be to ensure that member defaults are designed to minimise the > work that work that members need to do, so any check box that it is > expected peoiple will tick, should be defaultable ticked. > > > > > -- Dondley Communications http://www.dondleycommunications.com Communicate or Die: American Labor Unions and the Internet http://www.communicateordie.com

1 0