Looking for a volunteer to help with Elections
by Jan Kurik
Hi CommOps people,
according to the F24 schedule [1], we will start the post-F24
elections period on 2016-July-05. I am looking for someone who can
help me to organize these Elections.
As I am on vacations from 2016-June-25 to 2016-July-07 I will need
someone who can do full coverage of the "Election wrangler" role
during the beginning of the "Nomination period" (it is not much work,
do not worry :-) ).
Please let me know if anyone can help me here.
[1] https://fedorapeople.org/groups/schedule/f-24/f-24-elections.html
Thanks and Best Regards,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
7 years, 10 months
Marketing-trac: #227: Create the release announcement for Fedora 24
by Marketing Team
#227: Create the release announcement for Fedora 24
----------------------------------+------------------------
Reporter: jflory7 | Owner:
Type: task | Status: new
Priority: critical | Milestone: Fedora 24
Component: Release deliverables | Severity: urgent
Keywords: meeting | Blocked By:
Blocking: |
----------------------------------+------------------------
= Phenomenon =
It's about that time of year! Fedora 24 is just around the corner. For
Fedora 23, the idea came up of having a different kind of release
announcement, adding more "human" parts of the magic happening for each
release into the announcement. mattdm expressed interest in this then, but
due to the time crunch, we didn't have as much time to work on it as we
liked.
= Background Analysis =
We need to see how many hands we have available for this task, what kind
of angles we want to approach, and whether we want to do one or two
versions of the announcement (and if two, where the two types end up
going).
= Implementation Recommendation =
This will be a good topic for the meeting to decide how we want to shape
this release announcement. We will discuss it in today's meeting and then
also wait for feedback from others who are unable to attend.
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/227>
Marketing Team <https://fedoraproject.org/wiki/Marketing>
The Trac site for the Fedora Project Marketing team. This Trac serves as a place to list out tasks, define objectives, and work on monitoring our progress with key tasks and goals.
7 years, 10 months
Re: Update on the Fedora QA series
by Justin W. Flory
On 06/20/2016 01:20 AM, Sumantro Mukherjee wrote:
> Hey
>
> I would like to have an update about the Fedora QA series. I have one article in place which is in the community blog , may I have an update on when the other two articles are getting published ?
>
> Thanks
> Sumantro
>
Hi Sumantro,
I just had a chance to review your article on organizing Fedora Test
Days. I have a final draft of the article at the link below.
https://communityblog.fedoraproject.org/?p=1667&preview=1&_ppp=2ecd1d879b
I had a few questions remaining for the article, and I left these in
comments through the article. Do you think you would be able to better
clarify some of these points for readers or explain some of the concepts
mentioned? This will help out anyone who isn't familiar with the entire
process already or doesn't know what everything is.
I also was going to try uploading your screenshots separately to the
article since they were a low resolution, but I couldn't find a location
for higher resolution screenshots. Would you be able to send links for
where to find higher resolution screenshots we can use in the article?
Thanks for your time working on this!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 10 months
CommOps Weekly Meeting Recap 2016-06-21
by Justin W. Flory
Meeting ended Tue Jun 21 17:20:30 2016 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-21/commops.2016-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-21/commops.2016-...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-21/commops.2016-...
* * * * *
============================================
#fedora-meeting: Fedora CommOps (2016-06-21)
============================================
Meeting started by jflory7 at 15:57:07 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-21/commops.2016-...
.
Meeting summary
---------------
* Agenda (jflory7, 15:57:22)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-06-21
(jflory7, 15:57:27)
* (1) Roll Call / Q&A (jflory7, 15:57:31)
* (2) Announcements (jflory7, 15:57:41)
* (3) Action items from last meeting (jflory7, 15:57:42)
* (4) Tickets (jflory7, 15:57:46)
* (5) Wiki Gardening (jflory7, 15:57:50)
* (6) Community Blog (jflory7, 15:57:54)
* (7) Release Schedule (jflory7, 15:57:59)
* (8) Open Floor (jflory7, 15:58:03)
* Roll Call / Q&A (jflory7, 15:58:12)
* Name; Timezone; Sub-projects/Interest Areas (jflory7, 15:58:13)
* Huiren Woo; GMT+0800; Ambassador, common ops, marketing.
(GIANT_CRAB, 15:58:31)
* Dhanesh B. Sabane, UTC+5:30, CommOps, ML (dhanesh95, 15:58:34)
* Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors,
Infrastructure-fi, Join, and more (jflory7, 15:58:52)
* Corey Sheldon UTC -4 check fas for groups (linuxmodder, 15:59:03)
* Sachin S. Kamath; UTC +5.30 ; GSoC, Metrics, CommOps (skamath,
15:59:07)
* Trishna Guha; UTC+5:30; Infrastructure, Cloud, CommOps etc.
(trishnag, 15:59:50)
* Tummala Dhanvi; UTC+5:30; CommOps, Security, Docs, GSoC, *
(c0mrad3, 16:02:33)
* decause; UTC-4; CommOps, GSoC, Council, Budget, Flock, * (decause,
16:03:02)
* Announcements (jflory7, 16:04:20)
* === "Fedora 24 released!" === (jflory7, 16:04:30)
* LINK: https://fedoramagazine.org/fedora-24-released/ (jflory7,
16:04:37)
* We're in the middle of it today, team! Fedora 24 released hours ago.
Today is a very busy day across Fedora. Check out upgrading your own
system if you haven't already yet! :) (jflory7, 16:04:41)
* LINK:
https://www.facebook.com/TheFedoraProject/posts/10154250457540480
(jflory7, 16:04:45)
* LINK: https://twitter.com/fedora/status/745255602121674754
(jflory7, 16:04:50)
* LINK: https://plus.google.com/+fedora/posts/5aqqppyVuHS (jflory7,
16:04:54)
* LINK:
https://fedoramagazine.org/upgrading-fedora-23-workstation-to-fedora-24/
(jflory7, 16:04:58)
* === "Fedora Cloud FAD 2016 Report" === (jflory7, 16:05:04)
* LINK:
https://communityblog.fedoraproject.org/fedora-cloud-fad-2016-report/
(jflory7, 16:05:09)
* The Fedora Cloud Working Group finished their Fedora Activity Day
this past week. Learn all that was accomplished and what objectives
are on the table for the Cloud WG in this article. (jflory7,
16:05:15)
* === skamath's super cool statistic generation === (jflory7,
16:05:21)
* LINK: https://pagure.io/gsoc-stats (jflory7, 16:05:25)
* LINK:
https://docs.google.com/spreadsheets/d/1VatSWdON08MCLZIdJWRVYeFTMXxvo6HzE...
(jflory7, 16:05:30)
* LINK:
https://github.com/sachinkamath/fedstats-data/tree/master/interns-mid-term
(jflory7, 16:05:36)
* skamath's tool evaluates different parts of fedmsg activity to
generate statistics about the contributions of specific contributors
and where they spend their time in Fedora. You can see some of the
data that he has collected so far in the above links. You can find
the project source on Pagure! (jflory7, 16:05:41)
* === "Google's security princess talks cybersecurity" === (jflory7,
16:06:04)
* LINK:
https://opensource.com/life/16/6/interview-parisa-tabriz-google
(jflory7, 16:06:09)
* decause recently published his latest work on Opensource.com where
he interviewed Parisa Tabriz at PyCon 2016! (jflory7, 16:06:18)
* GSoC Midterm Evaluations are now open (skamath, 16:06:32)
* LINK: https://opensource.com/life/16/6/how-community-taught-me-code
(skamath, 16:09:08)
* Congratulations to trishnag on her interview on OSDC - make sure to
give it a read if you have not yet! (jflory7, 16:09:44)
* GSoC Midterm Evalations will be closing soon, so please read the
summer-coding list and meet w/ mentors (decause, 16:11:00)
* Action items from last meeting (jflory7, 16:11:20)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-14/commops.2016-...
(jflory7, 16:11:25)
* 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:11:30)
* === decause review the vFAD goals/objectives/etc === (jflory7,
16:11:43)
* ACTION: decause review the vFAD goals / objectives / etc. (jflory7,
16:12:26)
* === decause Work with jzb to organize the release party in Raleigh,
NC area === (jflory7, 16:12:30)
* jzb/decause decided to do a release party *after* summit (by the
time we got the "go" we had little time to prepare, and lots of
other prep for RHT Summit.) (decause, 16:13:18)
* === decause nail down Flock arrangements and add to fedocal ===
(jflory7, 16:13:41)
* ACTION: decause nail down Flock arrangements and add to fedocal
(jflory7, 16:14:03)
* === [COMPLETE] decause Finish "final" version of F24 GA Release
Announcement for review after go/no-go meeting on Thursday ===
(jflory7, 16:14:14)
* === [COMPLETE] jflory7 Create a WhenIsGood and share with CommOps
mailing list to decide on vFAD dates of July 2-3 or June 25-26 ===
(jflory7, 16:14:23)
* LINK: http://goo.gl/forms/ck9Dcxb9vqo6jqh62 (jflory7, 16:14:28)
* Mixed results, but low response rate on the poll. Will discuss
during Ticket #10. (jflory7, 16:14:35)
* === [COMPLETE] jflory7 Write YAML file for CommOps on-boarding badge
based on FAS group sponsorship === (jflory7, 16:14:43)
* LINK: https://fedorahosted.org/fedora-badges/ticket/464#comment:2
(jflory7, 16:14:49)
* === [INCOMPLETE] jflory7 Open a ticket to look into drafting an
(automated?) check-in email with members of CommOps to determine
activity === (jflory7, 16:14:56)
* ACTION: jflory7 Open a ticket to look into drafting an (automated?)
check-in email with members of CommOps to determine activity
(jflory7, 16:15:03)
* === [COMPLETE] commops File a ticket on the Pagure repository for
Fedora Hubs about creating a News widget that aggregates different
sources of information and puts it together for easy consumption by
a reader === (jflory7, 16:15:10)
* LINK: https://pagure.io/fedora-hubs/issue/203 (jflory7, 16:15:19)
* === [COMPLETE] jflory7 Update Ticket #71 with the "WHY" perspective
in relation to FOSCo === (jflory7, 16:15:24)
* LINK: https://fedorahosted.org/famsco/ticket/373#comment:23
(jflory7, 16:15:30)
* Added the info to the relevant ticket on the FAmSCo Trac (jflory7,
16:15:38)
* === decause Drop a line to the devel list to have anyone going to
Red Hat Summit add their info to the wiki page === (jflory7,
16:15:45)
* ACTION: decause Drop a line to the devel list to have anyone going
to Red Hat Summit add their info to the wiki page (jflory7,
16:18:14)
* === [COMPLETE] jflory7 Look into filing a ticket on Pagure for CCing
users / lists from a Pagure issue === (jflory7, 16:18:19)
* LINK: https://pagure.io/pagure/issue/746 (jflory7, 16:18:23)
* Tickets (jflory7, 16:19:11)
* LINK: https://fedorahosted.org/fedora-commops/report/9 (jflory7,
16:19:15)
* === Ticket #10 === (jflory7, 16:19:19)
* "CommOps vFAD 2016" (jflory7, 16:19:25)
* LINK: https://fedorahosted.org/fedora-commops/ticket/10 (jflory7,
16:19:31)
* LINK: https://fedoraproject.org/wiki/FAD_CommOps_2016 (jflory7,
16:19:35)
* LINK: http://goo.gl/forms/ck9Dcxb9vqo6jqh62 (jflory7, 16:19:40)
* AGREED: July 3-4 (GIANT_CRAB, 16:21:36)
* AGREED: Based on answers from the poll and in-meeting votes, July 3
- 4 seems like the preferred date for organizing our vFAD to knock
out some tasks in our backlog and get ahead on current tickets. Will
plan out final details ASAP this week in a hack session. (jflory7,
16:23:09)
* ACTION: jflory7 Don't forget to bring up Vector / Matrix.org later
on this meeting, during open floor (jflory7, 16:30:27)
* AGREED: Hack session time tonight: 14:30 US EST == 18:30 UTC ==
00:00 IST (jflory7, 16:33:35)
* === Tickets #34, 49 === (jflory7, 16:34:01)
* #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project
on-boarding badge series" (jflory7, 16:34:05)
* #49: "[Onboarding Series] CommOps!" (jflory7, 16:34:10)
* LINK: https://fedorahosted.org/fedora-commops/ticket/34 (jflory7,
16:34:15)
* LINK: https://fedorahosted.org/fedora-commops/ticket/57 (jflory7,
16:34:19)
* CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs
Team Badges Tracks and Widgets (jflory7, 16:34:23)
* LINK: https://fedorahosted.org/fedora-badges/ticket/464 (jflory7,
16:34:31)
* IDEA: Once badge is published, "core" part of the ticket is
completed. (jflory7, 16:38:57)
* IDEA: After badge is out, we can write a CommBlog post advertising
the badge, explain how it fits into the bigger picture of
on-boarding for the project, and how we want to help all other
sub-projects have similar paths for on-boarding (jflory7, 16:39:38)
* IDEA: There is an RFE already filed for Tahrir to point out "paths"
for contributors to earn new badges based on what they have already
earned (jflory7, 16:40:32)
* LINK: https://github.com/fedora-infra/tahrir/issues/343 (jflory7,
16:40:34)
* Development on this RFE for Tahrir is starting the next week
(jflory7, 16:41:13)
* AGREED: Will revisit this discussion about integration with Tahrir
in the hack session tonight (jflory7, 16:45:56)
* === Ticket #71 === (jflory7, 16:46:34)
* "Centralizing Ambassadors / Events resources and utilities"
(jflory7, 16:46:41)
* LINK: https://fedorahosted.org/fedora-commops/ticket/71 (jflory7,
16:46:48)
* ACTION: jflory7 Write up an initial draft of a wiki page outlining
the process for Ambassadors specifically to request assets from the
Design Team, include plans to reach out to regional Ambassadors from
all regions with this information later (jflory7, 16:53:24)
* Wiki Gardening (jflory7, 16:54:25)
* ACTION: commops New members, make sure you add your timezone /
interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
(jflory7, 16:54:39)
* Community Blog (jflory7, 16:56:20)
* 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,
16:56:36)
* === This Week in CommBlog === (jflory7, 16:56:47)
* (1) "Fedora Cloud FAD 2016 Report" (jflory7, 16:56:55)
* LINK:
https://communityblog.fedoraproject.org/fedora-cloud-fad-2016-report/
(jflory7, 16:57:01)
* Total Views (June 15 - June 21): 146 (jflory7, 16:57:03)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&vie...
(jflory7, 16:57:09)
* (2) "Official: Fedora 24 will release June 21 2016" (jflory7,
16:57:14)
* LINK:
https://communityblog.fedoraproject.org/official-fedora-24-will-release-j...
(jflory7, 16:57:20)
* Total Views (June 16 - June 21): 1,693 (jflory7, 16:57:27)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&vie...
(jflory7, 16:57:33)
* (3) "Another way to push package updates to stable in Fedora Bodhi"
(jflory7, 16:57:39)
* LINK:
https://communityblog.fedoraproject.org/push-package-updates-stable-bodhi/
(jflory7, 16:57:54)
* Total Views (June 17 - June 21): 152 (jflory7, 16:58:01)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&vie...
(jflory7, 16:58:06)
* === Coming Up in CommBlog === (jflory7, 16:58:21)
* (1) "Hosting your own Fedora Test Day" (jflory7, 16:58:37)
* LINK:
https://communityblog.fedoraproject.org/?p=1667&preview=1&_ppp=cb84ab4de6
(jflory7, 16:58:42)
* (2) "Southeast Linux Fest 2016" (jflory7, 16:58:48)
* LINK:
https://communityblog.fedoraproject.org/?p=1676&preview=1&_ppp=60042342dd
(jflory7, 16:58:52)
* (3) "Getting started with 'update-testing' Fedora QA part 2"
(jflory7, 16:58:58)
* LINK:
https://communityblog.fedoraproject.org/?p=1609&preview=1&_ppp=09ca15f4e9
(jflory7, 16:59:02)
* (4) "Getting started with Fedora QA part 3" (jflory7, 16:59:09)
* LINK:
https://communityblog.fedoraproject.org/?p=1610&preview=1&_ppp=11ae698d60
(jflory7, 16:59:16)
* (5) "Event Report: PyCon 2016" (jflory7, 16:59:21)
* LINK:
https://communityblog.fedoraproject.org/?p=1602&preview=1&_ppp=dae31f1c4d
(jflory7, 16:59:26)
* ACTION: jflory7 Get on top of editing this week and schedule some of
these articles for this / next week, reply back to authors waiting
for a response (jflory7, 16:59:35)
* (6) "Event Report: PearlHacks" (decause, 16:59:42)
* jflory7 will be spending extra time on CommBlog backlog this week to
edit existing drafts and get them out and published (jflory7,
17:02:00)
* puiterwijk helped deploy the new CDN from our sponsor for the
Community Blog and Fedora Magazine today. As of now, this helps
lighten the traffic load on the WordPress machines and helps keep
the websites running strong with increased loads! (jflory7,
17:06:41)
* Release Schedule (jflory7, 17:08:21)
* LINK:
https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html
(jflory7, 17:08:26)
* Final Release Public Availability (GA) Tue 2016-06-21
(jflory7, 17:08:37)
* Fedora 22 EOL auto closure Tue 2016-07-19 (jflory7, 17:08:51)
* IDEA: A CommBlog article for F22 EoL would be a good one to have
(jflory7, 17:09:01)
* ACTION: jflory7 Create a placeholder article for F22 EoL article in
CommBlog so we keep on the agenda (jflory7, 17:09:20)
* Open Floor (jflory7, 17:10:49)
* ACTION: jflory7 Prepare the hack session ticket and CC dhanesh95 so
he gets context to what they are for a CommBlog article (jflory7,
17:12:38)
* Hack session slated to begin in approximately 45 minutes from the
time of this message being sent! (jflory7, 17:13:06)
* === Vector (based off of Matrix) === (jflory7, 17:15:15)
* LINK: https://matrix.org/ (jflory7, 17:15:29)
* LINK: https://vector.im/ (jflory7, 17:15:35)
* Vector is a handy audio/video communication platform that can be
used for text, audio, and video conversations. It's all FOSS (based
off of Matrix) and has support for iOS and Android devices too. Also
works with file transfers if needed during a call and supports
end-to-end crypto. (jflory7, 17:16:34)
Meeting ended at 17:20:30 UTC.
Action Items
------------
* decause review the vFAD goals / objectives / etc.
* decause nail down Flock arrangements and add to fedocal
* jflory7 Open a ticket to look into drafting an (automated?) check-in
email with members of CommOps to determine activity
* decause Drop a line to the devel list to have anyone going to Red Hat
Summit add their info to the wiki page
* jflory7 Don't forget to bring up Vector / Matrix.org later on this
meeting, during open floor
* jflory7 Write up an initial draft of a wiki page outlining the process
for Ambassadors specifically to request assets from the Design Team,
include plans to reach out to regional Ambassadors from all regions
with this information later
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
* jflory7 Get on top of editing this week and schedule some of these
articles for this / next week, reply back to authors waiting for a
response
* jflory7 Create a placeholder article for F22 EoL article in CommBlog
so we keep on the agenda
* jflory7 Prepare the hack session ticket and CC dhanesh95 so he gets
context to what they are for a CommBlog article
Action Items, by person
-----------------------
* commops
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
* decause
* decause review the vFAD goals / objectives / etc.
* decause nail down Flock arrangements and add to fedocal
* decause Drop a line to the devel list to have anyone going to Red
Hat Summit add their info to the wiki page
* dhanesh95
* jflory7 Prepare the hack session ticket and CC dhanesh95 so he gets
context to what they are for a CommBlog article
* jflory7
* jflory7 Open a ticket to look into drafting an (automated?) check-in
email with members of CommOps to determine activity
* jflory7 Don't forget to bring up Vector / Matrix.org later on this
meeting, during open floor
* jflory7 Write up an initial draft of a wiki page outlining the
process for Ambassadors specifically to request assets from the
Design Team, include plans to reach out to regional Ambassadors from
all regions with this information later
* jflory7 Get on top of editing this week and schedule some of these
articles for this / next week, reply back to authors waiting for a
response
* jflory7 Create a placeholder article for F22 EoL article in CommBlog
so we keep on the agenda
* jflory7 Prepare the hack session ticket and CC dhanesh95 so he gets
context to what they are for a CommBlog article
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jflory7 (326)
* zodbot (74)
* decause (71)
* skamath (46)
* dhanesh95 (30)
* GIANT_CRAB (26)
* sayan (14)
* c0mrad3 (13)
* trishnag (13)
* x3mboy (11)
* devyani7 (10)
* linuxmodder (5)
* Southern_Gentlem (5)
* puiterwijk (5)
* jzb (2)
* commops (0)
* devhen (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 10 months
Re: [Marketing] [Need info] Fedora QA Series
by Matthew Miller
On Tue, Jun 21, 2016 at 07:04:59AM -0400, Sumantro Mukherjee wrote:
> In the last couple of week , Fedora QA email list is having new
> contributors coming in and many of them have made it to the mailing
> list after reading the first part of the article which was posted on
> the fedora community blog . Thanks for publishing . As the new comers
> are looking for the part 2 and part 3 and have asked me quite a
> number of times about it. I am requesting if someone can shed some
> light on when is the probable date when we can have it published in
> the community blog.Since,these are new contributors we would like to
> increase their involvement with Fedora QA by helping them out with
> the blogs and not delay it for long.
>
The community blog isn't a marketing project, really -- it's Community
Operations (or "CommOps"). I've CC'd that list. The process there
should be relatively lightweight.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
7 years, 10 months
Re: [fedora-badges] #464: CommOps Onboarding Series Badge
by fedora-badges
#464: CommOps Onboarding Series Badge
-------------------------------------+-------------------------------------
Reporter: skamath | Owner:
Type: New badge | skamath
idea | Status:
Priority: minor | new
Keywords: commops | Resolution:
Has a description: 1 | Has a name:
Artwork status: Concept | 1
External requirements: | Concept approved (reviewers only):
Triaged (triagers only): 1 | 0
| Badge definition status:
| Full, needs review
| Manually awarded:
| 0
-------------------------------------+-------------------------------------
Changes (by jflory7):
* has_complete_yaml: None => Full, needs review
Comment:
'''Badge automation ideas discussed in CommOps
[https://meetbot.fedoraproject.org/fedora-
meeting/2016-06-14/commops.2016-06-14-15.58.html 2016-06-14 meeting].'''
In our meeting, we decided it would be best to have the approval be based
off of the FAS group sponsorship, which is an easier one to write and we
know it is a less expensive operation. It also makes it a little more
human-verifiable as well.
I created the YAML file (and a patch for it) to add the badge rule to the
official repository. Note, as of now, the YAML + patch assumes the badge
name is "Dialed In". This obviously easy to change later if we decide to
use the other suggestion.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/464#comment:2>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 10 months
