mentored-projects

#117 Outreachy Proposal: Fedora Badges Design
Closed: fixed by riecatnor. Opened by smeragoel.

Closed: fixed
Reopen Issue

This is a proposed project for Outreachy. Note that once this ticket is
approved you will have to register as a mentor on the Outreachy page
and enter this information again. Many of these questions are based on
the application on the Outreachy website.

  • One-line name
    • Fedora Badges Design
  • Longer description of project
    • Fedora Badges is a fun website built to recognize contributors to the Fedora Project, help new and existing Fedora contributors find different ways to get involved, and encourage the improvement of Fedora’s infrastructure.
  • License of the project
    • Variety of licenses.
  • Longevity (How long has the team accepted contributions)
    • 9 years
  • Community size
    • 20+ people on the Badges Team which includes developers and designers.
  • How will this project benefit Fedora
    • Fedora Badges is a popular method of recognition in the community. Many teams across Fedora use badges to promote engagement and growth as well.
  • Sample plan of work for the 12 week internship. What are milestones the intern should be hitting? This doesn't need to be incredibly detailed and can change later but there needs to be a general breakdown of tasks.
    • Update/Modernize badge template
    • Update style guide
    • Revise old/outdated/bad art
    • Move art from old template to new template
    • Teach them how to push their own badges
    • Work through art requests on the badges pagure
    • Promotional work (banners, swag etc)
    • Create library of resources on Fedora PenPot
    • Badges sticker set for chat
    • Blog posts
  • Benefits to intern (What will the intern get out of this internship)
    • Confidence working in a professional environment.
    • A network of industry contacts.
    • Exposure to new skills.
    • Increased employability.
    • Exposure to world of open source.
  • Project website
    • https://docs.fedoraproject.org/en-US/badges/
  • Project repo
    • https://pagure.io/Fedora-Badges
  • Where can an applicant find application tasks?
    • https://pagure.io/Fedora-Badges
  • IRC/Element
    • https://matrix.to/#/#design:fedoraproject.org
    • fedora-design on Libera.Chat
  • Skills required including what level and if they are optional
    (e.g. Python Intermediate, CSS beginner, we'll teach you Puppet)
    • Excellent computer knowledge and proficiency on either OSX/Windows/Linux
    • Must be proficient in basic design programs such as Inkscape & GIMP or the Adobe Suite with a willingness to learn the open versions of this software.
    • Basic to intermediate knowledge of design theory
    • Basic to intermediate knowledge of typography, infographics, style guides, etc
    • Solid written, and interpersonal communication skills
  • Outreachy applicants are required to make a contribution as part of the application. What is the process for making a contribution?
    • Create a Fedora Account: https://accounts.fedoraproject.org/
    • Subscribe to the Badges mailing list: https://lists.fedoraproject.org/admin/lists/badges.lists.fedoraproject.org/
    • Introduce yourself to the team! (Element/IRC recommended)
    • Join #fedora-badges on IRC or fedora-badges on Element/Matrix https://matrix.to/#/#badges:fedoraproject.org
      • Note: register your nick on IRC or it will not let you send messages
    • Look for issues in the Fedora Badges repo tagged "outreachy"
    • Choose a ticket and ask one of your mentors @smeragoel or @riecatnor to assign it to you. Tag @smeragoel and/or @riecatnor in #fedora-badges on IRC/Element with your request.
      • Note: please take on only three tickets at a time. Once you have finished a ticket, you can take up a new one. Find more info on the Fedora Outreachy FAQ page. https://docs.fedoraproject.org/en-US/mentored-projects/outreachy/faq/
    • Work on the ticket and upload SVG & PNG files to the ticket. You will receive reviews/commentary most likely with some suggestions from improvement. Once you have incorporated the feedback, upload the new design and wait for another round of reviews. The process continues like this until the task is completed.

Mentor Questions

Questions from the top level Outreachy Program for the mentor application:

  • How long have you been contributing to the community?
    • I have been contributing to Fedora for about 1.5 years now.
  • What is your current role
    • Design team contributor
  • Have you mentored for a three-month internship program before
    • No I haven't.
  • Have you read the mentor page and understand the process of being a mentor
    • Yes, I have read the mentor page and understand the process.
  • Are you available for 5 hours a week during the internship period
    • Yes, I am.
  • Are you available for 5-10 hours a week during the application period
    • Yes, I am.
  • Are you aware you need to sign a mentor contract
    • Yes, I am aware.

Signing on as co-mentor for this project :)

Metadata Update from @riecatnor:
- Issue tagged with: Outreachy, project-idea
siddharthvipul1 commented

I love this.
I have a few questions just so I am at the same page :)

  1. From what I understand, main pain point and the bottle neck of a better user experience with Fedora badges is the tech stack it is running on. It's fragile, non-maintainable and needs work in both front-end and back-end. So far from this ticket, I understand it's a design task (which is nice to have). Do you plan to coordinate front end improvement as part of this project?

  2. How would you define success of this project? What I mean is, at the end of 3 months, do you have a "minimal target achieved" sorta thing in mind?

I am trying to understand what changes in the badges system can we expect by the end of the internship to call it a success

And yes, thank you for proposing the project idea. Love this!

  1. No, we are not planning to look at UI/UX unless the intern is so prolific that they finish all the deliverables with time to spare.

  2. Completing the deliverables listed in the plan of action would define the success of this project, which means refreshing all the art on the badges, updating the template, revising the style guide and creating a library of design resources on PenPot.

I hope this answers your questions. Super excited about this! :D

I love this.
I have a few questions just so I am at the same page :)

  1. From what I understand, main pain point and the bottle neck of a better user experience with Fedora badges is the tech stack it is running on. It's fragile, non-maintainable and needs work in both front-end and back-end. So far from this ticket, I understand it's a design task (which is nice to have). Do you plan to coordinate front end improvement as part of this project?

  2. How would you define success of this project? What I mean is, at the end of 3 months, do you have a "minimal target achieved" sorta thing in mind?

I am trying to understand what changes in the badges system can we expect by the end of the internship to call it a success

And yes, thank you for proposing the project idea. Love this!

I'd add some more questions and concerns from my end too, owing to the fact the design made here would eventually pave the way for the Fedora Badges reboot, to be undertaken by the Fedora Websites and Apps Engineering Team.

  1. Chiming in on what @siddharthvipul1 mentioned in his first question, the very reason why the Fedora Badges is in a state that it is - is because the engineering side of things is not capable or maintainable enough to hold through major changes made in the frontend code. I like how this proposal is centered on just the design aspect - which makes the objectives of the project, very achievable by both the interns, mentor and other stakeholders involved.

  2. Albeit, the very fact that the technical side is not involved would mean that the outcome of the project would potentially require revisions well after the internship period is completed - to make it fall in line with the technical requirements, which would add to the task backlog of the Fedora Websites and Apps Engineering Team and Fedora Websites Revamp (or Fedora Design) team. In that perspective, the tasks for the proposal are focussed but not self-contained/self-sufficient.

  3. To be honest, Fedora Badges does not only need changes to the way it looks and feels but in the project design standpoint, it requires a revamp in the way it operates - say the way it automates the process of awarding badges or quality of life improvements for people who are manually awarding them. So simply redesigning the existing pages might not be enough but if needed, adding some more new ones or getting rid of the existing ones, are in order. Wireframes connecting these elements would be needed too to get an idea of the flow.

@smeragoel, great work with the proposal and I appreciate the way the requirements and outcomes are lucidly described. Please let me know your perspectives about the aforementioned three points.

Hiya! I had a chat with @smeragoel to make sure we are on the same page so I could respond to this one :)

  1. Glad you approve- we tried to make the scope of work reasonable for a 12 week period.
  2. There should be nothing from this internship that would add to a task backlog. It is focused on the designs of the badges only, and working on that existing task backlog. @smeragoel has the knowledge to push badges and update the artwork files in the repo and we will pass that on to the intern. Any badge that needs automation will sit on a pile with the rest that are ready and need automation and wait for the badges dev/sysadmin side of things :)
  3. While I agree with you about badges needing a website revamp, redesigning the badges website UI/UX is not in the scope of this internship. If the intern finishes every other task we have outlined to completion, we could potentially have them explore UI/UX as well as other design related tasks but I don't foresee that happening. We plan to look for folks experienced with graphic design and brand, although many designers have overlapping skills, not all do and we don't plan to make UI/UX a requirement.

Hope that helps!
Edited by riecatnor
siddharthvipul1 commented

This looks good to me
+1 to get it in outreachy workflow ( @smeragoel please put it in there and I will approve it)

@riecatnor, thank you for your answers. Glad to see the the scope is focused and very exclusive to just designing badges (as in, the ones that are awarded and not the backend/automation side).

@smeragoel, please feel free to reach out to me should you feel the need with anything websites or infra-bound during this project and I would be glad to be of assistance.

Metadata Update from @t0xic0der:
- Issue assigned to t0xic0der

Metadata Update from @t0xic0der:
- Issue assigned to smeragoel (was: t0xic0der)

Metadata Update from @t0xic0der:
- Assignee reset

Also signing on as co-mentor for this project, mostly on the technical part, but also I've good knowledge on the design as well.

I can help as a co-mentor from the sysadmin side.

@nb awesome! We are in the application period now, fyi. We will have a lot of badges to get pushed out, we have a queue already[0]. If you could help out with that or triage tickets from the sysadmin side (for example if the badge is not possible, please close the ticket, or note that it should be possible in the future and leave it open)

https://pagure.io/fedora-badges/issues?tags=ready+to+push&status=Open

Metadata Update from @riecatnor:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)
Metadata
None

program - Outreachy type - project idea

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.