I am open to creative ideas for a fun and silly badge name.

Badge description

You submitted a Red Hat BEAR request for a Fedora event and got approved! Thanks for helping out at a Fedora event.

How is the badge earned?

The badge is earned when a Fedora contributor who does not work at Red Hat submits a Business Entertainment and Amenity Review (BEAR) request and is approved by Red Hat Legal. Once they receive approval from Red Hat Legal, the Fedora Community Architect manually awards the badge and closes the GitLab issue.

Who earns the badge?

Anyone who attends an event on behalf of the Fedora Project, receives financial sponsorship to do so, and is not employed by Red Hat. Typically, these are people who are either Ambassadors or Advocates.

Why do they do this?

This is a required compliance step that must happen any time someone who does not work at Red Hat is funded by Red Hat for travel, lodging, meals, or any other kind of event-related expenses. It is not always event expenses though, which is why I propose this badge as a Miscellaneous category badge, where we have other badges related to Fedora Legal too.

I want to bring more awareness to the BEAR process and also incentivize people to complete BEAR tickets fully and accurately. A badge seems like an effective way of doing so. It does take effort to fill these tickets out and there is little to no benefit of doing them for the person who completes them. Yet we have to do it, because the law is the law.

When do they do it?

Any time someone requests financial sponsorship to attend an event. This has to happen for each event. So, someone might do this activity only once, but others might do this three times in a year, depending.

There is a possibility to make this a series, although I am wary that this is a series that biases toward people who can travel and attend events. This is not always inclusive, so maybe a one-off badge is better.

How do they do it?

1. Open a new GitLab issue using the issue template: https://gitlab.com/redhat/ospo/bear
2. Fedora Community Architect processes the issue and takes the steps to submit the data to Red Hat Legal.
3. Red Hat Legal reviews and provides a decision.
4. The Fedora Community Architect communicates the decision back to the reporter.
5. If approved, the reporter is now authorized to spend and get reimbursed by Red Hat up to the approved amounts.

Artwork concepts?

One of our four Fedora mascots is a panda bear, so I think this badge needs to be a panda badge.

The function behind this badge is a legal and compliance function. In a way, it is sort of like a background check, but not really. Someone does provide personal data about their employer, where they work, and if they have any business connections to Red Hat. So, something around filling a form/document and submitting it for approval is the vibe.

Even though this badge is something tied closely to Red Hat… please do not use any hats for the panda in this badge. :)

I am open to creative ideas and artistic directions from the designer.