testing a new process for social media
Carlos Soriano was kind enough to create http://gitab.gnome.org/GNOME/engagement, and so you can now create issues for things like we want to advertise. As a test, I have put in November Bug Squash Month - https://gitlab.gnome.org/GNOME/engagement/issues/1. This way we have some way to track the things that need to be done and close them out easily when complete. sri ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: testing a new process for social media
On Sat, Nov 4, 2017 at 6:34 AM, Sriram Ramkrishna wrote: > Carlos Soriano was kind enough to create > http://gitab.gnome.org/GNOME/engagement, and so you can now create issues > for things like we want to advertise. As a test, I have put in November Bug > Squash Month - https://gitlab.gnome.org/GNOME/engagement/issues/1. > > This way we have some way to track the things that need to be done and close > them out easily when complete. Cool. How does that work exactly? You seem to imply that we will keep a single issue for the whole Bug Squash Month campaign. How do we e.g. plan tweets that need to be sent out or track those that have been? An issue in a bugtracker is supposed to be a single task and one closes it when they’re done with it, which allows progress to be tracked. -- Alexandre Franke GNOME Hacker & Foundation Director ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: testing a new process for social media
Is there documentation/walkthrough as to how this process would work? Especially for those of us who have never used gitlab before? Otherwise this seems like another technical barrier to entry for what should be a relatively nontechnical task. On Fri, Nov 3, 2017 at 10:34 PM, Sriram Ramkrishna wrote: > Carlos Soriano was kind enough to create > http://gitab.gnome.org/GNOME/engagement, and so you can now create issues > for things like we want to advertise. As a test, I have put in November > Bug Squash Month - https://gitlab.gnome.org/GNOME/engagement/issues/1. > > This way we have some way to track the things that need to be done and > close them out easily when complete. > > sri > > ___ > engagement-list mailing list > engagement-list@gnome.org > https://mail.gnome.org/mailman/listinfo/engagement-list > > -- Rosanna Yuen Director of Operations GNOME Foundation, Inc. ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: testing a new process for social media
On Sat, Nov 4, 2017 at 2:51 AM Alexandre Franke wrote: > On Sat, Nov 4, 2017 at 6:34 AM, Sriram Ramkrishna > wrote: > > Carlos Soriano was kind enough to create > > http://gitab.gnome.org/GNOME/engagement, and so you can now create > issues > > for things like we want to advertise. As a test, I have put in November > Bug > > Squash Month - https://gitlab.gnome.org/GNOME/engagement/issues/1. > > > > This way we have some way to track the things that need to be done and > close > > them out easily when complete. > > Cool. How does that work exactly? You seem to imply that we will keep > a single issue for the whole Bug Squash Month campaign. How do we e.g. > plan tweets that need to be sent out or track those that have been? An > issue in a bugtracker is supposed to be a single task and one closes > it when they’re done with it, which allows progress to be tracked. > I'm still learning it myself. So, my hope is that I can come up with a solid process where people can put requests in and we can monitor the queue. There is a TODO setup there, and hopefully that will help. A process is better than no process which is what we have right now. If Gitlab doesn't work for us then we will find something else that will. sri > -- > Alexandre Franke > GNOME Hacker & Foundation Director > ___ > engagement-list mailing list > engagement-list@gnome.org > https://mail.gnome.org/mailman/listinfo/engagement-list > ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: testing a new process for social media
On Sat, Nov 4, 2017 at 9:05 AM Rosanna Yuen wrote: > Is there documentation/walkthrough as to how this process would work? > Especially for those of us who have never used gitlab before? > > Otherwise this seems like another technical barrier to entry for what > should be a relatively nontechnical task. > Not yet, as I'm still familiarizing myself with gitlab. It'll try to document something this week and we can poke at it and see if it is the right tool. I'm hesitant to add new tools because it just adds more burden to the sysadmin team. But I think something to track it as a ticket I think would be useful than none at all. sri > On Fri, Nov 3, 2017 at 10:34 PM, Sriram Ramkrishna > wrote: > >> Carlos Soriano was kind enough to create >> http://gitab.gnome.org/GNOME/engagement, and so you can now create >> issues for things like we want to advertise. As a test, I have put in >> November Bug Squash Month - >> https://gitlab.gnome.org/GNOME/engagement/issues/1. >> >> This way we have some way to track the things that need to be done and >> close them out easily when complete. >> >> sri >> >> ___ >> engagement-list mailing list >> engagement-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/engagement-list >> >> > > > -- > Rosanna Yuen > Director of Operations > GNOME Foundation, Inc. > ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: testing a new process for social media
FWIW, FESCo and other Fedora teams often use Pagure projects to track issues. It might be worth seeing how some of those teams sort and organize tasks into issues. https://pagure.io/fesco https://pagure.io/fedora-marketing On Sun, Nov 5, 2017 at 6:21 PM, Sriram Ramkrishna wrote: On Sat, Nov 4, 2017 at 9:05 AM Rosanna Yuen wrote: Is there documentation/walkthrough as to how this process would work? Especially for those of us who have never used gitlab before? Otherwise this seems like another technical barrier to entry for what should be a relatively nontechnical task. Not yet, as I'm still familiarizing myself with gitlab. It'll try to document something this week and we can poke at it and see if it is the right tool. I'm hesitant to add new tools because it just adds more burden to the sysadmin team. But I think something to track it as a ticket I think would be useful than none at all. sri On Fri, Nov 3, 2017 at 10:34 PM, Sriram Ramkrishna wrote: Carlos Soriano was kind enough to create http://gitab.gnome.org/GNOME/engagement, and so you can now create issues for things like we want to advertise. As a test, I have put in November Bug Squash Month - https://gitlab.gnome.org/GNOME/engagement/issues/1. This way we have some way to track the things that need to be done and close them out easily when complete. sri ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list -- Rosanna Yuen Director of Operations GNOME Foundation, Inc. ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
