From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, tiwai@suse.de,
broonie@kernel.org
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem
Date: Sun, 12 Mar 2023 16:07:28 +0900 [thread overview]
Message-ID: <20230312070728.GA421475@workstation> (raw)
In-Reply-To: <20230311101554.14c211d4@kant>
Hi,
On Sat, Mar 11, 2023 at 10:15:54AM +0100, Stefan Richter wrote:
> On Mar 11 Takashi Sakamoto wrote:
> > I'm glad to see you again in the list ;)
> >
> > I really appreciate your long effort for the subsystem. I guess that your
> > life became swamped recently against your work in the subsystem, while I
> > feel that soft-landing of the project is still preferable for users.
>
> Thank you. I need to apologize that I neglected to (at least) drop my
> maintainership title myself. I should have done so when I started to
> realize that I am not able to fulfill this role anymore.
>
> > Below items are in my plan for the subsystem until being closed. I'm
> > pleased if getting your help in any time.
> >
> > * 2023, 2024, 2025, 2026
> > * take over the subsystem maintainer
> > * set up repositories in `<https://git.kernel.org/>`_
>
> Do you plan to re-use the existing (but neglected, by me) repos at
> kernel.org?
> https://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git
> https://git.kernel.org/pub/scm/libs/ieee1394/libraw1394.git
> https://git.kernel.org/pub/scm/libs/ieee1394/libiec61883.git
>
> If so, is there something which I can do to transfer access to you?
> (Although if yes, before that I need to enable myself to send encrypted
> e-mails again, after both of the mail user agents which I use dropped gpg
> support. Maybe the kernel.org admins can assist you quicker with repo
> access than I might.)
In the last week after posting the patch, I sent a request to system
administrator of kernel.org for the purpose. I think it will be done
within a few days so nothing left to us.
> > * refresh web site and update information
> > * take over the administration of communication channels
> > * adding the list archive of linux1394-devel to
> > `lore.kernel.org <https://korg.docs.kernel.org/lore.html>`_
> > * fix issues of subsystem
> > * modernize 1394 OHCI driver
> > * Pull requests to Linus
> > * get help from Linux Foundation to place documents for specification
> > defined by 1394 Trade Association
> > * If no problems, upload the documents to the new web site
> > * invite repositories of external librararies (``libavc1394``, ``libdc1394``)
> > * Announcement to distribution package maintainers about the upstream shift
> > * 2027, 2028
> > * Close announcement to below applications
> > * `FFMPEG <https://ffmpeg.org/>`_
> > * `GStreamer <https://gstreamer.freedesktop.org/>`_
> > * `VLC <https://www.videolan.org/vlc/index.ja.html>`_
> > * `MythTV <https://www.mythtv.org/>`_
> > * `FFADO <http://ffado.org/>`_
> > * 2029
> > * Close the project
> > * Close the communication channels
> > * Archive repositories
> > * Resign the subsystem maintainer
>
> It's good to see you being active in the kernel and related userland
> development/ maintainership, and that you have a plan for the next years.
At the moment, I have a problem about the list archive.
As you know, kernel development process heavily relies on mail. Recently
many developers use lore.kernel.org to store blasted message as
persistent storage. I would like to follow to it.
According to the documentation[1], the list archive should be prepared
including sent messages as much as possible. However I subscribed it Feb
2011 and sometimes lost messages.
I think you have the stock of enough amount of messages in your mail
box. If you have enough free time, I would ask you to create list
archive for the purpose.
[1] https://korg.docs.kernel.org/lore.html
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2023-03-12 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 3:58 [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem Takashi Sakamoto
2023-03-06 22:17 ` Randy Dunlap
2023-03-09 14:14 ` Takashi Iwai
2023-03-10 20:03 ` Stefan Richter
2023-03-11 8:03 ` Takashi Sakamoto
2023-03-11 9:15 ` Stefan Richter
2023-03-12 7:07 ` Takashi Sakamoto [this message]
2023-04-09 23:56 ` Randy Dunlap
2023-04-17 14:17 ` Takashi Sakamoto
2023-04-20 16:02 ` Takashi Sakamoto
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=20230312070728.GA421475@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox