All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] code sprints or focus-weeks
Date: Sat, 13 Jan 2007 00:28:25 +0100	[thread overview]
Message-ID: <eo95ir$gi5$1@sea.gmane.org> (raw)
In-Reply-To: <eo94rt$dlu$1@sea.gmane.org>

Rolf Leggewie wrote:

> None of them were a clear winner, though.

During my research I had also come across Nat's thoughts for a bounty 
system at http://nat.org/2005/january/#bountysystem which I fully agree 
with.  It seems this should not be so complicated.  I believe there are 
two possible routes forward: Hack something together and self-host or 
get some site such as launchpad.net to provide something usable.

I am afraid launchpad.net might take forever.  Furthermore, the software 
is closed which might turn some people off (not me).  The BIG plus is 
the all-encompassing approach.  Bounties are just like most things in 
FOSS about critical mass and joining loose ends together.  I am afraid 
that an OE-only approach might limit itself in people that can pitch in. 
  There are bugs being fixed in OE that benefit non-OE users, too.  But 
on the other hand, progress in launchpad.net is out of our control so 
unless we can work out some kind of time-frame with such an external 
site it might not be an option.




  reply	other threads:[~2007-01-12 23:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 12:13 [RFC] code sprints or focus-weeks Koen Kooi
2007-01-02 13:36 ` Rolf Leggewie
2007-01-12 21:36   ` Marcin Juszkiewicz
2007-01-12 21:47     ` Koen Kooi
2007-01-12 23:16     ` Rolf Leggewie
2007-01-12 23:28       ` Rolf Leggewie [this message]
2007-01-13 20:13     ` Koen Kooi
2007-03-10 17:22 ` Rolf Leggewie

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='eo95ir$gi5$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.