On Sun, Feb 17, 2013 at 09:09:34PM +0100, Robert Vehse wrote:
> 
> Am 17.02.2013 um 19:51 schrieb "Evan D. Schoenberg, M.D." <e...@adium.im>:
> 
> > I recently got an email from BountySource, a site that I'd signed up for 
> > years ago to check out, that they were alive again. (They'd been shut down 
> > for a time, IIRC, due to issues with using PayPal to hold $ for bounties).  
> > Might be worth checking out for Adium.  We do have several thousand dollars 
> > in donated funds that could be initial funding for bounties if good 
> > projects that need manpower were mapped out.
> > 
> > -Evan
> 
> Interesting!
> 
> On the topic of donated funds: I think there are donations waiting on Flattr 
> (http://flattr.com/thing/425476/Adium-on-Twitter). I vaguely remember having 
> tried to sign up in order for us to be able to collect them.
> 
> Cheers,
> Robbie

I think it's a great idea.

Speaking of Twitter, Adium and bounties, Twitter is about to shut down the 
API Adium currently relies upon: 
https://dev.twitter.com/blog/planning-for-api-v1-retirement 
(https://trac.adium.im/ticket/16118#comment:2). Fixing this would require 
MGTwitterEngine to use json instead of XML, or switching to a different 
Twitter framework entirely (note that Accounts.framework and 
NSJSONSerialization aren't options, it needs to support 10.6 and 10.7).  
Both of these would be quite a lot of work I'm not interested in doing.  
I think this would be a nice project for Adium to offer a bounty on (it's 
relatively self-contained, with a clear goal and a well-written API it 
should follow). It might be a bit harder to incentivize other people to 
contribute too ("Twitter currently works! Why do I need to pay to continue 
using it?"), but some people might really want to keep using Twitter and 
Adium and be willing to pay for that.

The exact amount of work is hard to estimate, so I don't really know how 
much Adium should offer for it. $250? $500?

What do you think?

Regards,
Thijs

Attachment: pgpLePIdoYCQY.pgp
Description: PGP signature

Reply via email to