[drupal-devel] CivicSpace development moving to Drupal

Gerhard Killesreiter killesreiter at physik.uni-freiburg.de
Thu Mar 24 12:50:42 UTC 2005

On Thu, 24 Mar 2005, Dries Buytaert wrote:

> On 24 Mar 2005, at 11:40, Gerhard Killesreiter wrote:
> > 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.
> I'm compiling a detailed list of things I believe are core-worthy and
> which I'd like to see included or worked on.  I'll share this list as
> soon as it's ready.  At the top of my head, in no particular order and
> lacking details:


I'll remove the items I am not interested in. The remaining list will
show which areas I am interested in and hope to join/lead an effort to
get that into core. I suggest that others do the same and we compile a

> 1. Workflow actions (and e-mail subscriptions/notifications in
> particular)
> 3. Profile fields per role
> 7. Folksonomies and taxonomy improvements
> 8. CCK

> 9. Improved administration structure, visual distinction, intuitive
> placement of settings

Maybe we can finally agree that it is a Bad Thing(tm) that menu items
move when translated...

> 10. Improved versioning


> 14. Contact module extension to let you contact groups of people.

Moshe has some code for contacting groups of people in og.module. I
borrowed that code for groups.module and extended it to honour the
"contact" preference of the individual users so that users can disable
those group mails.

> 16. Improved 'my account' page.

What kind of improvements?

> 17. One node-level permissions scheme (taxonomy-role?)

There are currently taxonomy_access and node_privacy_byrole.
taxonomy_access could use some codeing style cleanup. I have used a
previous version of taxonomy_access and do like it.

> 18. Better file handling/serving (permissions)

Yeah, the current private download is sub-optimal as the whole Drupal
is loaded per private file, ie if you have a user listing with 10 user
pictures and use privatze downloads, Drupal will be executed 11 times...

I've investigated to use an Apache module for this. The result isn't
quite clear atm (and not usable for most users I know). There could be a
small files.php file which does the file serving. This depends on the
split up of the .inc files in files that contain code and files that
execute it which I presented a short while ago.


More information about the drupal-devel mailing list