From: David Masterson <dsmasterson@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Corwin Brust <corwin@bru.st>, Max Nikulin <manikulin@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: Suggestion: User-contributed use-cases on orgmode.org ?
Date: Thu, 16 Nov 2023 21:13:33 -0800 [thread overview]
Message-ID: <LV8P223MB09202F19C408C6CA8B0F7257A2B7A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87cywa9gpg.fsf@localhost> (Ihor Radchenko's message of "Thu, 16 Nov 2023 09:43:07 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> David Masterson <dsmasterson@gmail.com> writes:
>
>> In worg-about, it looks like the repo is ~bzg/worg on src.ht, but "worg"
>> doesn't come up in the project search on src.ht (but "org" does). Is
>> the repo hidden (I don't have an account on src.ht yet -- perhaps
>> sourcehut should be explained a bit in worg-about).
>
> May you please provide more details?
I'll try.
> Do you refer to <https://orgmode.org/worg/worg-about.html>?
Yes.
> FYI, WORG is listed in "Repositories" right at https://sr.ht/~bzg/org/
I see no mention of "~bzg/org" in worg-about. I think my lack of
experience for many years is showing -- I didn't think to click on the
~bzg/worg link which would've told me about ~bzg/org. I assumed the
link was just telling me what to put on 'git clone'. Perhaps that
should be explained a little more in worg-about.
What I did was go to sr.ht to see what it looked like and maybe sign up
for an account. I followed the "More Projects" link and searched for
"~bzg/worg", but nothing came up. However, searching for "org" did
bring up "~bzg/org". Being out of practice, I was confused.
>>> Alternatively, perhaps the key element of "wiki" for some is "web
>>> accessible editing", in which case I wonder if using EmacsWiki would
>>> make sense.
>>
>> Duh! Why did I forget about EmacsWiki?!? Web accessible editing is a
>> plus to allow organic growth to the wiki -- as long as some rules are
>> followed. Wikis allow easy undoing of page edits (if necessary) and (I
>> think) locking pages to be edited only by a few people (creator/admins).
>> There could be a talk page for suggesting additions to a use-case to
>> make it more flexible which the use-creator creator could test and
>> incoporate into the use-case (or just tag it as interesting).
>
> Currently, we prefer all the discussions, including discussions of WORG
> pages, to happen on this mailing list.
And I'm beginning to warm to WORG's approach. I used FosWiki a long
time ago which is different.
> One interesting idea could be showing the comment threads right on the
> WORG pages, similar to
> https://isso-comments.de/
> https://staticman.net/
> https://meta.discourse.org/t/embed-discourse-comments-on-another-website-via-javascript/31963
> https://amnesiak.org/post/2021/01/30/hugo-blog-with-mastodon-comments-extended/
These each look interesting.
> Or we might consider https://git.sr.ht/~bzg/woof to automatically update
> WORG pages for appropriately marked mailing list threads.
Hmm. That sounds most interesting becuase it command line driven.
Perhaps a new mailing list should be created for this?
--
David Masterson
next prev parent reply other threads:[~2023-11-17 5:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 5:09 Suggestion: User-contributed use-cases on orgmode.org ? David Masterson
2023-11-14 8:36 ` Russell Adams
2023-11-14 10:31 ` Max Nikulin
2023-11-15 2:16 ` David Masterson
2023-11-15 3:23 ` Corwin Brust
2023-11-16 2:56 ` David Masterson
2023-11-16 9:43 ` Ihor Radchenko
2023-11-17 5:13 ` David Masterson [this message]
2023-11-17 9:31 ` Ihor Radchenko
2023-11-17 18:26 ` David Masterson
2023-11-18 10:51 ` Ihor Radchenko
2023-11-18 19:18 ` David Masterson
2023-11-19 15:38 ` Bastien Guerry
2023-11-15 2:14 ` David Masterson
2023-11-15 13:33 ` Russell Adams
2023-11-16 2:58 ` David Masterson
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=LV8P223MB09202F19C408C6CA8B0F7257A2B7A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
--to=dsmasterson@gmail.com \
--cc=corwin@bru.st \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--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).