[Minutes] [2016-08-16] Trac => Pagure, membership checks, FAD, FOSS Student Pack, Python SIG
by Justin W. Flory
Hey CommOps!
First off, thanks to everyone who showed, we had a very bustling meeting
with lots of participation. It was exciting to see so much interest and
discussion. :)
Big topics:
* 2016-08-29: Migration from Trac to Pagure
* Putting ideas on membership checks into proposals for voting on
* Current status of our (v)FAD planning
* Creating first edition of FOSS Student Pack
* Next up for on-boarding: Python SIG
Hope to see you all next week!
= = = = =
Meeting ended Tue Aug 16 17:30:47 2016 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-16/commops.2016-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-16/commops.2016-...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-16/commops.2016-...
* * * * *
============================================
#fedora-meeting: Fedora CommOps (2016-08-16)
============================================
Meeting started by jflory7 at 15:59:03 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-16/commops.2016-...
.
Meeting summary
---------------
* Agenda (jflory7, 15:59:16)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-08-16
(jflory7, 15:59:23)
* (1) Roll Call / Q&A (jflory7, 15:59:28)
* (2) Announcements (jflory7, 15:59:38)
* (3) Action items from last meeting (jflory7, 15:59:43)
* (4) Tickets (jflory7, 15:59:50)
* (5) Wiki Gardening (jflory7, 15:59:55)
* (6) Community Blog (jflory7, 16:00:02)
* (7) Release Schedule (jflory7, 16:00:07)
* (8) Open Floor (jflory7, 16:00:12)
* Roll Call / Q&A (jflory7, 16:00:23)
* Name; Timezone; Sub-projects/Interest Areas (jflory7, 16:00:24)
* Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors,
Diversity Team, and more (jflory7, 16:00:44)
* Sachin S. Kamath ; UTC +5.30; GSoC, CommOps, Metrics, etc (skamath,
16:01:09)
* Michael Downey; UTC -7:00; GSoC, commops, marketing, diversity,
you-name-it (downey, 16:02:04)
* Huiren Woo; UTC+8; CommOps, Ambassadors, Marketing (GIANT_CRAB,
16:02:08)
* Trishna Guha; UTC +5:30; Cloud, CommOps, Infrastructure (trishnag,
16:04:57)
* Tummala Dhanvi; UTC +5.30; CommOps, docs, security, * (c0mrad3,
16:07:24)
* Dhanesh B. Sabane, UTC +5:30, CommOps, ML, Kernel, RPM Packaging
(dhanesh95, 16:07:28)
* Announcements (jflory7, 16:08:29)
* === New metrics brainstorming wiki page === (jflory7, 16:08:35)
* LINK: https://fedoraproject.org/wiki/CommOps/Metrics_Ideas
(jflory7, 16:08:40)
* bee2502 has started working on generating some ideas on community
metric generation. Check out the wiki page with more information on
metric collection with regards to discussion at the CommOps Flock
workshop there. (jflory7, 16:08:47)
* HELP: Feel free to add some of your own ideas, thoughts, or wishes
for metrics to this page too! (jflory7, 16:09:01)
* === "Docs Project update from Flock 2016" === (jflory7, 16:09:07)
* LINK:
https://communityblog.fedoraproject.org/docs-project-update-flock-2016/
(jflory7, 16:09:14)
* On jflory7's "must read list of 2016" - very informative post about
the state of the Fedora Docs team and adds a lot of insight into the
issues they are facing and how they plan to overcome them. If you
haven't been following the Docs team and want to see what's up in a
single post, this is a good one to read. (jflory7, 16:09:24)
* === "Women in technology: Fedora campus presence" === (jflory7,
16:09:34)
* LINK:
https://communityblog.fedoraproject.org/women-technology-fedora-campus-pr...
(jflory7, 16:09:39)
* Outreach efforts towards women are ongoing in local Indian
communities. Read this brief report to see what is getting started
by a2batic and sumantrom. (jflory7, 16:09:47)
* === "Żegnajcie! Fedora Flock 2016 in words" === (jflory7, 16:10:24)
* LINK: https://blog.justinwflory.com/2016/08/fedora-flock-2016/
(jflory7, 16:10:24)
* jflory7's event report on Flock 2016. There's a section dedicated to
the Fedora CommOps workshop and feedback related to the workshop. It
may be worth a read for anyone interested in the workshop and what
kinds of results we got out of holding it. (jflory7, 16:10:34)
* Sayan Chowdhury;UTC+5:30; Infrastructure, Cloud, CommOps, Marketing,
Ambassadors etc. (sayan, 16:11:12)
* LINK: https://pagure.io/fedora-diversity/issue/12 (skamath,
16:14:44)
* Action items from last meeting (jflory7, 16:15:28)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-09/commops.2016-...
(jflory7, 16:15:34)
* 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:15:43)
* === [INCOMPLETE] jflory7 Write a promo on the CommBlog about the
ultimate women's Fedora t-shirt === (jflory7, 16:17:22)
* ACTION: downey Edit original UnixStickers shirt article to include
links / mentions of the women's sizes / editions too (jflory7,
16:17:46)
* === [INCOMPLETE] skamath file a ticket on fedmsg repo for the
mailman bug === (jflory7, 16:17:59)
* ACTION: skamath file a ticket on fedmsg repo for the mailman bug
(jflory7, 16:18:04)
* === [IN PROGRESS] jflory7 Work with bee2502 on writing a report /
update on the Flock 2016 CommOps workshop === (jflory7, 16:18:10)
* ACTION: jflory7 Work with bee2502 on writing a report / update on
the Flock 2016 CommOps workshop (jflory7, 16:18:21)
* jflory7 and bee2502 did some parsing of info on Saturday from the
workshop, but there's still a little more to do - jflory7 needs to
start a draft in the CommBlog next (jflory7, 16:18:27)
* === [IN PROGRESS] jflory7 Review emails for pending posts on the
CommBlog === (jflory7, 16:18:34)
* ACTION: jflory7 Review emails for pending posts on the CommBlog
(jflory7, 16:18:40)
* This is getting done every week, but there's a consistent amount of
more coming in each week for new posts and authors, which is
awesome. :) (jflory7, 16:18:49)
* === [IN PROGRESS] jflory7 bee2502 Take workshop feedback and parse
it into more accessible data (e.g. tickets / commits / CommBlog
posts / metrics / etc.) === (jflory7, 16:18:59)
* ACTION: jflory7 bee2502 Take workshop feedback and parse it into
more accessible data (e.g. tickets / commits / CommBlog posts /
metrics / etc.) (jflory7, 16:19:09)
* jflory7 and bee2502 did some parsing of info on Saturday from the
workshop, but there's still a little more to do - jflory7 needs to
start a draft in the CommBlog next (jflory7, 16:19:15)
* === [INCOMPLETE] jflory7 File tickets for Python SIG, add feedback
for Ambassadors from workshop === (jflory7, 16:19:27)
* ACTION: jflory7 File tickets for Python SIG, add feedback for
Ambassadors from workshop (jflory7, 16:19:39)
* === [COMPLETE] jflory7 Close ticket#80 === (jflory7, 16:19:45)
* LINK: https://fedorahosted.org/fedora-commops/ticket/80 (jflory7,
16:20:30)
* === [COMPLETE] jflory7 Follow up with nardasev ASAP on whether this
one is still good to publish post-Flock === (jflory7, 16:20:44)
* LINK:
https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject...
(jflory7, 16:20:51)
* === [INCOMPLETE] jflory7 Update guide for writing a new article
based on what's actually happening in 2016 now === (jflory7,
16:20:58)
* ACTION: jflory7 Update guide for writing a new article based on
what's actually happening in 2016 now (jflory7, 16:21:05)
* Tickets (jflory7, 16:22:06)
* LINK: https://fedorahosted.org/fedora-commops/report/9 (jflory7,
16:22:11)
* === Ticket #81 === (jflory7, 16:22:32)
* "Migrating to Pagure" (jflory7, 16:22:41)
* LINK: https://fedorahosted.org/fedora-commops/ticket/81 (jflory7,
16:22:45)
* It is now possible for us to migrate from Trac to Pagure (the
importer tool was recently completed by cverna). A staging repo of
what the import looks like exists on the Pagure staging instance.
Since we now have the tooling, we should set a hard date for
migrating the entire Trac over to Pagure and begin retiring it.
Rough timeline detailed in ticket. (jflory7, 16:22:51)
* LINK: https://stg.pagure.io/stg-fedora-commops/issues (jflory7,
16:22:57)
* IDEA: Migration date: Mon, 2016 Aug 29? +1/0/-1? (jflory7,
16:23:03)
* AGREED: CommOps Trac will migrate to Pagure on 2016-08-29 - more
details to come soon, watch mailing list for info (jflory7,
16:26:33)
* === Ticket #78 === (jflory7, 16:26:45)
* "Automating a check-in to evaluate activity of members" (jflory7,
16:26:51)
* LINK: https://fedorahosted.org/fedora-commops/ticket/78 (jflory7,
16:27:02)
* Two ways to do it: Infra-style with a manual post sent monthly, or
could use Fedocal to automate this once a month as check-in calendar
event to query members on regular, consistent basis. Non-responders
would be removed from the FAS group hypothetically. Need to discuss
implementation and if this is something we want to do. (jflory7,
16:27:07)
* IDEA: Would this be necessary for active members to also complete
every month? Is it better to separate into two "groups" -
apprentices and regular members? (jflory7, 16:27:13)
* IDEA: Blatantly removing people is the wrong approach: it will be
demotivating and isolate people from wanting to contribute
(jflory7, 16:35:26)
* IDEA: If any kind of consistent follow-up is to be done, it really
should be automated so it will always be consistent (jflory7,
16:35:43)
* IDEA: Start in a beginner group, then move to an "alumni" group for
contributors who are consistent and active (i.e. they no longer have
to do the regular check-in) (jflory7, 16:36:21)
* IDEA: A single ping is easy to miss and it could cause someone still
interested to be left out (jflory7, 16:36:37)
* IDEA: Responding to one email may not be the best gauge of activity
/ contributions, so makes it difficult to use as a tool to evaluate
merits (jflory7, 16:37:06)
* IDEA: Every team could have "three big things" an active person
does, follow up on them around a 3-month interval, judge inactivity
on those criteria (jflory7, 16:37:56)
* IDEA: Automated tools don't flag some for removal, but just review /
follow-up (jflory7, 16:38:22)
* IDEA: Instead of removing contributors, "retire" them - could
de-provision by removing from group, but note them somewhere along
with their contributions, kind of like a wall of fame sort of idea
(jflory7, 16:40:24)
* LINK:
https://gist.github.com/robbyoconnor/376099ee735985fede7e6c14e072db7c
(jflory7, 16:40:29)
* ACTION: jflory7 Sort through ideas on reviewing old contributor
discussion, form proposals in the ticket, share at next meeting
(jflory7, 16:42:03)
* AGREED: Lots of ideas and discussion on this ticket - jflory7 will
sort through these ideas, try turning them into separate proposals,
and then we can vote on them at the next meeting (jflory7,
16:42:39)
* === Ticket #10 === (jflory7, 16:44:09)
* "CommOps vFAD 2016" (jflory7, 16:44:15)
* LINK: https://fedorahosted.org/fedora-commops/ticket/10 (jflory7,
16:44:19)
* Based on Flock outcome, likely reasonable to begin planning out our
own FAD event. Can opt for an in-person FAD at first, and if
necessary, fall back to virtual event. Would be held in 2017 (after
February / March when budget for next fiscal year allocated). First
steps would be for defining purpose and matching up to outcomes and
results that align with Fedora mission. We can start now by using
mattdm's logic model template and (jflory7, 16:44:26)
* ...identifying key areas for us to focus on as team. (jflory7,
16:44:36)
* LINK: https://pagure.io/FedoraLogicModelTemplate (jflory7,
16:44:41)
* ACTION: jflory7 Remove Ticket #10 from meeting agenda, collaborate
with bee2502 on sorting through feedback / ideas from Flock
(jflory7, 16:47:28)
* === Ticket #70 === (jflory7, 16:49:39)
* "FOSS Student Pack" (jflory7, 16:49:45)
* LINK: https://fedorahosted.org/fedora-commops/ticket/70 (jflory7,
16:49:50)
* Key thing to get out of this is less on physical / costly items,
more on providing resources / tools to point people towards
contributing to open source and subsequently Fedora, e.g. IRC
client, bouncer service, development tools, software in Fedora,
etc.) (jflory7, 16:49:56)
* IDEA: Key to the gate: FAS account (guide to register and what a FAS
account gives you access to) (jflory7, 16:50:55)
* IDEA: Java IDE: Eclipse (jflory7, 16:51:00)
* IDEA: IRC client: HexChat (IRC beginner guide, how to use HexChat,
etc.) (jflory7, 16:51:07)
* IDEA: Photo editing: DarkTable (what it does, guides for using it,
etc.) (jflory7, 16:51:14)
* IDEA: Creating Fedora USB media: Whatever the preferred tool now is
for creating media correctly and with stability (Fedora Media
Writer?) (jflory7, 16:51:20)
* IDEA: IRCCloud temporary membership / full account as part of the
starter pack? [Warning: This would be a relationship we would have
to actively maintain] (jflory7, 16:54:55)
* IDEA: Starting small by identifying the "Fedora Essentials 101" for
what a student would need for Linux / FOSS (jflory7, 16:58:22)
* HELP: What tool helped you get started with Linux and FOSS? What
made Fedora so great for you? What could we offer students to help
introduce to FOSS, Linux, and then Fedora? Please add your ideas and
thoughts to the ticket so we can start building a first edition of
the pack! (jflory7, 17:01:18)
* === Tickets #34 === (jflory7, 17:02:58)
* #34: "[Onboarding Series] [MASTER TICKET] Creating sub-project
on-boarding badge series" (jflory7, 17:03:13)
* LINK: https://fedorahosted.org/fedora-commops/ticket/34 (jflory7,
17:03:18)
* Infrastructure ticket put on hold while current blocking issues are
resolved. More detail in the ticket. For now, we need to decide and
focus on a new sub-project / team to focus on. jflory7 would like to
propose the Python SIG as a team that is in need of some assistance
and help. Having difficulties on-boarding new members effectively.
Need to find ways for communicating this better and how to make it
simpler for getting involved. See (jflory7, 17:03:25)
* ...rough notes for Flock as a primer on this one. (jflory7,
17:03:33)
* LINK: https://etherpad.gnome.org/p/flock-2016-commops-workshop
(jflory7, 17:03:39)
* IDEA: Target focusing on Python SIG as next team to assist? +1/0/-1?
(jflory7, 17:05:01)
* AGREED: Will focus on Python SIG next for helping with on-boarding
process - jflory7 to file the ticket for them soon (jflory7,
17:08:05)
* Wiki Gardening (jflory7, 17:08:50)
* ACTION: commops New members, make sure you add your timezone /
interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
(jflory7, 17:08:56)
* Community Blog (jflory7, 17:12:12)
* 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:12:23)
* === This Week in CommBlog === (jflory7, 17:15:26)
* (1) "Women in technology: Fedora campus presence" (jflory7,
17:15:32)
* LINK:
https://communityblog.fedoraproject.org/women-technology-fedora-campus-pr...
(jflory7, 17:15:39)
* Total Views (Aug. 12 - Aug. 16): 178 (jflory7, 17:15:45)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&vie...
(jflory7, 17:15:50)
* (2) "Heroes of Fedora 23 bonus: Test Days" (jflory7, 17:15:57)
* LINK:
https://communityblog.fedoraproject.org/heroes-fedora-23-bonus-test-days/
(jflory7, 17:16:05)
* Total Views (Aug. 14 - Aug. 16): 30 (jflory7, 17:16:12)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&vie...
(jflory7, 17:16:17)
* (3) "Docs Project update from Flock 2016" (jflory7, 17:16:29)
* LINK:
https://communityblog.fedoraproject.org/docs-project-update-flock-2016/
(jflory7, 17:16:35)
* Total Views (Aug. 15 - Aug. 16): 138 (jflory7, 17:16:54)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&vie...
(jflory7, 17:17:04)
* === Coming Up in CommBlog === (jflory7, 17:17:10)
* (1) "FOSS wave: Bhopal, Madhya Pradesh, India" (scheduled:
2016-08-18, 8:15 UTC) (jflory7, 17:17:20)
* LINK:
https://communityblog.fedoraproject.org/?p=2096&preview=1&_ppp=2944783363
(jflory7, 17:17:26)
* (2) "List of Flock blogs and more" (jflory7, 17:17:32)
* LINK:
https://communityblog.fedoraproject.org/?p=2185&preview=1&_ppp=37e727fbf1
(jflory7, 17:17:38)
* Ready to publish, but pending feedback from cwickert for final
review (jflory7, 17:18:16)
* (3) "Heroes of Fedora (HoF) - F24 Alpha" (jflory7, 17:18:27)
* LINK:
https://communityblog.fedoraproject.org/?p=2091&preview=1&_ppp=38236c1722
(jflory7, 17:18:33)
* (4) "Heroes of Fedora (HoF) – F24 Beta" (jflory7, 17:18:38)
* LINK: https://communityblog.fedoraproject.org/?p=2142&preview=true
(jflory7, 17:18:45)
* (5) "FOSS Wave Delhi , IN" (jflory7, 17:18:54)
* LINK:
https://communityblog.fedoraproject.org/?p=2145&preview=1&_ppp=6f751ef7ee
(jflory7, 17:19:00)
* (6) "Onboarding Kickoff - Fedora QA, Bhopal" (jflory7, 17:19:07)
* LINK:
https://communityblog.fedoraproject.org/?p=2188&preview=1&_ppp=3836cca259
(jflory7, 17:19:13)
* (7) "Heroes of Fedora (HoF) - Fedora 24 Final" (jflory7, 17:19:19)
* LINK:
https://communityblog.fedoraproject.org/?p=2184&preview=1&_ppp=a7f8ba6bd1
(jflory7, 17:19:26)
* (8) "Python 3 porting: 50% done in Rawhide" (jflory7, 17:19:31)
* LINK:
https://communityblog.fedoraproject.org/?p=2141&preview=1&_ppp=dff4da09a5
(jflory7, 17:19:38)
* (9) "Event Report: WWFS-FWD'2016, Kolkata" (jflory7, 17:19:48)
* LINK:
https://communityblog.fedoraproject.org/?p=2046&preview=1&_ppp=e00cffc625
(jflory7, 17:19:54)
* (10) "Fedora 24 Release Party in Singapore!" (jflory7, 17:19:59)
* LINK:
https://communityblog.fedoraproject.org/?p=2010&preview=1&_ppp=3eef8bef67
(jflory7, 17:20:05)
* (11) "Modularity Infrastructure Design" (jflory7, 17:20:13)
* LINK:
https://communityblog.fedoraproject.org/?p=2154&preview=1&_ppp=9d83efdef2
(jflory7, 17:20:18)
* Open Floor (jflory7, 17:23:16)
Meeting ended at 17:30:47 UTC.
Action Items
------------
* downey Edit original UnixStickers shirt article to include links /
mentions of the women's sizes / editions too
* skamath file a ticket on fedmsg repo for the mailman bug
* jflory7 Work with bee2502 on writing a report / update on the Flock
2016 CommOps workshop
* jflory7 Review emails for pending posts on the CommBlog
* jflory7 bee2502 Take workshop feedback and parse it into more
accessible data (e.g. tickets / commits / CommBlog posts / metrics /
etc.)
* jflory7 File tickets for Python SIG, add feedback for Ambassadors from
workshop
* jflory7 Update 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
* jflory7 Remove Ticket #10 from meeting agenda, collaborate with
bee2502 on sorting through feedback / ideas from Flock
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
Action Items, by person
-----------------------
* commops
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
* downey
* downey Edit original UnixStickers shirt article to include links /
mentions of the women's sizes / editions too
* jflory7
* jflory7 Work with bee2502 on writing a report / update on the Flock
2016 CommOps workshop
* jflory7 Review emails for pending posts on the CommBlog
* jflory7 bee2502 Take workshop feedback and parse it into more
accessible data (e.g. tickets / commits / CommBlog posts / metrics /
etc.)
* jflory7 File tickets for Python SIG, add feedback for Ambassadors
from workshop
* jflory7 Update 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
* jflory7 Remove Ticket #10 from meeting agenda, collaborate with
bee2502 on sorting through feedback / ideas from Flock
* skamath
* skamath file a ticket on fedmsg repo for the mailman bug
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jflory7 (366)
* tatica (42)
* downey (38)
* zodbot (32)
* GIANT_CRAB (29)
* skamath (29)
* mailga (19)
* r0bby (10)
* dhanesh95 (7)
* trishnag (4)
* a2batic (4)
* sayan (4)
* c0mrad3 (2)
* misc (2)
* landim (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: Following up - Flock 2016 Preview: Speaker Interviews
by Justin W. Flory
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
7 years, 1 month
Fwd: Fedora 25 Alpha Release Readiness Meeting, Thursday, August 18 @ 19:00 UTC
by Justin W. Flory
Coming up this week!
-------- Forwarded Message --------
Subject: Fedora 25 Alpha Release Readiness Meeting, Thursday, August 18
@ 19:00 UTC
Date: Mon, 15 Aug 2016 15:32:13 +0200
From: Jan Kurik <jkurik(a)redhat.com>
Reply-To: logistics(a)lists.fedoraproject.org
To: Fedora Logistics List <logistics(a)lists.fedoraproject.org>,
ambassadors <ambassadors(a)lists.fedoraproject.org>, Fedora Design Team
<design-team(a)lists.fedoraproject.org>, docs
<docs(a)lists.fedoraproject.org>, Fedora Marketing team
<marketing(a)lists.fedoraproject.org>, For testing and quality assurance
of Fedora releases <test(a)lists.fedoraproject.org>, Paul W. Frields
<pfrields(a)redhat.com>, Matthew Miller <mattdm(a)fedoraproject.org>, dennis
<dennis(a)ausil.us>, Fedora Websites Team
<websites(a)lists.fedoraproject.org>, Fedora Translation Project List
<trans(a)lists.fedoraproject.org>, devel-announce(a)lists.fedoraproject.org
Join us on irc.freenode.net in #fedora-meeting for the Fedora 25 Alpha
Release Readiness Meeting meeting.
The meeting is going to be held on Thursday, August 18, 2016 19:00
UTC. Please check the [FedoCal] link for your time zone.
We will meet to make sure we are coordinated and ready for the Alpha
release of Fedora 25 on Tuesday, August 23nd, 2016. Please note that
this meeting is going to be held even if the release is delayed at the
Go/No-Go meeting on the same day two hours earlier.
You may received this message several times, but it is by purpose to
open this meeting to the teams and to raise awareness, so hopefully
more team representatives will come to this meeting. This meeting
works best when we have representatives from all of the teams.
[FedoCal] https://apps.fedoraproject.org/calendar/meeting/4486/
More information available at:
https://fedoraproject.org/wiki/Release_Readiness_Meetings
Thank you for your support and Regards, Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
_______________________________________________
logistics mailing list
logistics(a)lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/logistics@lists.fedoraproject...
7 years, 1 month
[Fedocal] Reminder meeting : Second Quarter Budget Report
by Viorel Tabara
Dear all,
You are kindly invited to the meeting:
Second Quarter Budget Report on 2016-08-15 from 12:00:00 to 13:00:00 UTC
At fedora-commops(a)irc.freenode.net
The meeting will be about:
* Fiscal Year: *FY17*
* Responsible: *Regional Treasurers → FCL*
**Note:**
The "→" above indicates that responsibility for that item feeds into a next step in responsibility; for example, regional treasurers are responsible for providing the FCL with the relevant information for their region, and the FCL is responsible for the general report to the community. Likewise, the Council is responsible for any top-level budget adjustment when the final budget comes in from our sponsor, and regions responsible to update accordingly if needed.
More information available at:
[Budget.next](https://fedoraproject.org/wiki/Budget.next)
Source: https://apps.fedoraproject.org/calendar/meeting/3317/
7 years, 1 month
FLOCK 2016 CommOps Workshop : Election Related Discussion Summary
by Bhagyashree Uday
Hi ,
This is a summary of the Election-related discussion we had in the CommOps
workshop in FLOCK 2016. We were starting to discuss some of these ideas and
how we can implement them for the next election. We thought you'd be
interested in some of these points and we could start working together on
creating a plan for the next elections cycle based on this feedback. The
notes follow below:
Overall, there was a wish for increased focus on improving interaction
between candidates and community members. Some of this could be by
improving how questions are submitted for interviews and using tools to
help motivate voting without putting too much strain on a single person
(i.e. automating them).
*New ways to encourage questions*
- Utilizing social media as a way for the user community to participate
in the elections (since anyone with a FAS account could participate in the
Council elections)
- Comments on Community Blog for taking questions. The questions could
then be taken out of the comments and into wiki (if this is communicated
to the community ahead of time, maybe its own post?)
*Visual Summary of all Candidate Interviews*
- Improved format for "what kind of issues" at the table
- Chart / table for where candidates fall on some of these issues or
topics (even as simple as Y/N with links to full interview?)
*Sending surveys after election for feedback and suggestions*
- Measuring voter satisfaction over what was successful and what was
ineffective
- For Survey collecting tools / follow-up with Diversity Team
- Open vs. closed tools, what options are available
*"I voted!" badge*
- Privacy concerns ? Why hasn't this been implemented yet ?
- Awarding the badge during / after election to encourage people to vote
- If the badge is awarded during the elections, it encourages voting
immediately?
- Utilizing fedmsg to deliver the badge
- One or per release cycle
*Sending statistics related to voting metrics daily to improve voter
turnout and keep contributors engaged*
- There was a peak in number of voters on the first and the last day
when reminders were sent out.
- On these lines, if we could send mails with # of voters per day, it
could perhaps help
*Pre-Election Promotion*
- Teaser article on Magazine about elections
- Done in Dec. 2015, but not June 2016 (one thing that maybe impacted
lower turnout in June?)
- Promotional piece about elections, what it means,
These are some of the ideas we collected at the workshop. We would be
interested in knowing what you all think of this or what some of your ideas
are based on this feedback.
Thanks!
Cheers,
Justin and Bee
7 years, 1 month
Article Series/Badge Idea
by Brian Exelbierd
Sirko recently wrote on his blog about awarding the F24 Release Party
Organizer badge only to people who wrote event reports[0]
This got me thinking. I wonder if we should propose a new badge and
create a new Magazine or Comm Blog Article series.
Have a wiki, trac or other method by which people can submit the urls
for event reports they write on their blogs. Once a month someone can
summarize them into a link post. A few words about what is after each
link and a link list. I suggest a title along the lines of "What
happened in Fedora last month around the world". Yes, that needs work.
The article should be a fairly fast and easy piece to write. It would
be a great article for new writers to write as well.
The corresponding badge series would be awarded to every blogger whose
article gets listed in the link list. It will need to be manually
awarded, but is only once per month. The series could be titled
something like "Fedora Reporter" with levels like wiki editing, etc.
Artwork could be a newspaper seller holding a newspaper and saying
"Extra Extra" (or if that is too Americentric, saying nothing.
My goal here is to increase the number of event reports and to allow the
Project to leverage them for additional PR.
I believe that the badge should only be awarded for event reports. So
if someone just posts a photo collection we can give them a paparazzi
badge or something similar. We can make it clear that we are looking
for a detailed event report that covers the basics. They don't need to
be transcripts. We can provide a set of questions to help guide
writers, but not require them.
Comments?
regards,
bex
[0]: http://karl-tux-stadt.de/ktuxs/?p=4936
7 years, 1 month
