That sounds like a significant improvement. +1 from me. Let's hear what other editors have to say. On Tue, May 5, 2020, 2:26 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote: > On Wed, Apr 29, 2020 at 11:56 PM <s40w5s@xxxxxxxxx> wrote: > > > After the last magazine meeting, I was looking at Pagure issues for > > topics that reflected what had been discussed as potential workload > > decrease for the transfer of issues (proposals) for Fedora Magazine > > articles from our pagure instance to the Taiga cards we use for article > > progress tracking. There is a plugin available at this link > > https://github.com/Pagure/pagure-taiga. It may be what we are needing. > > > > A simpler solution might be to switch to using Taiga's issues instead of > Pagure. Taiga has native support for promoting issues to user stories. We > can set Taiga's permissions to "allow unauthenticated users" to create > issues. This isn't as scary as it sounds because our FAS authentication > means that "unauthenticated" users are simply "users not members of this > specific Taiga project". > > > -- > Ben Cotton > He / Him / His > Senior Program Manager, Fedora & CentOS Stream > Red Hat > TZ=America/Indiana/Indianapolis > _______________________________________________ > Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to magazine-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/magazine@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to magazine-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/magazine@xxxxxxxxxxxxxxxxxxxxxxx
