Re: [Tails-dev] Proposal: migrate our blueprints to a GitLab wiki (#18079)
Hi, ignifugo (2021-01-03): >> 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! ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: migrate our blueprints to a GitLab wiki (#18079)
On 03/01/21 20:27, Zen Fu wrote: > Hi! > > 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. browse in the page, with the blue button edit, you can rename the page that you created. >> >> 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? > Not that I see. 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 have not solution for this now, only using gitlab. So every other strategy is... too long! hugs ignifugo > ___ > Tails-dev mailing list > Tails-dev@boum.org > https://www.autistici.org/mailman/listinfo/tails-dev > To unsubscribe from this list, send an empty email to > tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: migrate our blueprints to a GitLab wiki (#18079)
Hi! intrigeri writes: > Hi, > > Deadline if there are no major objections: January 9. This is because > I'd like to do this migration before we start using blueprints > intensively again while working on sponsor deliverables. > > In 2015 we decided to migrate our blueprints outside of our main > Git repository. > > - Be able to push more documents to our blueprints (images, office >documents, etc.) without polluting our main repo. > - Lock down all web editing on our main website. > - Allow more people to push changes to blueprints through Git if they >prefer this to the web editor. > - Maybe some day, host our website on servers that we don't trust to >push to tails.git. > > The implementation option we had chosen back then (setting up a new > ikiwiki) relied on sysadmin work, and never happened. Meanwhile, we > migrated to GitLab, so 2 new options are readily available to us: > > - GitLab wiki > - regular (non-wiki) Git repository hosted on GitLab > > 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. > IMO we can eliminate 2 of these options right away, because of deal > breakers, and I see no such blocker for the remaining option. > Here are the deal breakers I've spotted: > > - ikiwiki: > >- Lacks a nice syntax to link to GitLab issues, MRs, and commits >- Requires sysadmin work to migrate and maintain > > - 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 > > So, my questions to you today are: > > - Do you agree that these are deal breakers? Yes. > - Is there a deal breaker that I missed for the "GitLab wiki" option? Not that I see. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] [brainstorm] What are our public XMPP chat rooms useful for? (#17956)
Hi, Scope: "tails-dev" and "tails" public XMPP chat rooms. The server we currently use for our public XMPP chat rooms will stop operations later this year. First, I would like to better understand what these public chat rooms are currently useful for, for our project and its contributors. This will help decide whether we keep public chat rooms at all. And if we do, it'll tell us what we expect from such a service. So, my question is: What would we lose if we did not have any public chat room? In other words: What new problems would we face if we did not have any public chat room? Please share your input by January 17, after which I'll compile the answers publicly. Then, if it seems useful, I'll do a survey to better understand how important the benefits identified in this first round are to us as a group. Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
