Author: Ralph Ronnquist Date: To: devuan developers internal list Subject: Re: [devuan-dev] Use of wikis on gdo
+1
Evilham wrote on 31/8/19 2:42 am: > Hello,
>
> andy5995 raised some questions about wikis on the GitLab instance and
> golinux mentioned, so I took a look.
>
> The issue being: forks of a project don't contain any wiki pages and
> there is no functionality to contribute to them by non-project-mebmers,
> so they are kinda useless in that nobody is maintaining them and whoever
> could improve them faces the not-a-project-member wall.
>
> First thing: GitLab and gitea and GitHub deal with wiki as a special git
> repository, so migrating existing data is totally doable and not too
> complicated.
>
>
> I ran a thing against gdo and identified the projects with potentially
> relevant wikis.
> There are only 23 projects with wikis on gdo and some are on user's
> projects, so not relevant here.
>
> I've check the relevant wikis manually and identified three groups with
> a different general plan of action for each.
>
> Since this is non-critical and does not affect the OS, if nobody says
> anything against a particular point / for something different, I'll see
> that those who do use these even if every once in a while are OK with
> the proposal and go through with them in a couple weeks.
>
>
> # A. Project exists just for the wiki
>
> ## Various 'official' documentation
> * devuan-doc/manuals
> * devuan/devuan-documentation
> * devuan/devuan-project
> * devuan/devuan-maintainers
>
> Out of these, basically only devuan-project and devuan-maintainers have
> any content.
>
> ## dev1fanboy/Upgrade-Install-Devuan
> This one is a bit special, wiki and repository appear to be very
> similar; hopefully they are pretty much the same.
>
> On top of the above proposal to have a single wiki branch on a
> repository, I'd go further and recommend we merge all these projects
> into devuan/devuan-documentation, while maintaining attribution and git
> history for e.g. dev1fanboy's wiki.
> From a short IRC chat it appears that fsmithred and golinux agree this
> would be an improvement.
>
> This should make it significantly easier to have an overview of these
> things.
> On that note: the contents of all of these wikis is probably very
> outdated; this over-compartmentalising is likely at least partially at
> fault.
>
> Since GitLab / gitea / whatever do render markdown/asciidoc documents
> properly when browsing a repository, we could even disable the wiki and
> just import the documents to a 'wiki' branch that is the default.
> This would enable by-passers to change the pages and create Merge Requests.
>
> We could also optionally sync the wiki repository with that branch, so
> that the rendered wiki is the same as the source repository.
> But also we can disable the wiki functionality altogether and have less
> duplication for little-to-no gain.
>
> # B. Project does not have a specially useful wiki
>
> ## devuan-editors/devuan-art
> @golinux:
> Maybe the contents of the wiki could go to a docs directory in the main
> branch instead.
>
> ## devuan-editors/devuan-www
> @golinux:
> I doubt anyone looks at the wiki for this repository. If there is
> anything useful it should be moved to a docs directory in the main
> branches.
>
> ## devuan-packages/vtap
> @rrq:
> There doesn't seem to be any content. Just deleting and disabling the
> wiki would be enough.
>
> # C. Project appears to be useless (right now)
>
> Maybe these were useful in the past, maybe they never came to be.
> Either way, I'd think these projects should be marked as archived and
> revived if applicable in some future.
>
> ## devuan-editors/devuan-news
>
> ## devuan-infrastructure/Installer_Feedback
> @Centurion_Dan:
> Unsure if this is used anywhere, it doesn't look like it's ever been
> used though.
> --
> Evilham
> _______________________________________________
> devuan-dev internal mailing list
> devuan-dev@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev
::
Re: [devuan-dev] Use of wikis on gd…
