From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/news/
Date: Fri, 22 Dec 2017 11:20:48 +0000 (UTC) [thread overview]
Message-ID: <1513941569.8db770b1f0bd7f06151cf4285077695583e285f0.ulm@gentoo> (raw)
commit: 8db770b1f0bd7f06151cf4285077695583e285f0
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 21 13:52:03 2017 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri Dec 22 11:19:29 2017 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=8db770b1
general-concepts/news: Bring in line with updated GLEP 42.
Acked-by: Göktürk Yüksek <gokturk <AT> gentoo.org>
Closes: https://bugs.gentoo.org/641928
general-concepts/news/text.xml | 24 ++++++++++--------------
1 file changed, 10 insertions(+), 14 deletions(-)
diff --git a/general-concepts/news/text.xml b/general-concepts/news/text.xml
index d1af53e..06b5866 100644
--- a/general-concepts/news/text.xml
+++ b/general-concepts/news/text.xml
@@ -24,10 +24,14 @@ man page.
<ul>
<li>
- Choose a file name in the proper format: YYYY-MM-DD-name.lang.txt,
- where the date is followed by a name (a-z, 0-9, + (plus), - (hyphen)
- and _ (underscore)), the two-letter ISO language code (en for English
- must be chosen as default) and the file extension txt.
+ Choose a filename in the proper format:
+ <c>YYYY-MM-DD-shortname.lang.txt</c>, i.e. the date, followed by a very
+ short name of at most 20 characters and consisting only of <c>a-z</c>,
+ <c>0-9</c>, <c>+</c> (plus), <c>-</c> (hyphen) and <c>_</c> (underscore).
+ This is followed by <c>lang</c> which is an
+ <uri link="https://tools.ietf.org/rfc/bcp/bcp47.txt">IETF language
+ tag</uri>. Always use <c>en</c> for English, unless you are translating
+ a news item. Finally, the filename ends with the extension <c>txt</c>.
</li>
<li>
Write the news item, which is similar to a RFC-compliant email. Details
@@ -44,19 +48,11 @@ man page.
importance and should be revoked (can be possible).
</li>
<li>
- Upon acceptance, create a detached armored GnuPG signature with
- gpg --local-user --detach-sign --armor YYYY-MM-DD-name.lang.txt
- </li>
- <li>
- Verify that your signature is correct with
- gpg --verify YYYY-MM-DD-name.lang.txt.asc YYYY-MM-DD-name.lang.txt
- </li>
- <li>
Create a directory structure for your item in the gentoo-news repository
(<c>git+ssh://git@git.gentoo.org/data/gentoo-news.git</c>):
- YYYY/YYYY-MM-DD-name/.
+ <c>YYYY-MM-DD-shortname/</c>.
</li>
- <li>Add both the news file and the signature to that directory.</li>
+ <li>Add the news file to that directory.</li>
<li>Commit and push your changes to the gentoo-news repository.</li>
</ul>
next reply other threads:[~2017-12-22 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 11:20 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-21 13:49 [gentoo-commits] proj/devmanual:master commit in: general-concepts/news/ Ulrich Müller
2017-11-28 22:52 Ulrich Müller
2015-08-27 6:50 Justin Lecher
2014-07-24 18:06 Markos Chandras
2014-10-18 17:35 ` Markos Chandras
2012-03-17 10:07 Markos Chandras
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=1513941569.8db770b1f0bd7f06151cf4285077695583e285f0.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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