A caution and something to keep in mind and I am speaking from experience. Payment to a developer for working on a feature must not be tied or made contingent on that feature becoming part of the product. The developer ultimately has no control over the inclusion of a feature in a release.
Including a feature in a release is something that only the PMC decides and we do it on our own schedule without regards to anyone else's plans. Regards, Dave On May 1, 2013, at 1:08 PM, Donald Whytock wrote: > We can take it from both directions...mention BountySource in the context > of people offering money for changes, and Catincan for people asking for > money for changes. As examples of business models, along with VAR and > consulting. > > > On Wed, May 1, 2013 at 3:40 PM, Rob Weir <robw...@apache.org> wrote: > >> On Wed, May 1, 2013 at 3:16 PM, Donald Whytock <dwhyt...@gmail.com> wrote: >>> The answer from Catincan is, a developer is someone who can commit >> changes >>> to the project. "The person listing the project has to be able to have >> it >>> merged into the main branch or have the approve of a developer that can. >>> Our goal is to have all users be able to benefit from whatever features >> are >>> crowdfunded opposed to unsupported forks." >>> >> >> The tricky thing for us is that no committer's work is inviolable. >> Every committer has the ability to cast a technical veto. So one >> would need to be careful how one expresses expectations. >> >> Extreme hypothetical: Someone offers to pay a committer $10,000 if >> they add an advertisement to the splash screen of OpenOffice for >> www.OnlinePoker.com. There is nothing we (Apache) can do to stop that >> work from being contracted. But we can and would veto it from being >> included in a release. But the committer could certainly provide a >> private build of that change to their customer, modulo any trademark >> issue that might occur. >> >> So one should not promise (in a contractual sense) to add a feature or >> a bug fix to the official AOO release, since the contents of a release >> is determined by the PMC via their release votes, and not any one >> committer. >> >> >>> And the funding can go to either the individual or the project. So >> someone >>> can kick off a fundraiser for himself to submit a change, or the AOO PMC >>> could perhaps kick off a fundraiser that'd be paid to the ASF. >>> >>> Was there ever a page made about possible AOO-related business models? I >>> thought there was a discussion about it. >>> >> >> It was an idea for a blog post I had. It is still on my "list". But >> if we decide to do something with Catincan it could prompt an even >> earlier post. >> >> Regards, >> >> -Rob >> >>> Don >>> >>> >>> On Tue, Apr 30, 2013 at 3:15 PM, Donald Whytock <dwhyt...@gmail.com> >> wrote: >>> >>>> Working my way down the crowdfunding list found at >>>> >>>> http://en.wikipedia.org/wiki/Comparison_of_crowd_funding_services >>>> >>>> ...I find Catincan (catincan.com). Catincan lets people start >>>> fundraising efforts for opensource software feature development, but >> only >>>> existing developers on existing projects. You can't use Catincan to >> start a >>>> new project, and they won't accept your fundraising drive unless you're >> an >>>> existing developer. >>>> >>>> Not sure how this would apply to AOO...whether being a committer on the >>>> project would be considered being a developer, and whether said >> committer >>>> could accept funds on his own behalf to do coding as opposed to it >> having >>>> to go to the ASF. That would take an inquiry. >>>> >>>> Don >>>> >>>> >>>> On Thu, Apr 25, 2013 at 9:34 AM, janI <j...@apache.org> wrote: >>>> >>>>> On 25 April 2013 13:38, Rob Weir <robw...@apache.org> wrote: >>>>> >>>>>> On Wed, Apr 24, 2013 at 11:46 PM, Donald Whytock <dwhyt...@gmail.com >>> >>>>>> wrote: >>>>>>> Hey all... >>>>>>> >>>>>>> We talked a couple months ago about a Kickstarter-like scheme for >>>>> paying >>>>>>> for bug fixes and enhancements. Actually, it seems this sort of >> thing >>>>>>> exists in the other direction: >>>>>>> >>>>>>> http://en.wikipedia.org/wiki/Bountysource >>>>>>> >>>>>>> https://www.bountysource.com/ >>>>>>> >>>>>>> Bountysource is a site for people to put up funded requests for >>>>> changes. >>>>>>> People put up issues to fix, along with amounts pledged to the >>>>> fixing of >>>>>>> them (I've seen $0 pledges, so I guess the pledge is optional), >> and a >>>>>>> person receives the bounty if a fix is checked in and accepted. >>>>>>> >>>>>>> The site is for any open source project with a public homepage. >>>>> There's >>>>>>> entries for LibreOffice, VLC, PhoneGap plugins and others (none for >>>>>>> OpenOffice so far). They also, yes, have fundraising efforts for >>>>> really >>>>>>> big changes/features. >>>>>>> >>>>>>> Essentially anyone can say they fulfilled the bounty request. Then >>>>>> there's >>>>>>> two weeks for the bounty poster to say, "Oh no you didn't!", >> otherwise >>>>>> the >>>>>>> bounty gets paid. >>>>>>> >>>>>>> This from a ten-minute read of their FAQ. There's a little bit >> more >>>>> to >>>>>> it >>>>>>> than that, but that's the gist. >>>>>>> >>>>>>> Think we'll be seeing OpenOffice bounties? >>>>>>> >>>>>> >>>>>> The problem is this requires that both the person(s) funding and the >>>>>> person doing the work know about that website. But even those >> heavily >>>>>> involved with the project, or even power users, are unlikely to >>>>>> stumble upon that site. >>>>>> >>>>>> If we really want to encourage this kind of match ups then we'd >>>>>> probably need to encourage it somehow, even if just from the >>>>>> information sharing perspective. Although we cannot officially >>>>>> endorse these sites, maybe we can add something to the support page >>>>>> that says something like: >>>>>> >>>>>> "The following third-part websites help match users and coders >> seeking >>>>>> to fund development work in open source projects. Although the >> Apache >>>>>> OpenOffice project does not pay for development work, these websites >>>>>> may be useful for those wishing to independently make such >>>>>> arrangements." >>>>>> >>>>>> -Rob >>>>>> >>>>> Would it be an idea if we made our own subdomain and a couple of pages >>>>> (e.g. link to a mwiki page), that way we could direct >> sponsors/developers. >>>>> >>>>> I have on the other understood (maybe wrong) that we are not allowed to >>>>> accept dedicated donations, all donations must go to ASF treasury and >> be >>>>> distributed from there. >>>>> >>>>> rgds >>>>> jan I. >>>>> >>>>>> >>>>>>> Don >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>>>> >>>>>> >>>>> >>>> >>>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
