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 https://communityblog.fedoraproject.org/writing-community-blog-article/ 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 understandable manner.
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.
Action Items: - 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 them
Note: In the meeting today the article from PyCon Slovakia was published.
Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-... Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-... Log: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-...
On Tue, May 23, 2017 at 08:00:51PM +0200, Brian Exelbierd wrote:
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.
Action Items:
- 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 them
FWIW, I'm on a list of people with privileges for commblog, but have not really been involved in it. I think this happened because, during its initial setup, I was among the group of people administering Fedora Magazine. So I could help with setup and configuration and such. However, I don't have cycles available for an additional editorial job at this time, but I can let the team know if/when that changes.
On Tue, May 23, 2017, at 08:55 PM, Paul W. Frields wrote:
On Tue, May 23, 2017 at 08:00:51PM +0200, Brian Exelbierd wrote:
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.
Action Items:
- 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 them
FWIW, I'm on a list of people with privileges for commblog, but have not really been involved in it. I think this happened because, during its initial setup, I was among the group of people administering Fedora Magazine. So I could help with setup and configuration and such. However, I don't have cycles available for an additional editorial job at this time, but I can let the team know if/when that changes.
It seems reasonable that you would be a go to person with structural/administration issues. I'll make sure your admin rights don't get deleted.
regards,
bex
-- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com _______________________________________________ Fedora Community Operations (CommOps) mailing list -- commops@lists.fedoraproject.org To unsubscribe send an email to commops-leave@lists.fedoraproject.org
On Tue, May 23, 2017 at 2:00 PM, Brian Exelbierd bex@pobox.com wrote:
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 https://communityblog.fedoraproject.org/writing-community-blog-article/ 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 understandable manner.
I can understand not shooting for perfect prose, but I'd like to see to it that we're not throwing out grammatical train-wrecks.
e.g., I don't care if a writer misuses "comprise" or if sentences are a bit clunky. I do care if we're publishing stuff that is going to make people wince. (e.g. failing to get "its" and "it's" right, or "there/their/they're" confusions, "then/than" mixups, and so forth.)
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.
+1 - scheduling is unnecessary in this case.
Action Items:
- 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 them
Note: In the meeting today the article from PyCon Slovakia was published.
Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/ commops.2017-05-23-16.35.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/ commops.2017-05-23-16.35.txt Log: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/ commops.2017-05-23-16.35.log.html _______________________________________________ Fedora Community Operations (CommOps) mailing list -- commops@lists.fedoraproject.org To unsubscribe send an email to commops-leave@lists.fedoraproject.org
Hi Brian!
I'm a lot less active in both Diversity and CommOps now, and will be for a few more weeks... I'm still here, just can't really make meetings, i'm in a weird time when this meeting time just doesn't work for me, and I don't even know if it will get better. The thing is that right after that I would have .net meeting, so I have to either stay in the office til 21:00 or move before that meeting starts...
(I was cycling home during the meeting, after we split in the office)
Radka
------------------------------ *Radka Janeková* .NET Engineer, Red Hat *radka.janek@redhat.com radka.janek@redhat.com* IRC: radka | Freenode: Rhea
On Tue, May 23, 2017 at 8:00 PM, Brian Exelbierd bex@pobox.com wrote:
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 https://communityblog.fedoraproject.org/writing-community-blog-article/ 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 understandable manner.
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.
Action Items:
- 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 them
Note: In the meeting today the article from PyCon Slovakia was published.
Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/ commops.2017-05-23-16.35.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/ commops.2017-05-23-16.35.txt Log: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/ commops.2017-05-23-16.35.log.html _______________________________________________ Fedora Community Operations (CommOps) mailing list -- commops@lists.fedoraproject.org To unsubscribe send an email to commops-leave@lists.fedoraproject.org
On 05/23/2017 11:30 PM, Brian Exelbierd wrote:
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.
Hello Brian,
Thanks for writing this e-mail. It is my project meeting which clashes with CommOps meeting and that is why I cannot attend.
Suggestion: The writing process as described on https://communityblog.fedoraproject.org/writing-community-blog-article/ 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 understandable manner.
+1 , Defining editing in this way will help on-boarding more editors in team.
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.
Again +1 , Old posts are always gonna be there for reference, so I don't see a point in holding articles.
Action Items:
- 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
Do we have list of existing editors somewhere? It will help to evaluate, if we need more editors or not by comparing it with the article traffic, we generally have for CommBlog.
Thanks, Amita
- 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 them
Note: In the meeting today the article from PyCon Slovakia was published.
Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-... Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-... Log: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-... _______________________________________________ Fedora Community Operations (CommOps) mailing list -- commops@lists.fedoraproject.org To unsubscribe send an email to commops-leave@lists.fedoraproject.org
On 05/24/2017 03:39 PM, Amita wrote:
On 05/23/2017 11:30 PM, Brian Exelbierd wrote:
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.
Hello Brian,
Thanks for writing this e-mail. It is my project meeting which clashes with CommOps meeting and that is why I cannot attend.
Sorry, I mixed it with other meeting time. The reason is it is too late for IST (10:00 PM - 11:30 PM).
Suggestion: The writing process as described on https://communityblog.fedoraproject.org/writing-community-blog-article/ 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 understandable manner.
+1 , Defining editing in this way will help on-boarding more editors in team.
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.
Again +1 , Old posts are always gonna be there for reference, so I don't see a point in holding articles.
Action Items:
- 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
Do we have list of existing editors somewhere? It will help to evaluate, if we need more editors or not by comparing it with the article traffic, we generally have for CommBlog.
Thanks, Amita
- 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 them
Note: In the meeting today the article from PyCon Slovakia was published.
Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-...
Log: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-...
Fedora Community Operations (CommOps) mailing list -- commops@lists.fedoraproject.org To unsubscribe send an email to commops-leave@lists.fedoraproject.org
Fedora Community Operations (CommOps) mailing list -- commops@lists.fedoraproject.org To unsubscribe send an email to commops-leave@lists.fedoraproject.org
Hi everybody,
at this time, the infra tickets is:
https://pagure.io/fedora-infrastructure/issue/6077 (closed, only puiterwijk is both Infra Team Member and Blog Admin)
So we have a complete list of admins and editors (Thanks nb) :)
Also, I wrote to all authors with one or more draft entries and i hope have some feedback soon.
On 05/23/2017 01:00 PM, Brian Exelbierd wrote:
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 https://communityblog.fedoraproject.org/writing-community-blog-article/ 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 understandable manner.
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.
Action Items:
- 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 them
Note: In the meeting today the article from PyCon Slovakia was published.
Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-... Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-... Log: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-... _______________________________________________ Fedora Community Operations (CommOps) mailing list -- commops@lists.fedoraproject.org To unsubscribe send an email to commops-leave@lists.fedoraproject.org
On Wed, May 24, 2017, at 06:03 PM, Alberto Rodriguez S wrote:
Hi everybody,
at this time, the infra tickets is:
https://pagure.io/fedora-infrastructure/issue/6077 (closed, only puiterwijk is both Infra Team Member and Blog Admin)> So we have a complete list of admins and editors (Thanks nb) :)
Also, I wrote to all authors with one or more draft entries and i hope have some feedback soon.
I've opened a ticket to track the editor clean up here: https://pagure.io/fedora-commops/issue/111 regards,
bex
On 05/23/2017 01:00 PM, Brian Exelbierd wrote:
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 https://communityblog.fedoraproject.org/writing-community-blog-article/ 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 understandable manner. 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. Action Items: - 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 them Note: In the meeting today the article from PyCon Slovakia was published. Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-... Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-... Log: https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-05-... _______________________________________________ Fedora Community Operations (CommOps) mailing list -- commops@lists.fedoraproject.org To unsubscribe send an email to commops-leave@lists.fedoraproject.org
Fedora Community Operations (CommOps) mailing list -- commops@lists.fedoraproject.org> To unsubscribe send an email to commops-leave@lists.fedoraproject.org
commops@lists.fedoraproject.org
-
Alberto Rodriguez S -
Amita -
Brian Exelbierd -
Joe Brockmeier -
Paul W. Frields -
Radka Janekova