sajolida: > intrigeri: >> Where to ask questions and report problems >> ========================================== >> >> There are most certainly some rough edges, confusion, and bugs caused >> by this migration, so: >> >> - If you have questions or trouble with the new *workflow*, please >> either email <[email protected]> or [...] > > Another question. > > What's the plan to replace "Core Work" views and tickets? > > https://gitlab.tails.boum.org/tails/tails/-/issues?scope=all&utf8=%E2%9C%93&state=closed&search=%22Core+work+201%22 > > I see that other teams than UX and Technical Writing stopped using them > years ago, though I thought that it was still the somehow standard way > of giving transparency and accountability on the priorities of teams. > > I don't mind stopping using them myself if there's no plan for > replacement but I'm curious how other teams track their priorities. It > might be useful to avoid each team reinventing its own wheel and still > give some transparency and accountability. > > I guess that we can use Milestones but then, what do you do with tasks > that your team considers important but for which the team is lagging > behind in terms of capacity? > > - Using Milestones and postponing them for too long is not great. > - Relying on the Label "Core Work: $TEAM" might make it easier to loose > them from sight.
Sorry for the noise, a few hours later I realized that the labels "Core Work: $TEAM" are enough to give transparency and accountability and Milestones to explicit short-term priorities. And that it was already documented on: https://tails.boum.org/contribute/working_together/GitLab/#core-work -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing _______________________________________________ Tails-dev mailing list [email protected] https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
