The Cloud FAD is happening now, from June 7 -
8. The Cloud Working Group will be making decisions, tackling
tickets, and writing code to help with topics like automated
testing, documentation, and increasing the public cloud provider
footprint.(jflory7_,
16:07:38)
=== "Fedora Design Team lead Máirín Duffy wins
O’Reilly Open Source Award" ===(jflory7_,
16:07:46)
Big congrats to mizmo for winning big at the
O'Reilly Open Source Conference (OSCON) this year! Check out the
article to learn more about the award.(jflory7_,
16:08:02)
=== Fedora 24 releases June 14 ===(jflory7_,
16:08:09)
Just in case you forgot, Fedora 24 drops in
another seven days!(jflory7_,
16:08:18)
Action items from last meeting(jflory7_, 16:10:41)
How This Works: We look at past #action items
from the last meeting for quick follow-up. If a task is completed,
we move on to the next one. If it isn't, we get an update and
re-action it if needed. If no status, we'll try to get a quick
update and move forward.(jflory7_,
16:11:00)
=== decause Follow up with tatica and diversity
team about LimeSurvey availability ===(jflory7_,
16:11:08)
ACTION: decause
Follow up with tatica and diversity team about LimeSurvey
availability(jflory7_,
16:11:52)
=== [COMPLETE] jflory7 Open discussion on the
mailing list about Ticket #71 and centralizing Ambassador resources
(to get brainstorming going) ===(jflory7_,
16:12:02)
=== [COMPLETE] jflory7 Bring the CommOps vFAD
ticket back up to the table, make a wiki page, do the metadata
planning-esque type of tasks ===(jflory7_,
16:12:18)
=== decause Work with jzb to organize the
release party in Raleigh, NC area ===(jflory7_,
16:12:34)
ACTION: decause Work
with jzb to organize the release party in Raleigh, NC area(jflory7_,
16:12:42)
=== decause nail down Flock arrangements, add
them to Fedocal ===(jflory7_,
16:12:50)
ACTION: decause nail
down Flock arrangements, add them to Fedocal(jflory7_,
16:12:56)
=== decause / spot look into booking conference
rooms in the Tower (Fedora on 9 if it is available) ===(jflory7_,
16:13:06)
ACTION: decause /
spot look into booking conference rooms in the Tower (Fedora on 9 if
it is available)(jflory7_,
16:13:14)
=== [COMPLETE] decause / jflory7 Get article
source from maxamillion, decause will make edits, clear with
maxamillion, then push ===(jflory7,
16:13:56)
=== skamath File a ticket in the Fedora Badges
Trac for a CommOps on-boarding badge that is dependent on other
badges and/or hooks to be awarded; ask in #fedora-commops if
assistance is needed. ===(jflory7,
16:14:15)
ACTION: skamath File
a ticket in the Fedora Badges Trac for a CommOps on-boarding badge
that is dependent on other badges and/or hooks to be awarded; ask in
#fedora-commops if assistance is needed(jflory7,
16:14:40)
=== [COMPLETE] jflory7 Reach out to the Design
Team about centralizing Design / Marketing resources for Fedora and
get their thoughts about the discussions from today's meeting on
Ticket #71 ===(jflory7,
16:14:45)
=== [COMPLETE] jflory7 Follow up with decause
and maxamillion to see if where the original content is and if we
can pull the source ===(jflory7,
16:15:07)
IDEA: CommOps-related
git repos and Etherpads could be organized more effectively for
keeping tabs on information from IRC discussions, hack sessions, and
meeting discussions(jflory7,
16:20:59)
IDEA: Wiki could take
better advantage of categorization of pages(jflory7,
16:21:19)
IDEA: Similar to the
Infra team, have a monthly check-in for existing members of CommOps
to see if they are still interested in contributing (see: CommOps
wiki page members)(jflory7,
16:22:13)
IDEA: Talk pages on
wiki can be useful asynchronous discussion and having a record of
logged actions for important pages(jflory7,
16:22:32)
ACTION: jflory7 Write
a first draft of objectives / goals for the vFAD on wiki page, share
with commops, get feedback, look at finding open dates (cc:
decause)(jflory7,
16:24:58)
CommOps Team Onboarding Steps > Badges Team
Missing Badges > Hubs Team Badges Tracks and Widgets(jflory7,
16:26:18)
AGREED: skamath will
file a ticket for the CommOps on-boarding badge in the Badges Trac,
will drop a line in IRC / mailing list about ticket, we will revisit
then to work on how we can help the Design Team move forward on this
(Badge YAML, sysadmin side, maybe artwork too depending)(jflory7,
16:32:10)
IDEA: Design Team
strongly prefers being contacted ahead of time by Ambassadors or
others for artwork assets - maybe better aim is to help define the
process better for Ambassadors for how to get artwork and printed /
final products for events(jflory7,
16:37:36)
IDEA: Part of workflow
involves vendor interaction (not really a Design Team
responsibility), but Design Team should be in the loop.(jflory7,
16:43:30)
IDEA: Different
Ambassadors / regions approach this differently - more organization
around that would be useful and helpful(jflory7,
16:43:49)
IDEA: Centralizing the
vendors that Ambassadors use would also be extremely helpful for the
Design Team and help make their life easier(jflory7,
16:44:17)
IDEA: Design Team Trac
tickets have templates for filling out, but not all fields are
always filled - this slows down the process and makes it harder for
the Design Team to do their work(jflory7,
16:46:19)
IDEA: Sometimes an
Ambassador will file a ticket for a random swag idea (without
funding or prior discussion by others in region), so it is a
difficult situation to resolve for the Design Team(jflory7,
16:47:03)
ACTION: jflory7 Post
to the CommOps mailing list about Ticket #71 about creating the
Ambassador guidelines for artwork assets based on m izmo's
feedback(jflory7,
16:51:59)
How This Works: There is a quick blast of
information about what was published in the past week with some
metrics, followed by posts that are being drafted. After the
information blast, the floor is opened for any Community
Blog-related discussion. Here we go!(jflory7,
16:58:41)
decause Follow up with tatica and diversity team about LimeSurvey availability
decause Work with jzb to organize the release party in Raleigh, NC area
decause nail down Flock arrangements, add them to Fedocal
decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available)
skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed
jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause)
jflory7 Post to the CommOps mailing list about Ticket #71 about creating the Ambassador guidelines for artwork assets based on m izmo's feedback
commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
decause ship "final" version for review by EoB thursday of F24 GA Release Announcement
jflory7 Create a Fedocal event for the hack session, 2016-06-08 22:00 UTC
Action items, by person
commops
skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed
jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause)
commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
decause
decause Follow up with tatica and diversity team about LimeSurvey availability
decause Work with jzb to organize the release party in Raleigh, NC area
decause nail down Flock arrangements, add them to Fedocal
decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available)
jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause)
decause ship "final" version for review by EoB thursday of F24 GA Release Announcement
jflory7
jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause)
jflory7 Post to the CommOps mailing list about Ticket #71 about creating the Ambassador guidelines for artwork assets based on m izmo's feedback
jflory7 Create a Fedocal event for the hack session, 2016-06-08 22:00 UTC
skamath
skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed