Hi all,
What if we use the "due date" field in our Taiga [1] to set the publishing schedule?
I did that for the upcoming articles, and wrote a simple script [2] that can pull it out:
$ podman run asamalik/magazine-schedule Wed 27 Nov 2019: #105 How to rebase to Fedora 31 on Silverblue Fri 29 Nov 2019: #102 Create a VM with libvirt and Cockpit Mon 02 Dec 2019: #45 Toolbox Wed 04 Dec 2019: #69 Using Ansible to organize your ssh keys in AWS
(all you need to have on your system is podman)
What do people think?
Cheers, Adam
PS: I could also get that running in communishift or somewhere, which would give us a URL with the publishing schedule.
[1] https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban [2] https://github.com/asamalik/magazine-schedule
I like the idea.
On Tue, 26 Nov 2019 at 15:05, Adam Samalik asamalik@redhat.com wrote:
Hi all,
What if we use the "due date" field in our Taiga [1] to set the publishing schedule?
I did that for the upcoming articles, and wrote a simple script [2] that can pull it out:
$ podman run asamalik/magazine-schedule Wed 27 Nov 2019: #105 How to rebase to Fedora 31 on Silverblue Fri 29 Nov 2019: #102 Create a VM with libvirt and Cockpit Mon 02 Dec 2019: #45 Toolbox Wed 04 Dec 2019: #69 Using Ansible to organize your ssh keys in AWS
(all you need to have on your system is podman)
What do people think?
Cheers, Adam
PS: I could also get that running in communishift or somewhere, which would give us a URL with the publishing schedule.
[1] https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban [2] https://github.com/asamalik/magazine-schedule
--
Adam Šamalík
Senior Software Engineer Red Hat _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.org 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@lists.fedoraproject.o...
Pretty slick, Slick! I like it.
By the way, the Cockpit/libvirt article is ready, but it looks like I need to reschedule it for Friday to match your schedule. Sorry for getting that wrong!
Paul
On Tue, Nov 26, 2019 at 9:05 AM Adam Samalik asamalik@redhat.com wrote:
Hi all,
What if we use the "due date" field in our Taiga [1] to set the publishing schedule?
I did that for the upcoming articles, and wrote a simple script [2] that can pull it out:
$ podman run asamalik/magazine-schedule Wed 27 Nov 2019: #105 How to rebase to Fedora 31 on Silverblue Fri 29 Nov 2019: #102 Create a VM with libvirt and Cockpit Mon 02 Dec 2019: #45 Toolbox Wed 04 Dec 2019: #69 Using Ansible to organize your ssh keys in AWS
(all you need to have on your system is podman)
What do people think?
Cheers, Adam
PS: I could also get that running in communishift or somewhere, which would give us a URL with the publishing schedule.
[1] https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban [2] https://github.com/asamalik/magazine-schedule
--
Adam Šamalík
Senior Software Engineer Red Hat _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.org 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@lists.fedoraproject.o...
magazine@lists.fedoraproject.org