From: Bastien <bzg@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "András Simonyi" <andras.simonyi@gmail.com>,
"emacs-orgmode list" <emacs-orgmode@gnu.org>
Subject: Re: Screenshots in ORG-NEWS
Date: Tue, 03 Jan 2023 13:36:51 +0100 [thread overview]
Message-ID: <87cz7vdcbg.fsf@gnu.org> (raw)
In-Reply-To: <87edsbkitd.fsf@localhost> (Ihor Radchenko's message of "Tue, 03 Jan 2023 10:34:38 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> I am afraid that maintaining both etc/ORG-NEWS and also worg/news.org
> will be a bit too much.
Maintaining etc/ORG-NEWS is the responsability of maintainers.
Adding useful (possibly visual) informations on Worg is the task of
the community.
Of course, the work people like Tim are doing on their blog is also a
"community task" and a very useful one: if we can have some of these
efforts directed toward the community-maintained worg/news.org file,
that'd be good.
> Though maybe one can be a source for another?
etc/ORG-NEWS would definitely be the source for any worg/news.org
file, just as it is for community efforts to promote new (or even
"upcoming") stuff.
--
Bastien
next prev parent reply other threads:[~2023-01-03 12:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 9:42 [PATCH] oc-csl: Improve LaTeX bibliography formatting András Simonyi
2022-11-07 2:47 ` Ihor Radchenko
2022-11-07 11:15 ` András Simonyi
2022-11-08 5:26 ` Ihor Radchenko
2022-12-11 19:00 ` András Simonyi
2022-12-12 9:07 ` Ihor Radchenko
2022-12-12 11:15 ` András Simonyi
2022-12-12 11:24 ` Ihor Radchenko
2022-12-29 15:40 ` Bastien Guerry
2022-12-31 12:22 ` Screenshots in ORG-NEWS (was: [PATCH] oc-csl: Improve LaTeX bibliography formatting) Ihor Radchenko
2023-01-02 15:11 ` Screenshots in ORG-NEWS Bastien
2023-01-03 10:34 ` Ihor Radchenko
2023-01-03 12:36 ` Bastien [this message]
2022-12-13 16:05 ` [PATCH] oc-csl: Improve LaTeX bibliography formatting Timothy
2022-12-13 19:03 ` András Simonyi
2022-12-27 22:32 ` András Simonyi
2022-12-29 10:14 ` Ihor Radchenko
2022-12-29 21:51 ` András Simonyi
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cz7vdcbg.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=andras.simonyi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).