Is a drupal-chipin integration module needed by anyone and if YES what features?

I think that the module could be more useful if the users would be allowed to set which chipins must be showed, and until when.
I agree that if the module simply shows a chipin set by the user, then it is possible to create a custom block, and use that instead.

The integration with some WYSIWYG editors is also an interesting feature, to which could be added a Drupal filter that allows the users to add a chipin at any nodes they create.

The module is very much needed. I had been looking for years and when I found this module unmaintained at the time, I had given up hope.

I've been holding back quite a few websites centered around the concept. A Wikipedia for corruption, in which users collaboratively compiled information on the corrupt activities of corporations and politicians. Each Wiki page on an entity would have a ChipIn module for an attorney's fund to address the problems listed.

Similarly, an invention site whereby users would list their ideas, crowdsource the funding necessary to bring them to market via a ChipIn module, and record which users contributed for later revenue sharing once the products had been brought to market. Crowdsourced development, essentially.

Some means of integration with the ChipIn data, such as how close funds were to their targets, would allow these sites to rank and display them to users on a listing page sorted on that basis. Funds which were nearly there would be displayed first, making it easy for users to help them finish reaching their target marks.

Some means of recording which users chipped in and how much would provide for later profit sharing on the projects they chipped into. (Edit: According to ChipIn, information on which users contributed and how much is kept by ChipIn, but accessible only to the organizer. This will work, and obviously deprioritizes the urgency and feasibility of implementing this feature.)

Providing Triggers for the Action module when a fund reached various points would allow for e-mails to contributors, as well as moving the project from one phase into the next (i.e., funding is complete, now onto collaborative development or action).

Eventually, an ability for Drupal sites to generate ChipIns on a user's behalf would allow the sites to share and act on the data, as well as to more reliably enable site revenue sharing and distribution.

Pasted from email discussions:

> Hi, the current maintainer of the module here.

Hiya! Thanks for picking up the ChipIn module. It's been greatly needed, and will allow so much to make the world a better place.

> 0th - thanks for your vision - it is much appreciated.

I've wanted to do this for so long. =)

> 1st: I have the following questions:
>
> Can you give me several detailed examples of how would you use this un-made
> module? I mean:
> "
> 1. I go to the create-new-chipin page.
> 2. I click on ...
> 3. Then I have a chipin instance that shows on ... via ...
> 4. When the chipin-amount goes to ... the module sends emails to...
> "

Sure thing! Things are made simpler with the Triggers, Rules and Action modules, which take care of most of it. For the majority of event handling, all you need to do is create Triggers and allow the site Admin to set them to fire at given events.

Use Case #1:

1. A site's admin configs his site, and sets the global ChipIn Triggers to fire at various events:

Trigger A is tripped when a ChipIn reaches it's 50% funding mark.
Trigger B is tripped when a ChipIn reaches it's 90% funding mark.
Trigger C is tripped when a ChipIn reaches it's 100% funding mark.
Trigger D is tripped when a ChipIn only has a few days left to go.

The admin then sets the Rules and Actions module to catch the Triggers and perform various tasks when tripped.

On A, B, and C, the site sends e-mail's to the particular ChipIn's subscribers indicating the funding status. (The site knows who's subscribed because they'll be subscribing to the project where the ChipIn is featured.)

On C, the Rules and Actions modules are also set to take the project into another state... whatever that will be for the site. Perhaps it means taking the project to a new status, allocating different permissions for various people involved. Perhaps it means that the project is moved to the frontpage, or that a different group of people is now sent an e-mail regarding a newly-funded project that's just waiting for their expertise in order to go active (read: "We have a paid job for you just waiting. Interested?") Additionally, funding is disbursed according to the site owner's policies: Perhaps 10% will go to the site itself.
Perhaps he's checked a checkbox in the ChipIn configuration settings that always tosses 1% to the ChipIn module's maintainer.

On D, the Rules and Actions modules send an e-mail to subscribers telling them that the ChipIn is about to lapse, and reminding them to get their funding in now, because the project is at %percent% funding and has %days% left to go.

Now, the site is ready to have ChipIn projects created.

Use Case #2:

1. Registered user goes to create a new project. He creates a new node of type "project" (or whatever the admin has termed it). The nodetype will have the ChipIn embedded within it, but it will also act as a frontend. The user doesn't go to ChipIn.com to create the ChipIn, because that wouldn't allow the site access to the fund's statistics (contributors, who contributed how much and so on) and so the Drupal site wouldn't be able to verify it... or handle it. The site will want to know these things because perhaps the site owner will want to boost certain privileges for the contributors automatically, comp them in some way, or leave a paper trail for later compensation when the funded project takes off and begins showing returns. So the nodetype features the form fields necessary to create a ChipIn, and the site takes the data and works behind the scenes with ChipIn to create it. The ChipIn is not created with the user's account, nor does the user have access to it, for reasons of trust. Instead, the ChipIn is created using the site admin's PayPal to prevent untrusted user from skipping off with the funding. It should be noted that acting as a frontend for the ChipIn site, and passing the data through to Drupal, is the majority of the ChipIn module's development effort.

2. The ChipIn is created by the site, and the widget is embedded in the project node. A variable is stored indicating the percentage of funding reached (which the site can only know if it knows both the funding maximum and the current contribution amount for the ChipIn, and which it wouldn't know unless it had access to the ChipIn account over at ChipIn.com.) The site is now free to display these projects on a given page, ranked by how close they are to being fully-funded, their creation date, searchable by any tags the project has, or any combination of the above according to site behavior.

3. Other users check out the project listings, and begin to fund projects. They'll view a project's node, contribute via the widget, and the widget will update. How the Drupal site will know the project has just been updated, I don't know. Perhaps the site will have a cron task to check for new contributions from ChipIn's site for each account, then update the percentage, number of contributors and so forth. It would be great to have a button users could click that would alert the ChipIn module to go check the particular ChipIn's data with ChipIn.com, not only to update upon user contribution, but as a way of checking whether there has been more funding via the widget recently that the site may not be aware of.

4. With the stats updated, the site re-ranks the list of projects when the relevant page is viewed; no work needed there.

5. As the funding levels reach various points, the Triggers A, B, C, and D are tripped. Rules and Action take care of them.

> Trying to get a more do-able plan for this module...
>
> Also 2nd:
>
> 2.1. Is there a way to fund this module's development?

I have projects that should be getting off the ground soon, but if they pan out it will be at least a month.
See also 2.2, below.

> 2.2. Are there any chances for me to get some royalties/profit in the longer
> term - from the fact that I am the dev/maintainer of this module? (for
> example - my getclicky module brings me a small amount of dollars each month
> due to the clicky affiliate program . Also another example of royalties is
> that my other modules have links to my company...) For me doing
> good/contributing does not interfere with some profit :) Any ideas concerning
> the chipin module in particular?

I'm glad you asked, because it was in mind when I was going through the workflow and realized that yes, a checkbox that would allow site admins to divert 1% of everything the ChipIn modules brings in to the ChipIn maintainer would be completely feasible. Why shouldn't Drupal module designers reap the rewards of having made functional systems that lots of people end up benefitting from? Considering the amount of people who'd be building sites with your module, it looks like you'd be getting quite a bit of residual income for a long time to come from this.

Incidentally, this module itself will allow the creation of sites where users come up with ideas for other Drupal modules, ChipIn sees that they're funded, and then a roster of Drupal module developers can be notified when there's paid work ready if they want it. Gravy train much? =)

> Thanks for anything.
>
> Vlad.

Glad to assist! Let me know if there's anything I can clarify, or if I missed something. Hopefully you see what your module will enable people to do, and how it benefits everyone - including Drupal module developers!

Be well,

- Satori

Status?

Please downgrade this issue from "Status: active" to "Status: postponed", and update the module's page to indicate that the module is seeking a maintainer. Someone else may have the time, and it's inaccurate for Drupal site developers to read that 5.x and 6.x versions are coming soon.

+1 bounty for bringing ChipIn back to life. cheers

Subscribing...

subscribing

So what is the state of the chipin module?

Definitely interested for fundraising with the following features:
- Set a goal and current amounts in a thermometer style or something like that.
- Link it to Ubercart or PayPal
- Separate database of registered people
- Have built-in email capabilities to follow-up with contributors, verify their emails, etc.

Hopefully we can have a new maintainer/developer soon.

Thanks!

to which could be added a Drupal filter that allows the users to add a chipin at any nodes they create.

That seems like the most useful feature to me. See also #1613308: Create role for people who need to access Full HTML that isn't 'site maintainer'.

Google still brings this page up when searching abandoned projects, putting in link to https://www.drupal.org/node/251466

I am closing this issue, which is for a not supported Drupal version.