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

Re: [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@penguin.cz> wrote:

> Paul Sokolovsky wrote:
> > Hello,
> > 
> > On Wed, 20 Feb 2008 06:52:18 -0600
> > "Capn_Fish Zaurus" <capn.fish.zaurus@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@gmail.com

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

[Rolf Leggewie]

Paul Sokolovsky wrote:
>> 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.

Thanks for bringing that up.  I'd like to see more core devs pay
attention to 2194 which is essentially the bug "I reviewed it, it
contains a patch or request for change in unmistakable terms, but it
touches something I don't understand and might have too far-reaching
implication for me to dare and commit it" - triaged.  IOW, it needs more
experienced people to actually commit or reject the bug.

The bug with the new or updated bb files is 2228, not 2194.

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

[Rolf Leggewie]

Rolf Leggewie wrote:
> Thanks for bringing that up.  I'd like to see more core devs pay
> attention to 2194 [...] 2228

I believe mickeyl was in a mood these days that might indicate his
interest in adding himself to the cc list of 2228 and 2194 (hint, hint) ;-)

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

[Paul Sokolovsky]

Hello,

On Thu, 21 Feb 2008 12:48:50 +0100
Rolf Leggewie <no2spam@nospam.arcornews.de> wrote:

> Rolf Leggewie wrote:
> > Thanks for bringing that up.  I'd like to see more core devs pay
> > attention to 2194 [...] 2228
> 
> I believe mickeyl was in a mood these days that might indicate his
> interest in adding himself to the cc list of 2228 and 2194 (hint,
> hint) ;-)

Yeah, I even started to wonder if OpenMoko finished ;-).

[]

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

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

[Paul Sokolovsky]

Hello,

On Thu, 21 Feb 2008 12:40:48 +0100
Rolf Leggewie <no2spam@nospam.arcornews.de> wrote:

> Paul Sokolovsky wrote:
> >> 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.
> 
> Thanks for bringing that up.  I'd like to see more core devs pay

Like that, except not "core devs", but just "devs". If OE must depend
on core devs for each sneeze, then it's feet-tied. Core devs should
work on general problems and rules for OE, not on mundane recipes.

> attention to 2194 which is essentially the bug "I reviewed it, it
> contains a patch or request for change in unmistakable terms, but it
> touches something I don't understand and might have too far-reaching
> implication for me to dare and commit it" - triaged.  IOW, it needs
> more experienced people to actually commit or reject the bug.
> 
> The bug with the new or updated bb files is 2228, not 2194.

[]

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

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

[Rolf Leggewie]

Paul Sokolovsky wrote:
> Like that, except not "core devs", but just "devs". If OE must depend
> on core devs for each sneeze, then it's feet-tied. Core devs should
> work on general problems and rules for OE, not on mundane recipes.

you still mix up bug 2228 and 2194

And, recipes are anything but mundane.  How about some respect for the
people that maintain them, including the core devs?

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

[Paul Sokolovsky]

Hello,

On Thu, 21 Feb 2008 13:15:01 +0100
Rolf Leggewie <no2spam@nospam.arcornews.de> wrote:

> Paul Sokolovsky wrote:
> > Like that, except not "core devs", but just "devs". If OE must
> > depend on core devs for each sneeze, then it's feet-tied. Core devs
> > should work on general problems and rules for OE, not on mundane
> > recipes.
> 
> you still mix up bug 2228 and 2194

I didn't even talk about specific bugs, but about general idea. If you
made even a specific place for coredevs to poke at, good for you, keep
maintaining that.

> 
> And, recipes are anything but mundane.  How about some respect for the
> people that maintain them, including the core devs?

Let me guess, now we'll have another dictionary usage discussion?



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

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

[Rolf Leggewie]

Paul Sokolovsky wrote:
>> you still mix up bug 2228 and 2194
> 
> I didn't even talk about specific bugs

Well, I was.  And this whole sub-thread is.  Maybe I should have better
quoted like this

Paul Sokolovsky wrote:
>>> > > We even have http://bugs.openembedded.net/show_bug.cgi?id=2194 ,
>>> > > maintained by Rolf.
>> > 
>> > Thanks for bringing that up.  I'd like to see more core devs pay
> 
> Like that, except not "core devs", but just "devs".

to make clear that your "core devs vs devs"-paragraph bore no (founded)
relation to what I had written.  I certainly felt I should make that
clear given the fact that you quote my "core devs" to start off your
"core devs vs devs"-paragraph.

Just for you

2194: for core devs only
2228: for anybody, really
      core devs invited - yes, them too, if they like pushing those
      "mundane" recipes as you disrespectfully called them

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

[Rolf Leggewie]

I have just added the bb and patch keywords to the keyword list
http://bugs.openembedded.org/editkeywords.cgi

keywords are essentially tags and can help us with the multi-dimension
problems we have.  But then again, unlike meta-bugs they don't have
email notification.  They are a tool for aiding bugzilla search.  AFAIK,
it is possible to restrict power to change those tags to certain groups
of bugzilla users which is something we might want to use (if we had a
triaged keyword, for example.  Thinking about it, I'll add that keyword,
too, for experimenting with it)

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

[Rolf Leggewie]

Rolf Leggewie wrote:
> keywords are essentially tags and can help us with the multi-dimension
> problems we have.  But then again, unlike meta-bugs they don't have
> email notification.

But they have the great advantage of being available for "change several
bugs at once" which is a life-saver when changing a lot of bugs at the
same time.

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

[Junqian Gordon Xu]

On 02/21/2008 07:07 AM, Rolf Leggewie wrote:
> I have just added the bb and patch keywords to the keyword list
> http://bugs.openembedded.org/editkeywords.cgi

I got the following message when clicking the link. Is this expected? Am 
I able to view it at least?

"Sorry, you aren't a member of the 'editkeywords' group, and so you are 
not authorized to add, modify or delete keywords."

Regards
Gordon

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

[Rolf Leggewie]

Junqian Gordon Xu wrote:
> I got the following message when clicking the link.

http://bugs.openembedded.net/describekeywords.cgi is the correct link.
One gets there by clicking "Keywords:" in any of the bugs for example.

We are just testing this out right now.  But I think it will help us.
Should you require additional keywords just let one of the admins know.

Junqian, can you tell me if you can add or remove a keyword from a bug?

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

[Junqian Gordon Xu]

On 02/22/2008 04:49 AM, Rolf Leggewie wrote:
> Junqian Gordon Xu wrote:
>> I got the following message when clicking the link.
> 
> http://bugs.openembedded.net/describekeywords.cgi is the correct link.
> One gets there by clicking "Keywords:" in any of the bugs for example.
> 
> We are just testing this out right now.  But I think it will help us.
> Should you require additional keywords just let one of the admins know.
> 
> Junqian, can you tell me if you can add or remove a keyword from a bug?

Yeah, I can. The keywords are very helpful.

Thanks
Gordon

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

[Rolf Leggewie]

Junqian Gordon Xu wrote:
>> Junqian, can you tell me if you can add or remove a keyword from a bug?
> 
> Yeah, I can. The keywords are very helpful.


Thank you for the feedback.  Of course, I was hoping that tampering with
keywords can be restricted to a group of bugzilla users.