You are kindly invited to the meeting:
CommOps IRC Meeting on 2017-05-30 from 12:30:00 to 14:00:00 US/Eastern
The meeting will be about:
This meeting is for team members of the Community Operations (CommOps) team. The weekly agenda is mostly comprised of the different tasks detailed on the CommOps wiki page, although it is subject to change depending on time and context of what is going around the Fedora Project.
More information can be found on the [wiki page](https://fedoraproject.org/wiki/CommOps).
My name is Adad Jiram Osorio Hernández and I live in Mexico City. I'm a
bachelor in Computer Systems Engineer, I just finished my university in
December 2016. I have been using Linux for personal use and academic works
since 2012. I'm interested to help the Fedora Project so I can give back to
the community, the same has gave me a lot. Also I think that I can learn
more about Linux System Administration. My first profile is a Linux
Sysadmin. I want to acquire more experience and knowledge in the Linux
world so I can be a better sysadmin.
Facebook: Adad J Osorio Hdez
Mobile: (MX) 777-207-23-44
I'm Adrian Soliard (A.K.A. Chino Soliard), from Paraná, Argentina.
I'm contributing to the project since 2012, I'm member of the
ambassadors team; I've edited some wiki pages and written articles for
I've interest in joining CommOps team because I'd like to update and
organize the wiki (sometimes it sounds imposible) in things related to
Argentina, LATAM, and Ambassadors, and want to help with improvements
for ambassadors in general, also, in my free time, I would like to help
in the changes and updates that are within my reach.
Adrian "Chino" Soliard
Fedora Project Contributor
Hi. My name is Kambiz Aghaiepour. I am a long time Red Hat employee.
I worked at Red Hat from 2001 to 2006 on the production operations team.
I left Red Hat for 4 years while I worked at Duke University
(responsible for Linux@Duke while I was there) and I also worked for
MCNC before returning to Red Hat in 2011.
I occasionally notice typos and errors on the Fedoraproject wiki pages
and am requesting membership in commops as a non CLA* group in order to
fix said issues.
I'm currently heavily involved in Red Hat's OpenStack performance and
You can find me on IRC as "kambiz" (on freenode) and "kosh" on the
private redhat IRC network.
"All tyranny needs to gain a foothold is for people of good conscience
to remain silent." --Thomas Jefferson
On Tue, May 23, 2017 at 08:08:53PM +0200, Brian Exelbierd wrote:
> You've currently got editing/publishing rights on the Community Blog.
> There was a meeting today to work on the editing process and it would be
> great if you could weigh in on the mailing list discussion.
> In the meantime, we are trying to figure out who has time to actually do
> the publishing as articles have been sitting in the queue. Can you
> reply to this email and the commops mailing list with whether you
> a) Can check the list of pending articles at least once per week and
> publish per the process
> b) don't have time to do it right now and will let us know in the future
> if you can
b) is my situation. I don't have time to help out on this atm.
FWIW, I didn't even know I had editing/publishing rights on the
commblog(!). It probably makes sense to remove me.
We had a CommOps meeting today and focused on the Community Blog editing
process. I am not sure if it is just bad timing or what, but we only
had 2 people active in the meeting. Therefore it is important that
folks respond to the issues raised here on the mailing list as we didn't
have quorum to take any actions.
Suggestion: The writing process as described on
seems good. Writers should be encouraged to use this process.
Suggestion: Editing should be defined as checking that the post is
appropriate for the commblog and is understandable. The goal is not to
publish every article in perfect American English but instead to make su
re we are getting information out to contributors in a quick and
Suggesting: Publishing should be done as soon as a post is ready. There
is not a need to time articles on the commblog as it is a contributor
focused feed without a direct marketing initiative goal. We would r
ather get information to our contributors faster via the RSS feeds, etc.
than hold articles longer than needed.
- bt0 to email all authors with draft or on hold articles to find out
what their status is
- bexelbie to email all editors and find out if they have time to edit
so we can figure out if we need more people
- bt0 to open a ticket with infra to find out who on their team must
have access for administrative reasons so we don't accidentally remove
Note: In the meeting today the article from PyCon Slovakia was