Re: [DISCUSSION] Contributing policy for WORG

2025-04-28 Thread Ihor Radchenko
Ihor Radchenko writes: > I tried to reword worg-about to give instructions for people familiar > with git *and also people not familiar with git*. See the attached > tentative patch. Applied, onto master. https://git.sr.ht/~bzg/worg/commit/cfa22537 -- Ihor Radchenko // yantar92, Org mode maint

Re: [DISCUSSION] Contributing policy for WORG

2025-04-27 Thread Ihor Radchenko
Ihor Radchenko writes: > Corwin recently noticed that our > https://orgmode.org/worg/worg-about.html page is not very consistent > about whom and how should contribute to WORG. > > One part of that page suggests to "Create an account on Sourcehut" and > then push changes freely, while another par

Re: [DISCUSSION] Contributing policy for WORG

2025-04-23 Thread Bastien Guerry
Ihor Radchenko writes: > That would be welcome. You probably have a more clear picture of where > WORG should go. I will work on this and share something this week. -- Bastien

Re: [DISCUSSION] Contributing policy for WORG

2025-04-22 Thread Ihor Radchenko
Bastien Guerry writes: > "Taking care of Worg" means making this community-driven documentation > useful to as many users as possible. > > Maybe it means ... > > I suggest a call for volunteer, I can help drafting the call if needed. That would be welcome. You probably have a more clear picture

Re: [DISCUSSION] Contributing policy for WORG

2025-04-21 Thread Ihor Radchenko
Corwin Brust writes: > On Mon, Jan 20, 2025 at 4:27 PM Bastien Guerry wrote: >> >> Also thinking about Worg again: I don't know what Corwin and Krupal >> think, but maybe Worg deserves more maintainers? > > More maintainers sounds great! Should I create a call for maintainers? And, btw, what sh

Re: [DISCUSSION] Contributing policy for WORG

2025-04-21 Thread Bastien Guerry
Ihor Radchenko writes: > https://orgmode.org/worg/worg-about.html says "Their role is to take > care of the Worg repository and to empower new maintainers and > contributors.", but I am not sure what "take care" refers to here. Well, that's a good question. "Taking care of Worg" means making th

WORG licensing (was: [DISCUSSION] Contributing policy for WORG)

2025-04-20 Thread Ihor Radchenko
Bastien Guerry writes: >> Maybe I am missing something, but how can we do more than one license >> for the same WORG page? > > There are two ways in which two licences can "apply" to some content: > either by covering different parts of it, or by offering users a choice > of which licence to acce

Try gollum wiki to serve WORG (was: [DISCUSSION] Contributing policy for WORG)

2025-02-09 Thread Ihor Radchenko
Bastien Guerry writes: >>> What about gollum? >>> >>> https://github.com/gollum/gollum >>> >>> From what I understand, it would provide a way to let users modify Org >>> files by editing them from a web interface (without Git knowledge), on >>> top of rendering the .org files as HTML pages. >> >>

Re: [DISCUSSION] Contributing policy for WORG

2025-02-09 Thread Bastien Guerry
Ihor Radchenko writes: > I know for sure that git workflow scares off some users. So does email > workflow. > That's why I started thinking about alternatives. I agree that the current workflow for Worg contribution is not inclusive enough, experimentation for finding good alternatives is reall

Re: [DISCUSSION] Contributing policy for WORG

2025-02-09 Thread Bastien Guerry
Hi Ihor, Ihor Radchenko writes: > Bastien Guerry writes: > >> At some point, RMS asked for Worg content to be released under the GNU >> FDL, which is now the case. I think it would make sense to release it >> under *both* the GNU FDL and CC-by-SA 4.0. Perhaps it would also make >> sense to ask

Re: [DISCUSSION] Contributing policy for WORG

2025-02-09 Thread Ihor Radchenko
jman writes: > Joseph Turner writes: > >> Thanks for the suggestion! I imagine such a command would do this: > (...) > > I am not a Worg contributor but such workflow would definitively scare me off. > > Just out of curiosity: what is wrong with a git workflow to contribute to > Worg? I know

Re: [DISCUSSION] Contributing policy for WORG

2025-02-09 Thread Ihor Radchenko
Bastien Guerry writes: > At some point, RMS asked for Worg content to be released under the GNU > FDL, which is now the case. I think it would make sense to release it > under *both* the GNU FDL and CC-by-SA 4.0. Perhaps it would also make > sense to ask contributors to agree not to copy content

Re: [DISCUSSION] Contributing policy for WORG

2025-02-07 Thread Bastien Guerry
Bastien Guerry writes: > What about gollum? > > https://github.com/gollum/gollum Someone just mentioned gitit to me - we mentioned it already in 2013 and the project seems to be alive: https://github.com/jgm/gitit "Gitit is a wiki program written in Haskell. It uses Happstack for the web se

Re: [DISCUSSION] Contributing policy for WORG

2025-01-28 Thread Joseph Turner
Bastien Guerry writes: > Hi Joseph, > > Joseph Turner writes: > >>> What about gollum? >>> >>> https://github.com/gollum/gollum >>> >>> From what I understand, it would provide a way to let users modify Org >>> files by editing them from a web interface (without Git knowledge), on >>> top of ren

Re: [DISCUSSION] Contributing policy for WORG

2025-01-28 Thread Bastien Guerry
Hi Joseph, Joseph Turner writes: >> What about gollum? >> >> https://github.com/gollum/gollum >> >> From what I understand, it would provide a way to let users modify Org >> files by editing them from a web interface (without Git knowledge), on >> top of rendering the .org files as HTML pages. >

Re: [DISCUSSION] Contributing policy for WORG

2025-01-27 Thread Joseph Turner
Bastien Guerry writes: > Joseph Turner writes: > >>> I am not a Worg contributor but such workflow would definitively >>> scare me off. >> >> Understandable :) If we added some sort of bleeding-edge peer-to-peer >> way to contribute to worg, it would certainly be in addition to >> tried-and-true

Re: [DISCUSSION] Contributing policy for WORG

2025-01-20 Thread Bastien Guerry
Joseph Turner writes: >> I am not a Worg contributor but such workflow would definitively >> scare me off. > > Understandable :) If we added some sort of bleeding-edge peer-to-peer > way to contribute to worg, it would certainly be in addition to > tried-and-true methods like emailed patches. Be

Re: [DISCUSSION] Contributing policy for WORG

2025-01-20 Thread Joseph Turner
jman writes: > Joseph Turner writes: > >> Thanks for the suggestion! I imagine such a command would do this: > (...) > > I am not a Worg contributor but such workflow would definitively scare me off. Understandable :) If we added some sort of bleeding-edge peer-to-peer way to contribute to wor

Re: [DISCUSSION] Contributing policy for WORG

2025-01-20 Thread jman
Joseph Turner writes: Thanks for the suggestion! I imagine such a command would do this: (...) I am not a Worg contributor but such workflow would definitively scare me off. Just out of curiosity: what is wrong with a git workflow to contribute to Worg? Cheers,

Re: [DISCUSSION] Contributing policy for WORG

2025-01-20 Thread Corwin Brust
On Mon, Jan 20, 2025 at 4:27 PM Bastien Guerry wrote: > > Also thinking about Worg again: I don't know what Corwin and Krupal > think, but maybe Worg deserves more maintainers? > More maintainers sounds great!

Re: [DISCUSSION] Contributing policy for WORG

2025-01-20 Thread Bastien Guerry
Hi Joseph, thanks for sharing! I will continue to explore hyperdrive. Also thinking about Worg again: I don't know what Corwin and Krupal think, but maybe Worg deserves more maintainers? Worg should be treated like a real separate product, and maintainers need to "own" it in order to maintain it

Re: [DISCUSSION] Contributing policy for WORG

2025-01-20 Thread Joseph Turner
Ihor Radchenko writes: > Hi, > > Corwin recently noticed that our > https://orgmode.org/worg/worg-about.html page is not very consistent > about whom and how should contribute to WORG. > > One part of that page suggests to "Create an account on Sourcehut" and > then push changes freely, while ano

[DISCUSSION] Contributing policy for WORG

2025-01-19 Thread Ihor Radchenko
Hi, Corwin recently noticed that our https://orgmode.org/worg/worg-about.html page is not very consistent about whom and how should contribute to WORG. One part of that page suggests to "Create an account on Sourcehut" and then push changes freely, while another part suggests going through the ma