CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • General Discussion (please no support requests here!) (Moderator: Michał Mach) »
  • Streamline CiviCRM issue specific funding
Pages: [1]

Author Topic: Streamline CiviCRM issue specific funding  (Read 222 times)

ñull

  • I’m new here
  • *
  • Posts: 10
  • Karma: 0
  • CiviCRM version: 4.6.8
  • CMS version: Drupal
  • MySQL version: 5.5.41
  • PHP version: 5.4.39
Streamline CiviCRM issue specific funding
September 25, 2015, 02:12:48 am
In the issue queue I see them marked:

> Funding Source (see https://civicrm.org/issue-queue): Needs Funding

When I go to the link I can read a lot of funding unspecific information and nothing about how to actually fund an issue.

Wouldn't it be great to have it all right there in the issue? The estimated necessary work hours, price, how much already funded and how much still needed and a link to directly donate toward that issue?

I mean just the text "Needs Funding" without any hint how to actually do it specifically for the issue,  doesn't give me an encouraging impression. It leaves you with thoughts like, "Ah, why bother, let's live with the issue, too difficult to donate and it remains unsure my donation will in fact be dedicated to that particular issue".

The end result could be a growing number of what is considered "minor", "low priority" issues with little chance of ever being addressed with as sum total a product that is slowly deteriorating in quality and attractiveness.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • General Discussion (please no support requests here!) (Moderator: Michał Mach) »
  • Streamline CiviCRM issue specific funding

This forum was archived on 2017-11-26.