DevConf.cz 2016 Speaker #421

New issue

Closed

opened 2015-12-04 15:40:32 +00:00 by eischmann · 15 comments

eischmann commented 2015-12-04 15:40:32 +00:00

Copy link

What the badge should be granted for: for delivering a talk at DevConf.cz 2016, we'll give it to speakers manually, that's why I want to be an admin of this badge.
Badge description (like "You added a co-maintainer to a package. BFF!"): You delivered a talk at DevConf.cz 2016.

We can use the design from the last year, just change the year: ​https://fedorahosted.org/fedora-badges/ticket/335

What the badge should be granted for: for delivering a talk at DevConf.cz 2016, we'll give it to speakers manually, that's why I want to be an admin of this badge. Badge description (like "You added a co-maintainer to a package. BFF!"): You delivered a talk at DevConf.cz 2016. We can use the design from the last year, just change the year: ​https://fedorahosted.org/fedora-badges/ticket/335

mleonova commented 2015-12-07 13:56:16 +00:00

Copy link

attachment
dev-conf-presenter-2016_outl.svg

attachment [dev-conf-presenter-2016_outl.svg](//issue/raw/files/f9d591b1e0602d2897b6ecc889bcedb5a1324fcc000ea05696b3e6802b1976fe-dev-conf-presenter-2016_outl.svg)

mleonova commented 2015-12-07 13:56:16 +00:00

Copy link

attachment
dev-conf-presenter-2016_outl.svg

attachment [dev-conf-presenter-2016_outl.svg](https://pagure.io/Fedora-Badges/issue/raw/files/f9d591b1e0602d2897b6ecc889bcedb5a1324fcc000ea05696b3e6802b1976fe-dev-conf-presenter-2016_outl.svg)

mleonova commented 2015-12-07 13:56:26 +00:00

Copy link

attachment

attachment [](//issue/raw/files/6924df6ff2065b2d969dd208bf1034fbf3602bb546106637c0d681e3ac1bb74b-dev-conf-presenter-2016.png)

mleonova commented 2015-12-07 13:56:26 +00:00

Copy link

attachment

attachment [](https://pagure.io/Fedora-Badges/issue/raw/files/6924df6ff2065b2d969dd208bf1034fbf3602bb546106637c0d681e3ac1bb74b-dev-conf-presenter-2016.png)

mleonova commented 2015-12-07 13:58:39 +00:00

Copy link

Comment same as here: [https://fedorahosted.org/fedora-badges/ticket/420#comment:2]
Glowing effect is inconsistent in my Inkscape for some reason.

Image(http://i.imgur.com/sajpdIl.png)

Comment same as here: [https://fedorahosted.org/fedora-badges/ticket/420#comment:2] Glowing effect is inconsistent in my Inkscape for some reason. [[Image(http://i.imgur.com/sajpdIl.png)]]

mleonova commented 2015-12-07 13:58:39 +00:00

Copy link

Comment same as here: [https://fedorahosted.org/fedora-badges/ticket/420#comment:2]
Glowing effect is inconsistent in my Inkscape for some reason.

Image(http://i.imgur.com/sajpdIl.png)

Comment same as here: [https://fedorahosted.org/fedora-badges/ticket/420#comment:2] Glowing effect is inconsistent in my Inkscape for some reason. [[Image(http://i.imgur.com/sajpdIl.png)]]

riecatnor commented 2015-12-18 00:34:14 +00:00

Copy link

attachment
dev-conf-presenter-2016.svg

attachment [dev-conf-presenter-2016.svg](//issue/raw/files/b3f8c0144a21898218a80a47e7343f8d4920ccb3326a786e9bef773e8c901d94-dev-conf-presenter-2016.svg)

riecatnor commented 2015-12-18 00:34:14 +00:00

Copy link

attachment
dev-conf-presenter-2016.svg

attachment [dev-conf-presenter-2016.svg](https://pagure.io/Fedora-Badges/issue/raw/files/b3f8c0144a21898218a80a47e7343f8d4920ccb3326a786e9bef773e8c901d94-dev-conf-presenter-2016.svg)

riecatnor commented 2015-12-18 00:34:27 +00:00

Copy link

attachment

attachment [](//issue/raw/files/8b7442491a20d59bca63c518d8d304a166ee7dda18957f262c01245d87f2326e-dev-conf-presenter-2016.2.png)

riecatnor commented 2015-12-18 00:34:27 +00:00

Copy link

attachment

attachment [](https://pagure.io/Fedora-Badges/issue/raw/files/8b7442491a20d59bca63c518d8d304a166ee7dda18957f262c01245d87f2326e-dev-conf-presenter-2016.2.png)

riecatnor commented 2015-12-18 00:36:26 +00:00

Copy link

Updated the file to fix the lighting and the typeface for the year.

Image(dev-conf-presenter-2016.2.png)

Updated the file to fix the lighting and the typeface for the year. [[Image(dev-conf-presenter-2016.2.png)]]

riecatnor commented 2015-12-18 00:36:26 +00:00

Copy link

Updated the file to fix the lighting and the typeface for the year.

Image(dev-conf-presenter-2016.2.png)

Updated the file to fix the lighting and the typeface for the year. [[Image(dev-conf-presenter-2016.2.png)]]

ralph commented 2016-01-05 17:06:41 +00:00

Copy link

Thanks all! The badge has been created here: https://badges.fedoraproject.org/badge/devconf-2016-speaker

eischmann's account has access to create QR codes and to award it directly. If I should authorize any other accounts, let me know.

Thanks all! The badge has been created here: https://badges.fedoraproject.org/badge/devconf-2016-speaker eischmann's account has access to create QR codes and to award it directly. If I should authorize any other accounts, let me know.

ralph commented 2016-01-05 17:06:41 +00:00

Copy link

Thanks all! The badge has been created here: https://badges.fedoraproject.org/badge/devconf-2016-speaker

eischmann's account has access to create QR codes and to award it directly. If I should authorize any other accounts, let me know.

Thanks all! The badge has been created here: https://badges.fedoraproject.org/badge/devconf-2016-speaker eischmann's account has access to create QR codes and to award it directly. If I should authorize any other accounts, let me know.

eischmann commented 2017-03-01 19:36:23 +00:00

Author

Copy link

Metadata Update from @eischmann:

• Issue assigned to mleonova

**Metadata Update from @eischmann**: - Issue assigned to mleonova

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

staging

pack

rules-rework

add/badges-resources

pushing

No results found.

Labels

Clear labels   

AW: approved

artwork approved

  

AW: needed

artwork needed

  

AW: needs improvement

artwork needs improvement

  

C: community

  

C: content

  

C: development

  

C: event

  

Closed As

declined

Closed with the reason of declined

  

Closed As

duplicate

Closed with the reason of duplicate

  

Closed As

fixed

Closed with the reason of fixed

  

Closed As

needs info

Closed with the reason of needs info

  

Closed As

not yet possible

Closed with the reason of not yet possible

  

Closed As

pushed

Closed with the reason of pushed

  

Closed As

stale

Closed with the reason of stale

  

C: miscellaneous

  

C: quality

  

D: easy

  

D: hard

  

D: intermediate

  

good first issue

Good for newcomers (if you want to get involved, try working on one of these!)

  

outreachy-2023

  

Priority

critical (next week)

Priority of critical (next week)

  

Priority

minor (3-4 weeks)

Priority of minor (3-4 weeks)

  

Priority

no deadline

Priority of no deadline

  

Priority

normal (1-2 weeks)

Priority of normal (1-2 weeks)

  

S: blocked

Progress blocked by another task or issue

  

S: needs rules

Waits to get rules.yml

  

S: ready to push

Ticket needs sysadmin to push a badge

  

S: request for resources

Needs artwork resources to make progress on this ticket (e.g. getting logos or other source material)

  

S: review

Tagged for follow-up review with the next triage

  

T: badge request

  

T: bug

  

T: docs

Adding or updating documentation

  

T: feature request

List the feature that should be added to tahrir.

  

Backlog Status

Needs Review

Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  

Backlog Status

Ready

Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  

chore

Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  

documentation

Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  

points

01

A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  

points

02

This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  

points

03

Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  

points

05

A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  

points

08

Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  

points

13

Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  

Priority

High

This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  

Priority

Low

This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  

Priority

Medium

This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  

Sprint Status

Blocked

Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  

Sprint Status

Done

Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  

Sprint Status

In Progress

Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  

Sprint Status

Review

Work items that are complete but need review, testing, or approval before being marked as done.

  

Sprint Status

To Do

Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  

Technical Debt

Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  

Work Item

Bug

Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  

Work Item

Epic

Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  

Work Item

Spike

Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  

Work Item

Task

Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  

Work Item

User Story

User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels

AW: approved

AW: needed

AW: needs improvement

C: community

C: content

C: development

C: event

Closed As

declined

Closed As

duplicate

Closed As

fixed

Closed As

needs info

Closed As

not yet possible

Closed As

pushed

Closed As

stale

C: miscellaneous

C: quality

D: easy

D: hard

D: intermediate

good first issue

outreachy-2023

Priority

critical (next week)

Priority

minor (3-4 weeks)

Priority

no deadline

Priority

normal (1-2 weeks)

S: blocked

S: needs rules

S: ready to push

S: request for resources

S: review

T: badge request

T: bug

T: docs

T: feature request

Backlog Status

Needs Review

Backlog Status

Ready

chore

documentation

points

01

points

02

points

03

points

05

points

08

points

13

Priority

High

Priority

Low

Priority

Medium

Sprint Status

Blocked

Sprint Status

Done

Sprint Status

In Progress

Sprint Status

Review

Sprint Status

To Do

Technical Debt

Work Item

Bug

Work Item

Epic

Work Item

Spike

Work Item

Task

Work Item

User Story

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

4 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

apps/badges-assets#421

No description provided.