ACTION: commops New
members, make sure you introduce yourself on the CommOps mailing
list [ https://fedoraproject.org/wiki/CommOps/Join ](jflory7,
16:31:58)
Sachin S. Kamath; UTC +5.30; CommOps, Metrics,
GSoC, Join, *(skamath,
16:32:24)
Justin W. Flory; UTC-4; CommOps, Magazine,
Marketing, Diversity Team, Ambassadors, sysadmin-badges, and
more(jflory7,
16:32:43)
Dhanesh B. Sabane, UTC+5:30, CommOps,
Marketing, Python, Packaging(dhanesh95,
16:32:43)
Alberto Rodriguez;
UTC-5;Stats,Metrics,R,Python,storytelling and more(bt0,
16:33:09)
This blog post goes a little deeper into some
of the tooling behind making Fedora more modular in its composition.
Read more in nardasev's breakdown of Factory 2.0.(jflory7,
16:39:50)
The Fedora 25 Supplemental Wallpapers were
selected this week. You can see what will be included in the
upcoming release of Fedora 25 in this post.(jflory7,
16:40:43)
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:42:50)
=== skamath Follow up with Infrastructure team
on fas=>bz email lookup rules and whether a fix can be made to
gracefully handle failed lookups ===(jflory7,
16:42:59)
=== [COMPLETE] jflory7 File ticket for looking
into centralizing / making more clear what a member of Council or
FESCo does, what their responsibilities are, and centralize the info
in a wiki page or CommBlog article ===(jflory7,
16:45:14)
=== [COMPLETE] jflory7 Reach out to skamath
about Infrastructure / Bugzilla+FAS lookup rules ===(jflory7,
16:45:23)
=== jflory7 Begin drafting a Community Blog
post for Fedora Appreciation Day ===(jflory7,
16:45:29)
Holding off on this until a date will be
selected(jflory7,
16:45:39)
=== [COMPLETE] jflory7 Post to the mailing list
about selecting a new sub-project to work with on the on-boarding
process ===(jflory7,
16:45:51)
Discussed during meetings, have selected
Marketing + G11n(jflory7,
16:45:51)
=== jflory7 Open up discussion about Fedora
Appreciation Day date on the mailing list ===(jflory7,
16:45:57)
ACTION: jflory7 Open
up discussion about Fedora Appreciation Day date on the mailing
list(jflory7,
16:46:03)
=== [INCOMPLETE] jflory7 Take the discussion
points from today's meeting, lay out the earlier problems, expand on
solutions, and try to offer mock implementations in the Marketing
ticket ===(jflory7,
16:46:17)
ACTION: jflory7 Take
the discussion points from today's meeting, lay out the earlier
problems, expand on solutions, and try to offer mock implementations
in the Marketing ticket(jflory7,
16:46:26)
=== jflory7 Process and review pending
Community Blog articles for publishing ===(jflory7,
16:46:33)
ACTION: jflory7
Process and review pending Community Blog articles for
publishing(jflory7,
16:46:38)
As part of the Elections discussion in #90, it
would be helpful to better explain the roles of the Fedora Council
and FESCo to motivate new candidates to run for election.(jflory7,
16:53:21)
HELP: This ticket could
use someone to help lead efforts on communicating with members of
each body, coming up with ways to better communicate a list of tasks
and responsibilities, possibly help write a blog post about these,
and help communicate them leading up to the election. The intended
impact is to increase the number of nominees for election.(jflory7,
17:00:07)
Council: Executive decision-making body in
Fedora consisting of Red Hat and community members; FESCo:
Responsible for reviewing and handling all high-level technical
decisions within the project (I think this includes per-release
changes and packaging standards); FAmSCo: Decision-making body for
the Ambassadors that helps coordinate across all regions of the
world to assist with the needs of representing and advocating Fedora
in the field;(jflory7,
17:07:21)
[con] FOSCo: A soon-to-be group consisting of
people across the community to help enhance communication among
specific key groups(jflory7,
17:07:35)
ACTION: jflory7 Post
to the mailing list breaking down how to help with Ticket #93
(due:2016-10-25)(jflory7,
17:11:27)
Auxiliary planning note: FAmSCo and FOSCo will
not be participating in upcoming election, but both may exist at the
same time. Gathering facts for FAmSCo still has merit.(jflory7,
17:15:16)
Resuming previous discussion about generating
talking points about EDU outreach by Fedorans in academic settings.
Talking points would make it easier for a student, faculty, or staff
member at a school to help promote Fedora among their peers or in
the university itself.(jflory7,
17:17:38)
jflory7 will make a post to the mailing list
about updating status on this ticket and getting input by CommOps
members(jflory7,
17:18:22)
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,
17:23:08)
HELP: Problem will be
when getting packages into Fedora and trying to push them into
future releases(jflory7,
17:35:10)
HELP: Wiki is a first
area to focus on for SIG(jflory7,
17:35:30)
ACTION: Rhea File
ticket in CommOps Pagure for on-boarding help with Dotnet SIG,
particular to: (1) what you have created, (2) things you think would
be helpful, and (3) areas you think could use some extra
brainstorming or thinking from others(jflory7,
17:39:16)
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
jflory7 Open up discussion about Fedora Appreciation Day date on the mailing list
jflory7 Take the discussion points from today's meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket
jflory7 Process and review pending Community Blog articles for publishing
jflory7 Post to the mailing list breaking down how to help with Ticket #93 (due:2016-10-25)
Rhea File ticket in CommOps Pagure for on-boarding help with Dotnet SIG, particular to: (1) what you have created, (2) things you think would be helpful, and (3) areas you think could use some extra brainstorming or thinking from others
Action items, by person
commops
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
jflory7
jflory7 Open up discussion about Fedora Appreciation Day date on the mailing list
jflory7 Take the discussion points from today's meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket
jflory7 Process and review pending Community Blog articles for publishing
jflory7 Post to the mailing list breaking down how to help with Ticket #93 (due:2016-10-25)
Rhea
Rhea File ticket in CommOps Pagure for on-boarding help with Dotnet SIG, particular to: (1) what you have created, (2) things you think would be helpful, and (3) areas you think could use some extra brainstorming or thinking from others