Apologies for top-posting but all that scrolling . . .

Let's start with the first iteration of devuan.org in the current layout
that Hellekin and I put together for our first public release of Devuan
Jessie 1.0 Beta. Hopefully, it will put the issues brought up by Xenguy
at the last meet into historical perspective. Have a look here:

Jessie 1.0 Beta -
http://web.archive.org/web/20160604151752/http://www.devuan.org/

At that time I didn't even know what git was! I was entirely concerned
with the content, colors and layout of the site. Hellekin dealt with the
technical complexities of making it happen. It was quite a partnership!
You can see that all the navigation links were dumped on the index page.
Also note that dev1fanboy's docs were in a format detached from the
website proper and sourced from his git repo. This is the historical
reason that remains of dev1fanboy's "wiki" are present in the
documentation section. It was not some over-arching structural decision
for the www workflow which has ALWAYS been from www BETA to LIVE or
MASTER or whatever it was called at the time.

When Hellekin moved on, I took over www and eventually all public-facing
web content went through me, even dev1fanboy's and fsmithred's and the
docs that rrq and I crafted for the install disk(s). I had a LOT of
catching up to do but eventually managed to gain enough git
pointy-clicky proficiency to accomplish all the public-facing upgrades
to ascii and beowulf documentation as needed.

I also redesigned the site over the years to have a proper nav bar and
trimmed content down to the minimal needed. Mostly it consisted of
rearranging/compacting/rewriting and eliminating redundancies of
information already available. Please do take a tour on web.archive.org
to see how the site morphed over the years.

Then I just burned out - partly due to age; partly due to the enormous
workload - and Xenguy stepped up to take over www beginning with
Chimaera (though I still provided the matching default colors).

I should have thought to write this brief history of www earlier but now
that the issue came up, I finally mustered the focus to put things into
historical perspective. I do hope that it helps to clarify how we got to
where we are. Any questions? just ask!

golinux

On 2022-08-06 06:31, B Stack wrote:
> # Devuan meet 2022-08-04 @20:30 UTC
>
> Present: golinux, fsmithred, plasma41, rrq, Hendrik, Jaromil
>
> ## Old Business update of Devuan financial situation to 2022 Q2
> -jaromil
>
> ## Old Actions
>
> ## New Business
>
> ### Xenguy
>
> #### Documentation workflow There is a d1g forum thread here that has
> raised the (unresolved) issue of documentation workflow:
> https://dev1galaxy.org/viewtopic.php?id=5147 A fellow named Tomasz
> would like to improve the [Bullseye to Chimaera migration
>

> documentation](https://www.devuan.org/os/documentation/install-guides/chimaera/bullseye-to-chimaera.html).
>    In order to arrange this, Devuan team members need to clarify a
>   suitable agreed-upon documentation workflow.  I don't believe this is
>   something that I can sort out without assistance, discussion, and
>   feedback from the team members.  The situation at the moment seems
>   quite unclear to me, and I'm not 100% sure how to find a solution.

>
> ##### Question(s) for LeePen 1. IIUC (my git-fu is modest at best) git
> logs from the
>
> [www.devuan.org](https://git.devuan.org/devuan/www.devuan.org/commits/branch/new-beta)
> ('www') repo appear to indicate that you created documents such as:
> *
>
> https://www.devuan.org/os/documentation/install-guides/chimaera/bullseye-to-chimaera
> *
>
> https://www.devuan.org/os/documentation/install-guides/chimaera/upgrade-to-chimaera.html
> These appear to have been merged to the 'www' repo main branch from
> another branch 'wip/leepen' perhaps? I'm curious where these
> documents originated from though. For example, were they just copied
> from previous documents and then customized for Chimaera before being
> committed to a repo? (LeePen) I imagine something like that, although
> I don't remember precisely. 2. The same 2 documents above have now
> both been subsequently modified in 'www' repo by others. Are these
> documents intended to be the canonical or source versions at this
> point? To play devil's advocate, for example, this README file found
> in the same directory on 'www' seems to suggest that the canonical
> source of these files is *not* the 'www' repo but rather the
> 'installer-iso' repo:
>

> https://git.devuan.org/devuan/www.devuan.org/src/branch/new-beta/source/os/documentation/install-guides/chimaera/README.
>    When I check the latter repo, however, I do not see these same files
>   in evidence in the 'docs/docs' directory:

>
> https://git.devuan.org/devuan/installer-iso/src/branch/master/docs/docs
> . So just seeking some clarification regarding proper workflow for
> these files, going forward. (LeePen) I don't think it is completely
> clear. Some docs (certainly README, maybe others) have been created
> first for the installer-iso and then duplicated to www.
> * (Xenguy) Note that the README linked above is *not* be the main
> README
> file, e.g. for the ISO's. Click through and have a quick look, as I
> think perhaps it is inaccurate and creating confusion, and should
> perhaps be removed if it is no longer valid. The main question here
> is which files in which repos should be edited by others wanting to
> contribute to Devuan's documentation. This needs to be clarified, or
> folks like Tomasz won't be able to know which files to modify.
>

> ##### Question(s) for rrq 1. Is it possible to give a person 
> permissions
>   to modify a git repo like 'documentation' while *not* giving
>   permissions to modify the 'www' repo? (e.g. it would be nice to offer
>   new contributors a means to help us improve our documentation, whilst
>   not handing over all the keys to the publishing rights kingdom, if
>   that makes sense).
>   * (plasma41) Maybe it would be useful to start a devuan-patches
>     mailing list to allow accountless contributions to Devuan repos
>     using `git send-email`? (see also https://git-send-email.io/)
> * (rrq) afaik gitea does have per-project permissions, yes. Also, when
>   it comes to "larger" editing I think it common practice to fork the
>   project, then edit in the fork, and then make merge-requests for
>   propagating updates into the original project. The "documentation"
>   project was set up for developing and authoring various documentaion
>   pages and page sets, and then the "www.devuan.org" was seen as the
>   publishing place. I'm not sure if that process chain has actually 
> been
>   followed much (or at all) but rather that the published pages have
>   been hand-edited. So nowadays the connections between documents in 
> the
>   two projects is less immediate or clear. But in any case, the git
>   store is not meant to be a publishing place although essentially all
>   projects (at least the Devuan projects) are publically viewable
>   through the gitea wen interface.
> _______________________________________________

>