[oe] [Angstrom-devel] Best place to send new/updated bb files?

[Paul Sokolovsky]

Hello,

On Thu, 21 Feb 2008 11:53:25 +0100
Stanislav Brabec <utx at penguin.cz> wrote:

> Paul Sokolovsky wrote:
> > Hello,
> > 
> > On Wed, 20 Feb 2008 06:52:18 -0600
> > "Capn_Fish Zaurus" <capn.fish.zaurus at gmail.com> wrote:
> > 
> > > Is there a protocol for submitting new/updated bb files to the
> > > bugtracker (eg, importance markings, etc)? Or is there a better
> > > place to submit them?
> > 
> > Bugtracker is *the* place to submit .bb's in all cases. There's no
> > special meaning (from submitter's point of view) for priority, etc.
> > except common sense. In other words, in most cases default values
> > should be left as is.
> 
> In theory...
> 
> Simple search shows 50 potential open bugs with new recipes:
> http://bugs.openembedded.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=attachments.filename&type0-0-0=substring&value0-0-0=.bb


We even have http://bugs.openembedded.net/show_bug.cgi?id=2194 ,
maintained by Rolf.

> 
> I am not expert on monotone, but it supports submitting changes after
> peer review:
> http://monotone.ca/docs/Quality-Assurance.html

Oh, that must be zecke's favorite "wanna one sweet day in the
bright future" toy ;-).

But let's just be real about all this - all "process improvements" are
just those shiny toys, nothing more. For them to work, *people* should
use them. But if we talk about committing new recipes, then they would
need to be committed in the end, no matter what additional procedure is
built on top of that. And then, nothing precludes people with doing
that with the current procedure, which includes pre-review.

So, the way to improve this, IMHO, is raising awareness among the
developers with OE commit rights, that having the commit access is not
just to let them commit own stuff more easily, but entails
responsibility before community - just as before someone reviewed and
pushed their patches, the same way they should join with this important
service for new contributors.

And of course, people with newly acquired commit rights are in the best
position to actually help with that, because older developers
oftentimes acquire additional responsibilities and/or work areas which
precludes them from timely participation in new submission
processing ;-(.

> 
> Could it provide a better way?
> 
> -- 
> Stanislav Brabec
> http://www.penguin.cz/~utx/zaurus

[]

-- 
Best regards,
 Paul                          mailto:pmiscml at gmail.com