Hello Graham,<br><br><br>Here is how I see it, and this is Off the Top of my Head ROUGH draft....<br><br><br><span style="font-weight: bold;">1. </span> Someone wants a feature that isn't currently avaliable. It could be something that the CORE really should have, OR it could that only a few users could use.
<br><br><span style="font-weight: bold;">2</span>. We go to a "Bounty Place" currently hosted in the forums, but at some point and time I would like to see it on a system similar to scriptlance.<br><br><span style="font-weight: bold;">
3</span>. Someone would post a feature they want/need with their Specs and how much they are looking for pay for they part of the bounty.<br><br><span style="font-weight: bold;">4</span>. Other people would post that they are interested in joining this Bounty and what they would be willing to pay for their portion of the Bounty and any additional Specs they would like to see.
<br><br><span style="font-weight: bold;">5</span>. After a period of time, when enough interest is in the Bounty, or Enough money has been raised to casue interest from a Developer type, or it is seen that the feature isn't "worthy" of a Bounty and if I want it, I have to hire someone outright for it, then the discussion starts.
<br><br><span style="font-weight: bold;">6.</span> Everyone gets their input, the users that have "agreed" to the Bounty, which are the people fronting the money, and the developer/developers and everyone agrees what can and will be done and a timeline for it.
<br><br><span style="font-weight: bold;">7.</span> The people the want the Bounty will put the money up in escrow, perferably into the hands of someone at vTiger. They will hold the funds until the project is done, and everyone is in agreement that the project has done what was agreed upon.
<br><br><span style="font-weight: bold;">8.</span> vTiger, which has the funds will keep their portion, to help them offset their expensives and help them with more vTiger developement (not sure what this precentage is 5%? 10%? I don't know, that needs to be worked out.
<br><br><span style="font-weight: bold;">9. </span> The rest of the fund are released to the developer/developers and they get paid. The developer/developers release the code to the people that paid the bounty.<br><br><br>
<br>In theory that is how I see it working. There are many things to clear up. Like:<br><br><span style="font-weight: bold;">a.</span> What happens with the code then?<br><span style="font-weight: bold;">b.</span> Who owns it?
<br><span style="font-weight: bold;">c.</span> What if it's something really helpful and should be in the core?<br><span style="font-weight: bold;">d.</span> How do we justify a few people paying so all the others can sit back and reap the rewards without fronting any money?
<br><span style="font-weight: bold;">e</span>. What about a dispute?<br><span style="font-weight: bold;">f.</span> What is the people that want the feature can't agree on exactly what they want?<br><br><br>On my opinion, for the above options, I would address a few things this way:
<br><br><span style="font-weight: bold;">a/b.</span> I think it should be the property of the people that paid for it until the 2nd major release after it's finished<br><br><span style="font-weight: bold;">c/d.</span> If it's something that the core really needs, then I think it should be discussed with the people that bought it and see if they want to release it to the community right away. If not, then it will be released to the community after the 2nd major release after the project was done. That way it's a trickle effect, if someone wants something now, they pay for it, if not they can wait and get it in the future.
<br><br>This way, people can't not ante up if they want something, because they won't get it for a while, but on the other hand, the vTiger team would benefit in later releases because this would add features that are already coded to future versions.
<br><br><span style="font-weight: bold;">e.</span> I think the vTiger team only should have final say. They are unbasised and I know they will be fair.<br><br><span style="font-weight: bold;">f.</span> I think if we can't agree on the terms, then the bounty isn't
started, finished. Over time, maybe the minds of many can meet in the
middle.... until then nothing gets done.<br><br>This is how I see it, others may see it differently or have something to add.<br><br>Also, I agree with mike in that I don't think we need a Team for this, other than the vTiger team. I am sure all of us will pitch in and help out however we can. I think what Brian was thinking about was when we get a system in place <like scriptlance> other than the forums, we might need people then to help run that system.
<br><br><br>I have an will help the vTiger team with or without title. My company gives me enough hats to wear, I don't need another one. :)<br><br><br>Jamie<br><br><br><div><span class="gmail_quote">On 2/25/06, <b class="gmail_sendername">
Graham Anderson</b> <<a href="mailto:grahama@add-ons.co.uk">grahama@add-ons.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ok All<br><br>I think my problem is, I don't understand the bounty thing... how it works and how anyone (and I do mean ANYONE) can get involved.<br><br>Perhaps someone can take a moment to outline the way that this will pan out, over time, so that we can agree some ground rules, or disagree and make our comments public, for wider debate.
<br><br>I would really appreciate an umbrella overview of what is intended and expected to be involved.<br><br>Regards<br><br>Graham<br><br>________________________________<br><br>From: <a href="mailto:vtigercrm-developers-bounces@lists.vtigercrm.com">
vtigercrm-developers-bounces@lists.vtigercrm.com</a> on behalf of Mike Fedyk<br>Sent: Sat 25/02/2006 17:37<br>To: <a href="mailto:vtigercrm-developers@lists.vtigercrm.com">vtigercrm-developers@lists.vtigercrm.com</a><br>Subject: Re: [Vtigercrm-developers] Build a vTiger Bounty Team
<br><br><br><br>Jamie Jackson wrote:<br><br>> I'd call it marketing a fund raising system for developers. Right now,<br>><br>> Brian is the one interested in maintaining this portion of the<br>> community
<br>> and wants a title. So "Bounty Maintainer" seems fair.<br>><br>><br>> Hiya Mike,<br><br>Hi Jamie,<br><br>><br>> I don't you to take this the wrong way, but on the surface it would<br>
> seem you are skectical<sp> of this bounty system?<br><br><a href="http://forums.vtiger.com/viewtopic.php?t=5150">http://forums.vtiger.com/viewtopic.php?t=5150</a><br><br>I am for a bounty system.<br><br>><br>
> I am not sure why you would call it a fund raising system, although it<br>> does put money in the developers pocket that steps up and helps us<br>> non-programmers out with features our company needs. I wouldn't call
<br>> it a fund raising system. It just seems like a not so nice way of<br>> naming it.<br><br><br>I don't think anything is wrong with a bounty system for vtiger. What I<br>am doing is replying to a fellow developer that feels something is
<br>happening behind closed doors. If I brought up something like that and<br>they didn't acknowledge it and give me a straight answer, I wouldn't<br>believe them.<br><br>One part I am skeptical about is this "Bounty Team" thing. One thing I
<br>have learned is not to count anything until you see it, and it doesn't<br>align with the open source meritocracy (what I like to call an<br>"effort"ocracy) concept where you put in the work before getting<br>
recognition.<br><br>Maybe it's just a different management style, but I see it as marketing<br>to get them to do what you want. And I am inherently skeptical of<br>marketing.<br><br>><br>> We all understand that several things are true:
<br>><br>> 1. The Core vTiger group is busy with 5.0<br>> 2. You are busy with maintaining 4.2x<br>> 3. We non-programmers need features that aren't in the current system<br>> 4. There are many people that would want the same features, so
<br>> sharing the costs of said features is a benefit.<br>><br>> I believe a bounty system is a good thing, and a needed thing. I am<br>> sorry if I misunderstood your stance, but it just seemed on surface<br>
> that you didn't like this idea.<br>><br>> Also, Brian didn't ask for a title for the sake of having one, I<br>> believe he asked for the vTiger core group to get behind the idea of a<br>> bounty system and let the community know they are supportive of the idea.
<br><br><br>I think the core vtiger team has already endorsed the first steps in the<br>bounty system by creating a bounty forum and replying positively in the<br>above linked forum topic.<br><br>Also I think the request comes from a misunderstanding of the community
<br>process. If there is a need you fill that need and titles come later.<br>Nobody has full control of anything in the OSS community. If I make a<br>bad announcement or a bad commit I'll get called on it.<br><br>><br>
> Again, I am sorry if I misunderstood you, I just thought I would give<br>> you my input.<br><br>Not a problem. And it looks like this your first post to the<br>developer's mailing list.<br><br>Welcome.<br><br>Mike
<br>_______________________________________________<br>This <a href="http://vtiger.com">vtiger.com</a> email is sponsored by: Zoho Writer. Are you still using your desktop word processor for typing documents? Try the AJAX enabled, collaboration-friendly online word processor, Zoho Writer for FREE instead!
<br><br><a href="http://zohowriter.com/?vt">http://zohowriter.com/?vt</a><br><br><br><br>_______________________________________________<br>This <a href="http://vtiger.com">vtiger.com</a> email is sponsored by: Zoho Writer. Are you still using your desktop word processor for typing documents? Try the AJAX enabled, collaboration-friendly online word processor, Zoho Writer for FREE instead!
<br><a href="http://zohowriter.com/?vt">http://zohowriter.com/?vt</a><br><br><br></blockquote></div><br>