Hi, On Mon, Mar 30, 2020 at 01:59:07PM +0000, Leigh Griffin wrote: > On Mon, Mar 30, 2020 at 2:18 PM Till Maas <opensource@xxxxxxxxx> wrote: > > > Hi, > > > > On Mon, Mar 30, 2020 at 11:04:03AM +0100, Leigh Griffin wrote: > > > > > For transparency, we have published the full User Story list which is > > > linked within the blog and for ease of searching is here: > > > https://hackmd.io/@My419-DISUGgo4gcmO1D6A/HJB74lcL8 > > > > the user stories list does not seem to include the original user stories > > that I submitted regarding package life-cycle and permission management. > > These are requirements for dist-git but not necessarily for a git-forge. > > In the past they were fulfilled by package db, now pagure is solving > > this more. > > > We received a summarised User Story list from the Fedora Council, I would > suggest reaching out with your concerns. What is the list that you got. The list on the council discuss list contained these items, for example for FESCo members, proven packagers and dist-git repo admins: https://lists.fedoraproject.org/archives/list/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx/thread/OEPDGVKYAJIQ6YYZU5J3XT3LHXFROFI5/ In the hackmd story list, there are is only infosec, RH Legal Rep, RH Infocsec Rep, RH Developer, RHEL engineer and general users, project contributor, CPE team member. Nothing really maps to the user groups I mentioned. There is only | 41 | As a General User | I want groups and group membership and management | to allow me create access control on a suite of repositories but this is very vague. Also there seems to be nothing about orphaning/adopting/retiring packages, not even in a vague way. Thank you, Till _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
