Share Your Drupal Wishlist

1. I want flexinode in the Drupal core with the possibility to easily theme the content page, teasers and lists.

2. I want a more powerful Authorization and Permission system, like for example LiveUser (http://pear.limbourg.com/) with the possibility to create Areas (maybe using the taxonomy system?). I think the Auth and Permission containers would add some more flexibility (which is drupal style).

3. I want some theme switches for the taxonomy lists (or theming with keywords like someone already implemented).

4. I want a media browser with the media being decoupled from the node system, and the possibility to embed this media in every content type (optionally as inline content or hotlink). Uploaded files with image types should get a thumbnail generated with GD or imagemagick. There should be the possibility to give users and user groups the right to create such media content, with quota on a per-user basis.

There is also already a place for wishes (search for feature requests by changing the category). If anyone has specific ideas for enhancements to Drupal core or contributed modules, be sure to place a feature request.

Two things about feature requests:

1) Make sure your feature request has not already been made. If it already exists, don't create a new one but rather add your thoughts to the existing one.

2) Unforunately, there's no fairy god mother for granting wishes/feature requests. Nevertheless, a feature request can be useful. Throw your idea out there, for if a developer is working on something related, they may see it and think "that's a good idea" and end up implementing it.

Dries wants a Porsche which does not mean he is going to get one any time soon....
What is the purpose of this list? If you need something specific you can set up a bounty.
--
Drupal services
My Drupal services

I want every user to donate one when a developer spents a day of his or her life fixing issues, adding features, maintaining contributions and fixing CSS bugs in themes. Yea! And then you get it VERY cheap. normal prices are €50 an hour. So a whole day of coding could buy you 4 of these toys.

http://www.robosapien.nl/

---
if you dont like the choices being made for you, you should start making your own.
---
[Bèr Kessels | Drupal services www.webschuur.com]

I have no problem with people making wishlists. Wishlists indict areas of growth and niches to fill.

I do have a problem with people insisting that 'someone' has to fix 'it'. Post a patch if you can, and don't whine if you can't.

I have no problem with people saying 'Drupal could use improvement.' Everything can use improvement in life.

I do have a problem with people who don't take the time to learn how drupal does things. Drupal has a unique and powerful way of doing things. It's not intuitive at first, but it scales well, and it's proven to work well.

I have no problem with anyone finding flaws/bugs in existing modules. Patches are welcome, but just documenting the problem is often a good start. File a bug on the project... NOT a forum topic.
Don't file duplicate bugs either. If you find an answer, post it.
If you don't get an answer, post a reward for the answer. Nothing gets more attention than cash in hand.

I do have a problem with someone asking for 'why can't you just port XYZ?, it works, just make it work with Drupal' If you want something outside Drupal to work with Drupal, then you go code the bridge. Nobody deep into Drupal will likely do it, it doesn't move the project forward, and it's unlikely to be worth the effort in the long run, since it's not built with Drupal standards/models. Rest assured, others have talked the talk too... few have returned with results. But a few have.... Be one of the few, not one of the many.

I have no problem with someone posting beta code to check out, even if they aren't a code wizard. Many of us enjoy testing beta code, and use it because it does the job. Patches and critics will happen... take advantage of that: release early and often. Posting "This doesn't work" with code will get an answer.... posting just a 'How do I?' might or might not.

I do have a problem without someone expecting handholding who admits they don't know php, or sql, but wants custom php/sql snippets (or full modules) which nobody else wants except for their own personal project. If you don't understand the language Drupal is written in, perhaps you should either pay someone to do the hard work, or spend the time to learn php/sql yourself.... Drupal is written in a very well coded way if you understand basic php and sql.

I have no problem with those who do custom work for pay and then release code under the GPL for the rest of us. No problem at all.
I hope to be one of those people...

I do have a problem with someone who expects free support, and complains when it's not timely enough. Good, Fast, Cheap: pick two. Drupal itself is free... and the warranty is simple: you break it, you can keep both pieces. Extended warranties are usually extra... and the bigger the custom problem, the more likely you won't get fixed for free.

I have no problem with someone posting bounties, asking for people to do consulting work, or otherwise paying the community somehow for coding Drupal solutions they'd like to see, even in kind with support and other code.

In other words: post wishlists all you want.... they'll likely remain wishes without someone paying for the wished items somehow.

Need Drupal friendly hosting? Many of us use Site5 with good results

I wish a strong drupal community. I wish to help to it. I like this project and want to help to grow. Now the problem is that Drupal community doesn't seem very structurate. It might be but it doesn't look like. I don't like either to see people saying: 'hey, you need to fix this and you'll have to do it because I'm not going to do it my self'. This is fine with a commercial product. It's not with an OS project.

So let's think on how drupal.org is helping other people to get into it. Other OS projects 'seem' to do it better. They might not be doing better but they look like. Let's learn from them. This page (http://typo3.org/teams/) is a nice example of what I'm saying.

Can Drupal.org have something like this? This is my wish. And I'm not leaving this to be done by someone else. Whenever Dries thinks this is important and decides to go for it (I know you are busy like all of us or even more) will find my self ready to get involved. Just give me a shout.

Once we have a well structured community, with its own 'departments' and each department with its own team, we'll be able to work more efficiently on usability, targeting users (marketing), managing human resources, planning core developement, bux fixing tracking, 'customer' support, community support, financing needs, desing, security issues, etc.

Although we all are part of an OS community we'ld need to think not just as developers but as 'business' owners and be as effective as business men are. Drupal's community is growing fast and will need to structurate very well soon or it might die of its own success.

Why don't begin by asking what other members of the community know to do? Let's see if we can have a nice list of designers, accountants, marketing consultants, human resources coordinators, thinkers, specialists in other things than coding, all of them convinced drupalers.

I really think drupal community need to be integrated not only by developers but also by other people with other skills who will help to grow drupal community safely.

Please, core developers, think seriously on this matter. Drupal 4.7 is very important and you have enough material to think of. Start to delegate other matters than coding on trusted people.

Let's go ahead!

---
Robert Garrigos
Personal site:www.garrigos.org
Admin of: www.escolasafa.info - www.societatbach.org

My wish would be for all folks who benefit from fine opensource projects such as drupal etc... to contribute if they can and not bitch about some obscure feature that they think they need.

:)~

Thomas G. Willis

I want a system for creating custom Flexinode table views or basically some templates for building Flexinode views with a parent child architecture. For example on my site I created a Classifieds Flexinode and associated Taxonomy vocab for it:

See it here

It would be nice to work out a better view system.

If you use the Classifieds link at the top it takes you to a Drupal Page I built that links to different views using Taxonomy browser and the directories and what not to give Classifieds maintenance a more central feel.

I also would like to see a good central document of alot of the $variables available out there for working with flexinodes and what not. Alot of this is in the phpTemplate engine documentation but greedy me wants more without digging into the core code.

I want to see the system start bundeling modules into module packs that alone would alleviate alot of the forum concerns as if you built the forum pack to include the quote, url, and smilie filters as well as the flat forum module and pieces like the BBcode modules it would help. Most people gripe about the forums because they have not grasped the modularized parrallel architecture of Drupal. I mean all the forum features are there to match any other CMS feature to feature however out the box it takes a good deal of setup and planning to mimic that. I would like to see also the Theme section focus on an area dedicated to custom forum themeing or maybe add the custom forum themeing to said module pack. This would really slick up the newbie install of Drupal and gain it wider acceptanve beyond the coders and the dedicated bloggers.

I would like more thought put into the BBcode modules to make them work better with the forums and in particular with the comments to really function more like the other WYSIWYG editors available for Drupal.

I would like to see the some of the better security and privacy pieces like flaxinode be part of core such as node privace, privacy by role etc. If not included maybe as another module pack called the advanced security/privacy module.

I think that is a good enough list to start with.

Ken

"I drank what?!?" -Socrates

It would be helpful to have (on drupal.org):

• ROADMAP at a clean URL: drupal.org/roadmap ( or node/12202 ?) and reference this clean URL at http://drupal.org/project/releases/">Releases, About Drupal and Contribute.
• KEYFEATURES for next core: I'm not sure if there is some official decision making like "Drupal Improvement Proposals".
• ARCHITECTURE DIAGRAM at a clean URL: drupal.org/architecture or maybe more something like XOOPS