From: "Konstantin Ryabitsev via RT" <kernel-helpdesk@rt.linuxfoundation.org>
To: u.kleine-koenig@pengutronix.de
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [Kernel.org Helpdesk #86171] [linuxfoundation.org #86171] Re: Archive ptxdist@pengutronix.de on lore.kernel.org?
Date: Tue, 14 Apr 2020 17:31:22 -0400 [thread overview]
Message-ID: <rt-4.4.0-32647-1586899882-1406.86171-6-0@linuxfoundation> (raw)
In-Reply-To: <20200414213116.xpnbdvhzn7k3pcec@chatter.i7.local>
On Tue, Apr 14, 2020 at 05:52:53AM -0400, Uwe Kleine-König via RT wrote:
> >
> > I didn't hear back from you in reply to my request from three weeks ago.
> > Is this still on your radar and I just need some more patience?
>
> I still didn't hear anything back from you. The ticket on
> rt.linuxfoundation.org is still marked as "new".
>
> Following https://korg.wiki.kernel.org/userdoc/lore I'm currently in the
> step "Wait till you receive a response", but since I'm there since more
> than eight weeks I wonder if there is a problem on your side?
Hello, and sorry for radio silence. I wasn't deliberately trying to
stall -- I was just trying to figure out the best way to approach this.
While it's true that there are some things on lore.kernel.org that
aren't *directly* related to the kernel, we nevertheless try to stick to
lists that are either about low-level kernel subsystems, or about
various tools used for kernel development, or at least have predominant
topics that are close to the above two categories. The trouble with
ptxdist is that it doesn't really fit inside those boundaries, so I am
not sure whether it makes sense for it to live on lore.kernel.org.
Above all, I'd like to avoid turning lore.kernel.org into a central
resource that becomes a hard dependency for projects the same way gmane
was -- so much so, that when it disappeared, it caused serious ripple
across the open-source fabric.
We are encouraging others to set up their own instances of public-inbox,
and would prefer to mirror the resulting git repositories instead (and
offer indexing/searching capabilities) instead of doing archival on our
end. This is the approach we're taking with Yocto, and I would encourage
you to investigate the same option, as this would avoid making
lore.kernel.org a hard dependency for your project.
I hope that we'll be able to roll out our aggregated mirroring/indexing
service closer to mid-year -- and when that happens, we'll be happy to
mirror your lists and offer them alongside all others.
-K
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-04-14 21:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-86171@linuxfoundation>
2020-02-20 9:36 ` [ptxdist] " Uwe Kleine-König
2020-03-10 9:40 ` Uwe Kleine-König
2020-03-10 9:40 ` [ptxdist] [Kernel.org Helpdesk #86171] [linuxfoundation.org #86171] " Uwe Kleine-König via RT
2020-04-14 9:52 ` Uwe Kleine-König
[not found] ` <rt-4.4.0-32647-1586857973-606.86171-5-0@linuxfoundation>
[not found] ` <20200414213116.xpnbdvhzn7k3pcec@chatter.i7.local>
2020-04-14 21:31 ` Konstantin Ryabitsev via RT [this message]
2020-04-15 6:50 ` Uwe Kleine-König
2020-04-15 6:50 ` Uwe Kleine-König via RT
2021-11-26 10:28 ` Uwe Kleine-König
2022-02-23 7:50 ` Uwe Kleine-König
2022-05-03 7:04 ` Ahmad Fatoum
2022-06-30 7:55 ` Uwe Kleine-König
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=rt-4.4.0-32647-1586899882-1406.86171-6-0@linuxfoundation \
--to=kernel-helpdesk@rt.linuxfoundation.org \
--cc=ptxdist@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.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