All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: yocto-patches@lists.yoctoproject.org,
	"Mingyu Wang (Fujitsu)" <wangmy@fujitsu.com>
Subject: Re: FW: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch
Date: Wed, 26 Feb 2025 11:35:56 +0000	[thread overview]
Message-ID: <51035527e7cdfa359095a272fb6d43b4d30233e1.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-g0eJ2y7e2HvZkLbjwhfA1Rk6Ox+_FK_k3-Ycocp2Wcg@mail.gmail.com>

On Wed, 2025-02-26 at 11:03 +0100, Alexander Kanavin via
lists.yoctoproject.org wrote:
> On Wed, 26 Feb 2025 at 01:34, Mingyu Wang (Fujitsu)
> <wangmy@fujitsu.com> wrote:
> > > The only answer is: meta-java has no maintainer, and Tim, or
> > > anyone
> > > else, is unable to help you. You need to become the maintainer
> > > first.
> > 
> > I wonder if it means that I or somebody else can become the
> > maintainer of meta-java?
> 
> What you can do is make a fork of meta-java somewhere public
> (typically we suggest github, but that might be difficult for you to
> access from PRC). Then you can add your patches and fixes in it, and
> send announcements here when there are significant enhancements. If
> there's a good track record and commitment to making it work
> according
> to official yocto layer standards, then we can make it official.

We could also provide a contrib/ branch in the repo which you could
push your changes too as a staging area.

Cheers,

Richard


      reply	other threads:[~2025-02-26 11:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21  3:26 [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch Mingyu Wang (Fujitsu)
2025-02-21  3:40 ` Khem Raj
2025-02-21  8:27   ` Mingyu Wang (Fujitsu)
2025-02-21  9:12     ` Richard Purdie
2025-02-21  9:20       ` Alexander Kanavin
2025-02-25  0:07         ` FW: " Mingyu Wang (Fujitsu)
2025-02-25  0:21         ` Mingyu Wang (Fujitsu)
2025-02-25  7:55           ` Alexander Kanavin
2025-02-26  0:34             ` Mingyu Wang (Fujitsu)
2025-02-26 10:03               ` Alexander Kanavin
2025-02-26 11:35                 ` Richard Purdie [this message]

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=51035527e7cdfa359095a272fb6d43b4d30233e1.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=wangmy@fujitsu.com \
    --cc=yocto-patches@lists.yoctoproject.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.