#593 DevConf.cz 2018 Speaker
Closed: no longer relevant 7 years ago Opened 7 years ago by skamath.

Badge description (like "You added a co-maintainer to a package. BFF!"):

Devconf Speaker 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?

Speaking at Devconf '18

2) Who is doing them (are they packagers? translators? newcomers? veterans?
users? sponsors?)
-
*

3) Why are they doing them (is this a means to a different end?)

They are awesome! \o/

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

Every year, once in 2018

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

Lastly, do you have any ideas for artwork concepts?

Attaching the media files here for tracking :dancer:

dev-conf-presenter-2018.png
dev-conf-presenter-2018.svg


The artwork is done and is now a PR :)

I am not sure, should we do a speaker badge? I don't think we do a speaker
badge for other events.

On Mon, Jan 29, 2018 at 4:05 AM, Sachin S Kamath pagure@pagure.io wrote:

skamath added a new comment to an issue you are following:
The artwork is done and is now a PR :)

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-badges/issue/593

-1 to making a speaker badge. Last year we had 111 speaker badges and 128 regular badges. This seems about like having two different badges for the same thing. I think we should only have a separate speaker badge if it was some instance where most attendees are not also speakers.

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

7 years ago

-1 to making a speaker badge. Last year we had 111 speaker badges and 128 regular badges. This seems about like having two different badges for the same thing. I think we should only have a separate speaker badge if it was some instance where most attendees are not also speakers.

Makes sense to me too. Does not make sense to have separate badges. I guess we had the discussion earlier also about this. We should just have a single badge for the event unless required.

I wonder how the badges were pushed without being approved from the design team? @skamath

In that case we should delete the FLOCK speaker badges ;)

@sayan I was sitting right next to @skamath when this was created; I guess it slipped my mind that we agreed not to do those?

@sayanchowdhury Never said they were pushed. It is a PR now and feel free to close it :)

I don't think I have push access

Metadata Update from @skamath:
- Issue close_status updated to: no longer relevant
- Issue status updated to: Closed (was: Open)

7 years ago

@skamath Hmm, weird. I saw the commits were already there, I noticed it while pushing another badge.

@mleonova @nb I don't think there is issue with having the conference badge. But I would say to have a common badge with title "Devconf.cz 2018" with the description as "You have attended Devconf.cz 2018".

(The attendee badge was live during devconf, by the way...)

I really like to measure everything with the same meter. There are all kinds of other speaker badges, so why not devconf one as well? Or do you plan to remove the past speaker badges that people got? These are the only two fair options that I can see...

@skamath Hmm, weird. I saw the commits were already there, I noticed it while pushing another badge.

@sayanchowdhury, I am pretty sure you saw the Devconf attendee badge commit and not the speaker badge. If you are wondering about it, it was pretty much a last-minute push and we had to have the badge since it was the last day of Devconf and it was @mleonova made the changes to the badge. I sent a PR on her behalf and @jflory7 merged it.

I edited the Devconf speaker badge later and sent a PR for it thinking it would be there because it has always been there. Speaker badge was never pushed :)

@mleonova @nb I don't think there is issue with having the conference badge. But I would say to have a common badge with title "Devconf.cz 2018" with the description as "You have attended Devconf.cz 2018".

I would like answers to my comments. Why do we have speaker badges for everything everywhere except this specific event? Is this large decision taken by the community to stop doing all these speaker badges?

Why do we have speaker badges for everything everywhere

@rhea no, not anymore - for reasons mentioned above. If you look at badges index, you'll see that most of them are from 2016 at the latest.

If I remember correctly the last one created was just a few months ago, November or December 2017, hence why the surprise.

And I honestly don't see any reasons mentioned above, just "he said she said." There is also difference between not creating them, and not pushing created ones. The work into creating this already went in and it's here.

We are not pushing this badge. Most people who are attendees of this event are also speakers. Please see above. People should consult with badges admins before creating art, because just creating art doesn't mean that the badge will be created/pushed.

@rhea which speaker badge was created a few months ago? I would like to know. Although we still aren't approving this badge.

Ok I found it, latinoware 2017. Still, we are not making speaker badges in general anymore. And that goes for that event in the future also. Look at how many people are speakers and how many are attendees. We shouldn't have a separate badge unless there is a clear need, which there isn't in either case. This ticket is still closed wontfix.

Okay, thanks for the info

Log in to comment on this ticket.

Metadata
Attachments 2