Hi folks,
mleonova and I met today and did some ticket triage. It was only us two
who showed up - should we try changing the meeting time so more folks
can make it? Is the time a barrier?
Anyhow here's the meetbot minutes:
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...
Here's a quick summary copypasta from meetbot - I'm trying to make
better use of meetbot so that the meetbot minutes are more useful - let
me know if it's readable or if there's anything we need to tweak.
~m
1. *open floor* (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:07:41)
1.
https://fedorahosted.org/council/ticket/54 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:14:42)
2. /ACTION/: - mleonova re ticket 423, due next week - will revert
text, new flag design looks great, prolly no bleed required
(mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:15:40)
3. FAD for design proposed to council, waiting for their funding
decision (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:16:16)
2. *ticket triage - stalled tickets* (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:17:03)
1.
https://fedorahosted.org/design-team/ticket/401 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:17:56)
2. this is for updating to cheat cube to dnf - it's closed so we
need to tweak it to not show up in stalled tickets (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:18:25)
3. *aging tickets* (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:20:03)
1.
https://fedorahosted.org/design-team/ticket/199 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:20:40)
2. 199 is for ask.fpo usability (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:20:50)
3. anuradhaw updated the ask.fpo theme (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:21:55)
4. /ACTION/: mizmo to contact fedora admin to update ask.fpo skin
in stg (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:22:10)
5.
https://fedorahosted.org/design-team/ticket/279 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:22:36)
6. 279 = design for this week in fedora (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:22:47)
7. 279 looks like ryan grabbed the ticket but no updates for 2
months, will query in ticket for update (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:23:23)
8.
https://fedorahosted.org/design-team/ticket/367 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:23:55)
9. 367 is the fedora security team logo (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:24:06)
10. it looks like the requestors asked for a change 8 weeks ago, we
queried yogi for a response 4 weeks ago, no response (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:25:24)
11. we're opening 367 back up since we haven't had a response from
yogi in 4 weeks. he has done the bulk of the work here, just one
more tiny tweak and we can close this one out, it's been open
for quite some time so it would be nice to finish it off. (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:26:59)
12. /ACTION/: mleonova to finish off 367 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:30:09)
13.
https://fedorahosted.org/design-team/ticket/374 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:30:17)
14. 374 is the fedmenu UX feedback ticket - pushing it off another
few months until fedora-hubs is up (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:30:33)
15.
https://fedorahosted.org/design-team/ticket/402 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:31:00)
16. 402 - scaling down hackergotchi in fedora planet css (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:31:07)
17. 402 this one is still open but i vaguely recall from reading his
status report that ryanlerch may have actually fixed it. i'll
query him in the ticket and we can close it if he confirms
(mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:31:37)
18.
https://fedorahosted.org/design-team/ticket/422 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:32:18)
19. 422 Update digital promotional banners (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:32:36)
20. 422 it looks like inkscaper has been researching this one and
putting some things together, so i think i'll just query him for
a status update bc it has been 3 weeks (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:37:04)
4. *untriaged tickets* (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:39:00)
1.
https://fedorahosted.org/design-team/ticket/422 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:39:14)
2. 422 is actually triaged, just quickly adding the 'triaged'
keyword (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:39:25)
3.
https://fedorahosted.org/design-team/ticket/423 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:40:27)
4. 423 is actually triaged, just quickly adding the 'triaged'
keyword (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:40:36)
5.
https://fedorahosted.org/design-team/ticket/424 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:41:33)
6. 424 is actually triaged, just quickly adding the 'triaged'
keyword (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:41:44)
7. 424 T-shirts for contributors (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:42:19)
8.
https://fedorahosted.org/design-team/ticket/427 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:44:50)
9. 427 is Fedora specific mailman3/hyperkitty favicon (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:44:59)
10. mizmo made a favicon for hyperkitty (upstream) to match the
pagure icon ryanlerch did, she made it yesterday or the day
before because she wanted a nice icon to use for hyperkitty in
fedora hubs (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:45:47)
11. /ACTION/: mizmo to post hyperkitty favicon design to ticket 427
(mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:45:59)
12.
https://fedorahosted.org/design-team/attachment/ticket/427/hyperkitty_fav...
(mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:49:01)
13. 427 new upstream hyperkitty logo design
https://fedorahosted.org/design-team/attachment/ticket/427/hyperkitty_lar...
(mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:49:40)
14.
https://fedorahosted.org/design-team/ticket/428 (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:50:16)
15. 428 logo for South East Asian Translation Challenge (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:50:26)
16. 428 - asked in ticket if gnokii is intending to work on 428
(mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:53:21)
5. *logo usage guidelines / branding guidelines* (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:54:49)
1. one thing i forgot to file, it's on my personal todo but i
haven't opened a ticket for it, is to update the logo guidelines
(mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:55:12)
2. we've changed the fonts we use lately, so the guidelines need to
be updated to reflect that (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:55:25)
3. /ACTION/: to open a ticket and assign to self about updating
fonts in the branding guidelines (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:55:47)
4. we're replacing comfortaa with montserrat as a headline font,
and replacing cantarell with open sans for the body font (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:56:34)
5. we still use comfortaa in sublogos (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:56:45)
6. 429 is the branding guidelines update ticket (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:59:16)
6. *open floor* (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
12:59:19)
1. mleonova is going to do a badges workshop at an open house in
april (mizmo
<
https://meetbot.fedoraproject.org/fedora-design/2016-03-24/design-team.20...;,
13:01:00)
Action items, by person
1. mizmo
1. mizmo to contact fedora admin to update ask.fpo skin in stg
2. mizmo to post hyperkitty favicon design to ticket 427
2. mleonova
1. - mleonova re ticket 423, due next week - will revert text, new
flag design looks great, prolly no bleed required
2. mleonova to finish off 367