Write-access to wiki -- Directions on how to document

Hi!

I am new to public work on software, so please correct any misconceptions I have,
thanks in advance!


I am evaluating roundup for the use as an inhouse maintenance tracker for around
100 facilities / sites (hence the need for recurring tasks).

Currently I think the "Roundup TODO Template" (which I quickly got working yesterday)
is a good starting point. (I tried around 20 different solutions, and not one fit -
some would be passable but renting an cloud service, with no option to self host
for an essential inhouse service, would be insane!)

An estimate for the total numer of tasks does not exist but pessimistic me
thinks there may be around 100 per site, so 100 x 100 = 10.000 - this is why I
like the "Roundup TODO Template":
 > # By default, only the upcoming issue is added to the tracker.


Going forward I am uncertain on how to document the proccess and modifications
so others can use this.

Would the https://wiki.roundup-tracker.org/ be a good place?

Or would a development forge be a better choice? I find the interface of
https://sourceforge.net/ to be quite confusing, but there seems to be alternatives,
 - https://sourcehut.org/ and
 - https://codeberg.org/
would either be a choice to track the changes?


--
Have a fine day!

r2d2