[drupal-devel] CivicSpace development moving to Drupal
killesreiter at physik.uni-freiburg.de
Thu Mar 24 10:46:10 UTC 2005
On Thu, 24 Mar 2005, James Walker wrote:
> On 16-Mar-05, at 12:14 AM, Gerhard Killesreiter wrote:
> > I have told Dries somewhere between FOSDEM and Antwerp that I'd like to
> > see that he'd assign bugs to people. An advantage might be that those
> > bugs would a) get a patch sooner and b) that patch would be committted
> > sooner to cvs because Dries c) cares about that bug and d) would maybe
> > give some hints about the sort of solution he'd like to see.
> +1 (with a big "+").
Thanks. I'd really like to see the Drupal project advance a bit faster
than it does now.
Currently, I am often not sure if it is worth my time to work on a
specific bug/feature as I have not much of an idea if (and when!) it
will make it to core. I guess there are more people like me.
> Might even be better (even if as a longer term solution) if there
> was a way to have issues for "components" automatically assigned to
Would be nice, yes.
> I know I know ... "feel free to patch project.module". But,
> personally, it would speed response up greatly if, say, all
> image.inc issues automatically showed up in "my issues" (and
> consequently in my issue feed).
Well, you can subscribe to the Drupal project and get all those things
mailed. Some procmail magic might even sort the image.inc mails into the
right mailbox. I know, not really what you want.
> I mean, I realize this delegation sorta happens now informally...
> but I also know I've been asked to have a look at patch X and if I
> don't do it right away (or make a note to do it later) I forget.
Yeah, like the message_access() patch. ;)
And no, I don't think I'd like to introduce the kind of bureaucrazy that
Nedjo proposed. ;)
More information about the drupal-devel