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.
- 1 event badge per event (non Fedora, or Fedora)
- 3 event badges per Flock
- party attendee
- 1 event badge per Fudcon
- 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.
- 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?
- 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.
- 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.
- 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
On 08/10/2018 05:26 PM, Máirín Duffy wrote:
> The internship would be a development one, right? So from design you'd
> be looking for a designer to work on mockups and advise the intern on
> them from a design POV but the development mentor would be the primary
> mentor right?
Yes, this is correct.
> Is the work that is needed scoped well for a 12 week intern engagement?
Not yet. Sayan is perhaps best to know what current work is most needed
from a development POV. I hope by starting this conversation we can find
someone willing to mentor, and we could scope the work once there is a
To be transparent, I don't anticipate having time to work directly on
this. But there was interest from our discussion at Flock and there is a
need for more development interest and focus on Tahrir. I hoped to start
this discussion as one avenue to source more development interest on
Justin W. Flory
On 10.8.2018 12:17, Justin W. Flory wrote:
> Hi, I'm following up from the side conversation about finding mentors
> for a Tahrir UI/UX development internship with Outreachy and when we can
> find time to discuss this further.
> During the sysadmin workshop, some of the UI/UX pain points of Tahrir's
> interface came up when running through the workflow with a live
> audience. We briefly discussed the possibility of trying to drive new
> development through an Outreachy internship. Many of us familiar with
> the stack don't have enough time to drive new development, but could
> mentor a contributor working on the project.
> We need to identify possible mentors from a development and design angle
> for the project. Marie did not have time now to be a mentor. Ryan's name
> came up as a possible suggestion, but we haven't had a chance to discuss
> this with him.
> Since it seemed like a good idea to breathe new development life into
> Tahrir, I wanted to make sure we followed up on this discussion
> post-Flock and see if we can pull it off for this or a future Outreachy
> internship cycle.
I've CCed the mailing list. It would be nice if we could keep such