owned this note
owned this note
Published
Linked with GitHub
# Fedora Badges community roundtable
_Notes and agenda for the monthly Fedora Badges community roundtable meeting_.
## Social Agreement
* Focus on listening.
* Stay present as much as possible. Refrain from email/chat/etc.
* Let everyone have a chance to speak, be aware of how much time you are talking.
* Be mindful of the meeting schedule and help to move the dialog forward.
* Use the raise hand function when you want to speak.
* Stay on mute when you are not speaking.
## Meeting structure
1. Intros, welcomes, hellos (~5m)
1. Team announcements & news (~5-10m)
1. Follow-ups from last meeting (if any) (~5-10m)
1. Ticket discussions (remaining time)
1. Open floor (remaining 5-10 minutes)
## Monthly agendas and notes
### 2024-04-17
***Chair(s)***
* Sandro (penguinpee/gui1ty) 🪑
* Emma (ekidney) 🗒️(Support ☕)
***Attendees***
* Michal (zlopez)
* Justin (jflory7)
* Aurelien (abompard)
* Roland (rolandixor)
* Akashdeep (t0xic0der)
#### Team announcements & news (~5-10m)
* Upcoming blog post about Badges by Fedora Infra/CPE. [A preview is available](https://communityblog.fedoraproject.org/?p=13547&preview=1&_ppp=b52f320c08).
* CPE and Infra team commited to current infra until end of 2024
* Can we get other communities and contributors excited about Badges?
* Helps set the context of where Fedora infra is at with where they can support
* Sharing: soon (end of the week or next week)
* Aurelien has news! He has looked at the badges code for the last fews weeks
* Plan on deploying fixes and such into production
* Not part of the servers that are frozen
* Should be easy to get community involvement and is very visible and yet we dont get many contributors
* Dont think we will get something significantly better by rewriting it
* Try to pitch an application to the community in a way that will be exciting and intrigue contributors
* Use graphs, diagrams, videos to generate interest
* Break problems down into smaller, more digestible tasks
* Get the ball rolling before Flock
* JWF: what timeline?
* Aurelien: Once code is rolled out we can start thingking about this. Should be start of May when code improvements are rolled out.
* Ready to migrate away from RHEL 7
* Aurelien will start logging issues in the Badges repos, some will be good first issues, others not.
* Need to document a list of all issues and papercuts
* Other areas and ideas for new badges to award people
* Have something to point people at to see what things / areas they could potentially help with. Aurelien would prefer this to be in an issue tracker on GitHub. Sandro agrees.
#### Follow-ups from last meeting (if any) (~5-10m)
* Reminders for next time:
* Badges RHEL 7 migration (*see notes above*)
* Flock papers
* Who will submit a talk / activity?
* Dev focus? Design focus?
* Akash submitted proposal about the badges system architecture. Probably wont be able to be there due to visa issues. Need someone to be there who can go through his material.
* Blog post (Sandro)
* Sorry, totally forgot about it. :frowning:
* See link above in annoucements section
#### Main topic discussions (remaining time)
* Akash will discuss a topic later in Matrix chat due to issues with A/V
#### Next month's chair
* **What does this entail?**
* Preparing the agenda based off the last meeting and next steps in the revamp
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* **Volunteers?** :eyes:
* Sandro (chair)
* Emma (notetaker)
---
### 2024-03-20
***Chair(s)***
* Marie (riecatnor) 🪑
* Sandro (penguinpee/gui1ty) 🗒️(Support ☕)
***Attendees***
* Justin/JWF (jflory7)
* Julia (jbley)
* Emma (ekidney)
* Sumantro (sumantrom)
* Aurelien (abompard)
* Akashdeep (t0xic0der)
* Sandro (Penguinpee)
* Roland (rolandixor)
* Chris (chris idoko)
#### Team announcements & news (~5-10m)
* Flock CfP open!
* https://communityblog.fedoraproject.org/flock-2024-cfp-until-april-21st/
* DEI team, planning is getting started from the FWD event!
* There is a call for volunteers
* https://discussion.fedoraproject.org/t/help-us-organize-fedora-week-of-diversity-2024/108576
#### Follow-ups from last meeting (if any) (~5-10m)
* Hackfest discussion
* Come back to this after looking at RHEL 7 EOL situation
* Marie's discussion post
* I didn't get to this :white_frowning_face:
#### Main topic discussions (remaining time)
* RHEL7 EOL
* Justins call with Fedora infrastructure, an update:
* No one wants to see Badges go away, or give up on it as a project
* It's a challenge to understand the success metrics/scope
* There might be a case where we can't migrate everyones current badges
* If we can't get interest this year, we might be looking at shutting down the service.
* Sumantro adds: do we have a solid timeline? this is Fedoras #1 recognition tool.
* Justin thinks we need to get this in place by the end of this year. If we can get to Flock knowing what we will do, that would be promising. Making a decision will influence what people will submit for Flock.
* Akash adds that fedora-messaging is the pain point. The automation piece is shaky. Someone from Community infra will explain the situation (a community blog post) and next steps. When?
* Julia asks, did we eliminate the option of getting an external provider based on an open source solution? I agree with Justin's timeline, Flock as a hard deadline.
* Aurelien comments that Mozilla OpenBadges was dropped in favor of open badges. Aurelien thinks that he can figure out how to make badges worsuk with RHEL9 before RHEL7 goes EOL. A lot of work. Not going to provide a refreshed system, just keeps it on life support. Long term, it takes quite a bit of maintenance to keep the system up to date. Not a lot of value in having folks manage this life support effort bc they would need to know fedora-messaging in and out. Agreed on flock timeline.
* Is this a sure thing? Yes, probably. Outreachy is happening and plenty of other things. Will have a good idea by May if this will happen.
* Justin shares: https://gitlab.com/fedora/commops/home/-/issues/13
* Aurelien adds: in fedmsg there wasn't any schema, the messages were a big dictionary. For fedora-messaging there is a library that pulls out the interesting info (which got out of sync quickly). Aurelien doesn't plan to spend too much time on making improvements to this library/system. Quite a few messages that are sent without a schema currently.
* Sandro asks, can we add the schema?
* Aurelien replies, yes, it makes sense to write the schema and send the owner of the project and ask them to add the schema. Right now fed-badges uses fedmsg to extract the info.
* Clear path forward:
* Aurelien will move badges to the next source of life support. will not address any updates/refresh aspects.
* Need to determine a longer term plan:
* Before flock we need to gather interested/invested volunteers.
* Sumantro notes that visas are a piece of the picture around flock. Justin notes that we want to make it more of a hybrid event this year. No promises about how this would work, but its something we want to do better on this year.
* We could present the situation at flock
* We could work on it at flock.
* Badges downtime post(s) needed?
* Maybe, maybe not, we will check in with Aurelien in May.
* Flock to Fedora
* CfP open until April 21st
* Gives us about a month.
* Who will be there?
* Marie
* Justin
* Hope to be there:
* sumantro ( depends on budget)
* Akash
* Emma
* Roland
* Most likely not:
* Sandro
* Aurelien (unlikely, but would love to test hybrid)
* Julia
* Chris (visa :( stuff)
* Let's check in with a couple weeks?
* Justin's idea: submit a session with the hopefuls, if we can't get funding, we can withdraw.
* Do we want to do something for badges?
* E.g. session, half hack
* Akash plans to propose a talk that covers the new infrastructure for badges. If he can't make it, the content will be produced and someone else can present it. Co-presenter? Akash to work on an abstract.
* Badges Design hackfest by Marie. This hinges on the future of badges. Could this be part of a design clinic? Or Marie to run the design clinic? Can Emma check in with community design team to see who will be at flock? Yes. Madeline won't be able to attend, Mo will probably attend.
* UI/UX? Emma would do it if there are things to share.
* Additional comments:
* Adding speculative sessions that aren't sure, don't make a lot of sense because we are blocking slots for other sessions.
* We should get the ball rolling in the lead up to Flock. Putting the word out, I mean. We need to make the community aware of the predicament. Coordinate with infra blog post? Sandro would be up to coordinate
#### Next month's chair
* **What does this entail?**
* Preparing the agenda based off the last meeting and next steps in the revamp
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* **Volunteers?** :eyes:
* Sandro (chair)
* Emma (notetaker)
#### Open floor (remaining 5-10 minutes)
---
### 2024-02-21
***Chair(s)***
* Marie (riecatnor) 🪑
* Sandro (penguinpee/gui1ty) 🗒️(Support ☕)
***Attendees***
* Marie
* Sandro
* Akash
* Emma
* Chris
* JWF (late)
#### Team announcements & news (~5-10m)
* Akash tested fedmsg in container, wasn't able to get it working :(
* Sandro asks, is there any chance of getting it ported? Akash responds no, because of dependencies
#### Follow-ups from last meeting (if any) (~5-10m)
* Hackfest Discussion Thread
* Sandro to follow up with Justin, is it still an option? DevConf.CZ is the most likely option
* Hackfestt will likely not happen in person before RHEL7 EOL
* Flock might be an opportunity
* Virtual hackfest is on the table
* Sandro is unlikely to attend Flock this year
* We need to start planning for the hackfest (availability, etc.)
* Chris wonders how many people are interested in taking part in hackfest (sign up page)
* Marie suggests an announcement be made of some kind
* Directly inviting people might be a good idea
* Akash: virtual hackfest before Flock might be a good opportunity to get more people involved
* Marie won't have an opportunity in April and May. That leaves March or June.
* Sandro asks if we still want to use hackfest for current Badges live support
* Akash suggests to use the hackfest for working on Badges 2.0
* Marie suggests there's a lesser role for design team at hackfest
***Older topics (may be skipped, if no longer relevant)***
* Justin: Update on Badges development participation
* Can be discussed further outside the meeting, but needs more immediate attention re: RHEL7 EOL
* Justin says he's not the right rep for this since he's not hacking on it.
* Justin: Good First Issues (GFIs)
* Skip for this meeting- but we want to make sure we get Justin on the next call
* This should create opportunities to onboard people in participating in badges development
* Might be a task for a co-lead
* Justin suggests it needs someone who has a good understanding of the code to decide what GFIs are
#### Main topic discussions (remaining time)
* RHEL7 goes EOL on **30 June 2024**
* Marie wonders if it is time to let go of Badges
* It's a hard decision, but we should not shy away from discussing it.
* Justin suggests the option of integrating it in Discourse (Discussion) as has been discussed before.
* Marie reminds us that Discourse integration comes with its own challenges
* Akash mentions the limitations of types of badges we can support if integrating them into Discourse
* Akash points out that the frontend is not what's giving us grief
* Justin: I think we are at the end of the rope for getting the 2.0 system done. We need bottom-liners, not just new contributors 😕
* Akash: Bottom-liners are people who stick around, for the most parts. The ones who are a go-to for stuff related to badges and can help point others to the right direction.
* Badges in Discourse would be a new project, ***not*** a migration
* Sandro: If we go that route, wouldn't that make Discourse Fedora's FB? Once you are in, it's hard to get out.
* Marie would be saddened to see all the artwork go. But there's probably other options of re-using them.
* Justin: Discourse badges are visible on people's profiles We can also come up with fun ways to let people pin badges onto their avatar when replying to other topics on Discussion.
* Sandro suggests a blog post to let the community know what's going on
* Sandro volunteers to write a draft
* Justin notes:
* We need to have a clear path forward if we want to make this continue.
* Suggested first next steps:
* Marie's post about level of commitment and stepping away
* Noting Justin has a meeting March 8th with Fedora leadership and infra about the future of badges. Let's wait for the community blog post until that meeting happens.
#### Next month's chair
* **What does this entail?**
* Preparing the agenda based off the last meeting and next steps in the revamp
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* **Volunteers?** :eyes:
* Marie (chair)
* Sandro (notetaker)
#### Open floor (remaining 5-10 minutes)
#### Follow Up's and Action Items
---
### 2024-01-17
***Chair(s)***
* Sandro (penguinpee/gui1ty) 🪑
* Marie (riecatnor) 🗒️(Support ☕)
***Attendees***
- Emma (ekidney)
- Akash
- Roland
#### Team announcements & news (~5-10m)
* Creative Freedom Summit is next week! https://creativefreedomsummit.com/
#### Follow-ups from last meeting (if any) (~5-10m)
* Justin: Update on Badges development participation
* Can be discussed further outside the meeting, but needs more immediate attention re: RHEL7 EOL
* Marie: Event Badges Reframing Identify Badges
* Still on the to do list! Can be taken off the follow ups
* Justin: Good First Issues (GFIs)
* Skip for this meeting- but we want to make sure we get Justin on the next call
* Hackfest Discussion Thread
* Sandro to follow up with Justin, is it still an option? DevConf.CZ is the most likely option
* Marie to pitch in but most likely not attending in person, would participate virtually
#### Main topic discussions (remaining time)
* RHEL7 goes EOL on **30 June 2024**.
* Current badges is still running on RHEL7 servers due to the old software stack requiring Python 2.x
* Infra team needs to upgrade those machines or turn them off
* More info: https://discussion.fedoraproject.org/t/rhel7-status-in-fedora-infra-early-2024-edition/101411
* We need a plan on how to move Badges off these old servers and, _preferably_, move it to fedora messaging at the same time, since fedmsg also depends on Python 2.x
* Meeting discussion:
* The machines will be upgraded, going to python 3, but Akash is talking with CPE about putting some resources towards upgrading badges to move to the new system
* Sandro: how much work would it be for porting from python 2 to 3. Would need to use fedora-messaging over fedmsg.
* Akash: fedmsg is the thing that is holding us back, We need to move to fedora-messaging. Aurelien(abompard) could help here as the author of fedora-messaging.
* We need to figure out what is needed to port to fedora-messaging and can we deliver this in time for RHEL7 EOL
* Marie asks: is this something that could be dealt with at a hackfest around devconf?
* Akash responds: that would be too late for the EOL
* Sandro responds: the hackfest should be focused on the system upgrade, but we could deal with some bugs in the upgrade to fedora-messaging
* Marie comments: I can help out with the project mgmt side, it would be good to be making a plan at our next call
* Akash: We will be contacting folks to come up with a to do list & plan
* Sandro, Akash, & Emma, will all be at FOSDEM and could discuss
* Marie had an idea to create a campaign of "Badges will DIE if you don't help", our badger is dying :(
#### Next month's chair
* **What does this entail?**
* Preparing the agenda based off the last meeting and next steps in the revamp
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* **Volunteers?** :eyes:
* Marie (chair)
* Sandro (notetaker)
#### Open floor (remaining 5-10 minutes)
* Discussion about the health of our revamp, the participation, sub-groups
#### Follow Up's and Action Items
---
### 2023-12-20
**Meeting cancelled due to holiday period and many people being unavailable**
---
### 2023-11-15
***Chair(s)***
* Sandro (penguinpee/gui1ty) 🪑
* Marie (riecatnor) 🗒️(Support ☕)
***Attendees***
* Marie
* Justin/JWF
* Emma
* Sandro
#### Team announcements & news (~5-10m)
* Pagure exporter coming (to be published [here](https://communityblog.fedoraproject.org/?p=12839&preview=1&_ppp=f0d69c606f) on Thu 16 November)
* What does this mean for Badges?
* We have the functionality to now export the Badges design repo from Pagure to GitLab, including issues and files uploaded to issues
* Will need to update the "criteria" field on the current badges website (necessary?)
* There is a script that can do this for us
* Let's make sure we are coordinated on timing as a team
* We also want to communicate this out to the wider community
* [Fedora Discussion topic for coordinating this change](https://discussion.fedoraproject.org/t/pagure-exporter-is-available-should-we-move-fedora-badges-artwork-to-gitlab/95944)
#### Follow-ups from last meeting (if any) (~5-10m)
* Emma: Results Questionaire Front End UI
* Should be ready by end of the week
* Super busy :(
* Emma will share next week, taking off follow up list
* Akashdeep: Badges development participation
* Akash not here, Justin going to check in for an update
#### Main topic discussions (remaining time)
* Marie & Justin: Event Badges Reframing
* [Discussion Thread](https://discussion.fedoraproject.org/t/feedback-requested-proposal-to-re-categorize-badges-to-manage-disproportion/90282)
* Are we all on board with this change?
* Proposal: Recategorize some of the event badges to community or content categories to help balance the disproportionate amount of current event badges now and in the future
* [5 +1's, no 0's or -1's]
* First Step: Need to identify which badges we want to change
* Marie to take this on
* Need to change the art
* Need to change the tag on the website
* Justin: Good First Issues (GFIs)
* Not sure where we left things off, we need to understand the next steps here
* Justin to check in with Akash about this topic
* Might need to get a clearer picture of the roadmap before we can make the good first issues
* Can be moved to follow up's
#### Next month's chair
* **What does this entail?**
* Preparing the agenda based off the last meeting and next steps in the revamp
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* **Volunteers?** :eyes:
* Marie
#### Open floor (remaining 5-10 minutes)
* Finding new contributers (development specific)
* A lot of weight was put on Akash, but he has other commitments (which is totally fine and good!)
* Ideas:
* A badge for working on the revamp
* Blog post
* Discussion post
* 1 on 1's are very helpful to engage new contributors (Marie)
* Hackfest
* Could be around Flock, or another community event like FOSDEM, DevConf.CZ, PyCon, Pro's: easier $$ wise
* Could be standalone, pro's: get to spend time together and focus on badges entirely
* For example: https://www.fedoraproject.org/wiki/Badges_Hackfest_2020
* Next step would be a discussion post, Marie will take this
* Three events, add dates:
* FOSS Backstage
* Linux App Summit
* DevConf.CZ
#### Follow Up's and Action Items
---
### 2023-11-01
#### Informal meeting to prep for release party
Attendees:
Marie
Emma
Akash
Agenda:
To Do:
- [ ] - Marie to finish up intro page
- [ ] - Akash to add one more slide with engineering stack
- [x] - Emma to add some badgers in
- [ ] - Emma to add infographic in
- [X] - Marie to track down release party ticket and provide availability
---
### 2023-10-18
***Chair(s)***
* Sandro (penguinpee/gui1ty) 🪑
* Marie (riecatnor) 🗒️(Support ☕)
***Attendees***
* Emma (ekidney)
* Sandro (Penguinpee)
* Onuralp (thunderbirdtr) ☕
* Chris idoko (chris)
* Roland Taylor (rolandixor)
#### Team announcements & news (~5-10m)
#### Follow-ups from last meeting (if any) (~5-10m)
* **Emma: Badges Front End UI**
* Closed questionaire on Discussions
* Reviewing data
* Not sure format to display results?
* In a google sheet now
* Graphic representation would be nice
* Emma will work on creating this
* some feedback:
* Outdated visually
* 50% of people have trouble accessing information/navigating
* [ticket](https://gitlab.com/fedora/websites-apps/fedora-badges/liberation/-/issues/1)
* High-fi wireframes in progress
* [ticket](https://gitlab.com/fedora/websites-apps/fedora-badges/liberation/-/issues/2)
* [penpot](https://design.penpot.app/#/view/52961d58-0a92-80c2-8003-2f68a60c2cdf?page-id=52961d58-0a92-80c2-8003-2f68a60c2ce0§ion=interactions&index=0&share-id=52961d58-0a92-80c2-8003-30b7e2a70d84&zoom=fill)
* Marie: pink is standing out a bit on page 2, maybe try a blue?
* **Marie & Justin: Event Badges Reframing**
* [Discussion Thread](https://discussion.fedoraproject.org/t/feedback-requested-proposal-to-re-categorize-badges-to-manage-disproportion/90282)
* _Please move to **Main Topics** if applicable_
* Marie: I think this is more of a to do, then a topic of discussion if everyone is on board
* Sandro: let's make this a main topic
* Marie: +1
* **Akashdeep: Badges development participation**
* Follow up on the meeting guide and continue to look for a volunteer for an earlier time zone.
* Onuralp provides an update:
* Some work happening on the backend
* Meetings have been well attended at times, sometimes just Akash & Onuralp
* Onuralps perspective is that the meeting is helpful. Sometimes different opinions pop up, which is useful.
* Two meeting times, alternating, to help with scheduling
* Action: can we get new invitations for the Badges Development calls?
*
#### Main topic discussions (remaining time)
* Release Party
* November 10/11th
* Who would like to participate?
* Note availability:
* Marie: Full availability as of right now. Friday preferred.
* Emma: Same as Marie ^
* Sandro: Available on saturday. Friday could be possible.
* Available until UTC 1700.
* For Friday availability would need time to request from work
* Akash:
* Onuralp: Can do it, full availability
* Chris: Full availability
* General presentation about the revamp
* [Slide deck](https://docs.google.com/presentation/d/1P8tgEWWu2IwMyLzS9qxmm7mUcDtlq_-UZtgW9OBXCg0/edit?usp=sharing) review
* Notes:
* Emma to add in slide about community feedback
* Emma to sprinkle badgers in across the slides
* Good to talk about how we're moving to gitlab
* General overview: why we are doing the revamp, what work has been done, what needs to be done, and what the future looks like
* Outreach, let's invite people to join!
* Set a meeting: whenisgood, Marie to set up
* Internship/Design specific presentation
* Would be nice to have this right before/after
* Chris/Roland
* Chris: full availability
* Roland: full availability
* Marie to advise them off call
* Justin: Good First Issues (GFIs)
* Justin is out today, let's push to next meeting
#### Next month's chair
* **What does this entail?**
* Preparing the agenda based off the last meeting and next steps in the revamp
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* **Volunteers?** :eyes:
* Sandro
* Marie (pending schedule okay!)
#### Open floor (remaining 5-10 minutes)
* Chatting and catching up!
* Marie/Smera working on the style guide on a weekly basis
* Sandro: go through open tickets
* Emma: using the new or old template for current badge requests?
#### Follow Up's and Action Items
---
### 2023-09-20
***Chair(s)***
* Justin W. Flory (jflory7/jwf)
* Sandro (penguinpee/gui1ty) [note-taker]
***Attendees***
* Marie (riecatnor)
* Aoife
* Shaun
* Sandro (Penguinpee/gui1ty)
* Ida
* Roland (rolandixor)
* Akashdeep
* Justin/JWF (jflory7)
#### Team announcements & news (~5-10m)
* Development hacking calls for backend to move to fortnightly
#### Follow-ups from last meeting (if any) (~5-10m)
* **Akashdeep: Pagure infra tickets for backend/data migration**
* Business as usual. Incremental progress on development.
* Resolved for now. This can be dropped for the next roundtable!
* **Emma: Badges Front End UI**
* Emma is on vacation today
* **Marie & Smera: Badge Design updates**
* Updated style guide is being worked on
* [Style Guide](https://docs.fedoraproject.org/en-US/badges/_attachments/fedora-badges-style-guide.pdf) (pdf)
* Design templates are overhauled
* [Badges Design Guide](https://docs.fedoraproject.org/en-US/badges/design-badges/)
* Marie/Smera met this week to discuss the plan moving forward
* The plan:
* Marie/Smera to wrap up style guide (we need this for the next step of the plan)
* We will set up a series of meetings for about 6-8 weeks where people can join and help us finish the badge designs
* Work on the handover for the design assets, make sure all info is gathered for maintainers/developers to implement new designs
* Work on drafting new documentation for designing badges and push to docs page once the new system is implemented
* When setting up the next sprint, this will be an update shared by Marie. Can be an update in the announcements.
* This can be dropped for the next roundtable!
* **Marie & Justin: Event Badges Reframing**
* [Discussion Thread](https://discussion.fedoraproject.org/t/feedback-requested-proposal-to-re-categorize-badges-to-manage-disproportion/90282)
* Wait to implement this change until the new system is set up.
* Keep this one for next time, probably as discussion as a main topic in next month's roundtable.
* **Akashdeep: Badges developer pool**
* That is meant to give a status if we have enough participants in development.
* Reforming the backend developer call to have better uniformity/consistency for time to develop and hack together.
* See previous announcement about change to timing/cadence of backend dev call.
* Different timezones? Do we have an overview of the timezones of current participants?
* Typically European time zones that attend and participate.
* GLB attends rarely at 3:30 AM (!!), but he wants to learn more.
* Q: Is there a guide for running these backend developer meetings?
* No, but this could be a good first step.
* Q: Is there someone who could help run the meetings in a more western-friendly timezone?
* Need to identify who.
* For next time, follow up on the meeting guide and continue to look for a volunteer for a earlier time zone.
#### Main topic discussions (remaining time)
* Presentation for the next release party (~November)
* Revamp general presentation
* Bottom-liner?
* Badge Design Internship presentation
* Presented by recent Outreachy Fedora grads Chris & Roland
* 25-minute session to showcase their work
* Actions:
* Check in with Roland & Chris and make sure they are on board, if yes, ask them to work on a deck (Marie)
* Initiate Slide Deck (Marie)
* [Slide Deck for General Presentation](https://docs.google.com/presentation/d/1P8tgEWWu2IwMyLzS9qxmm7mUcDtlq_-UZtgW9OBXCg0/edit?usp=sharing)
* Link should be open, request edit access if needed/desired
* Each part of the team builds 3-5 slides
* Development
* UI/UX
* Graphic Design
* Follow-up for next time, re: general presentation about the revamp.
* Good first issues
* Overview of what a GFI is: https://unicef.github.io/inventory/dpg-indicators/8/good-first-issue/
* Design: Sprint for finishing the final stretch with the new style guide.
* AI: JWF to join a backend dev call with Akashdeep and brainstorm on GFIs for backend dev.
#### Next month's chair
* **What does this entail?**
* Preparing the agenda based off the last meeting and next steps in the revamp
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* **Volunteers?** :eyes:
#### Open floor (remaining 5-10 minutes)
#### Follow Up's and Action Items
* [ ] Drop "Pagure infra tickets for backend/data migration" from follow ups
* [ ]
---
### 2023-08-16
***Chair(s)***:
* Marie Nordin (riecatnor)
* Justin W. Flory (jflory7/jwf) [note-taker]
***Attendees***:
* Roland Taylor (rolandixor)
* Nikita Tripathi (nekonya3)
* Akashdeep Dhar (t0xic0der)
* Chris Idoko (chris)
* Conor
* Aoife
* Shaun
* Aurelien
#### Team announcements & news (~5-10m)
* **Travelers: How was Flock 2023?**
* Any productive discussions about badges at Flock?
* Akashdeep
* Discussion with Justin Forbes regarding automated badges for kernel testers
* Sumantro Mukherjee requesting admin access to award badges manually during test days
* Nikita Tripathi expressed her interest to work on both frontend and backend
* JWF
* Nikita presented the traditional Badges talk and repped the recent changes to badges style to the community (the new artwork came as a (good!) surprise to some contributors)
* Recording: [Fedora Badges - How to](https://www.youtube.com/watch?v=bD2R4Yt8m88&list=PL0x39xti0_64OcXEGLCtoI4nouADqaTcT&index=1&t=26691s)
* Virtual feedback:
* Some rooms did not have mic runners between speakers in a room. (We had moderators, but maybe more training/guidance for our volunteers.)
* Dedicated virtual social sessions alongside the conference. Being intentional about it and giving people time to plan to participate.
* Questions from virtual attendees making it to the in-person Q&A. (Maybe having a dedicated volunteer for each track/room for the online/virtual presence?)
#### Follow-ups from last meeting (if any) (~5-10m)
* **Akashdeep: Documentation of relevant back-end transition information**
* Do you need help finding volunteers?
* Ongoing task - Documentation is added as new changes are made to the codebase
* Could use a dedicated volunteer for shadowing and documenting stuff
* A small group is currently documenting the API and adding code to the 2.0 codebase. Still looking for more people though.
* Q from JWF: Is there a next action or could this be cleared from the past follow-ups?
* Can be cleared
* **Other business**
* Chris Onoja Idoko reached out to Akashdeep to volunteer in the development process
* Chris is more interested in front-end and possibly some documentation.
* Invited Chris to the new Matrix room.
* **Web&Apps team: Smaller scope engineering related collaboration meetings**
* Has this been promoted at all? Maybe a short post on commblog/discussion would be helpful. Could incorporate the above request for volunteers for docs transition
* JWF: A new Matrix room was created earlier today to be the organizing home for back-end development chatter. [**#badges-devel:fedoraproject.org**](https://matrix.to/#/#badges-devel:fedoraproject.org)
* Marie: Can this be cleared from follow ups?
* can be cleared
* **Akashdeep: Pagure infra tickets for backend/data migration**
* How is this progressing?
* Akashdeep
* Triaged a bunch of issue tickets on GitLab
* Connected relevant epics with the tasks
* Authentication set up for modification of the existing entries
* Links to tickets:
* https://pagure.io/fedora-infrastructure/issue/11323
* https://pagure.io/fedora-infrastructure/issue/11324
* We need more info into the Epics, Akash will work on in the next week
* Akash & Justin to connect on opening more tickets
* Let's keep this on the follow up list
* **Emma: Badges Front End UI**
* How did it go gathering feedback on the mockups?
* Design team
* Flock
* Need us to help out with this or are you ready to move forward?
* **Marie & Smera: Badge Design updates**
* Interns to upload updated templates and palettes within the next week
* Where should these go:
*
* Interns to upload all of their artwork into Gitlab
* Do they need some permissions to do this?
* FAS ID's are chris and rolandixor
* Let's confirm this is where the artwork should go:
* https://gitlab.com/fedora/websites-apps/fedora-badges/collection/-/tree/main
* Short answer: yes
* Long answer: still discussing how to structure assets
* Interns to summarize their learnings so that can be translated into the style guide
* Marie/Smera/Nikita to work on finishing up the style guide based on these changes once the internship ends (august 25th)
#### Main topic discussions (remaining time)
* **Marie & Justin: event badges reframing**
* Justin proposed we adjust how we do badges here:
* https://pagure.io/fedora-badges/issue/910
* Before we change a long standing decision, let's get into this a bit as a team
* Marie found the breakdown of current badges are as follows:
* Content - 91
* community - 132
* event - 256 (!!)
* misc - 13
* quality - 57
* development - 96
* We discussed things a bit further and came up with a potential middle ground:
* Make organizer badges fall under community
* Would this cover all things related to organizing? Or should there be another badge that falls under content? For tasks such as:
* Design, marketing/communications
* JWF: Speaking/presenting, but as an annual series (not event-specific)
* Marie: I think it makes sense to create this many badges for Fedora events, but generally not for third party events (such as FOSDEM). If folks want more badges for that, I think we have things related to Ambassador/advocates which should cover that, or could be proposed.
* Akash: Q regarding retirement. Do we have a concern about folks awarding badges after events happen?
* Not so much- we trust organizers to award the badges on merit and not unfairly (Marie + JWF)
* Justin: Q: For speakers, would it make more sense to do an annual series, or event specific pieces?
* e.g. "you spoke at F00 release party" or "you spoke 1, 2,5, 10 series"
* aka should this be for specific high level events or a generic series
* Shaun: A series makes sense like some of the other badges.
* Marie: Ownership of the badges is a pre-requirement. Who awards the badges? Where does someone go to get the badge once they have done one of these activities?
* Shaun: Makes sense, maybe Mindshare should own this?
* JWF: Or [CommOps 2.0](https://fedoraproject.org/wiki/CommOps/2.0)?
* Akash: Easy for things to fly under the radar if the community is not empowered to know where/whom to ask for getting the badge.
* Next steps:
* Marie to write: Discussion post to get community input
* JWF: We need an owner for event badges. (CommOps & Mindshare would be the natural owners for this sort of thing)
* **Team: How is the revamp progressing, let's do a temperature check**
* Are any folks feeling burdened? Are any folks feeling under-utilized?
* Marie: Badge design efforts are going great. Our current interns have spent a lot of time on their work. A lot of my time is going there. After the internship, I could look at more design aspects. I have been keeping a healthy boundary with the time I can commit, but I am wondering more about the development side of things.
* Akash: Going great but slowly. Limited in the number of people on board right now. Hoping to grow this with the increased interest post-Flock. The regular calls for back-end development are helping build a cadence and maintain momentum. Hope that the pace of things continues to improve over time.
#### Next month's chair
* **What does this entail?**
* Preparing the agenda based off the last meeting and next steps in the revamp
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* **Volunteers?** :eyes:
* JWF is happy to take notes if nobody else wants to take it on!
* Sandro
#### Open floor (remaining 5-10 minutes)
* **Marie: Preview of badge design updates process**
* Anything else we should be capturing as the internship finishes up? (August 25th)
* JWF: its important to have everything organized correctly in the gitlab repo, for current system and future system.
* Akash: adds that we are aiming to have an updated interface to add new badges/artwork.. in the future anyone should be able to add badges from the interface
* The question we likely need Sandro and/or other Badge admins to answer is how they want to handle the updated artwork from a workflow POV. Do we update all artwork at once? Push them iteratively in small batches? Etc.
* Anything else we should be considering for after the internship ends?
#### Follow Up's and Action Items
* [ ] Example action item
* [ ]
### 2023-07-19
#### Intros, welcomes, hellos (~5m
***Chair(s)***:
* Onuralp Sezer (thunderbirdtr)
* Marie Nordin (riecatnor)
* Sandro (Penguinpee/gui1ty), backup
***Attendees***:
* Marie (riecatnor)
* Sandro
* Akashdeep
* Onuralp
* Aurelien
* Roland
* Smera
* Emma
* Chris
* Justin/JWF
* Ngobiri
#### Team announcements & news (~5-10m)
* **Akashdeep: Development state of affairs**
* Development work is going at full speed ahead - We now have regular calls at 0830UTC
* Database Abstraction Layer is now the part of the [Server](https://gitlab.com/fedora/websites-apps/fedora-badges/server) - thus simplifying the structure
* The [API interactions](https://gitlab.com/fedora/websites-apps/fedora-badges/server/-/blob/main/badges_server/system/router/user.py) for `USERS` is about to be completed - some interactions remaining
* To keep an open ecosystem of 3rd party applications, we are implementing [access tokens](https://gitlab.com/fedora/websites-apps/fedora-badges/server/-/blob/main/badges_server/system/router/user.py#L98-L104)
* Discussions of [OpenIDC based authentication](https://fastapi.tiangolo.com/tutorial/security/#openid-connect) and internal authorization are in progress
* The existing [issues tickets](https://gitlab.com/fedora/websites-apps/fedora-badges/server/-/issues) have now been tagged appropriately with their [parent epics](https://gitlab.com/groups/fedora/websites-apps/-/epics/?state=opened&page=1&sort=start_date_desc&label_name[]=app::Badges)
* A working [HTTP basic authentication](https://gitlab.com/fedora/websites-apps/fedora-badges/server/-/blob/main/badges_server/system/auth.py) is implemented for now with two access levels
* We now have two more CPE folks, James Richardson and Tomas Hrcka onboard
* We were constantly mentored by Aurelien Bompard, Ryan Lerch and Nils Philippsen
* Wanna help shaping up our Fedora Badges backend - request for ticket assignment [here](https://gitlab.com/fedora/websites-apps/fedora-badges/server/-/issues)
#### Follow-ups from last meeting (if any) (~5-10m)
* **Akashdeep: Documentation of relevant back-end transition information**
* Being a recurring target to meet, some progress has been made here
* We could use some more volunteers to shadow and write documentation
* **Akashdeep, Onuralp et al.: Smaller scope engineering related collaboration meetings?**
* We now have regular meetings at 0830UTC on Monday, Wednesday and Thursday
* We have folks contributing asynchronously as well as timezones can be difficult
* Holler at us with your email address if you want in - we will invite you on board
* **Justin & Akashdeep: Pagure infra tickets for backend/data migration**
* Links:
* https://pagure.io/fedora-infrastructure/issue/11323
* https://pagure.io/fedora-infrastructure/issue/11324
* We now need more epics to be created as issues on fedora-infrastructure issue tracker due to the significant progress we made
* We need new issue tickets pertaining to the existing epics. Collaborating with Aoife to map the work needed. Akash is overseeing this, with the help of volunteers and folks from CPE infra.
* **Emma: Badges Front End UI**
* Link:
* https://discussion.fedoraproject.org/t/badges-front-end-ui/85259)**
* Next steps:
* Onuralp to give input on thread
* Emma to take her work/the post to the design team to get input
* Justin suggests reaching out to individuals/small groups to get input on the wireframe mockups
* People who are on the leaderboard
* Group interview with volunteers
* Fedora design team
* Fedora w&a team
* Corner people at flock to give input ;) "hallway track"
* **Marie & Smera: Collaborate on providing feedback to Nikita to help complete the style guide**
* How did this go? Were you able to achieve this?
* Same status as last month both Smera and myself are meeting with our two interns bi-weekly which takes up all the time we have available for the time being. This is still on the to do list, but we are prioritizing the interns to enable as much badges design work as possible.
* **Marie to rework the badge design templates and palettes**
* Same status as last month: the updated templates and palettes are "in testing" by our interns
* In the last couple weeks of their internship, they will be putting the finalized templates/palettes into gitlab
#### Main topic discussions (remaining time)
* **Roland Taylor / Chris Onoja Idoko: Badges conversion**
* Interns will be presenting their work
* Suggestion to create a discussion post with some of the interns work
* The badges outreachy team will discuss the feedback as well
* Roland's Slides link: https://drive.google.com/file/d/1K45YgmjAX4usORHJl7ajOfCn9_ovoDO7/view?usp=drive_link & PDF: https://drive.google.com/file/d/1eNgkhlu92vrm_bGuano9yoeLkexvCHMn/view?usp=sharing
* Chris's Slides link: https://docs.google.com/presentation/d/14qc0qVA_9j1NrggQSrm4rnGJEW8e_3W3dZ-BjYqxE7o/edit?usp=sharing
* Feedback:
* love the slide design for the intro slide
* That looks nice with the new "borderless" borders (outlines).
* borderless style is new "thing" nowadays so it is very natural to see that as well
* It could do with a drop shadow to make it stand out.
* I also wish to see Colúr! in couple of badge like "panda"
* very sleek, i love these!
* It might be nice to create a discussion post? Roland & Chris we can discuss 😃
* Minor detail: the blood dropping on to the border looks "better".
* Marie I think we need more "Colúr!" since we already have Panda and badger in there I think it is time to bring 3rd mascot more ??? just idea ?
#### Next month's chair
* What does this entail?
* Preparing the agenda based off the last meeting and next steps in the revamp
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* Volunteers? :eyes:
* Marie Nordin (riecatnor)
* Sandro
#### Open floor (remaining 5-10 minutes)
* Akash shares badges server work with a demo
* shows off cool web interface that interacts with API endpoints!
#### Follow Up's and Action Items
* [ ] Example action item
* [ ]
### 2023-06-21
#### Intros, welcomes, hellos (~5m
***Chair(s)***:
* Sandro (Penguinpee/gui1ty)
* Roseline Amarachi
***Attendees***:
* Zlopez
* Akashdeep
* Shaun
* Marie (Riecatnor)
* Nikita Tripathi
* Paul Power
* Emma (Ekidney)
* Roland Taylor
* Onuralp Sezer (thunderbirdtr)
* Jhennifer
#### Team announcements & news (~5-10m)
* t0xic0der:
* Fedora Badges [Developer Database environment](https://discussion.fedoraproject.org/t/fedora-badges-developer-database-environment-is-now-available/84168) is now available!
* Added license statement and cleaned up documentation for various components
* Added [documentation](https://gitlab.com/fedora/websites-apps/fedora-badges/database-models/-/tree/main) about databases. (Hint: follow the links)
* Database Models work in now in full swing
* Phasing out of the Collections entity from the system
* Will remain as a secondary entity for historical records for artworks and entities
* But the artworks and rules will now be stored in the database entity itself
* Helps simplify by having a single source of truth for the system instead of two.
* Onuralp, Akash and Sandro to discuss further on something related to the database.
* Following discussions are in progress - People are recommended to participate in them
* [Badges for Discourse](https://discussion.fedoraproject.org/t/badges-for-ask-fedora-and-fedora-discussion-overall/46123)
* [Implementation of Discourse badges](https://discussion.fedoraproject.org/t/implementation-details-for-fedora-discussion-badges/83648)
#### Follow-ups from last meeting (if any) (~5-10m)
* **Permission issue for transferring Epics to Badges GitLab**
* Sandro how did this go? What is the update on the permissions? Do we need to do anything more?
* 0-]Concluded to leave as is, there is lacking functionality in Gitlab to make that possible.
* **Sandro & Sayan to reconnect about pushing badges & writing rules**
* Were you able to connect? How did it go?
* Postponed for the time being
* **Documentation of relevant back-end transition information**
* What is the update? How is this going?
* Action item for Akash
* This is not done yet however the progress made in the developer database environment can be counted.
* **Smaller scope engineering related collaboration meetings?**
* How is this going? Was this successful?
* We plan on using the weekly Fedora Websites and Apps Team Call for this
* For the design side, Marie & Smera meeting with interns twice weekly.
* Sandro suggested that the Engineering team set up a small scope meeting once a week. Akash to set up meeting and sending out invites.
* Links:
* **Pagure infra tickets for backend/data migration**
* Justin and Akashdeep how did this go?
* This isn't done but things are in progress. Database side of things is also in progress.
* Links:
* https://pagure.io/fedora-infrastructure/issue/11323
* https://pagure.io/fedora-infrastructure/issue/11324
* **Naming and location conventions for updated art**
* Marie and Sandro, how did this go? Do we need anything more?
* Agreed:
* Use subdirectories for each category
* Use category_shorttitle.ext format
* The repository would still exist and be in place but wouldn't be actively looked into.
* Links: https://discussion.fedoraproject.org/t/naming-conventions-for-revamped-badge-art-files/83023
* **Emma to start wireframing for comparing a new frontend versus a Discourse-based UI**
* What is the progress on this? Do we need anything more?
* Research document and low-fi design is in progress.
* Actions/pages for creating a QR code and manually awarding badges should be added to the User flow.
* Akash suggested the frontend to be stand alone based on discussions with community/CPE
* Marie suggested Emma to post work on the Wireframe on discussion so folks can review and give feedback.
* Akash suggested Emma should clarify the flow between search and the user so it is clear what the actual flow is.
* Links:
* https://hackmd.io/@ekidney/ryx-PHdD3
* **Outreachy Interns to begin internship**
* How is this going? Everyone settled in?
* This already started and about a month in.
* Artworks are being moved and the progress is going fine.
* Making improvements to the files while following the style guide.
* Interns will be presenting their work at the next meeting.
* **Marie and Smera to collaborate on providing feedback to Nikita to help complete the style guide**
* How did this go? Were you able to achieve this?
* Time has gone to supporting the interns, but this is still on the to do list.
* It's a work in progress, however, it still looks good but there are small changes to be done.
* **Marie to rework the badge design templates and palettes**
* How did this go? Do we need anything more?
* This is complete and in "testing" by the interns.
* Once we solidify their functionality, they will be added to a pagure ticket and on gitlab, and eventually to badges docs once we move to the new system. Adding them to docs before we make the transition could be confusing for incoming designers.
#### Next month's chair
* What does this entail?
* Preparing the agenda based off the last meeting and next steps in the revamp
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* Volunteers? :)
* Onuralp
* Sandro
* Marie (notetaker)
#### Open Floor
* Marie: is anyone submitting proposals for Flock?
* Nikita is planning to submit a badges related talk regarding using the template. Marie & Nikita to meet. It's been extended
* Akash has submitted a session.
* Sandro will be attending, has not submitted a session (it's close by)
* Emma will be attending
* Chris (intern) is submitting a session
* Akash: demonstration
* Follow Up's and Action Items
* [ ] Example action item
* [ ]
* ****
* **Collaboration with the Fedora Badges Revamp project’s developer sub-team**
*
#### Main topic discussions (remaining time)
* JWF: Reviewing docs for Fedora Badges and unifying our docs to fewer places
* AM: Developer working groups to be spun up outside of monthly round-table now that the developer database environment is available
#### Open floor (remaining 5-10 minutes)
### 2023-05-17
* Chair:
* Marie Nordin
* Roseline Amarachi
* Attendees:
* Name (FAS ID)
* Emma Kidney (ekidney)
* Sayan Chowdhury (sayanchowdhury)
* Shaun McCance
* Akashdeep Dhar (t0xic0der)
* Aoife Moloney (amoloney)
* Sandro (Penguinpee or gu1lty)
* Roseline Amarachi
* Roland Taylor
* Michal Konecny (zlopez)
* Marie Nordin (riecatnor)
* Chris Onoja Idoko
* Justin W. Flory (jflory7)
* Olive Oparaocha
#### Team announcements & news
* [Two Outreachy applicants]([https:/](https://www.outreachy.org/alums/2023-05/)/) have been selected. Congrats to Roland and Chris! Sincere gratitude to *all* of the applicants :blue_heart: we know that life takes us where we need to be, but you are all welcome in Fedora & badges!
#### Follow ups on last month's to do's
* **Sandro to move charters to Badges gitlab wiki**
* How did this go? Do we need to do anything more?
* The charters are on WIkI already
* Links:
* **Sandro to move Epics to Badges gitlab**
* How did this go? Do we need to do anything more?
* No option to move epics to gitlab
* If we move, we lose the comments
* Not sure if we should move them or keep them where they are
* Sandro moved the main epic to badges, we can link to the epic with commentary
* We might need to address this later on
* **Sandro to add structure documentation to Badges gitlab wiki**
* How did this go? Do we need to do anything more?
* https://discussion.fedoraproject.org/t/picking-a-place-to-organize-and-implement-fedora-badges/46866
* All done!
* Links:https://gitlab.com/groups/fedora/websites-apps/fedora-badges/-/wikis/home
* https://discussion.fedoraproject.org/t/summary-of-april-2023-fedora-badges-community-round-table-meeting/81155/7
* **Sandro & Sayan to reconnect about pushing badges & writing rules**
* Were you able to connect? How did it go?
* Wasn't able to connect this month.
* Check in again next month.
* **Marie, Smera, & Nikita to finalize work to prep for design internship**
* How did this go? Do we need to do anything more?
* Marie & Smera created a timeline for Outreachy interns
* Marie & Smera to meet with interns next week
* Marie & Smera working on feedback for Nikita to complete style guide
* Marie in progress on reworking badge design templates and palettes
#### Topics & Notes
* Questions for sub-teams:
* Design: Could we start a wireframing / prototyping phase for comparing a new frontend versus a Discourse-based UI? This might help break the draw on which direction we go.
* There is capacity for this to be done.
* A timeline discussion is necessary. Next month's roundtable is a good starting place for reviewing wireframes and pushing us toward a decision on which direction to go.
* Emma could give a follow up before next month's roundtable and also a probability to track the progress on Gitlab.
* Engineering: Are there clear docs on our selected tools for the revamp? How could we make the developer experience better for Badges newcomers?
* Do we have a concrete documentation for developer environment setup?
* We don't have a concrete documentation yet but it would be nice to have this and also link the proposed framework we use in the documentation.
* Proposed technologies: https://fedora-arc.readthedocs.io/en/latest/badges/prop_rewrite_technologies.html
* Challenge to think about: how to keep people engaged and activated. Maybe thinking about "bite sized tasks" or good first issues
* First steps for engineering & design sub-teams
* Engineering
* https://discussion.fedoraproject.org/t/summary-of-february-2023-fedora-badges-community-roundtable-meeting/46815/8
* Organize frequent meetings and discussions to plan the engineering efforts thoroughly
* Regarding this piece of the scope, does this mean independent engineering meetings? Or does this refer to the standing monthly call?
* Smaller scope, engineering related collaboration meetings could be once or twice a week
* Sandro: bi-weekly meetings to work on design and engineering
* We need to open pagure infra tickets for backend/data migration (Justin)
* discussion of making the database available for testing
* Step 2 and 3 of proposed roadmap (separate tickets with specific tags)
* Justin: are we done with the first step of the proposed roadmap? Yes!
* Akash to work on those tickets once opened
* Design
* Should the new art files (PNGs) be named exactly the same as the old files?
* Sandro: would need to look into it, but maybe not an issue to be renamed
* Akash: it helps on the automation to keep them the same
* Sandro: the naming is currently incoherent, it could be helpful to rename
* Sandro to look into the naming of the art files. If we do not need to stick to the same naming scheme, it gives us a chance to do this better.
* Sandro and Marie to have a chat and finalize on this.
* Where will the new art files go in the Gitlab structure?
* Akash to create a repository for the art (PNG & SVG)
* Link:
* https://discussion.fedoraproject.org/t/summary-of-february-2023-fedora-badges-community-roundtable-meeting/46815/6
* Work closely with the Fedora Badges Revamp project’s developer sub-team to understand the goals and objectives and reflect them in the UI / front-end and badge designs.
* This poses the question: do we have a consensus on what our front end will be? This will inform what the design sub-team does.
* If we have a unique front end, this will mean:
* Start development of UI/UX mockups
* If we use discourse as a front end, this will mean:
* Understanding customization capabilities of discourse. For example: can we adjust the design for the discourse badges page?
* Other pieces of the scope will be addressed with the internship
#### Next month's chair
* What does this entail?
* Preparing the agenda based off the last meeting and next steps in the revamp
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* Volunteers? :)
* Sandro & Roseline
* Actions
* [ ] Example action item
* [ ]
### 2023-04-19
Chair:
* Marie Nordin
Attendees:
* Sandro (penguinpee/gui1ty)
* Michal Konecny (zlopez)
* Akashdeep Dhar (t0xic0der)
* Roland Taylor (rolandixor)
* Aoife Moloney (amoloney)
* Nikita Tripathi (nekonya3)
* Ida Delphine (idadel)
* Jhennifer
* Chris Onoja Idoko
* Roseline Amarachi
* Erolkeskin
* Megha Sharma
* Ngobiri Falyne Chinaero
Team announcements & news:
* CPE team had planning meeting, factored in badges work
* backend refactoring / database migration
Topics & notes:
* Finalize Engineering & Design Charters
* Engineering Charter
* https://discussion.fedoraproject.org/t/summary-of-february-2023-fedora-badges-community-roundtable-meeting/46815/8
* Any last minute feedback?
* Going once.. twice.. Finalized!
* Design Charter
* https://discussion.fedoraproject.org/t/summary-of-february-2023-fedora-badges-community-roundtable-meeting/46815/6
* Any last minute feedback?
* Going once.. twice.. Finalized!
* To Do's
* Push charters to Gitlab repo.
* https://gitlab.com/fedora/websites-apps/fedora-badges
* Let's confirm exactly where this should go- notes from last call say "Main repo"
* Link: https://gitlab.com/groups/fedora/websites-apps/fedora-badges/-/wikis/home
* Volunteers to push charters to gitlab repo? :)
* Penguinpee volunteers
* Revisit structure of Fedora Badges Gitlab
* Akashdeep's structure proposal: https://discussion.fedoraproject.org/t/picking-a-place-to-organize-and-implement-fedora-badges/46866/1
* Any last minute feedback?
* Going once.. twice.. Finalized!
* Justin's Epic proposal:
* https://gitlab.com/groups/fedora/websites-apps/-/epics/2
* https://discussion.fedoraproject.org/t/early-look-using-gitlab-epics-for-tracking-fedora-badges-development-work/79207
* All in agreement of using Epics?
* Aye or nay?
* Going once.. twice.. Finalized!
* Based on this discussion I think we need to move this Epic to the Badges repo
* To Do's
* Add structure to gitlab wiki page
* https://discussion.fedoraproject.org/t/picking-a-place-to-organize-and-implement-fedora-badges/46866/1
* https://gitlab.com/groups/fedora/websites-apps/fedora-badges/-/wikis/home
* Volunteers?
* Sandro
* Volunteers to make the W&A Epics to Badges Epics move?
* Sandro
* Anything other to do's related to Gitlab structure/org?
* Sharing knowledge around pushing badges and creating rules
* Did Sandro & Sayan connect in the last month?
* If yes, awesome! Sandro do you feel you have what you need?
* Yes, this happened. Sayan passed some info, but they need to reconnect again.
* If not, maybe this could be recorded?
* Follow up: is it possible to get this information published/clarified in Badges docs?
* Pushing of badges is documented well
* Pushing the rules files is a bit more intimidating and complicated
* Python syntax
* Some complications because of some broken things in badges backend
* Sandro suggests to add a documentation task related to the revamp
* To Do's
* Sandro to reconnect with Sayan
* Badges design internship
* Dates of internship: May 29th-Aug 25th
* Smera and Marie will mentor two interns
* Finalize padding requirements for badge template in accordance with whatever new front-end we go with.
* Do we have a decision about using discourse versus unique front end?
* Maybe it doesn't matter either way. Padding should/could be built into the website, and not the art files?
* This would work for both options
* In this case we would leave a couple pixels on each side of the badge art
* Akash: transparency necessary (PNGs needed), padding in front end makes sense to me
* Decided:
* Adjust templates to have a few pixels of space around each side (padding NOT built into art templates)
* To Do's
* Finalize style guide (Nikita and/or Smera)
* Marie to send Nikita feedback
* Finalize templates
* Updated palette files
* Next month's meeting chair:
* What does this entail?
* Preparing the agenda based off the last meeting
* Reminding the Badges chat and sending the video link the day of the meeting
* Hosting the meeting and ensuring we stay on agenda
* Writing a meeting summary and posting on discussion.fpo
* Co-chairing is an option!
* Volunteers? :)
* Roseline & Marie
* Follow Up's and Action Items
* [x] Marie to publish meeting summary on discussion.fpo under #badges-team
* [ ] Sandro to move charters to Badges gitlab wiki
* [ ] Sandro to move Epics to Badges gitlab
* [ ] Sandro to add structure documentation to Badges gitlab wiki
* [ ] Sandro & Sayan to reconnect about pushing badges & writing rules
* [ ] Marie, Smera, & Nikita to finalize work to prep for design internship
* [ ] Roseline & Marie to co-chair the May roundtable
### 2023-03-15
Chair:
* Aoife Moloney
Attendees:
* Marie Nordin
* Emma Kidney
* Paul Power
* Aoife Moloney
* Akashdeep Dhar
* Justin/JWF
* Sayan Chowdhury
* Sandro (Penguinpee)
Topics & notes:
* Design Charter Reveal/Review (Marie)
* https://discussion.fedoraproject.org/t/summary-of-february-2023-fedora-badges-community-roundtable-meeting/46815/6
* Timeboxing this to 1month for review. Will be finalized at the next rountable meeting
* Feedback preferred through discourse (JWF to split topics)
* Engineering Charter Reveal/Review (Akashdeep)
* https://discussion.fedoraproject.org/t/summary-of-february-2023-fedora-badges-community-roundtable-meeting/46815/8
* Engineering charter feedback to happen in new thread
* 1month for review, closing out at next roundatable
* Epics! (JWF)
* Context
* https://discussion.fedoraproject.org/t/early-look-using-gitlab-epics-for-tracking-fedora-badges-development-work/79207/1
* TODO: Pick start & end dates to flesh out the roadmap
* IN PROGRESS: familiarise with the structure, gather feedback on the epics listed,
* Q(penguinpee): what needs to happen to get access to the Fedora space(s) Gitlab?
* A(JWF): sign up through your FAS account or through a link to sign up
* Q(AM): How can CPE get involved in this work? Are there labels we can use to assign/watch work?
* A(JWF): There is a label to help tracking issues and feedback is welcome if there are ways to make the project work management better for CPE engagement, and other interested parties
* (AM): The board is great, Id like to reference/use it when planning with the wider CPE team to get more involvement from that team to support the initiative
* Structuring of the projects and repositories (Akashdeep)
* Context
* https://discussion.fedoraproject.org/t/picking-a-place-to-organize-and-implement-fedora-badges/46866/1
* Subgroup
* https://gitlab.com/fedora/websites-apps/fedora-badges
* Projects
* Accolades API https://gitlab.com/fedora/websites-apps/fedora-badges/accolades-api
* Accolades CLI https://gitlab.com/fedora/websites-apps/fedora-badges/accolades-cli
* Collection https://gitlab.com/fedora/websites-apps/fedora-badges/collection
* Liberation https://gitlab.com/fedora/websites-apps/fedora-badges/liberation
* Messages Consumer https://gitlab.com/fedora/websites-apps/fedora-badges/messages-consumer
* Documentation https://gitlab.com/fedora/websites-apps/documentation (Websites and Apps Team)
* Some assistance regarding pushing badges and setting rules etc. (Penguinpee)
* Understanding the expectations
* Trying to get more context around how that should be done
* Supervision and more information is requested
* Decisions
* Charter reviews
* Both design & engineering charters are open for review for 1 month.
* They will be finalized in April Roundtable
* Final site for both should be GitLab repo
* [Akashdeep] We are attempting to have one source of truth for all documentation for the websites and applications that fall under our remit
* [Marie] Have a separate section for housing the charters as a part of the revamp that happens now ("Fedora Badges 2.0" or "Fedora Badges 2023 revamp"?)
* Once charters are signed off, they should be pushed to main repo in GitLab
* Follow Ups & Action Items
- [ ] J.W.F to split out topics on discourse to centralise feedcentral
- [ ] JWF to follow up on epics on about whether they should live in the Websites & Apps sub-group or the Fedora Badges sub-group
- [x] Aoife to post a summary using #badges-team tag to discussion.fpo
- [ ] Sayan & Sandro to sync in the next couple weeks on automated badges
- [x] Marie to chair April's roundtable
### 2023-02-15
_Meeting chair_: Akashdeep Dhar
Attendees:
* Akashdeep Dhar
* Emma Kidney
* Bhavya Verma
* Michal Konecny
* David Fan
* Marie Nordin
* Jan Kuparinen
* Sandro (Penguinpee)
* Ida Delphine
* Lenka Segura
* Paul Power
Topics & notes:
* Expansion of scope
* From Fedora Badges to $(SOMENAME) Badges -
* To include other communities (Esp. downstream and sidestreams)
* Discussed between Justin Flory and Akashdeep Dhar (during the Fedora Council F2F Hackfest)
* Sandro
* Concerns about the implementation details
* Authorization, authentication
* We can let the idea linger around for longer
* Maybe come back to it when the revamp is done?
* How do we deal with the authentication across multiple account systems?
* Does an OpenSUSE contributor require a Fedora Project account too?
* How do we ensure uniqueness of users with accounts in different projects?
* Shaun
* Interested in the Badges system for the CentOS contributors participation
* Expansion in the scope to include CentOS contributors is welcome
* Rename is not required - Happy to use Fedora Badges as-is
* CentOS branding is required - Color palettes, Design language etc.
* Do they need a FAS account to be a part of this expanded ecosystem?
* Marie
* What kind of scope expansion are we looking for?
* Fedora Badges name should stay put - We're contributing to amount for it
* Expansion of the scope should take a backseat - Lets refine the refresh scope
* With the design language, we are accompanying other communities as much as we can
* Inconsistencies in design can lead to disagreements and inconsistencies in look and feel
* Akashdeep
* A lot of new users might feel left back just because Fedora Project users have lots
* Projects that we do not have a tie-in - we need not include those
* Voting for if we would want to use Discourse as our primary frontend
* https://discussion.fedoraproject.org/t/so-we-investigated-discourse-to-confirm-if-it-is-worthy-of-being-the-fedora-badges-frontend/46104
* Voting to end TODAY (i.e. 15 February 2023)
* Sandro
* What if Discourse goes bust?
* How difficult would it be to maintain both the standalone web frontend and Discourse frontend?
* The concerns about continuity (how the workflow would go on if this goes dark) versus the concerns around the data loss
* Marie
* Require context around the workflow that the design has to make use of in order to be able to be best compatible with the platform
* How should the new template and design should look like for them to be compatible with the new badges frontend (whichever it might be)?
* Elaborate representation of the team in DevConf.CZ
* Marie would like to contribute.
* Sandro would love to have more context about this as we go on.
* Finding a place to discuss our plans
* #action t0xic0der for the discussions fp.o. post around this
* Coming up with a charter for the project
* Questions to answer
* Scoping up what needs to be done?
* Who would be involved?
* Who would be affected?
* What timeline do we expect to have it delivered in?
* Design co-captains
* #action riecatnor and ekidney for drafting up a design-centric charter
* Technical co-captains
* #action t0xic0der and penguinpee for drafting up a technical-centric charter
* [Marie] Re: Outreachy design internship for may-august cohort.
* What changes would we need in the existing Badge template?
* Would we want to remove the padding (compatibility with Discourse) or make it stay (compatibility with the existing Tahrir web interface)?
* I am fine with either method- I just want to ensure that whatever the intern works on will be used in production.
* If badge design needs to be adjusted, we should look into getting this done in an automated fashion as to reduce workload in the design team. (Sandro)
* Open floor
* We should do something of a hackfest during the Flock
* A design-centred hackfest
* A technical-centred hackfest
* The CFP would be out soon so we would want to send in proposal
### 2023-01-18
_Meeting chair_: Ellen O'Carroll
Attendees:
* JWF/jflory7
* Akashdeep Dhar/t0xic0der
* Marie Nordin/riecatnor
* Ellen O'Carroll/eocarrol
* Joseph Walton-Rivers/webpigeon
* Emma Kidney/ekidney
* Bogomil Shopov/bogomil
* Lenka Segura/lsegura
* Sandro/Penguinpee/gu1lty
* Ida Delphine/idadel
* Bhavya Verma/bhavya-verma
Topics & notes:
* Team announcments & news:
* **ARC investigation completed by Akash, Lenka, Michal**. Looked into old code to see if we salvage in a rewrite. Old code used old frameworks without an active community maintaining them. No-go on salvaging. Proposed action is a total rewrite, which would mean new workflows/processes, inspired by the old system.
* https://fedora-arc.readthedocs.io/en/latest/badges/
* TL;DNR: https://discussion.fedoraproject.org/t/concluding-fedora-badges-arc-investigation/45609
* **Creative Freedom Summit is happening now, this week!** Promoting creative open source software, connect creatives, all in a fully FOSS virtual platform. Fedora Badges design process & history will get a spotlight there too.
* https://creativefreedomsummit.com/
* Jump in on Matrix, the chat and venue for the event: https://matrix.to/#/#creativefreedom:fedora.im
* **Discourse as a front-end?** A possible integration down the line. API seems possible to do this but probably not as the _primary_ front-end due to platform limitations in comparison to the old (i.e. current) Badges system.
* **Bringing in more folks.** Sandro is working on pulling in another person into the fold. He was a bit busy, but keep an eye out for another voice on the development chatter. (erolkeskin and ankitsinha)
* **Information hosting & platforms**: Planning and managing how and where we work.
* Synchronous messaging
* #fedora-badges Matrix room (https://matrix.to/#/#badges:fedoraproject.org)
* Video conferencing discussions (https://meet.jit.si/fedora-badges-community-roundtable)
* Asynchronous discussions
* #badges-team tag on Discussions fp.o. (https://discussion.fedoraproject.org/tag/badges-team)
* **Documentation**: Where should we keep track of information and decisions made for the future of Badges?
* We _have_ a docs page but it is pretty quiet/empty…
* https://docs.fedoraproject.org/en-US/badges/
* https://pagure.io/fedora-badges/docs
* **Sub-teams**: Development & Design, how will it work? Co-captain introduction.
*
* **Tickets** (not yet ticket-driven, but we will work to get there next time): Do any Badgers need a review or discussion about an ongoing ticket?
* 3-D printing assets: Where should these go? The repo is big. @Sandro to start a Discussion topic about what to do about them.
* **Technologies**: Looking for more feedback on proposed tools and tech:
* Proposed technologies can be found here https://fedora-arc.readthedocs.io/en/latest/badges/prop_rewrite_technologies.html
* Please share your feedback here https://discussion.fedoraproject.org/t/concluding-fedora-badges-arc-investigation/45609
* Q: "Will rewriting it with the new version of fedora-messaging going to solve the problems we are having with fedbadges ? I really don't think so cause some of the problems are not related to old tools but rather they are related to whole architecture of fedbadges."
* **Q: Deadline for feedback?** Next roundtable meeting in February. (15 Feb)
* **Q: What is missing from the current feedback thread? What makes us confident in locking in the tech stack?** Review the ARC documentation report and proposed stack for the rewrite (link above). Add a comment to the conclusion topic on Fedora Discussion. Do you understand the proposed tools? Do you have questions? Does something seem unaccounted for?
* By the next meeting, we will conclude the tech stack discussion and then take the first steps into development.
* In the meantime, try using some of the proposed tools, check out or build a demo apps, and spend time to learn the tools.