[Minutes] [2016-08-23] Everything you want to know about Python SIG, CommOps toolbox, and wikieditor FAS
by Justin W. Flory
Hi all!
Par for the course, today was a very full meeting. We spent a lot of
time covering details on the needs of the Python SIG for on-boarding
(based on discussions at Flock), migrating some tools in the CommOps
toolbox to a single place, and also details about some of the discussion
with the wikieditor FAS group.
More information is all available in the logs. Also, I will be proposing
moving the meetings starting 30 minutes ahead due to sudden changes in
my schedule - more on that in a separate email. Thanks everyone for
coming out today!
= = = = =
Meeting ended Tue Aug 23 17:24:01 2016 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-23/commops.2016-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-23/commops.2016-...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-23/commops.2016-...
* * * * *
============================================
#fedora-meeting: Fedora CommOps (2016-08-23)
============================================
Meeting started by jflory7 at 15:58:40 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-23/commops.2016-...
.
Meeting summary
---------------
* Agenda (jflory7, 15:58:58)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-08-23
(jflory7, 15:59:01)
* (1) Roll Call / Q&A (jflory7, 15:59:05)
* (2) Announcements (jflory7, 15:59:09)
* (3) Action items from last meeting (jflory7, 15:59:16)
* (4) Tickets (jflory7, 15:59:20)
* (5) Wiki Gardening (jflory7, 15:59:26)
* (6) Community Blog (jflory7, 15:59:30)
* (7) Open Floor (jflory7, 15:59:34)
* Roll Call / Q&A (jflory7, 15:59:40)
* Name; Timezone; Sub-projects/Interest Areas (jflory7, 15:59:44)
* Sachin S. Kamath; UTC +5.30; GSoC, Metrics, CommOps (skamath,
16:00:06)
* Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors,
Diversity Team, Join SIG, and more (jflory7, 16:00:10)
* Michael Downey; UTC -7:00; CommOps, Marketing, also <3 for gsoc,
docs, design, * (downey, 16:00:54)
* John M. Harris, Jr.; UTC-4; CommOps, Games SIG, Java SIG (JohnMH,
16:01:42)
* Announcements (skamath, 16:01:43)
* Wesley Otugo; GMT +1 (wesleyotugo, 16:01:43)
* === Fedora 25 Alpha Release: 2016-08-30 === (skamath, 16:01:49)
* LINK: https://fedoraproject.org/wiki/Releases/25/Schedule
(skamath, 16:02:04)
* The current targeted date for the Fedora 25 Alpha is for August 30,
2016. (skamath, 16:02:08)
* === "List of Flock blogs and more" === (skamath, 16:02:28)
* LINK:
https://communityblog.fedoraproject.org/list-of-flock-blogs-and-more/
(skamath, 16:02:34)
* Brief overview of Flock 2016 with links to individual contributor
blog posts and reports about the event. Good way to reflect / review
on discussions and focuses from Flock or to see what happened if you
were not able to attend. (skamath, 16:02:45)
* === "FOSS wave: Bhopal, Madhya Pradesh, India" === (skamath,
16:03:02)
* LINK:
https://communityblog.fedoraproject.org/foss-wave-bhopal-madhya-pradesh-i...
(skamath, 16:03:13)
* Ongoing efforts to introduce FOSS, Fedora Quality Assurance, and
testing to students across India. Sumantro Mukherjee (sumantrom) is
helping lead these efforts. Watch for more information on the
Community Blog in coming weeks! (skamath, 16:03:23)
* === REMINDER: Pagure migration, 2016-08-29 === (skamath, 16:03:33)
* Reminder that the migration from Trac to Pagure is targeted for
Monday, August 29th, 2016. We will be abandoning Trac soon. More
information to come. (skamath, 16:03:42)
* Action items from last meeting (skamath, 16:05:05)
* LINK:
https://meetbot.fedoraproject.org/teams/commops/commops.2016-08-16-15.59....
(skamath, 16:05:13)
* 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. (skamath,
16:05:20)
* === [INCOMPLETE] downey Edit original UnixStickers shirt article to
include links / mentions of the women's sizes / editions too ===
(skamath, 16:05:33)
* ACTION: downey Ping jflory7 for editing article / adding paragraph
into article (skamath, 16:06:37)
* === skamath file a ticket on fedmsg repo for the mailman bug ===
(skamath, 16:06:44)
* LINK:
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/issues/399
(skamath, 16:07:18)
* === [INCOMPLETE] jflory7 Work with bee2502 on writing a report /
update on the Flock 2016 CommOps workshop === (skamath, 16:07:59)
* ACTION: jflory7 Work with bee2502 on writing a report / update on
the Flock 2016 CommOps workshop (skamath, 16:08:31)
* === [INCOMPLETE] jflory7 bee2502 Take workshop feedback and parse it
into more accessible data (e.g. tickets / commits / CommBlog posts /
metrics / etc.) === (skamath, 16:08:43)
* ACTION: jflory7 bee2502 Take workshop feedback and parse it into
more accessible data (e.g. tickets / commits / CommBlog posts /
metrics / etc.) (skamath, 16:08:51)
* === [COMPLETE] jflory7 Review emails for pending posts on the
CommBlog === (skamath, 16:09:09)
* ACTION: jflory7 Review emails for pending posts on the CommBlog
(skamath, 16:09:21)
* === [INCOMPLETE] jflory7 File tickets for Python SIG, add feedback
for Ambassadors from workshop === (skamath, 16:09:35)
* ACTION: jflory7 File tickets for Python SIG, add feedback for
Ambassadors from workshop (skamath, 16:10:06)
* === [INCOMPLETE] jflory7 Update Community Blog writing guide for
writing a new article based on what's actually happening in 2016 now
=== (skamath, 16:10:29)
* ACTION: jflory7 Update Community Blog writing guide for writing a
new article based on what's actually happening in 2016 now
(skamath, 16:10:38)
* === [INCOMPLETE] jflory7 Sort through ideas on reviewing old
contributor discussion, form proposals in the ticket, share at next
meeting === (skamath, 16:11:38)
* ACTION: jflory7 Sort through ideas on reviewing old contributor
discussion, form proposals in the ticket, share at next meeting
(skamath, 16:11:45)
* === [COMPLETE] jflory7 Remove Ticket #10 from meeting agenda,
collaborate with bee2502 on sorting through feedback / ideas from
Flock === (skamath, 16:12:15)
* Tickets (skamath, 16:15:02)
* LINK: https://fedorahosted.org/fedora-commops/report/9 (skamath,
16:15:11)
* === Ticket #78 === (skamath, 16:15:18)
* "Automating a check-in to evaluate activity of members" (skamath,
16:15:23)
* LINK: https://fedorahosted.org/fedora-commops/ticket/78 (skamath,
16:15:29)
* AGREED: Due to lots of raw ideas and discussion from last week's
meeting, would like to defer further discussion until there are more
solid proposals to discuss / agree on (jflory7, 16:24:00)
* === Ticket #34 === (jflory7, 16:25:14)
* "[Onboarding Series] [MASTER TICKET] Creating sub-project
on-boarding badge series" (jflory7, 16:25:19)
* LINK: https://fedorahosted.org/fedora-commops/ticket/34 (jflory7,
16:25:24)
* Last meeting, we agreed that next target group (outside of final
follow-up on tickets awaiting badges) would be the Python SIG due to
discussions that happened at the CommOps workshop at Flock 2016
(jflory7, 16:28:06)
* Background on the Python SIG: Around 20 members, handles reviewing
Python packages in Fedora, deals with Python-specific technical
decisions in Fedora, also sometimes handles security-critical issues
with Python packages in Fedora (jflory7, 16:29:24)
* Noted at Flock that the on-boarding process for new members has
difficulties: Unclear process for newcomers to follow,
distinguishment between mailing lists (one public, one private for
security bugs) unclear, need more items to be able to help guide
newcomers to, sometimes there are "human" decisions that need to be
made when reviewing new applicants (jflory7, 16:31:09)
* IDEA: Revamping wiki page / establishing numbered steps for
newcomers to follow to become involved (jflory7, 16:31:49)
* IDEA: Making it clear what info is needed from newcomers for current
members of the SIG to understand what newcomers are familiar with,
interested in contributing towards, or able to do (jflory7,
16:32:17)
* IDEA: Coming up with creative solutions for how something that
sometimes requires a subjective, "human" review process to follow
general guidelines or points for evaluating newcomers (with context
to revealing security bugs or issues) (jflory7, 16:33:21)
* LINK: https://fedoraproject.org/wiki/SIGs/Python (jflory7,
16:35:26)
* LINK:
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedorapr...
(jflory7, 16:35:41)
* LINK:
https://admin.fedoraproject.org/pkgdb/packager/group::python-sig/
(jflory7, 16:35:53)
* LINK: https://fedoraproject.org/wiki/SIGs/Python/Members_list
(jflory7, 16:36:17)
* LINK: http://fedora.portingdb.xyz/ (jflory7, 16:36:30)
* IDEA: Improving communication about Python SIG member list being on
the wiki over a FAS group (and that's the official source for people
involved with the Python SIG) (jflory7, 16:45:05)
* IDEA: An apprentice-esque type approach for newcomers to Python
SIG??? (jflory7, 16:45:23)
* === Ticket #82 === (jflory7, 16:47:55)
* "Move CommOps toolbox to Pagure" (jflory7, 16:48:00)
* LINK: https://fedorahosted.org/fedora-commops/ticket/82 (jflory7,
16:48:04)
* ACTION: skamath File a ticket in Fedora Infra Trac for proposing an
official migration from fedora-infra GitHub organization into Pagure
since it has stabilized since the last time this was discussed (to
jflory7's knowledge, anyways ;) ) (jflory7, 16:54:00)
* ACTION: jflory7 Reach out to decause about the idea of migrating his
tools in the CommOps toolbox to Pagure and granting access to the
CommOps group (jflory7, 16:54:46)
* Wiki Gardening (jflory7, 16:56:45)
* ACTION: commops New members, make sure you add your timezone /
interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
(jflory7, 16:56:52)
* wikieditor FAS group: Group created not as a default "join to get
access" kind of context, but more for edge cases where it's more
plausible to add them to a standalone FAS group versus onboarding in
a group (also might not have a FAS group). Example used was remixer
who maintains a wiki page but nothing else. (jflory7, 17:03:20)
* Community Blog (jflory7, 17:05:40)
* 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:05:48)
* === This Week in CommBlog === (jflory7, 17:05:53)
* (1) "FOSS wave: Bhopal, Madhya Pradesh, India" (jflory7, 17:05:58)
* LINK:
https://communityblog.fedoraproject.org/foss-wave-bhopal-madhya-pradesh-i...
(jflory7, 17:06:04)
* Total Views (Aug. 18 - Aug. 22): 18 (jflory7, 17:06:10)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&vie...
(jflory7, 17:06:16)
* ACTION: jflory7 Do a social media blast promoting the FOSS Wave
article for Bhopal (jflory7, 17:06:22)
* (2) "List of Flock blogs and more" (jflory7, 17:06:27)
* LINK:
https://communityblog.fedoraproject.org/list-of-flock-blogs-and-more/
(jflory7, 17:06:31)
* Total Views (Aug. 18 - Aug. 22): 54 (jflory7, 17:06:36)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&vie...
(jflory7, 17:06:41)
* === Coming Up in CommBlog === (jflory7, 17:06:56)
* (1) "FOSS Wave: Delhi, India" - scheduled 2016-08-23 (jflory7,
17:07:03)
* LINK:
https://communityblog.fedoraproject.org/?p=2145&preview=1&_ppp=143a11a08f
(jflory7, 17:07:09)
* (2) "Fedora 24 Release Party in Singapore" - scheduled 2016-08-24
(jflory7, 17:07:15)
* LINK:
https://communityblog.fedoraproject.org/?p=2010&preview=1&_ppp=1df831e1a4
(jflory7, 17:07:21)
* (3) "Modularity Infrastructure Design" - scheduled 2016-08-25
(jflory7, 17:07:33)
* LINK:
https://communityblog.fedoraproject.org/?p=2154&preview=1&_ppp=7146c2ee3c
(jflory7, 17:07:39)
* (4) "Say No to Wiki SPAM!" (jflory7, 17:07:45)
* LINK:
https://communityblog.fedoraproject.org/?p=2208&preview=1&_ppp=1cf79eb584
(jflory7, 17:07:50)
* ACTION: jflory7 Revisit wiki spam article with context of current
situation with FAS groups (jflory7, 17:08:01)
* (5) "Globalization improvements in Fedora 24" (jflory7, 17:08:07)
* LINK:
https://communityblog.fedoraproject.org/?p=2212&preview=1&_ppp=005a502ebc
(jflory7, 17:08:13)
* (6) "Modularity and Containers" (jflory7, 17:08:20)
* LINK:
https://communityblog.fedoraproject.org/?p=2235&preview=1&_ppp=4da4ccff52
(jflory7, 17:08:25)
* (7) "What are Personas and Why Should you Care?" (jflory7,
17:08:30)
* LINK:
https://communityblog.fedoraproject.org/?p=2230&preview=1&_ppp=33758937f3
(jflory7, 17:08:35)
* (8) "Heroes of Fedora (HoF) - F24 Alpha" (jflory7, 17:08:41)
* LINK:
https://communityblog.fedoraproject.org/?p=2091&preview=1&_ppp=98aec2b146
(jflory7, 17:08:46)
* (9) "Heroes of Fedora (HoF) - F24 Beta" (jflory7, 17:08:56)
* LINK:
https://communityblog.fedoraproject.org/?p=2142&preview=1&_ppp=405ee85506
(jflory7, 17:09:01)
* (10) "Heroes of Fedora (HoF) - F24 Final" (jflory7, 17:09:06)
* LINK:
https://communityblog.fedoraproject.org/?p=2204&preview=1&_ppp=0c855ab7c8
(jflory7, 17:09:10)
* Open Floor (jflory7, 17:19:29)
Meeting ended at 17:24:01 UTC.
Action Items
------------
* downey Ping jflory7 for editing article / adding paragraph into
article
* jflory7 Work with bee2502 on writing a report / update on the Flock
2016 CommOps workshop
* jflory7 bee2502 Take workshop feedback and parse it into more
accessible data (e.g. tickets / commits / CommBlog posts / metrics /
etc.)
* jflory7 Review emails for pending posts on the CommBlog
* jflory7 File tickets for Python SIG, add feedback for Ambassadors from
workshop
* jflory7 Update Community Blog writing guide for writing a new article
based on what's actually happening in 2016 now
* jflory7 Sort through ideas on reviewing old contributor discussion,
form proposals in the ticket, share at next meeting
* skamath File a ticket in Fedora Infra Trac for proposing an official
migration from fedora-infra GitHub organization into Pagure since it
has stabilized since the last time this was discussed (to jflory7's
knowledge, anyways ;) )
* jflory7 Reach out to decause about the idea of migrating his tools in
the CommOps toolbox to Pagure and granting access to the CommOps group
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
* jflory7 Do a social media blast promoting the FOSS Wave article for
Bhopal
* jflory7 Revisit wiki spam article with context of current situation
with FAS groups
Action Items, by person
-----------------------
* bee2502
* jflory7 Work with bee2502 on writing a report / update on the Flock
2016 CommOps workshop
* jflory7 bee2502 Take workshop feedback and parse it into more
accessible data (e.g. tickets / commits / CommBlog posts / metrics /
etc.)
* commops
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
* downey
* downey Ping jflory7 for editing article / adding paragraph into
article
* jflory7
* downey Ping jflory7 for editing article / adding paragraph into
article
* jflory7 Work with bee2502 on writing a report / update on the Flock
2016 CommOps workshop
* jflory7 bee2502 Take workshop feedback and parse it into more
accessible data (e.g. tickets / commits / CommBlog posts / metrics /
etc.)
* jflory7 Review emails for pending posts on the CommBlog
* jflory7 File tickets for Python SIG, add feedback for Ambassadors
from workshop
* jflory7 Update Community Blog writing guide for writing a new
article based on what's actually happening in 2016 now
* jflory7 Sort through ideas on reviewing old contributor discussion,
form proposals in the ticket, share at next meeting
* skamath File a ticket in Fedora Infra Trac for proposing an official
migration from fedora-infra GitHub organization into Pagure since it
has stabilized since the last time this was discussed (to jflory7's
knowledge, anyways ;) )
* jflory7 Reach out to decause about the idea of migrating his tools
in the CommOps toolbox to Pagure and granting access to the CommOps
group
* jflory7 Do a social media blast promoting the FOSS Wave article for
Bhopal
* jflory7 Revisit wiki spam article with context of current situation
with FAS groups
* skamath
* skamath File a ticket in Fedora Infra Trac for proposing an official
migration from fedora-infra GitHub organization into Pagure since it
has stabilized since the last time this was discussed (to jflory7's
knowledge, anyways ;) )
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jflory7 (217)
* skamath (103)
* zodbot (17)
* Guest_84847 (14)
* wesleyotugo (14)
* nirik (13)
* downey (12)
* JohnMH (7)
* pviktori (5)
* a2batic (2)
* cprofitt (2)
* bt0 (1)
* bee2502 (1)
* commops (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 1 month
Re: Request for article approval
by Justin W. Flory
On 08/12/2016 01:38 PM, Courtney Pacheco wrote:
> My apologies... I realized that my link was not viewable to the public!
> Here's the actual link:
>
> https://fedoramagazine.org/?p=14038&preview=1&_ppp=992550a43b
>
>
> Please do let me know if this belongs in the community blog instead. I
> was on the fence with this article.
>
>
> On 08/12/2016 01:22 PM, Courtney Pacheco wrote:
>> Hi everyone,
>>
>> I'm looking to publish an article about Modularity's infrastructure
>> design.
>>
>> Here is a link to the article I wrote:
>> https://fedoramagazine.org/?p=14038&preview_id=14038&preview_nonce=634686...
>>
>>
>> The article is a follow-up to:
>> https://communityblog.fedoraproject.org/introduction-to-modularity/
>>
>> Please let me know your opinions and if anything needs to be
>> modified/updated. :)
>>
>> Thanks,
>> Courtney
>>
Hey Courtney, thanks so much for writing this article up!! This was
definitely an easy one to review, thanks so much for spending the time
writing this overview of the modularity's infrastructure design (I
learned a fair bit reading it).
You can see a preview of the article currently here:
https://communityblog.fedoraproject.org/?p=2154&preview=1&_ppp=7146c2ee3c
I am going to schedule it for Thursday, 2016-08-25, at 8:15 UTC (so it
has its own full day on the front page). Let me know if you see anything
that needs to be changed or modified before then.
Also, feel free to add some info about yourself on this page to be
displayed on the bottom of the article in your author biography box so
people can know what your role in the project is. :)
https://communityblog.fedoraproject.org/wp-admin/profile.php
Thanks again for writing!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 1 month
Sorry for the inactivity
by John M. Harris, Jr.
I’ve been almost entirely inactive for quite a while now, and I believe I’ve
finally worked around the issues I previous had with my mail server, among
other things. I’m “back” now, either way.
--
John M. Harris, Jr. <johnmh(a)openblox.org>
Project Lead, OpenBlox
https://openblox.org/
7 years, 1 month
[CommBlog] "Fedora 24 Release Party in Singapore" edited and scheduled
by Justin W. Flory
Hello all,
This is a long overdue notification that the "Fedora 24 Release Party in
Singapore" article by woohuiren is edited and scheduled for 2016-08-24,
at 8:15 UTC. You can find a public preview of the article here:
https://communityblog.fedoraproject.org/?p=2010&preview=1&_ppp=1df831e1a4
Thanks Woo for writing this article and being so patient in having it
reviewed - in the future, be sure to to drop a line here on our mailing
list once it's ready for a quicker review.
If anyone notices anything needing fixing or correcting with the
article, please let me know. Thanks!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 1 month
Request to review
by Sumantro Mukherjee
Hey All
I have just put up a report of an activity which took place in Delhi, IN . Sessions on FOSS & Fedora with understanding GIT and Fedora QA were taken by Saurabh! This is one of the many another activities which helps the Fedora community in India to expand & grow.
Thanks
Sumantro
7 years, 1 month
Re: [Marketing] Re: Following up - Flock 2016 Preview: Speaker Interviews
by Justin W. Flory
On 08/17/2016 09:50 AM, Natalie Ardasevova wrote:
> Hi Justin,
>
> so Christoph gave me feedback, now I am waiting for Sylvia to send me a link to her blog post to include it there. After that, it should be ready for publishing!
>
> :)
>
> Natalie Ardasevova
> nardasev(a)redhat.com
> Marketing Communications Specialist
>
Hey Natalie, I'm playing a little bit of catch-up now, but it looks like
you published this on your own on Friday? If so, any more follow-up
needed here? Just wanted to be sure before archiving this thread. Thanks!
>
> ----- Original Message -----
> From: "Justin W. Flory" <jflory7(a)gmail.com>
> To: "Fedora + Community + Operations = Fedora CommOps" <commops(a)lists.fedoraproject.org>
> Cc: "Natalie Ardasevova" <nardasev(a)redhat.com>, "Fedora Marketing team" <marketing(a)lists.fedoraproject.org>
> Sent: Monday, August 15, 2016 8:49:01 PM
> Subject: [Marketing] Re: Following up - Flock 2016 Preview: Speaker Interviews
>
> On 08/15/2016 12:46 PM, Natalie Ardasevova wrote:
>> Hey Justin,
>>
>> great edits, thank you! Only thing I would now do is show this to Christoph before we publish it, there may be updates from his side. I'll send it to him now and let you know when he replies, ok? :)
>>
>> I scrapped the interview draft on the Comm Blog.
>>
>> Cheers,
>>
>> Natalie Ardasevova
>> nardasev(a)redhat.com
>> Marketing Communications Specialist
>>
>
> This sounds good to me. Once you hear back from Christoph, we can work
> on putting it on the schedule for this week!
>
>>
>> ----- Original Message -----
>> From: "Justin W. Flory" <jflory7(a)gmail.com>
>> To: "Fedora + Community + Operations = Fedora CommOps" <commops(a)lists.fedoraproject.org>
>> Cc: "Natalie Ardasevova" <nardasev(a)redhat.com>, "Fedora Marketing team" <marketing(a)lists.fedoraproject.org>
>> Sent: Monday, August 15, 2016 6:14:07 PM
>> Subject: [Marketing] Re: Following up - Flock 2016 Preview: Speaker Interviews
>>
>> On 08/12/2016 06:34 PM, Natalie Ardasevova wrote:
>>> Hi Justin.
>>>
>>> Ah, snap. I did publish the pre-Flock article on my blog which is linked to Fedora Planet and then probably forgot to do that in the comm blog:
>>>
>>> https://nardasev.wordpress.com/2016/08/01/flock-pre-event-speaker-intervi...
>>>
>>> This is what I got now:
>>>
>>> https://communityblog.fedoraproject.org/?p=2185&preview=1&_ppp=7e5cad8cf7
>>>
>>> it includes the previous interviews, as well as links to other blogs. That could go to the comm blog and the I can do a summary article for the Fedora magazine. What do you think?
>>>
>>> Natalie Ardasevova
>>> nardasev(a)redhat.com
>>> Marketing Communications Specialist
>>>
>>>
>>
>> Okay, sounds good about the original post being on your personal blog. I
>> recommend that we scrap the draft on the Community Blog for now, and we
>> can refer back to your personal blog for that one. It would be tough to
>> update it now since Flock has already wrapped up.
>>
>> This one looks good to me! I just went through and applied some edits,
>> and added a featured image. Let me know if this looks good, and I'll
>> throw it on the schedule for this week!
>>
>>
>> https://communityblog.fedoraproject.org/?p=2185&preview=1&_ppp=f5204f5365
>>
>> Thanks again for writing these up. :)
>>
>>> ----- Original Message -----
>>> From: "Justin W. Flory" <jflory7(a)fedoraproject.org>
>>> To: "Natalie Ardasevova" <nardasev(a)redhat.com>
>>> Sent: Friday, August 12, 2016 9:34:41 AM
>>> Subject: Following up - Flock 2016 Preview: Speaker Interviews
>>>
>>> Hey Natálie,
>>>
>>> Wanted to follow up quickly on one of the articles we had for Flock on
>>> the CommBlog that never quite made it out:
>>>
>>>
>>> https://communityblog.fedoraproject.org/?p=2022&preview=1&_ppp=a00312e1b6
>>>
>>> It was worded and targeted as pre-Flock interviews, but there's a lot of
>>> really good content in here, and if we could freshen it up a little bit
>>> as "post-Flock" instead, or maybe salvage it in some way, I'd love to
>>> try to push it out if we can. I wanted to check in with you about
>>> whether this is something you think would be doable or if you'd rather
>>> scrap the article and focus on new content instead.
>>>
>>> Let me know what you want to do. Thanks! :)
>>>
>>
>> --
>> Cheers,
>> Justin W. Flory
>> jflory7(a)gmail.com
>>
>
> --
> Cheers,
> Justin W. Flory
> jflory7(a)gmail.com
>
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 1 month
[Community Operations (CommOps)] #81: Migrating to Pagure
by fedora-badges
#81: Migrating to Pagure
-------------------------+------------------------
Reporter: jflory7 | Owner: jflory7
Type: task | Status: new
Priority: this week | Milestone: ASAP
Component: General | Severity: not urgent
Keywords: nextmeeting |
-------------------------+------------------------
= phenomenon =
The [https://pagure.io/pagure-importer Pagure Importer] tool recently
added support for attachments. The CommOps Trac can migrate to Pagure.
= background analysis =
All fedorahosted.org instances (including Trac) is targeted to become
obsolete in 2017. This means all existing instances will be moved or
removed. Migrating on our own will save us time in the future, give us
time to adapt to a new tool, and save work for the Fedora Infrastructure
team later on.
The tool was demonstrated by cverna in
[https://stg.pagure.io/testcli/issues Exhibit A] (excluding tags in
import) and [https://stg.pagure.io/stg-fedora-commops/issues Exhibit b]
(including tags in import). A fair amount of manual work in updating tags,
milestones, and priorities will be needed, but it's better to begin doing
that now than even months later.
= implementation recommendation =
1. Play with test repos a little more to figure out how we could adapt
Pagure to our needs
2. Set target date for migration (two weeks from today?)
3. At date, move to new, official repository
4. Verify successful migration (all tickets present? all attachments
moved? all data accounted for?)
5. Update tags, milestones, priorities, other settings for Pagure
6. Give Trac one more month just in case of any mishaps, ensure all team
documentation points to Pagure instead of Trac
7. Request closure of Trac instance
--
Ticket URL: <https://fedorahosted.org/fedora-commops/ticket/81>
Community Operations (CommOps) <https://fedoraproject.org/wiki/CommOps>
Community Operations (CommOps) aims to build and improve community infrastructure to better communication across the Project and to help tell the story of Fedora.
7 years, 1 month
