On December 17, 2013 at 3:27:48 AM, David Smith (catfish....@gmail.com) wrote:
Hmm. iMessage support seems almost too large to be a reasonable bounty (given all the reverse engineering, etc... involved), but it would be a huge boon. The neat think about bounties is that they do let the programmer decide if it’s worth it or not. I don’t think in the general since that bounties are going to compensate most people for the work put in; it’s a case of “if you have to pay me, you can’t afford me” in many situations. I think this would be a fine thing to put as one of the large bounties… in addition, it might serve as a nest egg for other people to pitch in and make it a sizable bounty. Amelia Rose wrote: > How are the tickets going to be picked? I think one way is by the number of > positive votes received already. I don’t think we should use votes exclusively but that’d be an excellent way to cull some candidates. Why don’t you create a list of the top 10 open tickets by vote and send it to the list for discussion? Thijs wrote: > - Are official devs eligible for the bounties, or is this just to bring in > new blood? Yes, at least in this initial effort. Maybe we iterate on how we’re doing this and it changes later, or limit it in some way as Amelia suggests, but I say start with as few rules as possible as see how it plays out. > - How do we decide how much to reward each ticket? I suggested a completely arbitrary metric of "$200 on bounty source on large tickets and $50 on medium tickets.” I stand by my arbitrary suggestion :) > To be blunt: I would not mind receiving some bounty rewards. :) However, I > feel like it would be disingenuous if I started arguing about offering a > bounty for a ticket and then collect it myself. How about we ask for disclosure during discussion of tickets? Just something like, “I think ticket #401948 is a good candidate. I probably won’t get to it otherwise, but if there were a bounty I would prioritize it and work on it myself.” And of course if you later decide to take on a ticket with a bounty, but you weren’t thinking of doing it when the bounty was placed, that’s fine… ‘later’ in this context means that if someone don’t disclose they are going to work on it, it should be 2 weeks after the bounty is posted before they can claim it, and if a new contributor posts in the ticket that they are working on it then they are to be given a reasonable timeframe to do so. Again, minimal rules, honorable people, yadda yadda. I’m sick of these donated funds doing nothing awesome, and I have no problem at all with them going to the people making awesomeness happen. I’m not likely to have time to work on Adium in the near future so I consider myself a reasonably impartial arbiter. (I won’t have time to do detailed arbitering either so will err on the side of “this seems right and is a simple solution” to most problems!). -Evan David On Dec 15, 2013, at 5:43 PM, Evan Schoenberg, M.D. <tek...@gmail.com> wrote: Ok, we have bandied this about a number of times and a number of ways, but #413's recent bounty and near-immediate uptake by a coder inspired me. Let's pick 5 "large" and 5 "medium" size tickets. As a starting point we'll put $200 on bounty source on large tickets and $50 on medium tickets. The idea is not to hire a programmer but rather to provide visibility and a bonus incentive for involvement. Feel free to suggest tickets you would be willing to take on yourself. Open to further suggestions but let's overall just do this and see what happens, not obsess over the details. -Evan Begin forwarded message: From: "Adium Trac" <t...@adium.im> Date: December 15, 2013 at 7:46:30 PM EST Subject: Re: [Adium Trac] #413: Rename contact groups Reply-To: t...@adium.im #413: Rename contact groups -------------------------+------------------------------------------------- Reporter: | Owner: anonymous | Status: new Type: | Component: Adium UI enhancement | Severity: normal Milestone: Adium | Keywords: rename change name contact buddy 1.6 | list blist group Version: 0.82 | Resolution: | Patch Status: | -------------------------+------------------------------------------------- Comment (by Affix): I seen this on bountysource and decided to take this bug. Shouldn't be hard to impliment depending on how Adium stores group names. -- Ticket URL: <https://trac.adium.im/ticket/413#comment:20> Adium Trac <https://www.adium.im/> Adium
