badges-team September 2018

badges@lists.fedoraproject.org

2 participants
3 discussions

Re: [commops] Re: Event Badges - Policy Discussion
by Justin W. Flory 12 Oct '18

12 Oct '18

On 9/24/18 11:43 AM, Brian (bex) Exelbierd wrote: > > > On Mon, Sep 24, 2018 at 1:32 AM Justin W. Flory <jflory7(a)gmail.com > <mailto:jflory7@gmail.com>> wrote: > > Hi! I've been thinking about this thread for a while. > > This is great feedback and I wonder how we could try to improve the > contributing experience for Fedora Badges. In 2015, an early idea was to > equip CommOps to work with the Design Team on creating and establishing > badge policy and strategy. Perhaps we could revisit this again. > > I'd like to figure out where we can begin tracking this feedback and > organize an effort to address some of these. > > (One example on my mind is hosting a docs.fedoraproject.org > <http://docs.fedoraproject.org> page on > Fedora Badges to explain policy and badge rules. It could also be a "new > home" for the style guide.) > > > I agree that getting this documented is key. > > Marie, would it be helpful if we worked together to get a docs repo set > up for badges. It can be in the existing badge repo. This would allow > the policy to be published and commented on easily. > > WDYT? > From my point of view as a Badges sysadmin, I am a big +1 to getting a docs.fp.o Badges section set up. -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 1

Re: [commops] Re: Event Badges - Policy Discussion
by Brian (bex) Exelbierd 24 Sep '18

24 Sep '18

resending as I dropped badges@ by accident On Mon, Sep 24, 2018 at 5:43 PM Brian (bex) Exelbierd <bexelbie(a)redhat.com> wrote: > > > On Mon, Sep 24, 2018 at 1:32 AM Justin W. Flory <jflory7(a)gmail.com> wrote: > >> Hi! I've been thinking about this thread for a while. >> >> This is great feedback and I wonder how we could try to improve the >> contributing experience for Fedora Badges. In 2015, an early idea was to >> equip CommOps to work with the Design Team on creating and establishing >> badge policy and strategy. Perhaps we could revisit this again. >> >> I'd like to figure out where we can begin tracking this feedback and >> organize an effort to address some of these. >> >> (One example on my mind is hosting a docs.fedoraproject.org page on >> Fedora Badges to explain policy and badge rules. It could also be a "new >> home" for the style guide.) >> > > I agree that getting this documented is key. > > Marie, would it be helpful if we worked together to get a docs repo set up > for badges. It can be in the existing badge repo. This would allow the > policy to be published and commented on easily. > > WDYT? > > regards, > > bex > > >> >> >> On 8/18/18 9:57 AM, Marie Nordin wrote: >> > Hello All! >> > >> > I am opening up this thread to discuss event badges-- I think it would >> > be helpful to brainstorm and finalize some standards/regulations >> > regarding event badges with the input from leadership, design, and >> > development side. I will do my best to list all the different >> > thoughts/issues that have been raised. Please feel free to jump in with >> > other points and/or correct if I don't have the latest info. >> > >> > _*Current policy:*_ >> > - 1 event badge per event (non Fedora, or Fedora) >> > - 3 event badges per Flock >> > - attendee >> > - contributor >> > - party attendee >> > - 1 event badge per Fudcon >> > - attendee >> > - in the past we have also had speaker/organizer badges >> > >> > _*Common issues we encounter:*_ >> > - People pointing to older badges and asking why we don't make them any >> more >> > - I actually haven't seen this as much lately, but have in the past >> > - People not knowing what or where to find a policy regarding event >> > badges. People pose potential badges, and we have to turn them down. >> > - From creation/pushing to site aspect, not getting enough notice that >> > an event badge is needed, or it gets lost in a sea of update emails >> > (best to request an event badge at least 1-1.5 months in advance, so we >> > can see & address at a badges meeting (held bi-weekly unless something >> > comes up)). Then there is time for gathering of resources (logos), >> > creation of artwork, and pushing to site. >> > >> > _*Outdated badges:*_ >> > - We have old speaker/organizer badges. Do we want to remove those and >> > replace them with the new contributor badges? Would this be too big an >> > effort for the outcome? >> > >> > _*New ideas:*_ >> > - Fedora meet up badge - IMHO, if we created this it should just be one >> > badge overall that is used for multiple events? Or yearly, so "you >> > attended a fedora meet up in 2018" I think this is a great idea for >> > people who are unable to make it to some of the larger conferences, >> > giving them a chance to earn event badges. On the other side, those >> > privileged to go to the larger badges will most likely earn these as >> > well. https://pagure.io/fedora-badges/issue/641 >> > - Non-Fedora badges - this idea made by Bex on issue 642. I would be >> > interested to hear more about what this would entail and how to >> > implement. https://pagure.io/fedora-badges/issue/642 >> > >> > _*More Thoughts:*_ >> > - Why did we move from speaker/organizer badges to contributor badges? >> > Who made this decision and why? >> > - A note here is that I am fine with this policy, I am just curious how >> > this decision came about, and why it wasn't really finalized >> > "officially" and discussed with the badges team as a whole. I think it >> > was announced on a badge issue, and we then had to adapt. >> > >> > >> > That is all I have for now. I think it would be great if we had input on >> > these thoughts, and any others, from all the people who makes badges >> > happen :) >> > >> > Best, >> > - riecatnor >> > >> > >> > _______________________________________________ >> > Fedora Badges mailing list -- badges(a)lists.fedoraproject.org >> > To unsubscribe send an email to badges-leave(a)lists.fedoraproject.org >> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> > List Archives: >> https://lists.fedoraproject.org/archives/list/badges@lists.fedoraproject.or… >> > >> >> -- >> Cheers, >> Justin W. Flory >> jflory7(a)gmail.com >> >> _______________________________________________ >> Fedora Community Operations (CommOps) mailing list -- >> commops(a)lists.fedoraproject.org >> To unsubscribe send an email to commops-leave(a)lists.fedoraproject.org >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.o… >> > > > -- > Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com > Fedora Community Action & Impact Coordinator > @bexelbie | http://www.winglemeyer.org > -- Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org

1 0

Event Badges - Policy Discussion
by Marie Nordin 24 Sep '18

24 Sep '18

Hello All! I am opening up this thread to discuss event badges-- I think it would be helpful to brainstorm and finalize some standards/regulations regarding event badges with the input from leadership, design, and development side. I will do my best to list all the different thoughts/issues that have been raised. Please feel free to jump in with other points and/or correct if I don't have the latest info. *Current policy:* - 1 event badge per event (non Fedora, or Fedora) - 3 event badges per Flock - attendee - contributor - party attendee - 1 event badge per Fudcon - attendee - in the past we have also had speaker/organizer badges *Common issues we encounter:* - People pointing to older badges and asking why we don't make them any more - I actually haven't seen this as much lately, but have in the past - People not knowing what or where to find a policy regarding event badges. People pose potential badges, and we have to turn them down. - From creation/pushing to site aspect, not getting enough notice that an event badge is needed, or it gets lost in a sea of update emails (best to request an event badge at least 1-1.5 months in advance, so we can see & address at a badges meeting (held bi-weekly unless something comes up)). Then there is time for gathering of resources (logos), creation of artwork, and pushing to site. *Outdated badges:* - We have old speaker/organizer badges. Do we want to remove those and replace them with the new contributor badges? Would this be too big an effort for the outcome? *New ideas:* - Fedora meet up badge - IMHO, if we created this it should just be one badge overall that is used for multiple events? Or yearly, so "you attended a fedora meet up in 2018" I think this is a great idea for people who are unable to make it to some of the larger conferences, giving them a chance to earn event badges. On the other side, those privileged to go to the larger badges will most likely earn these as well. https://pagure.io/fedora-badges/issue/641 - Non-Fedora badges - this idea made by Bex on issue 642. I would be interested to hear more about what this would entail and how to implement. https://pagure.io/fedora-badges/issue/642 *More Thoughts:* - Why did we move from speaker/organizer badges to contributor badges? Who made this decision and why? - A note here is that I am fine with this policy, I am just curious how this decision came about, and why it wasn't really finalized "officially" and discussed with the badges team as a whole. I think it was announced on a badge issue, and we then had to adapt. That is all I have for now. I think it would be great if we had input on these thoughts, and any others, from all the people who makes badges happen :) Best, - riecatnor

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

[MOVED TO DISCOURSE] Fedora Badges - https://discussion.fedoraproject.org/tag/badges-team September 2018