On Tue, Jan 17, 2017 at 6:21 AM, Adam Miller <maxamillion@xxxxxxxxxxxxxxxxx> wrote: > On Thu, Jan 12, 2017 at 12:02 PM, Adam Miller > <maxamillion@xxxxxxxxxxxxxxxxx> wrote: >> On Wed, Jan 11, 2017 at 4:50 PM, Adam Miller >> <maxamillion@xxxxxxxxxxxxxxxxx> wrote: >>> Hello all, >>> Recently I attempted to start a mailing list thread that was the >>> product of a discussion on IRC about putting together an Atomic WG >>> workshop session[0] at DevConf[1]. >>> >>> This was then discussed during today's Atomic WG Meeting[2] where it >>> was decided that we should make this Workshop into a re-occurring >>> Virtual Fedora Activity Day(FAD[3]) instead taking place every 2 >>> months. >>> >>> I would like to propose the following: >>> Each Virtual FAD occurs on a Thursday, the day after a Fedora >>> Atomic WG meeting such that we can use the meeting the day before to >>> plan out the work to be done at the Virtual FAD. All work will be >>> tracked in a kanban[4] board, I've created one for this purpose in >>> Fedora's Taiga instance[5] (Note: I don't know why my FAS name is in >>> the URL, Taiga just does that). >>> In the kanban board, we would create cards in the NEW column >>> through out the two month cycle between Virtual FADs (these should >>> correlate to tickets in pagure[6]), then on the meeting before the FAD >>> we would "groom" the NEW cards that we want to accomplish on the >>> following day of the Virtual FAD, these "groomed" cards would be >>> placed into the READY column to signify they are ready to be worked >>> on. On the day of the VFAD, participants/contributors would then >>> assign a card to themselves that they want to work on, and move the >>> card into "IN PROGRESS" so that everyone knows what is being worked on >>> and nobody attempts to work on the same thing (unless that's >>> intentional, in that case both people's names should be listed in the >>> card description for reference). Once a task is done, then it should >>> be moved to the DONE column. This will give a good reflection of what >>> work was accomplished during the VFAD and we can (optionally) have a >>> retrospective meeting after the VFAD about what went well, what didn't >>> go well, and what we could do better next time. Also the day before >>> the next VFAD at the start of the "grooming" session (the weekly >>> Atomic WG meeting), all the previous VFAD's cards in the DONE column >>> from the previous VFAD should be moved to ARCHIVED for posterity. >>> >>> Cards created should be units of work that can feasibly be >>> accomplished in a day or less worth of work. >> >> Based on previous feedback in the thread I have come with a modified >> proposal (effectively the same, just a different tracking mechanism so >> we're doing everything in one place). >> >> Modifications to proposal: >> We will create a Pagure Roadmap Milestone[0] for each Virtual FAD, >> items that we want to accomplish in that VFAD that we groom in the >> meeting before the VFAD will be assigned to that milestone. From there >> we will create the Pagure Labels: NEW and IN_PROGRESS (we can >> un-capitalize or format differently if anyone has a preference). >> Everyone will also create a Pagure Label with their FAS name that can >> be applied to Issue Tickets that people are working on (this will also >> be nice because a Ticket can have multiple labels so if multiple >> people are working on a single Ticket, we can track that). >> Tickets will be given the NEW Label when they are assigned to a >> Milestone during grooming. On the day of the VFAD, at the point in >> time someone wants to work on something: the NEW Label is removed, he >> IN_PROGRESS Label is applied, and the FAS account name Label of the >> person(s) working on the Ticket is added. Once a Ticket is complete: >> the IN_PROGRESS label should be removed, and the Ticket Closed. This >> will leave it in the Milestone of the VFAD but mark it as Closed, >> effectively both completing it and archiving it. >> >> I created a milestone demo and added everyone from the atomic-wg[1] >> pagure repo there in case anyone wants to play around with the >> proposed workflow[0]. >> >> Also as a side, we should really have an atomic-wg FAS group. :) >> >> Thoughts? > > Thread bump. Anyone had a chance to read this? Any comments? I looks good to me, I say we get rolling with it and iterate as needed, but the basic plan here seems solid. Jason > > -AdamM > >> >> Thanks, >> -AdamM >> >> [0] - https://pagure.io/milestones-demo/roadmap >> [1] - https://pagure.io/atomic-wg >> >>> >>> I would like to ultimately propose we move to a more iterative cycle >>> where we use this workflow weekly instead of dedicating a single day >>> every 2 months (these periods of time are often known as a "sprint" in >>> Agile[7]) but my hope is that this is a good place to start and we can >>> improve over time. >>> >>> If this is acceptable as a change we would like to adopt as a group, I >>> am happy to pre-populate the kanban board with work items we had >>> previously discussed that we wanted to accomplish as the original >>> agenda to the (now defunct) DevConf Workshop. From there I would >>> propose that the first meeting after DevConf (2017-02-01) be used as >>> the first grooming session and the following Thursday be the first >>> VFAD (2017-02-02). From there we would set a schedule for every 2 >>> months to have a VFAD. >>> >>> If everyone is in agreement, I'll also get a section of the Wiki page >>> (which we need to move out of the Cloud namespace) added to document >>> this workflow for newcomers who would like to join the Atomic WG. >>> >>> Thank you, >>> -AdamM >>> >>> >>> [0] - https://lists.fedoraproject.org/archives/list/cloud@xxxxxxxxxxxxxxxxxxxxxxx/thread/WBTWBLOYWG66EDXJO2I4G3XY3X6EFAIF/ >>> [1] - https://devconf.cz/index.html >>> [2] - https://lists.fedoraproject.org/archives/list/cloud@xxxxxxxxxxxxxxxxxxxxxxx/thread/36EBX5WS36OSO57GDWBJVIU6CXRXT237/ >>> [3] - https://fedoraproject.org/wiki/Fedora_Activity_Day_-_FAD >>> [4] - https://en.wikipedia.org/wiki/Kanban >>> [5] - https://taiga.fedorainfracloud.org/project/maxamillion-fedora-atomic-wg/kanban >>> [6] - https://pagure.io/atomic-wg/issues >>> [7] - https://en.wikipedia.org/wiki/Agile_software_development > _______________________________________________ > cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
