From: Mark Asselstine <mark.asselstine@windriver.com>
To: Henning Heinold <henning@itconsulting-heinold.de>,
Mario Domenech Goulart <mario@ossystems.com.br>,
Maxin John <maxin.john@intel.com>,
Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-devel@lists.openembedded.org
Subject: [meta-java] maintainer status
Date: Tue, 5 Jun 2018 11:11:26 -0400 [thread overview]
Message-ID: <10630413.xVAl2E7OaH@yow-masselst-lx1> (raw)
Several of us have noticed that nothing has been merged to meta-java since
mid-April (roughly 8 weeks ago). With about a dozen commits sent to the list
and pending merges I thought I might email you, the maintainers, directly to
determine if this is expected to continue. Should we be looking to update the
maintainers list and/or recruiting new people to restore the vitality of this
repo? Have your roles or positions changed making it no longer viable for you
to contribute to this repo?
Thanks in advance for your responses.
Mark
next reply other threads:[~2018-06-05 15:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 15:11 Mark Asselstine [this message]
2018-06-05 15:18 ` [meta-java] maintainer status Mark Asselstine
2018-06-05 15:51 ` Mark Asselstine
2018-06-05 16:48 ` Otavio Salvador
2018-06-05 17:45 ` Mark Asselstine
2018-06-06 7:38 ` Mario Domenech Goulart
2018-06-06 13:31 ` Mark Asselstine
2018-06-07 14:10 ` Mario Domenech Goulart
2018-06-07 14:14 ` Mark Asselstine
2018-06-06 20:42 ` Henning Heinold
2018-06-07 5:44 ` Richard Leitner
2018-06-07 13:22 ` Henning Heinold
2018-06-07 13:53 ` Richard Leitner
2018-06-07 13:56 ` Otavio Salvador
2018-06-07 14:11 ` Mark Asselstine
2018-06-07 14:32 ` Richard Leitner
2018-06-11 11:30 ` Maxin B. John
2018-06-11 12:08 ` Henning Heinold
2018-06-12 7:23 ` Richard Leitner
2018-06-12 20:59 ` Michael Halstead
2018-06-13 5:42 ` Richard Leitner
2018-06-13 10:05 ` Burton, Ross
2018-06-13 13:44 ` Richard Leitner
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=10630413.xVAl2E7OaH@yow-masselst-lx1 \
--to=mark.asselstine@windriver.com \
--cc=henning@itconsulting-heinold.de \
--cc=mario@ossystems.com.br \
--cc=maxin.john@intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.