#621 Badge request for LinuxCon Beijing 2018 attendee [easyfix]
Closed: pushed 2 years ago Opened 2 years ago by zsun.

Badge description (like "You added a co-maintainer to a package. BFF!"):
"You joined Fedora related events in LinuxCon Beijing 2018"

Help the badges team understand what this idea is all about. If this badge is awarded for certain kinds of activities:
1) What are those activities?
During LinuxCon Beijing 2018 time slot (June 25 – 27, 2018), we will have a booth with Red Hat and possible a small meetup(TBD). In order to encourage the participants, we want to have this badge.

2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)
It can be anyone with a FAS who joined us in a Fedora related event during that time.

3) Why are they doing them (is this a means to a different end?)
Encourage more participants to Fedora.

4) When do they do them (every day? once a year?)

5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)

Lastly, do you have any ideas for artwork concepts?
Just reuse the design last year and change the year number should be fine https://pagure.io/fedora-badges/issue/541

@riecatnor @mleonova can we get this labeled with an easy fix? This conference is coming up in late June.

I'll be happy to do the badge push when it is ready.

Metadata Update from @bex:
- Custom field artwork adjusted to None
- Custom field concept_review_passed adjusted to None

2 years ago

Metadata Update from @mleonova:
- Issue tagged with: artwork-easy, artwork-needed, event

2 years ago

Here you go!

So I believe the next step is waiting for this to be pushed out.

Metadata Update from @mleonova:
- Issue untagged with: artwork-needed
- Issue tagged with: artwork-approved, ready to push

2 years ago

@bex please push, since you so kindly offered =)

Metadata Update from @mleonova:
- Issue assigned to mleonova

2 years ago

This badge has been pushed. I can provide a QR code in Beijing.

Metadata Update from @bex:
- Issue close_status updated to: pushed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Attachments 1
Attached 2 years ago View Comment