Mr Leers.

I think if you put up a chip in, you would get an especially positive response from a lot of people (me included).

We all realize that this is an especially complicated module and takes an especially talented programmer.
Since this is the only module that provides the necessary functionality to make taxonomy et al really work, there are a lot of people would be glad to contribute to allow you to fulfill your vision of what H.S. 4 could be.

Many modules are sponsored by one company. How about collective sponsorship by the community?

Comments

dgastudio’s picture

dgastudio commented

+1

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Version: 7.x-3.0-alpha2 » 7.x-3.0-alpha3

I deeply appreciate this gesture! Thanks, MrPhilbert & Kervi!

However, given the fact that I'll be doing an internship at Facebook, I can't tell with any amount of certainty whether I would or would not be able to start working on HS 4 by a given date.

I'm not sure if it'd be appreciated by many if I'd start a ChipIn *now*, but don't offer an ETA on HS4.

What do you think? :)

avilao’s picture

avilao commented

Hey Wim

Any new developments about your job? Is the chipin still off the table?

Regards

kars-t’s picture

kars-t commented
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed"

If there is new information, please re-open the issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.