[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guix Documentation Meetup
From: |
Matt |
Subject: |
Re: Guix Documentation Meetup |
Date: |
Sat, 08 Jan 2022 11:24:35 -0500 |
User-agent: |
Zoho Mail |
> > I would like for Guix to host a community wiki (in addition to a more
> > discoverable official documentation).
>
> That’s the purpose of the Cookbook, which is open to all contributors.
The cookbook is a great resource. I'd like to contribute to it.
Let me walk through what that looks like from my perspective. I'm afraid,
however, that it comes across as aggressive, ungrateful, or demanding. None of
those are my intent! I genuinely want to help but struggle to understand the
process. My goal is to outline a "user story".
>From my perspective, contributing to the cookbook looks as follows. I've
>tried to be factual and ask rhetorical questions.
How do I contribute to the cookbook? I see no information in the cookbook about
how to do that. I'm looking at
https://guix.gnu.org/cookbook/en/guix-cookbook.html
The contribute page (https://guix.gnu.org/en/contribute/) links to this mailing
list. I am willing and ready to contribute. Now what?
I see the manual has a section on contributing:
https://guix.gnu.org/manual/en/html_node/Contributing.html#Contributing
I see nothing about how to contribute to documentation.
Do I need to submit a patch?
How do I submit a patch?
Do I have to write in TexInfo?
What is the roadmap from me spending hours authoring something to it being
available for review from experts or to being useful to others?
I see https://guix.gnu.org/manual/en/html_node/Commit-Access.html says I would
need three people to vouche for me, have to apply for maintainership, and some
other stuff I didn't read.
Would anyone actually vouche for me at this point?
I have two documents written in Org:
1. http://excalamus.com/test-guix-case-study-plover-python-dictionary.html
2. http://excalamus.com/2021-10-06-guix-debug.html
Do I have to convert them to TexInfo?
Who will review them?
Is the layout and style appropriate for info distribution?
Are there any licensing concerns to be aware of?
To close, I apologise for how aggressive all the questions can feel. Reading
over it is overwhelming, even for me. I'm afraid it may come across as simply
yelling "Why? Why? Why?" I would like to help provide answers. However, it
feels like myself and others are practically begging for direction on how to do
that. Someone has the authority and means to address these issues. Who is that
person and what is their gameplan for addressing the issues raised in this
thread? How do I (and others) figure into that plan? How I and others fit into
this community?
Thank you for your time and patience! (And for everyone, including you,
Ricardo, who have contributed to making Guix something myself and others want
to use and extend).
- Re: Guix Documentation Meetup, (continued)
- Re: Guix Documentation Meetup, Oliver Propst, 2022/01/10
- Re: Guix Documentation Meetup, Matt, 2022/01/10
- Re: Guix Documentation Meetup, jgart, 2022/01/11
- Re: Guix Documentation Meetup, Matt, 2022/01/11
- Re: Guix Documentation Meetup, jgart, 2022/01/11
- Re: Guix Documentation Meetup, Matt, 2022/01/11
- Re: Guix Documentation Meetup, Matt, 2022/01/11
Re: Guix Documentation Meetup, calcium, 2022/01/08
- Re: Guix Documentation Meetup, Ricardo Wurmus, 2022/01/08
- Re: Guix Documentation Meetup, calcium, 2022/01/08
- Re: Guix Documentation Meetup,
Matt <=
- Re: Guix Documentation Meetup, Ricardo Wurmus, 2022/01/08
- Re: Guix Documentation Meetup, Leo Famulari, 2022/01/08
- Re: Guix Documentation Meetup, Matt, 2022/01/09
- Re: Guix Documentation Meetup, André A . Gomes, 2022/01/10
- Re: Guix Documentation Meetup, Matt, 2022/01/10
- Re: Guix Documentation Meetup, André A . Gomes, 2022/01/10
- Re: Guix Documentation Meetup, Matt, 2022/01/11
Re: Guix Documentation Meetup, Leo Famulari, 2022/01/12
Re: Guix Documentation Meetup, Matt, 2022/01/12
Planet of Guix-related posts?, zimoun, 2022/01/10