[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Communication problems and possible problems with the website

From: Russell Adams
Subject: Re: Communication problems and possible problems with the website
Date: Fri, 25 Feb 2022 15:26:36 +0100

On Fri, Feb 25, 2022 at 12:48:17PM +0000, c.buhtz@posteo.jp wrote:
> 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."

Pardon. M-x report-emacs-bug opens a side panel which clearly states
you can copy the message content out for another email program.

Perhaps we should update the information popup in
org-submit-bugreport. Can you recommend some additional explaination?

> >> It is unclear where the repositories for the source code and the code
> 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.

Are they? Many Emacs users pull direct from repos, which is why it's
front and center on the main orgmode site.

I think the difference here is between users and developers, where in
Emacs many users are developers and use tools like Git daily.

> In contribute the git thing is explained in "Details on how to submit
> patches" but there is a repo url missing.

I think we should consider adding the repo to the top of contribute as
well. Good idea.

> btw: I would suggest to create links or mirror repos on your GitHub
> page.

This could be done in Worg.

> > 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.

I agree this is rather confusing. I think maybe we should consider
creating a comprehensive list of repos on Worg.

Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

reply via email to

[Prev in Thread] Current Thread [Next in Thread]