[fedora-commops] Issue #92 `Start a yearly Fedora Appreciation Day`
by Pagure
cprofitt added a new comment to an issue you are following:
``
> @ankursinha rightfully noted that some parts of the project are a lot less visible than others, and
> there could be an issue with some core parts of the project and community members involved
> there who may not be recognized for their work. While I think it's impossible to guarantee that
> everyone will be thanked for something, I think we can make it easier for people to know who to
> thank for what.
-----
Potentially, we can mention those areas of the project when we announce this initiative.
> Additionally, we should be leveraging this to build a marketing outcome from this so that we
> don't just celebrate internally but we attract more of the target audiences to Fedora.
----
I agree we need to leverage this outside of the traditional Fedora channels. Do we have a list of Linux / FOSS media sites that we could try to use to publicize the event? (1) I would be willing to write an introduction to 'Fedora Appreciation Days' to be published. (2) Our posts of appreciation need not be limited to Fedorans. People can post message of appreciation for other open source projects / upstreams that they are thankful for.
> I agree. I'm going to make a note for creating a draft of this for after DevConf / FOSDEM
> (after Feb. 5th).
-----
Justin, let me know how I can assist. I would like to help create the draft as well.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-commops/issue/92
7 years, 2 months
Introduction
by Jeremy Bohrer
Hello. I am Jeremy Brennan Bohrer. I am 18. Not quite sure how to create an IRC Nick. But my time zone is eastern standard time. I would love to help in ANY area possible. Thanks!
Sent from my iPhone
7 years, 2 months
draft article for Cloud Base Image
by Matthew Miller
I drafted up an article "Fedora Cloud Base Image has a new home!" that
I'd like to publish sometime this week or next. It could use an editing
pass and whatever beautification y'all find appropriate.
Thanks!
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
7 years, 2 months
[fedora-commops] Issue #93 `Elections: Better explain roles of Council and FESCo`
by Pagure
jflory7 added a new comment to an issue you are following:
``
**Discussed in [2017-01-24 meeting](https://meetbot.fedoraproject.org/fedora-meeting/2017-01-24/comm...
Ultimately, we decided on following the Council's thoughts that their wiki page was already busy enough and that anyone running for the Council should be able to understand the roles and responsibilities of the Council from existing information and participating in meetings.
For FESCo, we still believed an improvement could be made, but we will move this as a downstream ticket to the FESCo ticketing instance. @dhanesh95 volunteered to work on this one, with a **deadline of Sunday, 27 January 2017.** Once the ticket is filed downstream, we agreed to close this ticket and let FESCo determine what is best to describe their operations as they see fit.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-commops/issue/93
7 years, 2 months
[Minutes] [2017-01-24] Setting the pace
by Justin W. Flory
Hey everyone! Our meeting ended just a bit ago and it was a fully loaded
meeting! Thanks everyone who made it out.
Today, we covered some of the older tickets and tried breaking them up
into smaller, more achievable tasks. I'd like to continue looking at
some of our older tickets next week too, but we should have a firm
agenda taking shape now too.
See you all next week (or at DevConf, if you will be there)!
= = = = =
Meeting ended Tue Jan 24 19:10:57 2017 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2017-01-24/commops.2017-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2017-01-24/commops.2017-...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2017-01-24/commops.2017-...
* * * * *
============================================
#fedora-meeting: Fedora CommOps (2017-01-24)
============================================
Meeting started by jflory7 at 17:29:36 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2017-01-24/commops.2017-...
.
Meeting summary
---------------
* Agenda (jflory7, 17:29:52)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2017-01-24
(jflory7, 17:29:57)
* (1) Roll Call / Q&A (jflory7, 17:30:01)
* (2) Announcements (jflory7, 17:30:06)
* (3) Action items from last meeting (jflory7, 17:30:29)
* (4) Tickets (jflory7, 17:30:32)
* (5) Community Blog - skipping today, but will be back next week!
(jflory7, 17:30:36)
* (6) Open Floor (jflory7, 17:30:42)
* Roll Call / Q&A (jflory7, 17:30:47)
* Name; Timezone; Sub-projects/Interest Areas (jflory7, 17:30:53)
* ACTION: commops New members, make sure you introduce yourself on the
CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
(jflory7, 17:30:58)
* Radka Janek; UTC+1; CommOps, Diversity, DotNet,... (Rhea, 17:31:11)
* Justin W. Flory; UTC+1; CommOps, Magazine, Marketing, Ambassadors,
Diversity, Join SIG, sysadmin-badges, and more (jflory7, 17:31:34)
* Alberto Rodriguez; UTC-6; CommOps, metrics and more (bt0, 17:31:45)
* Dhanesh B. Sabane, UTC +5:30, CommOps, Marketing, ML, Python,
Packaging and more to come (dhanesh95, 17:37:01)
* Announcements (jflory7, 17:38:20)
* === "Elections Retrospective, January 2017" === (jflory7, 17:38:25)
* LINK:
https://communityblog.fedoraproject.org/elections-retrospective-january-2...
(jflory7, 17:38:29)
* jkurik combined a brief retrospective of the past election cycle.
This was one of the top participated elections of Fedora history!
Awesome job for everyone involved with the election process. The
feedback in this post will be helpful for a later analysis of the
election cycle and seeing what we can do better for next time.
(jflory7, 17:38:35)
* === Upcoming travel arrangements === (jflory7, 17:38:45)
* DevConf (27-29 Jan.) and FOSDEM (3-5 Feb.) are coming up soon. As a
result, many people may be away or busy for the next couple of
weeks, so be aware activity may slow down a little in some parts of
the project until after the two conferences. (jflory7, 17:38:50)
* HELP: Are you going to be traveling at all for the next couple of
weeks? Make sure you add your travel schedule to the Fedora vacation
calendar so people know whether or not you will be around.
(jflory7, 17:39:19)
* LINK: https://apps.fedoraproject.org/calendar/vacation/ (jflory7,
17:39:27)
* Action items from last meeting (jflory7, 17:40:45)
* LINK:
https://meetbot.fedoraproject.org/teams/commops/commops.2017-01-17-17.28....
(jflory7, 17:40:50)
* 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,
17:40:55)
* === Rhea Post on Reddit with the Election results === (jflory7,
17:41:02)
* ACTION: jflory7 Work with Rhea on adding her as a subreddit mod
(due:2017-01-25) (jflory7, 17:41:44)
* [COMPLETE] CommBlog post summarized the elections and was posted
into the subreddit (jflory7, 17:42:21)
* === bt0 to try to get a list of Fedora contributors & talks out of
FOSDEM calendar === (jflory7, 17:42:29)
* [IN PROGRESS] Will revisit during ticket discussion (jflory7,
17:44:23)
* Tickets (jflory7, 17:44:41)
* LINK: https://pagure.io/fedora-commops/issues?tags=meeting
(jflory7, 17:44:45)
* Today's ticket queue was intentionally left empty to give us a
chance to look through some older tickets and see if we can either
(1) consolidate, (2) close, or (3) reevaluate what is needed to
complete them. We may also file some new tickets based on recent
discussions elsewhere. (jflory7, 17:45:46)
* ***** EXISTING TICKETS ***** (jflory7, 17:46:09)
* === Ticket #98 === (jflory7, 17:46:44)
* "Round Up of Fedora Contributor Talks @ FOSDEM" (jflory7, 17:46:47)
* LINK: https://pagure.io/fedora-commops/issue/98 (Rhea, 17:46:48)
* ACTION: bt0 Verify the accuracy of the current list of Fedora
speakers attending FOSDEM (due: 2017-01-25) (jflory7, 17:58:00)
* ACTION: dhanesh95 Put a call out on the devel mailing list asking
for any Fedorans speaking at FOSDEM to please check if their name is
added to our list so that they are covered in a later post on the
Fedora Magazine (due: 2017-01-26/27) (jflory7, 18:00:04)
* ACTION: jflory7 Write article introducing Fedora speakers at FOSDEM
on Tue., Jan. 31, publish on Wednesday or Thursday before FOSDEM
(due: 2017-01-31) (jflory7, 18:00:47)
* These three items, once completed, will close the ticket. (jflory7,
18:00:57)
* === Ticket #93 === (jflory7, 18:01:57)
* "Elections: Better explain roles of Council and FESCo" (jflory7,
18:02:03)
* LINK: https://pagure.io/fedora-commops/issue/93 (jflory7,
18:02:07)
* ACTION: dhanesh95 File a new ticket in the FESCo Trac/Pagure
requesting more information to the wiki page about their
responsibilities and common tasks (bullet points are great, but if
they have time, longer descriptions would help too) (due:
2017-01-29) (jflory7, 18:13:22)
* === Ticket #90 === (jflory7, 18:16:06)
* "Improving Fedora Elections Process." (jflory7, 18:16:08)
* LINK: https://pagure.io/fedora-commops/issue/90 (jflory7,
18:16:12)
* ACTION: cprofitt Work on pulling feedback and ideas mentioned in
Ticket #90 into smaller, more achievable items, either as bullets in
a ticket comment on #90 or as new tickets (due: 2017-01-31)
(jflory7, 18:30:33)
* === Ticket #95 === (jflory7, 18:33:25)
* "[Onboarding Series] DotNet SIG" (jflory7, 18:33:32)
* LINK: https://pagure.io/fedora-commops/issue/95 (jflory7,
18:33:36)
* Rhea will follow up with others to see about the logistics of
packaging dilemma with FAS groups and pkgdb, will update in ticket
as needed (jflory7, 18:49:21)
* HELP: Info for new packagers was difficult to find for how new teams
should proceed, along with documentation for pkgdb. Better
documentation about how to get started is something that would help
others in the future. (jflory7, 18:50:06)
* === Ticket #28 === (jflory7, 18:51:28)
* "Creating an online contributor classroom - "Fedora University""
(jflory7, 18:51:32)
* LINK: https://pagure.io/fedora-commops/issue/28 (jflory7,
18:51:36)
* AGREED: Ticket will be closed - this idea is out of our scope to
complete. Instead, we will refocus efforts on the Fedora Classroom
with members of the Join SIG, to provide a mentorship / teaching
opportunity for those who want to learn more about contributing to
Fedora or other misc. topics related to Fedora (jflory7, 18:58:36)
* ***** NEW TICKETS ***** (jflory7, 18:59:07)
* IDEA: Collaboration with Join SIG on reviving Fedora Classroom and
finding ways to make them easier to run for volunteers and
organizers - new ticket idea for discussion (jflory7, 19:03:25)
* IDEA: FOSCo branch??? (jflory7, 19:05:17)
* ACTION: jflory7 File a new ticket to discuss the idea of reviving
Fedora Classroom more in depth (jflory7, 19:05:34)
* Open Floor (jflory7, 19:07:02)
Meeting ended at 19:10:57 UTC.
Action Items
------------
* commops New members, make sure you introduce yourself on the CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* jflory7 Work with Rhea on adding her as a subreddit mod
(due:2017-01-25)
* bt0 Verify the accuracy of the current list of Fedora speakers
attending FOSDEM (due: 2017-01-25)
* dhanesh95 Put a call out on the devel mailing list asking for any
Fedorans speaking at FOSDEM to please check if their name is added to
our list so that they are covered in a later post on the Fedora
Magazine (due: 2017-01-26/27)
* jflory7 Write article introducing Fedora speakers at FOSDEM on Tue.,
Jan. 31, publish on Wednesday or Thursday before FOSDEM (due:
2017-01-31)
* dhanesh95 File a new ticket in the FESCo Trac/Pagure requesting more
information to the wiki page about their responsibilities and common
tasks (bullet points are great, but if they have time, longer
descriptions would help too) (due: 2017-01-29)
* cprofitt Work on pulling feedback and ideas mentioned in Ticket #90
into smaller, more achievable items, either as bullets in a ticket
comment on #90 or as new tickets (due: 2017-01-31)
* jflory7 File a new ticket to discuss the idea of reviving Fedora
Classroom more in depth
Action Items, by person
-----------------------
* bt0
* bt0 Verify the accuracy of the current list of Fedora speakers
attending FOSDEM (due: 2017-01-25)
* commops
* commops New members, make sure you introduce yourself on the CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* cprofitt
* cprofitt Work on pulling feedback and ideas mentioned in Ticket #90
into smaller, more achievable items, either as bullets in a ticket
comment on #90 or as new tickets (due: 2017-01-31)
* dhanesh95
* dhanesh95 Put a call out on the devel mailing list asking for any
Fedorans speaking at FOSDEM to please check if their name is added
to our list so that they are covered in a later post on the Fedora
Magazine (due: 2017-01-26/27)
* dhanesh95 File a new ticket in the FESCo Trac/Pagure requesting more
information to the wiki page about their responsibilities and common
tasks (bullet points are great, but if they have time, longer
descriptions would help too) (due: 2017-01-29)
* jflory7
* jflory7 Work with Rhea on adding her as a subreddit mod
(due:2017-01-25)
* jflory7 Write article introducing Fedora speakers at FOSDEM on Tue.,
Jan. 31, publish on Wednesday or Thursday before FOSDEM (due:
2017-01-31)
* jflory7 File a new ticket to discuss the idea of reviving Fedora
Classroom more in depth
* Rhea
* jflory7 Work with Rhea on adding her as a subreddit mod
(due:2017-01-25)
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jflory7 (214)
* Rhea (83)
* bt0 (30)
* x3mboy (28)
* dhanesh95 (25)
* zodbot (23)
* cprofitt (16)
* mailga (16)
* shantorn (3)
* commops (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 2 months
Today's meeting - evaluating goals/priorities?
by Justin W. Flory
Hey CommOps,
I'm finally finished moving this week, but getting ready for conferences
these coming next two weeks. I was thinking that for today's meeting, we
might just follow a short schedule and try to reevaluate priorities and
goals we want to accomplish for 2017?
We'll follow a normal format for the rest of the meeting, but for the
tickets section, we can do triaging to identify tasks and tickets we
want to focus in on for the next month or two. I figure this will give
us a good chance to retool for the coming year since the meetings have
been inconsistent over the holidays and the start of January (big thanks
to Radka for helping pick up for me in absences again!).
Thanks all!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 2 months
