Re: Minutes of the Board meeting of August 29th, 2014

I wasn't aware of those terms. I guess I should read those ToS things every once in a while ;)

I'm not sure if I would recommend GNOME Foundation putting out bounties.

For us, it seems we've had more success using it as a way to incent our own developers than to attract new ones. It's been an interesting experiment. But there is a feeling that we have a large sum of money kind of trapped on BountySource now.

If we were operating with a larger budget, I think it might be more productive to contract developers directly.

However, for some very odd reason there's a number of people who feel comfortable paying into our BountySource account that don't feel comfortable paying into our account directly on our website. I have no idea why this is. Perhaps they are under the false impression that we can't withdraw from that account or that paying directly to us somehow won't end up funding development.

On Mon, Sep 15, 2014 at 6:30 AM, Michael Catanzaro <mcatanzaro gnome org> wrote:
> > Their terms of service [1] are also highly questionable. They reserve
> > the right to take all the money in our account, or cancel our bounties
> > without refunding our money, at any time and without any explanation,
> > without cause or notice (section 6.5). "Without cause" seems like a
> > pretty good place for us to draw a line....
> Daniel Foré should probably be the one who we should alert.

OK, I've CCed Daniel to make sure he's aware about the issues with
Bountysource's ToS. It's probably not a huge risk, but it would not be
fun to be wrong about that....

> We don't
> use it ourselves.  However, I am intrigued if people believe that we
> should put out bounties?  What I get a lot of times and you've seen
> this yourselves is that a lot of bugs are complex and takes a lot of
> intimate knowledge of the GTK+ or GNOME stack.  Would it be effective?
> sri

I think it could be effective, but it's something that would really
require strategic discussion to decide which bugs to place bounties on,
and how large the bounty. Presumably we would get better at this with
experience. I suspect that the most effective approach would be to
identify high-profile bugs that are not attracting sufficient developer
attention (e.g. the bad search experience in nautilus), and try to guess
the appropriate amount of money that will incentivize work on the bug.

Adam's $400 bounty for what appeared to be a simple crash actually
required digging into the webkitgtk+ sandboxing code, which basically
limited the bug to those who already have at least some webkit
experience. It did work in the end when it attracted my attention, but
that took a while.

My $150 bounty on the gnome-shell desktop background bug hasn't been
successful yet; it probably wasn't large enough to motivate anyone
unfamiliar with gnome-shell to look into the problem. I figured a
smaller amount of money would be appropriate since it's probably a
fairly simple issue and I pointed out a commit that I thought was wrong.
Maybe someone will work on it in the end, but I have a feeling it will
end up being solved by an experienced gnome-shell developer, and I guess
the bounty will probably not be significant motivation for doing so.

My $250 bounty on the gnome-shell calendar bug seems to have been just
right, though: that bug wasn't getting any attention and wouldn't have
been fixed without the bounty, and now it's very likely to be resolved


Daniel Foré

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]