From: c.buhtz@posteo.jp
To: Emacs orgmode <Emacs-orgmode@gnu.org>
Subject: Re: Communication problems and possible problems with the website
Date: Fri, 25 Feb 2022 12:48:17 +0000 [thread overview]
Message-ID: <aa38e5c1859221f7866e5736d0bd7106@posteo.de> (raw)
In-Reply-To: <87ilt3yvqj.fsf@localhost>
Am 25.02.2022 13:30 schrieb Ihor Radchenko:
> If you think that the current wording is confusing, please point out
> which parts. We are pretty much blind here on the potential issues for
> the newcomers (for obvious reason - we are too familiar with Org).
> Pointing to the confusing parts would help a lot.
The text in the buffer after M-x org-submit-bugreport says in the first
line "You are about to submit a bug report to the Org mailing list".
This does not explain how this is done. As a (very fresh not Emacs
familiar) user I wouldn't assume that I have to setup my Emacs as a mail
client in that case. I would assume that there is some magic in behind.
;)
Just write something like "Make sure your Emacs is setup to send emails
or copy and paste the resulting buffer into an Email client of your
choice."
>> 5.
>> It is unclear where the repositories for the source code and the code
>> of
>> the website are. If I had found them I would have created a PR/patch
>> for
>> 2.
>
> This is confusing. If you go to orgmode.org, the git link is in the
> front
> page. Also, orgmode.org -> Install will bring you to the relevant page
> of the manual, which provides all possible installation options
> including cloning the official git repo.
But the front-page and the Install are not the place where I would
expect infos like that. Repos are for contributers not for users.
Users are reading "Install" and sometimes the front-page. I have not
read the front-page but clicked on contribute.
In contribute the git thing is explained in "Details on how to submit
patches" but there is a repo url missing.
> Similarly, https://orgmode.org/worg/ has the links to its code in the
> first heading:
>
>>> Worg documentation on your machine
>>> git clone https://git.sr.ht/~bzg/worg
Definitly my fault.
btw: I would suggest to create links or mirror repos on your GitHub
page.
> Do you recall the urls where you tried to search for the source code?
I searched behind the GitHub link (right top corner of the website)
first.
I searched around on savannah but still have problems with the
interface; which is another topic.
The point is that the users have to search (e.g. DuckDuckGo) because the
links to the repo or to description that there is no public repo are not
at the usual (compared to most of the other FOSS projects) places.
next prev parent reply other threads:[~2022-02-25 13:09 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 11:29 Communication problems and possible problems with the website c.buhtz
2022-02-25 12:20 ` Byung-Hee HWANG
2022-02-25 12:25 ` Russell Adams
2022-02-25 12:38 ` c.buhtz
2022-02-25 13:12 ` Russell Adams
2022-02-25 12:57 ` Ihor Radchenko
2022-02-26 9:09 ` Bastien
2022-02-25 12:30 ` Ihor Radchenko
2022-02-25 12:48 ` c.buhtz [this message]
2022-02-25 14:18 ` Ihor Radchenko
2022-02-25 14:24 ` c.buhtz
2022-02-25 15:08 ` Russell Adams
2022-02-26 9:19 ` Bastien
2022-02-25 15:14 ` Links to javascript-based websites from orgmode.org: Paypal and Github (was: Communication problems and possible problems with the website) Ihor Radchenko
2022-02-25 15:38 ` Michael Powe
2022-02-25 17:39 ` Links to javascript-based websites from orgmode.org: Paypal and Github Bastien Guerry
2022-02-26 5:50 ` Ihor Radchenko
2022-02-26 8:57 ` Bastien
2022-02-26 15:18 ` Jean Louis
2022-02-27 17:18 ` Bastien Guerry
2022-02-27 17:32 ` Neil Jerram
2022-02-27 4:11 ` Richard Stallman
2022-02-27 17:57 ` Bastien
2022-02-27 4:43 ` Bradley M. Kuhn
2022-03-20 11:27 ` Ihor Radchenko
2022-03-21 1:22 ` Bradley M. Kuhn
2022-02-27 11:29 ` Max Nikulin
2022-02-27 12:58 ` Timothy
2022-02-27 14:25 ` Michael Powe
2022-03-20 6:31 ` Ihor Radchenko
2022-06-18 1:29 ` Ihor Radchenko
2022-06-18 9:51 ` Ihor Radchenko
2022-06-18 14:31 ` Bastien
2022-06-19 15:52 ` Richard Stallman
2022-06-20 0:13 ` briangpowell
2022-06-20 1:22 ` Ihor Radchenko
2022-06-20 2:11 ` briangpowell
2022-06-20 2:35 ` Ihor Radchenko
2022-06-27 3:43 ` Richard Stallman
2022-06-27 10:11 ` Ihor Radchenko
2022-06-28 3:25 ` Richard Stallman
2022-06-28 3:35 ` Vikas Rawal
2022-07-02 3:33 ` Richard Stallman
2022-07-02 16:23 ` Vikas Rawal
2022-07-04 3:39 ` Richard Stallman
2022-07-04 4:32 ` Timothy
2022-07-04 12:38 ` Ihor Radchenko
2022-07-04 17:48 ` Michael Powe
2022-07-06 2:50 ` Richard Stallman
2022-07-06 14:42 ` Hendursaga
2022-07-08 3:33 ` Richard Stallman
2022-07-08 4:32 ` Tim Cross
2022-07-08 4:48 ` tomas
2022-07-08 5:25 ` Dr. Arne Babenhauserheide
2022-07-11 3:16 ` Richard Stallman
2022-07-11 4:37 ` Dr. Arne Babenhauserheide
2022-06-28 7:02 ` Dr. Arne Babenhauserheide
2022-06-28 8:23 ` Tim Cross
2022-06-30 3:09 ` Richard Stallman
2022-06-30 18:21 ` Dr. Arne Babenhauserheide
2022-07-01 3:34 ` Richard Stallman
2022-07-01 3:53 ` Tim Cross
2022-07-01 17:54 ` Michael Powe
2022-07-01 18:42 ` Samuel Banya
2022-07-02 17:02 ` Jeremie Juste
2022-07-01 3:59 ` Ihor Radchenko
2022-07-02 3:32 ` Richard Stallman
2022-07-02 3:56 ` Ihor Radchenko
2022-07-02 7:52 ` Thomas Dye
2022-07-02 8:43 ` Ihor Radchenko
2022-07-02 16:45 ` Thomas S. Dye
2022-07-04 12:31 ` Ihor Radchenko
2022-07-05 3:01 ` Richard Stallman
2022-07-05 3:34 ` Tim Cross
2022-07-05 8:45 ` Dr. Arne Babenhauserheide
2022-07-06 2:52 ` Richard Stallman
2022-07-06 7:15 ` Dr. Arne Babenhauserheide
2022-07-07 7:25 ` Richard Stallman
2022-07-06 17:55 ` Thomas S. Dye
2022-07-07 9:53 ` Ihor Radchenko
2022-07-07 16:02 ` Thomas S. Dye
2022-06-27 22:42 ` Tom Gillespie
2022-06-27 23:42 ` Tim Cross
2022-06-28 1:46 ` Michael Powe
2022-06-28 1:54 ` Ihor Radchenko
2022-06-28 19:48 ` Michael Powe
2022-06-28 2:29 ` Ihor Radchenko
2022-07-03 23:31 ` Jean Louis
2022-07-04 0:11 ` Ihor Radchenko
2022-02-26 8:21 ` c.buhtz
2022-02-26 9:05 ` Bastien
2022-02-26 9:13 ` Communication problems and possible problems with the website Bastien
2022-02-25 14:26 ` Russell Adams
2022-02-26 8:58 ` Bastien
2022-02-26 15:16 ` Jean Louis
2022-02-27 6:56 ` Ihor Radchenko
2022-02-27 17:17 ` Bastien Guerry
2022-02-27 18:25 ` Tim Cross
2022-02-27 23:15 ` Timothy
2022-02-28 13:51 ` c.buhtz
2022-03-20 6:44 ` Ihor Radchenko
2022-02-27 17:10 ` Bastien
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=aa38e5c1859221f7866e5736d0bd7106@posteo.de \
--to=c.buhtz@posteo.jp \
--cc=Emacs-orgmode@gnu.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.
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).