From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: Reverse-engineering SD specs for collie
Date: Thu, 04 Jan 2007 17:54:52 +0100 [thread overview]
Message-ID: <enjbgu$c1o$1@sea.gmane.org> (raw)
In-Reply-To: <1167841321.13059.2.camel@fleuret>
Anthony and Patrik, great. Thank you.
I made a little entry on the FAQ page at wiki.openzaurus.org shortly
after sending out my mail. Maybe you want to commit to your pledge
there as well. http://wiki.openzaurus.org/FAQ
On a more general note, we should discuss about when the bounty shall be
paid out. I made the current wording more strict to be on the safe
side. Getting a patch into upstream kernel would of course be the
ultimate goal, but I would be happy to pay even before that goal is
achieved (for example if main devs accepted the patch into OE). This is
something we need to discuss.
I am somewhat inexperienced with bounties but I think having a clear and
measurable goal is important both for the willingness of contributors to
pledge and for devs to go ahead and do it. I wonder if there are any
online tools one can use to manage the process better and increase
visibility. A quick google hunt turned up the following:
http://www.opensourcexperts.com/
https://launchpad.net/bounties/
http://bountycounty.org/
https://www.bountysource.com/
http://donorge.org/
Any comments? This is something of general interest for OE, I think.
next prev parent reply other threads:[~2007-01-04 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-01 15:40 Reverse-engineering SD specs for collie Rolf Leggewie
2007-01-01 16:18 ` Richard Purdie
2007-01-01 17:33 ` Rolf Leggewie
2007-01-03 8:59 ` Patrik Gfeller
2007-01-03 16:22 ` Anthony Joseph Seward
2007-01-04 16:54 ` Rolf Leggewie [this message]
2007-01-04 18:53 ` Justin Patrin
2007-01-06 8:37 ` Patrik Gfeller
2007-01-24 18:02 ` Anthony Joseph Seward
2007-03-19 16:19 ` Anthony Joseph Seward
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='enjbgu$c1o$1@sea.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox