💾 Archived View for rawtext.club › ~sloum › geminilist › 006082.gmi captured on 2023-11-14 at 09:37:28. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Stephane Bortzmeyer stephane at sources.org
Sun Mar 14 09:08:48 GMT 2021
- - - - - - - - - - - - - - - - - - -
On Sat, Mar 13, 2021 at 08:30:19PM -0700, Thomas Frohwein <tfrohwein at fastmail.com> wrote a message of 79 lines which said:
Thirdly and lastly, about Gitlab. I strongly dislike the fact that
discussions which can have quite an impact on all Gemini users are
happening in Gitlab issues; to stay up-to-date on all these
requires regularly going through multiple webpages, and to comment
requires a Gitlab account! I think this is a mistake.
Agree, even with this one.
Group work is funny. When the discussion on the specification was onthe mailing list, everybody complained that it made a lot of messages,that it was difficult to follow, to know for sure what was decided ornot, etc. (I did share some of these complaints but not all; manyproblems were simply because some people do not use some features oftheir email client, such as threading and full-text search.) Nobodydefended the mailing list and asked for the specification discussionto remain there.
Now that we moved to another system, people (but may be not the same)complain about the new system. My (long) experience with "groupware"is that it is impossible to find a solution that will pleaseeveryone. I just note that an issue tracking system is used by someSDO (for instance the IETF) with success. (And, of course, it is usedby many programming teams.)
Regarding Gitlab, there is not yet (I regret it) a well-known andwidely used decentralized issue tracking system allowing not to havean account of the central system. (There are many experiments, butnothing solid yet.) So, it had to be a centralized system. We maydiscuss about gitlab vs. gitea and about one given gitlab hostervs. another one but I regard this as details.