All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: daisy branch for meta-openembedded, meta-qt5 / maintainer wanted
Date: Mon, 16 Jun 2014 15:48:50 +0200	[thread overview]
Message-ID: <20140616134850.GP2428@jama> (raw)
In-Reply-To: <20140511145337.GE22774@jama>

[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]

On Sun, May 11, 2014 at 04:53:37PM +0200, Martin Jansa wrote:
> On Wed, May 07, 2014 at 11:32:34AM -0700, Philip Balister wrote:
> > On 05/05/2014 09:45 AM, Martin Jansa wrote:
> > > On Mon, May 05, 2014 at 09:32:04AM -0700, Adam Lee wrote:
> > >> Hi JaMa, what does it take to be a maintainer?
> > >>
> > >> Do I need to build check all the packages everyday?
> > > 
> > > Definitely no everyday, there are more patches coming in just after the
> > > release, but later it's something like 1-5 patches in month.
> > > 
> > > So it doesn't need much time, but it's always good when it's done by
> > > someone else then master maintainer (to setup separate builds etc).
> > > 
> > > Possibly more time is spent on watching the ML, because many people
> > > don't read README file and instead of following the proper procedure for
> > > backports to relase branches they just say somewhere in ML "BTW: also
> > > merge this to dora".
> > > 
> > > You can also have some co-maintainer if you find way to split the work
> > > without duplicating it.
> > 
> > Adam,
> > 
> > I'd be glad to help scan the list for backport requests.
> 
> Can one of you send README update patch?

There are first few backport requests and we still don't have official
daisy maintainer and README update.

Can anyone please volunteer and send README update patch?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2014-06-16 13:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 14:37 daisy branch for meta-openembedded, meta-qt5 / maintainer wanted Martin Jansa
     [not found] ` <CAFeBWL5HuWex48xB_JZX_C7RMhzgfH93=AVJAkO7Qk7DUToFxg@mail.gmail.com>
2014-05-05 16:45   ` Martin Jansa
2014-05-07 18:32     ` Philip Balister
2014-05-11 14:53       ` Martin Jansa
2014-06-16 13:48         ` Martin Jansa [this message]
2014-06-17 20:55           ` Otavio Salvador
2014-06-18  1:32             ` Cliff Brake
2014-06-18  1:45               ` Cliff Brake
2014-06-18 11:27               ` Otavio Salvador
2014-06-18 14:04                 ` Cliff Brake
2014-06-18 14:21                   ` Martin Jansa
2014-06-18 14:34                     ` Cliff Brake
2014-06-23  7:15                       ` Steffen Sledz
2014-06-23 11:01                         ` Martin Jansa
2014-06-23 11:13                           ` Steffen Sledz
2014-06-18 15:20                   ` Otavio Salvador
2014-06-18 16:41                     ` akuster808
2014-05-11 23:03       ` Otavio Salvador

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=20140616134850.GP2428@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.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.