Hi,
ignifugo (2021-01-03):
>> intrigeri <intrigeri@???> writes:
>>> I've compared these 3 options on
>>> https://gitlab.tails.boum.org/tails/tails/-/issues/18079
>> Thanks for the historic view and to all involved for the research.
> yes, thanks for share the process about Why and the comparison
>>> - non-wiki Git repository hosted on GitLab:
>>>
>>> - Lacks an easy way to attach files; this is one major use case for
>>> our blueprints
>>> - Lacks an easy way to create or rename a page
>
> I added the description in the table in the issue.
>
> You need be in a directory, there is the + button to upload file and new
> page.
Thanks! It's good that there's at least _a_ way to create pages and
upload files.
I think this "+" button may qualify as "easy" for page creation: even
though I was not able to find it myself, it's a design pattern that's
used in other places in GitLab, so I don't want to blindly generalize
my own experience.
I don't think this "+" button qualifies as "easy" for attaching files,
though: it's out of the flow of editing a page, so it's awkward
compared to how attachments work elsewhere in GitLab (and in wikis).
> browse in the page, with the blue button edit, you can rename the page
> that you created.
Thanks. Even with your explanation in hand, it took me a few more
minutes to figure out how to do it: the only way the UI hints me is
that the file path is an editable text area, which took me a while to
notice; then, the UI does not tell me that modifying the file path
will rename the page, so I had to actually try in order to confirm it
would do this (that's a bit scary). So this definitely does not
qualify as "easy" in my experience.
>>> So, my questions to you today are:
>>>
>>> - Do you agree that these are deal breakers?
>
> I'm not agree, but sure you have my consent for the migration.
>
> I think that also the gitlab markdown repo, not has an excellent navigation.
>
> And this could be a deal breaker for me.
>>> - Is there a deal breaker that I missed for the "GitLab wiki" option?
>
> I added a comment in the page issue page about usability of the
> navigation of gitlab wiki.
>
> https://gitlab.tails.boum.org/tails/tails/-/issues/18079#note_163274
> but is only to inform you/us, I don't want that we change strategy. only
> that recognize that could be exist this problem.
I'll read your comment carefully in the next few days.
I think it's important to have in mind the limitations of a tool
before we decide to migrate to it, so I thank you for this input.
I am tempted to do a quick'n'dirty prototype migration to
a (temporary) GitLab wiki, so we can see for ourselves how bad the
navigation would be.
Cheers!
