All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Package Maintenance
Date: Tue, 24 Mar 2009 21:16:04 +0100	[thread overview]
Message-ID: <gqbf24$k5$1@ger.gmane.org> (raw)
In-Reply-To: <b6ebd0a50903241301r5b8972b4s59df7be41052ab7a@mail.gmail.com>

On 24-03-09 21:01, Chris Larson wrote:
> On Tue, Mar 24, 2009 at 12:51 PM, Tim Ellis<tim@ngndg.com>  wrote:
>> I am happy with whatever the outcome of this is as long as my packages as
>> specified in the MAINTAINERS file end up being maintained by me - we should
>> start whatever changes by transferring the information there to wherever it
>> is destined to go and then assessing the logs of individual packages imho.
>> Once a decision has been made getting devs that are listed there to transfer
>> the information would be a good way to see who is active and actually wants
>> to maintain their packages.
>>
>> I don't really have a problem with the way it is at the moment to be honest
>> and try to contact people using git log on packages and the MAINTAINERS file
>> if I have a need to touch other packages, which isn't really that hard!
>>
>
> I don't think the current method is difficult, persay, but rather I'd
> like to see:
> - More individual responsibility in the project in general,
> particularly in class and recipe maintenance.

I'm all for that.

> - Clearer delineation between what gets the most attention and what does not.

This kind of 'passive' QA can be quite usefull, I really hope someone 
gets Junqians suggestion working so we have some hard data.

regards,

Koen




  reply	other threads:[~2009-03-24 20:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 19:18 Package Maintenance Chris Larson
2009-03-17 19:25 ` Koen Kooi
2009-03-17 19:32   ` Chris Larson
2009-03-17 19:43   ` Frans Meulenbroeks
2009-03-23 20:35 ` Chris Larson
2009-03-24  9:06   ` Richard Purdie
2009-03-24 15:08     ` Chris Larson
2009-03-24 18:36       ` Frans Meulenbroeks
2009-03-24 18:54         ` Tom Rini
2009-03-24 18:55         ` Chris Larson
2009-03-24 19:14           ` Koen Kooi
2009-03-24 19:24             ` Chris Larson
2009-03-24 19:50               ` Tom Rini
2009-03-24 19:59                 ` Chris Larson
2009-03-24 18:56         ` Junqian Gordon Xu
2009-03-24 19:05           ` Chris Larson
2009-03-24 19:19             ` Junqian Gordon Xu
2009-03-24 19:29               ` Philip Balister
2009-03-24 19:51                 ` Tim Ellis
2009-03-24 20:01                   ` Chris Larson
2009-03-24 20:16                     ` Koen Kooi [this message]
2009-03-24 20:30                     ` Lon Lentz
2009-03-24 20:44                       ` Junqian Gordon Xu
2009-03-25  8:51                         ` Frans Meulenbroeks
2009-03-25 11:03                           ` Koen Kooi
2009-03-25 13:36                             ` Richard Purdie
2009-03-25 14:16                               ` Holger Schurig
2009-03-25 14:40                                 ` Richard Purdie
2009-03-25 15:32                                 ` Holger Schurig
2009-03-25 14:26                               ` Otavio Salvador
2009-03-25 16:05                             ` Mike (mwester)
2009-03-25 16:20                               ` Koen Kooi
2009-03-25 18:03                                 ` Jeremy Lainé
2009-03-25 18:22                                   ` Koen Kooi
2009-03-25 18:13                                 ` Mike (mwester)
2009-03-25 22:07                                 ` Frans Meulenbroeks
2009-03-25 22:27                                   ` Jeremy Lainé
2009-03-25 23:54                                     ` Mike (mwester)
2009-03-27  9:22                                       ` Richard Purdie
2009-03-24 19:59         ` Mike (mwester)

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='gqbf24$k5$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.