finos / a11y-theme-builder

DesignOps toolchain theme builder for accessibility inclusion using Atomic Design.
Apache License 2.0
41 stars 70 forks source link

[REQUEST] Enable LF Badges for Theme Builder contributions #786

Open PaulaPaul opened 7 months ago

PaulaPaul commented 7 months ago

Suggestion/Concern

To help build our community of contributors and maintainers we would like to acknowledge first time contributors and eventually more regular contributors to Theme Builder with LF badges that they can post on their LinkedIn profiles and LFX profiles. We can promote these badges as a way to attract contributors, and include information about the badges at collaboration summits.

Proposed Solution

@PaulaPaul has reached out to Rob Moffat who was involved in establishing the FDC3 badges with LF to find out what the process is for creating LF Badges. We can track the suggested names/types of badges in comments associated with this issue, and close the issue once the initial badge or badges are created.

Rob Moffat put us in touch with Mary Simpkins (msimpkins@linuxfoundation.org) at LF - if we use credly to create the badges Mary can help us establish them with LF. Paula will start an email thread with Mary, @lwnoble and @aaronreed708 to get more details.

Proposed initial badge(s)

Future badges (ideas)

PaulaPaul commented 7 months ago

We've been put in touch with Magdalene Stepien at LF 9mstepien@linuxfoundation.org) who has provided the following information:

Hi All,

I will be happy to help. I can create these badges in Credly and can either grant you a badge issuer role or take care of issuing the badges myself. To proceed with badge creation, I’ll need the following information:

Badge name Examples from other projects - Linkerd Hero Nominee; Keynote Speaker: Open Networking & Edge Summit 2020; cdCon 2020 Speaker.

Badge image Specifications: Must use square images in PNG format, with dimensions between 600x600 and 2048x2048 pixels.

Badge description(s) Please explain what learners/earners achieved to obtain this badge, max. 500 characters including spaces, e.g. Linkerd Heroes are community members who best represent the spirit of the Linkerd community. Whether it’s for helping others, sharing success (or failure) stories, or contributing code, docs, or energy to the project, the Linkerd Hero badge is bestowed only upon those who have been nominated by the community as instrumental in making Linkerd the amazing project it is today.

URL Where to find additional information about the project/event.

Skills 1-3 word descriptions of the skills, competencies, or tools demonstrated by the earner, e.g. Cloud Native; Linkerd; Open Source; Service Mesh.

Badge Criteria Criteria defined by listing activities the earner completed to earn this badge. You can choose more than one from the following list: Application, Assessment, Badge, Course, Credential, Educational Experience, Member, Other, Participant, Payment, Portfolio, Presenter, Project, Professional Experience, Schedule/Registration, Volunteer. For each criteria, you can provide a short description. Examples: Member: Active membership and engagement in the Linkerd open source community with notable improvements to the project and community; Assessment: Nomination by Linkerd maintainers.

Attributes These are optional and provide additional details about the badge. You can choose from the following settings:

  • Type: Experience, Learning, Validation, Certification
  • Level: Foundational, Intermediate, Advanced
  • Time: Hours, Days, Weeks, Months, Years (how long did it take a recipient to master their skills)
  • Cost: Free, Paid

I let Magda know that the community group would circle back to her with details on badges - plan to discuss this at the next community call/

PaulaPaul commented 7 months ago

Adding @lwnoble to this for visibility- we can brainstorm on the design for these badges and use them to help grow community!

PaulaPaul commented 7 months ago

From @aaronreed708 - suggested we also leverage LF Mentorship program to reward mentors/participants. @PaulaPaul will open a separate community issue to track this- https://docs.linuxfoundation.org/lfx/mentorship

codyzu commented 6 months ago

@lwnoble said we should have some designs ready for review in about a week. Progress is happening 🚀

kris-reed commented 5 months ago

Hi! So nice to meet everyone!

PaulaPaul commented 5 months ago

Badge designs complete! @PaulaPaul will draft the additional information needed for LF to enable the badges and post here for review- Thanks @lwnoble and @chessel (I've also closed #797 and attached the badge images there as well)

Image

Chessel commented 5 months ago

Here is the stand alone badge ![Uploading TB-contributor badge.png…]()

aaronreed708 commented 5 months ago

From @Chessel

IMG_0141

PaulaPaul commented 5 months ago

Badge names

Badge image Specifications: Must use square images in PNG format, with dimensions between 600x600 and 2048x2048 pixels. (see above)

Badge description(s)

  1. A11Y Theme Builder Community Champion: This badge is awarded to community members who join the Theme Builder community or project calls, comment on issues, write blog posts or create videos about Theme Builder, help other Theme Builder community members, and/or help refine issues that lead to PRs. The Theme Builder project team and core maintainers can nominate community champions by identifying their comments and issue activity in GitHub or on social media.
  2. A11Y Theme Builder Design Contributor: This badge is awarded when a contributor provides a Figma design for Theme Builder components or capabilities. The Theme Builder project team and core maintainers can nominate design contributors based on shared Figma artifacts related to an open GitHub issue in a Theme Builder repository.
  3. A11Y Theme Builder Core Contributor: This badge is awarded when a contributor has their first documentation or code contribution PR merged to Dev in a Theme Builder repository.

URL https://github.com/finos/a11y-theme-builder

Skills Accessibility; Design; Open Source

Badge Criteria

  1. Assessment, Volunteer, Member: Nominated by Theme Builder maintainers
  2. Project, Participant: Contributes accessible design artifacts to the project via merged PR(s)
  3. Project, Participant: Contributes code to the Theme Builder SDK to enable end to end accessibility via merged PR(s)

Attributes These are optional and provide additional details about the badge. You can choose from the following settings:

@aaronreed708 @lwnoble @evangk6 @codyzu - I've created draft Credly badge descriptions that the LF needs in order to issue Theme Builder badges. Can you look these over and comment or give a thumbs up here if everything looks good to you? Once we finalize this information I will send it to the LF contact who can create and issue badges- Let me know what you think!

aaronreed708 commented 4 months ago

I have two comments

PaulaPaul commented 4 months ago

Hello! I've updated the descriptions based on your feedback @aaronreed708 (great call outs!). What do you think?

aaronreed708 commented 4 months ago

I gave @PaulaPaul feedback via email. FInal descriptions were wonderful. Thank you!

aaronreed708 commented 4 months ago

@PaulaPaul as part of this issue (or close this issue as complete and open a new one) can you please document the Credly badges, the requirements for each and the process for awarding them. Should probably link to the badge documentation from the root README.md.

aaronreed708 commented 4 months ago

@PaulaPaul asking around for best practices for establishing a badging process. We are currently considering a private Slack channel in which to accumulate nominations, etc.

PaulaPaul commented 3 months ago

The proposed badging process is as follows:

  1. People who are listed as Theme Builder Maintainers can nominate individuals for any of the three badges.
  2. The nomination and badging process involves:
    • Adding the person to the private channel #a11y-theme-builder-badges on the FINOS Slack
    • Following up with that person privately to confirm the desired name and email address they would like to use for receiving their badge
    • Adding that information to the Linux Foundation spreadsheet for the appropriate badge. The LF spreadsheets are named with a prefix for the current month (e.g. '2024-05...').
    • On the first working day of the next month, links to the the spreadsheets for the previous month will be sent to our LF contact for badging mstepien@linuxfoundation.org (Magdelena Stepien).
    • Post a message to the badging channel saying that badge requests have been sent, and asking individuals to please confirm in the channel if they receive or do not receive their badges within a week of the request to LF.

@aaronreed708 for discussion on the project call - once we are agreed on this, I can add it to the project README or other docs (TBD) and we can close this issue... thanks!