Re: [Tails-dev] Spring cleaning our GitLab labels
Hi, intrigeri (2022-02-22): > 1. Delete these labels > >- Camouflage: no open issues, probably never coming back >- I2P: no open issues, probably never coming back >- Handbook: only 2 open issues, can be tracked just fine with other > labels >- Feed Reader: no open issues; can now be tracked with "Email > Client" since Thunderbird is our feed reader nowadays >- Security Check: 1 open issue, 5 closed issues ⇒ not worth it >- Verification Extension: we stopped using this a year ago > so at this point I think the drawbacks of keeping this label > outweigh the benefits of listing these 48 closed issues Done. > 2. Merge these labels: > >- "C: Installation", "C: Installation Assistant", "C: Installer" > → "C: Installation" Done. > 3. Rename these labels: > >- "T: Test" → something that is harder to confuse with "C: Test > suite"; ideas welcome; if nothing convincing arises I'll skip > this one. Note done, by lack of proposals. 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] Spring cleaning our GitLab labels
intrigeri: > 2. Merge these labels: > >- "C: Installation", "C: Installation Assistant", "C: Installer" > → "C: Installation" I also thought about that this other day. So, yes! -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ 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] Spring cleaning our GitLab labels
Hi, Zen Fu (2022-02-22): > I'm not sure how important such historical metadata is, though, so maybe > it's not a problem. For the labels I proposed to delete, IMO historical metadata will probably never be useful again. But if affected people have doubts about this for some of these labels, then I would lean towards being conservative and deprecate them instead of deleting them. > If it's desired to maintain such historical metadata, one alternative > could be to rename them and add some flag that means they're deprecated, > like described here[2]. This does not achieve one of my goals here: e.g. when I type "install" in the label selection entry field, the filtered list GitLab gives me would still have 3 labels, 2 of them being marked as deprecated, while with my proposal, I would see only 1, which is the one I want. Same for "security". But I can live with that too if folks prefer :) Thanks for making this explicit: I had it in mind when I wrote my original proposal but forgot to make it clear. 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] Spring cleaning our GitLab labels
Hi, the only concern that comes to my mind is loss of historical metadata. "If you delete a label, it is permanently deleted. All references to the label are removed from the system and you cannot undo the deletion." [1] I'm not sure how important such historical metadata is, though, so maybe it's not a problem. If it's desired to maintain such historical metadata, one alternative could be to rename them and add some flag that means they're deprecated, like described here[2]. From my side, feel free to decide how to go about it, I just wanted to bring some food for thought. [1] https://docs.gitlab.com/ee/user/project/labels.html [2] https://about.gitlab.com/handbook/marketing/project-management-guidelines/labels/#dont-delete-deprecate -- intrigeri writes: > Hi, > > We've been using GitLab since a while and I think it's a good time to > make our set of labels a bit leaner and easier to use. > > I want to focus on low hanging fruits here. I don't think it's a good > time to take a step down and do a full revamp of our labels. > > I propose we: > > 1. Delete these labels > >- Camouflage: no open issues, probably never coming back >- I2P: no open issues, probably never coming back >- Handbook: only 2 open issues, can be tracked just fine with other > labels >- Feed Reader: no open issues; can now be tracked with "Email > Client" since Thunderbird is our feed reader nowadays >- Security Check: 1 open issue, 5 closed issues ⇒ not worth it >- Verification Extension: we stopped using this a year ago > so at this point I think the drawbacks of keeping this label > outweigh the benefits of listing these 48 closed issues > > 2. Merge these labels: > >- "C: Installation", "C: Installation Assistant", "C: Installer" > → "C: Installation" > > 3. Rename these labels: > >- "T: Test" → something that is harder to confuse with "C: Test > suite"; ideas welcome; if nothing convincing arises I'll skip > this one. > > I'm ready to drop any of these ideas if there are objections from > people who use these labels. > > I plan to proceed no earlier than in 2 weeks. > > 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. ___ 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] Spring cleaning our GitLab labels
Hi, We've been using GitLab since a while and I think it's a good time to make our set of labels a bit leaner and easier to use. I want to focus on low hanging fruits here. I don't think it's a good time to take a step down and do a full revamp of our labels. I propose we: 1. Delete these labels - Camouflage: no open issues, probably never coming back - I2P: no open issues, probably never coming back - Handbook: only 2 open issues, can be tracked just fine with other labels - Feed Reader: no open issues; can now be tracked with "Email Client" since Thunderbird is our feed reader nowadays - Security Check: 1 open issue, 5 closed issues ⇒ not worth it - Verification Extension: we stopped using this a year ago so at this point I think the drawbacks of keeping this label outweigh the benefits of listing these 48 closed issues 2. Merge these labels: - "C: Installation", "C: Installation Assistant", "C: Installer" → "C: Installation" 3. Rename these labels: - "T: Test" → something that is harder to confuse with "C: Test suite"; ideas welcome; if nothing convincing arises I'll skip this one. I'm ready to drop any of these ideas if there are objections from people who use these labels. I plan to proceed no earlier than in 2 weeks. 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.
