#518 FOSDEM 2017 Attendee
Closed 3 years ago Opened 3 years ago by jflory7.

== Badge metadata ==

  • Name: FOSDEM 2017 Attendee
  • Description: You visited the Fedora community stand at FOSDEM 2017!

== What is it? ==

This is the annual badge for the FOSDEM conference held in Brussels, Belgium each year. Normally, we have a badge for attendees to scan and collect during the conference, and this is one of our most highly collected event badges (last year's conference gaining 78 badge hunters). However, I think eischmann normally filed the tickets, but we missed doing that this year since he isn't attending.

The conference is tomorrow and most of us are traveling today/tomorrow, so I'm going to try to whip up something quick and get it pushed before the conference, so we have time to figure out details when we get there. I have other Ambassadors / contributors CC'd to this ticket.

== Ticket review ==

I'm going to complete this badge tonight and push it out, but I'm going to keep it open until we get a sign-off from the Design Team members because I don't want to push a badge without getting some kind of approval from the folks running the show. We can always change the PNG on the site later, but I'll get something up tonight so we have something to work with tomorrow.


== Proposed artwork attached ==

Badge artwork added to the ticket. I also [https://fedorahosted.org/fedora-badges/attachment/ticket/518/fosdem-attendee-2017.stl generated an STL] that we could use, should we find a 3D printer, to try getting hard copies of the badge to make.

== Note for the Design Team ==

For reference, all of the text in the badge seemed to be a vector, so I just deleted the '6' and replaced it with a textbox and a '7'. This isn't the first time where I've tried interacting with a badge that had all of its objects (including text) as some sort of vector object, so I am really curious as to why this is, and what I could study a little more to try to one-up my Inkscape skills. I don't know if this makes any sense to a Design Team member, but if it does, I'd love a clarification!

In either case, it would be nice if someone could just check the file and make sure it's done properly since this a badge that has a very high probability of being reused as-is for next year too.

== Proposed artwork attached ==

Badge artwork added to the ticket. I also [https://fedorahosted.org/fedora-badges/attachment/ticket/518/fosdem-attendee-2017.stl generated an STL] that we could use, should we find a 3D printer, to try getting hard copies of the badge to make.

== Note for the Design Team ==

For reference, all of the text in the badge seemed to be a vector, so I just deleted the '6' and replaced it with a textbox and a '7'. This isn't the first time where I've tried interacting with a badge that had all of its objects (including text) as some sort of vector object, so I am really curious as to why this is, and what I could study a little more to try to one-up my Inkscape skills. I don't know if this makes any sense to a Design Team member, but if it does, I'd love a clarification!

In either case, it would be nice if someone could just check the file and make sure it's done properly since this a badge that has a very high probability of being reused as-is for next year too.

= Badge pushed =

= Ticket open, pending feedback from Design Team =

= Badge pushed =

= Ticket open, pending feedback from Design Team =

Looks good to me.

Replying to [comment:2 jflory7]:

= Badge pushed =

= Ticket open, pending feedback from Design Team =

Looks good to me.

Replying to [comment:2 jflory7]:

= Badge pushed =

= Ticket open, pending feedback from Design Team =

Metadata Update from @jflory7:
- Issue assigned to jflory7
- Issue tagged with: fosdem

3 years ago

Metadata Update from @mleonova:
- Custom field concept_review_passed adjusted to on (was: 1)
- Custom field has_description adjusted to on (was: 1)
- Custom field has_name adjusted to on (was: 1)
- Custom field needs_manual_award adjusted to on (was: 1)
- Custom field triaged adjusted to on (was: 1)
- Issue close_status updated to: None
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata
Attachments 2