Sitelet https://github.com/tip4commit/tip4commit/issues/152
Skip to content

Make this opt-in like Gratipay or similar services #152

Description

@verint

While this is going on #127 the main issue is that any project can be added without wish/permission from maintainers.

So, make it opt-in, i.e maintainers can choose to sign up if they wish to get money for contribution to their project or an individual contributor can sign up claiming/showing his contribution to different projects.

Activity

  1. changed the title [-]Make this opt-in[/-] [+]Make this opt-in like Gratipay or similar services[/+] on Nov 1, 2014
  2. arsenische commented on Nov 1, 2014

    @arsenische
    Contributor

    Thanks for creating the ticket. I think it will be quite limiting for people who want to donate and contribute though.

    the main issue is that any project can be added without wish/permission from maintainers.

    We have nothing to do with project maintainers. What's the motivation behind the requested feature?

    Quote from current version of FAQ:

    If somebody wants to reward independent contributors of random opensource project, does he or she needs a permission from project maintainers? Should the project maintainers have the power over economic activities of other people?

  3. verint commented on Nov 1, 2014

    @verint
    Author

    @arsenische this #127 (comment)

    Are you guys that dumb or what?

  4. canpolat commented on Nov 1, 2014

    @canpolat

    If somebody wants to reward independent contributors of random opensource project, does he or she needs a permission from project maintainers? Should project maintainers have the power over economic activities of other people?

    This is not only about project maintainers. You don't have the consent of the individual contributors either.

  5. ubernostrum commented on Nov 1, 2014

    @ubernostrum

    Repeating myself like a broken record: you do not have my consent as an individual developer. See #146 for requested action and expected timeline of resolution.

  6. csvan commented on Nov 1, 2014

    @csvan

    So can this now be considered the official continuation of #127? Namely, the one single complaint that has been leveraged against tip4commit so far is simply that this service acts for (or on behalf of) individuals and projects without their consent.

  7. arsenische commented on Nov 1, 2014

    @arsenische
    Contributor

    Let's create a separate issue on developers so that nobody mentions project maintainers there, or this ticket will turn into flood again.

  8. csvan commented on Nov 1, 2014

    @csvan

    so that nobody mentions project maintainers

    They are pretty much in the same boat, so I don't see why you need separate tickets. Again, everything boils down to one single complaint - why so many tickets?

  9. csvan commented on Nov 1, 2014

    @csvan

    Oh well, separate issues created.
    Developers - #154
    Maintainers - #155

  10. arsenische commented on Nov 1, 2014

    @arsenische
    Contributor

    When you need to fix a problem, you need to identify it first. ticket creator stated that "the main issue is that any project can be added without wish/permission from maintainers.". If this issue is resolved, let him decide and discuss particular thing here.

    Most of the complaints come from project maintainers, not developers who received tips above the threshold.

    However it seems like developers have a problem too, so it needs to be addressed. Please create a ticket.

    Update: Oh, I see #154 (#155 is a duplicate of #152 I guess)

    Thanks!

  11. verint commented on Nov 1, 2014

    @verint
    Author

    @csvan opt-out is least asked.

  12. arsenische commented on Nov 1, 2014

    @arsenische
    Contributor

    Created #157 for completeness.

  13. bill-auger commented on Nov 1, 2014

    @bill-auger
    Contributor

    this could be implemented by sending an email to the project maintainer when someone searches/adds a project requiring them to opt-in before a bitcoin address is generated and the project becomes accessible on the live site - or mosre stringently - the add-upon-search feature could be removed and require each project maintainer to add it themselves or not at all

  14. ubernostrum commented on Nov 1, 2014

    @ubernostrum

    Please read GitHub's Terms of Service, particularly item 10 of section G:

    You must not upload, post, host, or transmit unsolicited email, SMSs, or "spam" messages.

    If you have difficulty understanding what is meant by "You must not... transmit unsolicited email", I suggest speaking with GitHub support. Personally I find it quite clear, and thus I reiterate: explicit opt-in by an individual developer to tip4commit to explicitly consent to contact and services before tip4commit sends any email to that developer is the only acceptable policy.

  15. sczizzo commented on Nov 1, 2014

    @sczizzo

    +1

  16. 7 remaining items

  17. chrisfranklin commented on Nov 2, 2014

    @chrisfranklin

    Opt in or shut down, its that simple. What you are doing here is totally immoral and you know it.

  18. andyleap commented on Nov 2, 2014

    @andyleap

    @lavagetto Best they could do would be opening an issue on the repo that got searched for. Sending an unsolicited email for a service where tip4commit would be getting profits would be spam. Even issues would be iffy, IMHO.

  19. arsenische commented on Nov 2, 2014

    @arsenische
    Contributor
    1. tip4commit is opt-in for developers now (Developers must opt-in to receive tips. #168 )
    2. we don't send email notifications anymore
    3. we have a warning that we are not affiliated with project maintainers
    4. project maintainers are not supposed to be part of tip4commit or involved into it (I don't quite understand why they are the ones who comlain) but we are currently discussing the feature that would enable them to remove their projects. we have a pull request already (Allow projects to be blacklisted for tips. #163)
  20. canpolat commented on Nov 2, 2014

    @canpolat

    @arsenische Project maintainers matter. Consider the following corner case scenario:

    Let's say I have a project on GitHub and there is this one person who liked it and wanted to donate 1 bitcoin (wow). He finds T4C and donates it. But, I may be the only developer for my project (and may decide to reject all other contributions), and if I didn't opt-in to your donation system, there is no way I will get that donation (I may not be interested in donations). So, you took a donation for the project implying that it will go to the contributors but due to how I handle contributions, you have no way to deliver that donation and you sit on that "money" forever, meaning you took money on behalf of the contributors of my project but never delivered it. This is a terrible business model and if you don't clear things with maintainers, you'll not convince anybody that you have good intentions.

    You have to make sure that contributors will get those donations before collecting them. And there are at least two reasons as to why they may not get them:

    1. The maintainer may not allow it (as in my example scenario)
    2. They may not be interested in them

    So, maintainers matter. They may even start rejecting pull requests from the developers that are registered in your system. As many others said, making it opt-in for everyone (contributors and maintainers alike) will make your life easier and convince people that you're trying to do something good for the community.

  21. arsenische commented on Nov 2, 2014

    @arsenische
    Contributor

    @canpolat what if we explicitly say that donations will go to project contributors or if not claimed within 30 days - will be passed to the Free Software Foundation?

  22. lavagetto commented on Nov 2, 2014

    @lavagetto

    @arsenische for the record, I do complain as a contributor as well, but as @canpolat pointed out, maintainers matter.

    I think I do have the right not to want you to collect donations for my projects. So, please, make this opt-in. I don't want to have to crawl your site to opt-out in case.

  23. arsenische commented on Nov 2, 2014

    @arsenische
    Contributor

    Opt-out feature for project maintainers has been merged #163

  24. canpolat commented on Nov 2, 2014

    @canpolat

    @arsenische I think, instead of finding work arounds, you should make peace with the project maintainers. They may end up being the people promoting your system to their contributors. Collecting donations for projects that haven't opted in your system will not result in anything good (no matter where the money goes). You may want to read the the reactions to a similar situation here.

  25. stickytruth commented on Nov 2, 2014

    @stickytruth

    Would tip4commit exist without the existence of project maintainers?

    How can you organize your service by project maintainers' names and projects and simultaneously say "project maintainers are not supposed to be part of tip4commit or involved into it"?

    If you don't want to deal with maintainers then refactor tip4commit to not depend on them in any way.

  26. chadwhitacre commented on Nov 2, 2014

    @chadwhitacre

    Fwiw, here's the ticket where we went through this for Gittip/Gratipay a couple years ago: gratipay/gratipay.com#28.

  27. chhantyal commented on Nov 2, 2014

    @chhantyal

    Oh @whit537 I just saw that issue gratipay/gratipay.com#28

    It's exactly same issue here. Glad that @gratipay listened to people, resolved the issue without fuss (made it opt-in) and everyone is happy.

    I don't understand why guys at @tip4commit can't give a better response to community and make what community wants. So far response from them has been very shady, irresponsible and immoral.

  28. chadwhitacre commented on Nov 2, 2014

    @chadwhitacre

    @chhantyal Maybe someone should give them a PR? ;-)

  29. andyleap commented on Nov 2, 2014

    @andyleap

    @whit537 Question, why do we have to work to fix problems with their code? I don't know ruby. Do I need to learn it so I can fix their crap? And as far as I concerned, they have a PR already that fixes it to my satisfaction, #160.

  30. arsenische commented on Nov 4, 2014

    @arsenische
    Contributor

    @whit537 I admire the way you handled the situation, that is something to learn from you

    @chx It is opt-in for developers now; requests of project maintainers to remove their projects are being fulfilled

    @chhantyal We've taken steps in the direction proposed by community and are considering closing the project or making it opt-in for project maintainers.

    It is hard to read and respond to every message and accusation. Much of the criticism is fair, but even more of it is based on outdated information, misinterpretation and pure hate.

    We always tried to find a compromise and if we understood that what we did cause problems, we apologized and tried to fix them.

    The goal was to allow anybody on Earth to help any open source project by donating money to donation pool that could be used to attract attention of new indepedent developers and reward existing ones.

    But with all that hate originally caused by problem with excessive notifications regarding micro-donations (that was fixed over a month ago) I am not sure this goal can be reached now.

    Nothing is perfect, especially this little project. You don't need a microscope to find flaws in it. They were expected to be fixed while it grows.

    Everything can be changed. Wording (we are not native speakers), user agreements (we are not lawyers), tip distribution algorithm (e. g. reward contributors for the first commit/day only to avoid commit spam), notification system (disabled now), etc.

    We expected community to help us solve all this or at least to have enough patience before we fix it. Instead we got a smear campaign that was probably started by respectable project maintainers whose permission wasn't asked.

    Anyway, sorry for trouble, we'll try to fix everything or close the project.

  31. arsenische commented on Nov 13, 2014

    @arsenische
    Contributor

    Even though we never intended to act on behalf of project maintainers, tip4commit is opt-in for them now. Projects that don't have donations have been removed.

    Would be nice if someone implements #196

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions