Transition from monotone/trac to git/gitlab (housekeeping task?)
The repository still contains not updated references to the old tool base (monotone/trac) in both, the scripts/code and the texts.
Code
Notably site-updater.sh and site-updater-i2hq.sh provide their functionality in both, a git and a monotone flavour. If monotone is not used at all any more (as was stated on irc/i2p-dev) then those code portions for monotone could probably just be removed.
However, completely refactoring might involve a lot more still as for example echo "Git revision: $(git log -n 1 | grep commit | sed 's/commit: //' | sed 's/ .*$//')" >./i2p2www/pages/include/mtnversion
suggests that paths will still reflect those origins. Those might then appear in any of the more internal functions not even using any vcs as well then.
Unsure, how important this is, but wanted to bring it up as I stumbled over it ...
Text
In the textual parts (actual documentation) there are also still parts in which current state (solely using git/gitlab instead of the prior monotone/trac) is not accurately reflected, yet. I will try to find and eliminate those in a local branch myself to come up with a merge request of some kind for those then.
Complete Files Removal/Renaming?
The following files could be irrelevant or have an outdated naming by now (?):
- keys.txt, (only file in that dir also)
- monotonerc.html -> this becomes included in license-agreements.html which accordingly has this name/path to be changed (the signed messages there also refer to "my monotone key" btw)
- monotone.html - this is referenced in index.html and [threat-model.html] (/i2p2www/pages/site/docs/how/threat-model.html) (multiple times)
- transition-guide.html
Other things I couldn't (fully) address
- Navigation Community > Develop > Bugtracker is still set to trac. Now this uses i2pconv() to translate between clearnet/i2p addresses as needed, but I noticed that while the dictionary does contain i2pgit.org, the translation there is to the i2p address instead of to the clearnet address? So just changing the url to the git version would still leave the link "broken" on clearnet as it would display only the .i2p address? Unsure about implications and how exactly this is supposed to be ... Same translation is in get-involved then.
-
jbigi.html - I couldn't even figure out where this is in the navigation, so I assume it might be somewhere in the blog posts maybe? When searching it via DDG it's found as
https://geti2p.net/en/misc/jbigi
- same for cvs.html -
new-translators
- has a link to ugha.i2p - which hasn't been reachable for me for a while?
- The rather detailed workflow seems to be "more" outdated than just transitioning from monotone to git, e.g. the files listed for console translations have moved/changed or so?
- I'm placing a "Please note the suggested workflow for git on our git-page." there (in my changes), but cannot add a link "without touching tags" - which I refrain from, as I do not understand them yet
- release-signing-key, signed-keys, and developers-keys - all sound too important for me to touch but refer to monotone a lot. Someone (TM) should have a look ;)
- ports.html currently lists three (!) ports as reserved for monotone. I don't know how much of a (how long lasting) standard this defines and if it's still relevant for all three of them
- team page lists eche|on as the monotone guru. Not sure at what point you guys might want to (re)move that?
This all needs to be double-checked by someone more experienced, though. I don't quite understand building/navigation etc., yet. The second file could to be the key-file and just "still named monotone" from the looks ... url-variables are named monotone but already point to git at several places.