Re: asciidoc git workflow vs libreoffice change tracking

--===============5216517176186430891==
Content-Type: multipart/alternative; boundary="0000000000006efc7105cd641ea9"

--0000000000006efc7105cd641ea9
Content-Type: text/plain; charset="UTF-8"

>
> On Fri, Sep 24, 2021 at 10:08:58PM +0000, Leslie S Satenstein wrote:
> > I have used asciidoc and just find that it is acceptable, because the
> > maintenance is in ascii, but it is not convenient for tracking changes
> and
> > collaboration.
>

Thanks for volunteering to help with the documentation Leslie! Since you
are working on the installation guide, you may find the examples on the
page linked below insightful.

https://pagure.io/fedora-docs/install-guide/pull-requests?status=False

Each "Pull Request" listed on the above linked page tracks exactly who made
exactly what change and when (browse the "Files Changed" tab for each PR to
see exactly what was changed). There is a bit of a learning curve to using
git if you aren't already familiar with it. But it is extremely powerful in
terms of its ability to track changes (they can also be undone and "cherry
picked" and there is support for merging conflicting changes by different
authors but you don't need to worry about any of that to get started).

I would suggest starting small just to get things figured out. Try
submitting a pull request to correct a small grammar mistake or typo first
just to get the hang of how things work. Your submission should show up on
the "Pull Requests" tab here: https://pagure.io/fedora-docs/install-guide

Once accepted ("merged"), the record of your change will be archived under
the "XX Merged" link on the pull requests page.

Thanks for contributing!

--0000000000006efc7105cd641ea9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">On Fri, Sep 24, 2021 at 10:08:58PM +0000, Leslie S Saten=
stein wrote:<br>
&gt; I have used asciidoc and just find that it is acceptable, because the<=
br>
&gt; maintenance is in ascii, but it is not convenient for tracking changes=
 and<br>
&gt; collaboration.<br></blockquote><div><br></div><div>Thanks for voluntee=
ring to help with the documentation Leslie! Since you are working on the in=
stallation guide, you may find the examples on the page linked below insigh=
tful.</div><div><br></div><div><a href=3D"https://pagure.io/fedora-docs/ins=
tall-guide/pull-requests?status=3DFalse">https://pagure.io/fedora-docs/inst=
all-guide/pull-requests?status=3DFalse</a><br></div><div><br></div><div>Eac=
h &quot;Pull Request&quot; listed on the above linked page tracks exactly w=
ho made exactly what change and when (browse the &quot;Files Changed&quot; =
tab for each PR to see exactly what was changed). There is a bit of a learn=
ing curve to using git if you aren&#39;t already familiar=C2=A0with it. But=
 it is extremely=C2=A0powerful in terms of its ability to track changes (th=
ey can also be undone and &quot;cherry picked&quot; and there is support fo=
r merging conflicting changes by different authors but you don&#39;t need t=
o worry about any of that to get started).</div><div><br></div><div>I would=
 suggest starting small just to get things figured out. Try submitting a pu=
ll request to correct a small grammar mistake or typo first just to get the=
 hang of how things work. Your submission should show up on the &quot;Pull =
Requests&quot; tab here:=C2=A0<a href=3D"https://pagure.io/fedora-docs/inst=
all-guide">https://pagure.io/fedora-docs/install-guide</a></div><div><br></=
div><div>Once accepted (&quot;merged&quot;), the record of your change will=
 be archived under the &quot;XX Merged&quot; link on the pull requests page=
.</div><div><br></div><div>Thanks for contributing!</div></div></div>

--0000000000006efc7105cd641ea9--

--===============5216517176186430891==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG9jcyBtYWls
aW5nIGxpc3QgLS0gZG9jc0BsaXN0cy5mZWRvcmFwcm9qZWN0Lm9yZwpUbyB1bnN1YnNjcmliZSBz
ZW5kIGFuIGVtYWlsIHRvIGRvY3MtbGVhdmVAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmcKRmVkb3Jh
IENvZGUgb2YgQ29uZHVjdDogaHR0cHM6Ly9kb2NzLmZlZG9yYXByb2plY3Qub3JnL2VuLVVTL3By
b2plY3QvY29kZS1vZi1jb25kdWN0LwpMaXN0IEd1aWRlbGluZXM6IGh0dHBzOi8vZmVkb3JhcHJv
amVjdC5vcmcvd2lraS9NYWlsaW5nX2xpc3RfZ3VpZGVsaW5lcwpMaXN0IEFyY2hpdmVzOiBodHRw
czovL2xpc3RzLmZlZG9yYXByb2plY3Qub3JnL2FyY2hpdmVzL2xpc3QvZG9jc0BsaXN0cy5mZWRv
cmFwcm9qZWN0Lm9yZwpEbyBub3QgcmVwbHkgdG8gc3BhbSBvbiB0aGUgbGlzdCwgcmVwb3J0IGl0
OiBodHRwczovL3BhZ3VyZS5pby9mZWRvcmEtaW5mcmFzdHJ1Y3R1cmUK

--===============5216517176186430891==--