From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30133] New: proposed new mini service: linkdump aggregator
Date: Fri, 17 Feb 2023 16:03:00 +0000 [thread overview]
Message-ID: <bug-30133-14326@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30133
Bug ID: 30133
Summary: proposed new mini service: linkdump aggregator
Product: sourceware
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: Infrastructure
Assignee: overseers at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
Let's consider adding a new service that allows contributors to assemble a
curated collection of links for the broader sourceware community. Many of our
guest projects' contributors publish blog posts here and there regularly, but
lack an easy searchable index & collection.
One simple possibility is to create a new wiki (moin or iki), one wiki page per
link, and use Categories/Tags for grouping links by topic.
Would propose a fairly open editor/contributor policy.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-02-17 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 16:03 fche at redhat dot com [this message]
2023-02-17 16:03 ` [Bug Infrastructure/30133] " fche at redhat dot com
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=bug-30133-14326@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).