Hi all,
I have been contributing to hubs for some time now and was helping
out new contributors recently. En route I found that many new contributors
are facing some trivial issues while setting up the Hubs environment, so
I have drafted a post[1] explaining what Hubs is, giving an in-depth idea
how one
can start contributing to hubs and widgets. Also, explanation of a few known
issues which might crawl up when one is setting up Hubs.
[1] https://fedoramagazine.org/fedora-hubs-getting-started
<https://fedoramagazine.org//>/
Thanking You,
Devyani Kota
--
[image: --]
Devyani Kota
[image: https://]about.me/devyanikota
<http://t.sidekickopen63.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XZs1…>
Hey CommOps! Today's meeting was another rollercoaster - here's a quick
recap of what we covered!
We spent some time revisiting an older ticket on elections. Based on
feedback and comparisons from the Dec. 2015 and July 2016 elections as
well as feedback from Flock, we have some ideas we want to share. These
will be posted in the ticket later this week.
We also covered on-boarding topics for both the QA team and the Python
SIG. Thanks a2batic, sumantro, and mhroncok for the feedback and
suggestions! We're trying to make ground on the Bugzilla datagrepper
queries and new badge tickets. The Python SIG wiki page is also being
rewritten and introducing the possibility of two FAS groups for the SIG.
We also discussed an older ticket on "owning" the release announcement
process. tl;dr: we shouldn't "own" the process, but we should help with
improving communication by generating a template for working groups and
SIGs to fill in.
Finally, please check out this ticket about a new meeting time! We met
at this time today, but I want to give everyone a chance to review this
before Thursday afternoon.
https://pagure.io/fedora-commops/issue/86
Thanks everyone! Feels like we're getting back into a rhythm again. :)
Hopefully we can get hack sessions up and rolling again soon as well.
= = = = =
Meeting ended Tue Sep 6 17:58:22 2016 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2016-09-06/commops.2016-09…
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2016-09-06/commops.2016-09…
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2016-09-06/commops.2016-09…
* * * * *
============================================
#fedora-meeting: Fedora CommOps (2016-09-06)
============================================
Meeting started by jflory7 at 16:25:00 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-09-06/commops.2016-09…
.
Meeting summary
---------------
* Agenda (jflory7, 16:25:19)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-09-06
(jflory7, 16:25:25)
* (1) Roll Call / Q&A (jflory7, 16:25:30)
* (2) Announcements (jflory7, 16:25:34)
* (3) Action items from last meeting (jflory7, 16:25:39)
* (4) Tickets (jflory7, 16:25:44)
* (5) Wiki Gardening (jflory7, 16:25:49)
* (6) Community Blog (jflory7, 16:25:53)
* (7) Release Schedule (jflory7, 16:25:58)
* (8) Open Floor (jflory7, 16:26:04)
* Roll Call / Q&A (jflory7, 16:26:15)
* Name; Timezone; Sub-projects/Interest Areas (jflory7, 16:26:15)
* ACTION: commops New members, make sure you introduce yourself on the
CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
(jflory7, 16:26:22)
* Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors,
Diversity Team, Join SIG, sysadmin-badges, and more (jflory7,
16:26:48)
* Dhanesh B. Sabane; UTC+5:30; CommOps, RPM Packaging, ML, Linux
Kernel, Python (dhanesh95, 16:27:36)
* Sachin S. Kamath; UTC +5.30 ; GSoC, Metrics, CommOps (skamath,
16:28:22)
* Announcements (jflory7, 16:34:54)
* === [Reminder] CommOps has moved to Pagure === (jflory7, 16:35:00)
* LINK: https://pagure.io/fedora-commops (jflory7, 16:35:05)
* All of our tickets and data from Trac was migrated to Pagure last
week. We will no longer use Trac for task management / tickets.
Please sign into Pagure with your FAS account and check out the
repository if you have not done so yet! (jflory7, 16:35:11)
* === "Announcing the release of Fedora 25 Alpha!" === (jflory7,
16:35:31)
* LINK:
https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.…
(jflory7, 16:35:36)
* The Fedora Project is pleased to announce the availability of the
Fedora 25 Alpha, an important milestone on the road to our Fedora 25
release in November. (jflory7, 16:35:43)
* === "Welcoming our new Fedora Community Action and Impact
Coordinator" === (jflory7, 16:35:48)
* LINK:
https://fedoramagazine.org/welcoming-new-fedora-community-coordinator/
(jflory7, 16:35:53)
* "Good news, everybody! I’m pleased to announce that we have
completed our search for a new Fedora Community Action and Impact
Coordinator, and he’ll be joining the Open Source and Standards
(OSAS) team to work with Fedora as of 3 October. Please give a warm
welcome to Brian Exelbierd (bexelbie)!" (jflory7, 16:36:00)
* === "Keeping Fedora beautiful: contribute your wallpaper!" ===
(jflory7, 16:36:11)
* LINK:
https://fedoramagazine.org/keeping-fedora-beautiful-contribute-wallpaper/
(jflory7, 16:36:16)
* The Fedora 25 supplementary wallpaper dropbox is now open. Submit up
to two wallpapers to be voted on by the Fedora community for
inclusion in F25 supplementary wallpapers! A great way to
participate in the Fedora release process. (jflory7, 16:36:22)
* Action items from last meeting (jflory7, 16:37:34)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-30/commops.2016-08…
(jflory7, 16:37:39)
* 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:37:45)
* === [IN PROGRESS] jflory7 bee2502 Take workshop feedback and parse
it into more accessible data (e.g. tickets / commits / CommBlog
posts / metrics / etc.) === (jflory7, 16:37:52)
* ACTION: jflory7 bee2502 Take workshop feedback and parse it into
more accessible data (e.g. tickets / commits / CommBlog posts /
metrics / etc.) (jflory7, 16:38:00)
* === [COMPLETE] jflory7 Review emails for pending posts on the
CommBlog === (jflory7, 16:38:07)
* ACTION: jflory7 Review emails for pending posts on the CommBlog
(jflory7, 16:38:14)
* === [INCOMPLETE] jflory7 Update Community Blog writing guide for
writing a new article based on what's actually happening in 2016 now
=== (jflory7, 16:38:33)
* ACTION: jflory7 Update Community Blog writing guide for writing a
new article based on what's actually happening in 2016 now
(jflory7, 16:38:40)
* === [INCOMPLETE] jflory7 Sort through ideas on reviewing old
contributor discussion, form proposals in the ticket, share at next
meeting === (jflory7, 16:38:48)
* ACTION: jflory7 Sort through ideas on reviewing old contributor
discussion, form proposals in the ticket, share at next meeting
(jflory7, 16:38:56)
* === [INCOMPELTE] skamath File a ticket in Fedora Infra Trac for
proposing an official migration from fedora-infra GitHub
organization into Pagure === (jflory7, 16:39:06)
* ACTION: skamath File a ticket in Fedora Infra Trac for proposing an
official migration from fedora-infra GitHub organization into Pagure
(jflory7, 16:39:13)
* ACTION: jflory7 bee2502 Arrange for some personal hacking to close
out Flock items (jflory7, 16:42:37)
* === [COMPLETE] skamath 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:42:44)
* LINK: https://pagure.io/fedora-commops/issue/82 (jflory7,
16:42:45)
* === [COMPLETE] jflory7 Follow up on Pagure importer tool for use
with decause's CommOps toolbox repositories === (jflory7, 16:42:55)
* LINK: https://pagure.io/fedora-commops/issue/82 (jflory7,
16:42:56)
* === [COMPLETE] jflory7 Remove Ticket #81 from meeting agenda ===
(jflory7, 16:43:01)
* === dhanesh95 Start IRC / mailing list discussion on wiki gardening
for Python SIG === (jflory7, 16:43:08)
* ACTION: dhanesh95 Start mailing list discussion on wiki page changes
for Python SIG (jflory7, 16:45:08)
* === [COMPLETE] jflory7 Do some srs ticket triaging / updating this
week === (jflory7, 16:45:14)
* The CommOps Pagure is completely triaged and migrated to work well
in Pagure versus Trac (jflory7, 16:45:22)
* === [COMPLETE] amitsin6h Double-check subscription to the mailing
list and make sure you are receiving mail from the list ===
(jflory7, 16:45:33)
* === [COMPLETE] jflory7 Come up with a more fitting introductory item
to place into the meeting === (jflory7, 16:45:45)
* === [COMPLETE] jflory7 Revisit Join page and edit / alter section
about wiki page === (jflory7, 16:46:30)
* LINK: https://fedoraproject.org/wiki/CommOps/Join (jflory7,
16:46:36)
* === [COMPLETE] skamath Garden the CommOps wiki page to remove
mention of Trac and replace with Pagure (and update hyperlinks) ===
(jflory7, 16:46:57)
* LINK: https://fedoraproject.org/wiki/CommOps (jflory7, 16:47:03)
* LINK: https://fedoraproject.org/wiki/CommOps/Join (jflory7,
16:47:06)
* === [COMPLETE] downey Migrate the member table from
https://fedoraproject.org/wiki/CommOps#Interest_Areas to
https://fedoraproject.org/wiki/CommOps/Members === (jflory7,
16:47:10)
* LINK: https://fedoraproject.org/wiki/CommOps/Members (jflory7,
16:47:15)
* Tickets (jflory7, 16:47:55)
* LINK: https://pagure.io/fedora-commops/issues?tags=meeting
(jflory7, 16:48:04)
* === Ticket #19 === (jflory7, 16:48:17)
* "Improve automation of Elections communication" (jflory7, 16:48:24)
* LINK: https://pagure.io/fedora-commops/issue/19 (jflory7,
16:48:31)
* LINK: https://etherpad.gnome.org/p/flock-2016-commops-workshop
(jflory7, 16:50:39)
* IDEA: New ways to encourage questions: Utilizing social media as a
way for the user community to participate in the elections, comments
on Community Blog for taking questions (jflory7, 16:53:09)
* IDEA: 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 (jflory7,
16:53:59)
* IDEA: 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 (jflory7,
16:54:41)
* IDEA: "I voted!" badge: Awarding the badge during / after election,
utilizing fedmsg to deliver the badge, one or per release cycle
(jflory7, 16:55:12)
* IDEA: Sending statistics related to voting metrics daily to improve
voter turnout and keep contributors engaged (jflory7, 16:55:38)
* ACTION: bee2502 jflory7 Work on moving election-specific information
from Flock into ticket #19, share with jkurik after (jflory7,
16:59:54)
* LINK: http://limesurvey.org/ (skamath, 17:01:52)
* === Ticket #34, 52, 84 === (jflory7, 17:02:36)
* #34: "[Onboarding Series] [MASTER TICKET] Creating sub-project
on-boarding badge series"; #52: "Quality Assurance"; #84: "Python
SIG" (jflory7, 17:02:42)
* LINK: https://pagure.io/fedora-commops/issue/34 (jflory7,
17:02:48)
* LINK: https://pagure.io/fedora-commops/issue/52 (jflory7,
17:02:51)
* LINK: https://pagure.io/fedora-commops/issue/84 (jflory7,
17:02:56)
* HELP: Need info and research on writing datagrepper queries with
Bugzilla hooks to be used for badge series on filing bugs (1 bug =
badge, 5 bugs = badge, etc.) (jflory7, 17:03:08)
* ACTION: skamath Research Bugzilla datagrepper queries for new bug
report tickets (jflory7, 17:09:33)
* ACTION: sumantro a2batic File tickets in Fedora Badges Trac for
filing Bugzilla bugs, for completing release validation testing, and
getting sponsored to the QA group (jflory7, 17:13:00)
* LINK: https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
(jflory7, 17:16:20)
* LINK: https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python/Join
(jflory7, 17:16:25)
* IDEA: Two FAS groups for Python: python-sig for interested members
contributing to Python in Fedora, python-packagers for proven
members of the community who can receive security-related bugs
(jflory7, 17:24:23)
* ACTION: dhanesh95 Make changes to Python SIG pages based on
feedback, post to python-devel mailing list requesting feedback on
the rewrites, explain idea of splitting Python SIG into two FAS
groups (python-sig for interested members, python-packagers for
security-related bugs / pushing to packages git) (jflory7,
17:27:54)
* === Ticket #67 === (jflory7, 17:28:42)
* "[Objective] Owning the Release Announcements Process" (jflory7,
17:28:47)
* LINK: https://pagure.io/fedora-commops/issue/67 (jflory7,
17:29:02)
* IDEA: Using a single format for fill-in-the-blank type of
information gathering for use by all involved working groups / SIGs
(jflory7, 17:38:01)
* IDEA: Using a Pagure repo to centralize this information over the
wiki (jflory7, 17:38:13)
* AGREED: Focus on developing a single format to be used to collect
info from all involved working groups / SIGs (e.g. fill-in-the-blank
sort of template as much as possible) (jflory7, 17:41:10)
* === Ticket #86 === (jflory7, 17:41:23)
* "Adjust meeting time by 30 minutes" (jflory7, 17:41:30)
* LINK: https://pagure.io/fedora-commops/issue/86 (jflory7,
17:41:34)
* ACTION: skamath dhanesh95 sumantro Leave vote in ticket #86 for
revised meeting time (jflory7, 17:43:08)
* ACTION: jflory7 Close ticket #86 no sooner than 2016-09-08
(jflory7, 17:43:29)
* Wiki Gardening (jflory7, 17:43:45)
* Community Blog (jflory7, 17:45:02)
* 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:45:08)
* === This Week in CommBlog === (jflory7, 17:45:15)
* (1) "Fedora 24 Release Party in Singapore" (jflory7, 17:45:19)
* LINK:
https://communityblog.fedoraproject.org/fedora-24-release-party-singapore/
(jflory7, 17:45:25)
* Total Views (Aug. 24 - Sep. 5): 100 (jflory7, 17:45:31)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=…
(jflory7, 17:45:37)
* (2) "Modularity Infrastructure Design" (jflory7, 17:45:47)
* LINK:
https://communityblog.fedoraproject.org/modularity-infrastructure-design/
(jflory7, 17:45:52)
* Total Views (Aug. 25 - Sep. 5): 109 (jflory7, 17:45:56)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=…
(jflory7, 17:46:03)
* (3) "Globalization improvements in Fedora 24" (jflory7, 17:46:09)
* LINK:
https://communityblog.fedoraproject.org/globalization-improvements-fedora-2…
(jflory7, 17:46:15)
* Total Views (Aug. 30 - Sep. 5): 383 (jflory7, 17:46:21)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=…
(jflory7, 17:46:27)
* (4) "FOSS Wave: Delhi, India" (jflory7, 17:46:39)
* LINK: https://communityblog.fedoraproject.org/foss-wave-delhi-india/
(jflory7, 17:46:45)
* Total Views (Aug. 31 - Sep. 5): 26 (jflory7, 17:46:57)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=…
(jflory7, 17:46:57)
* IDEA: Social media booster on FOSS Wave tag for all articles in this
series? (jflory7, 17:47:11)
* (5) "Say no to wiki SPAM!" (jflory7, 17:47:16)
* LINK: https://communityblog.fedoraproject.org/say-no-to-wiki-spam/
(jflory7, 17:47:21)
* Total Views (Sep. 1 - Sep. 5): 89 (jflory7, 17:47:26)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=…
(jflory7, 17:47:31)
* (6) "Want to be Fedora contributor? Start with Fedora 25 translation
sprint!" (jflory7, 17:47:48)
* LINK:
https://communityblog.fedoraproject.org/fedora-25-translation-sprint/
(jflory7, 17:47:58)
* Total Views (Sep. 2 - Sep. 5): 327 (jflory7, 17:48:02)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=…
(jflory7, 17:48:07)
* (7) "FUDCon Phnom Penh: Call for Papers" (jflory7, 17:48:20)
* LINK:
https://communityblog.fedoraproject.org/fudcon-phnom-penh-call-for-papers/
(jflory7, 17:48:25)
* Total Views (Sep. 3 - Sep. 5): 81 (jflory7, 17:48:35)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=…
(jflory7, 17:48:41)
* (8) "FOSS Wave: Women in Technology (Part 2)" (jflory7, 17:48:50)
* LINK:
https://communityblog.fedoraproject.org/foss-wave-women-in-technology-part-…
(jflory7, 17:48:54)
* Total Views (Sep. 5): 30 (jflory7, 17:49:00)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=…
(jflory7, 17:49:05)
* === Coming Up in CommBlog === (jflory7, 17:49:13)
* (1) "Event Report: WWFS-FWD’2016, Kolkata " (jflory7, 17:49:20)
* LINK:
https://communityblog.fedoraproject.org/?p=2046&preview=1&_ppp=4423883c9d
(jflory7, 17:49:25)
* (2) "Onboarding Kickoff – Fedora QA, Bhopal" (jflory7, 17:49:30)
* LINK:
https://communityblog.fedoraproject.org/?p=2188&preview=1&_ppp=f0ebdc1766
(jflory7, 17:49:34)
* (3) "FOSS and Fedora #FOSS Wave BLR IN" (jflory7, 17:49:40)
* LINK:
https://communityblog.fedoraproject.org/?p=2282&preview=1&_ppp=17dea148f1
(jflory7, 17:49:45)
* (4) "Fedora 24 release party in Paris" (jflory7, 17:49:51)
* LINK:
https://communityblog.fedoraproject.org/?p=2380&preview=1&_ppp=f15bf599d2
(jflory7, 17:49:56)
* Release Schedule (jflory7, 17:51:40)
* LINK:
https://fedorapeople.org/groups/schedule/f-25/f-25-key-tasks.html
(jflory7, 17:51:44)
* (1) Beta Freeze (Tue 2016-09-27, 00:00 UTC) (jflory7, 17:52:05)
* (2) Beta Release Public Availability (Tue 2016-10-11) (jflory7,
17:52:23)
* Open Floor (jflory7, 17:52:46)
* LINK: https://communityblog.fedoraproject.org/feed/ (skamath,
17:55:39)
* HELP: Community Blog should be sending out email notifications to
subscribers - related to Magazine problems as well? (jflory7,
17:55:44)
Meeting ended at 17:58:22 UTC.
Action Items
------------
* commops New members, make sure you introduce yourself on the CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* 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 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
* jflory7 bee2502 Arrange for some personal hacking to close out Flock
items
* dhanesh95 Start mailing list discussion on wiki page changes for
Python SIG
* bee2502 jflory7 Work on moving election-specific information from
Flock into ticket #19, share with jkurik after
* skamath Research Bugzilla datagrepper queries for new bug report
tickets
* sumantro a2batic File tickets in Fedora Badges Trac for filing
Bugzilla bugs, for completing release validation testing, and getting
sponsored to the QA group
* dhanesh95 Make changes to Python SIG pages based on feedback, post to
python-devel mailing list requesting feedback on the rewrites, explain
idea of splitting Python SIG into two FAS groups (python-sig for
interested members, python-packagers for security-related bugs /
pushing to packages git)
* skamath dhanesh95 sumantro Leave vote in ticket #86 for revised
meeting time
* jflory7 Close ticket #86 no sooner than 2016-09-08
Action Items, by person
-----------------------
* a2batic
* sumantro a2batic File tickets in Fedora Badges Trac for filing
Bugzilla bugs, for completing release validation testing, and
getting sponsored to the QA group
* bee2502
* jflory7 bee2502 Take workshop feedback and parse it into more
accessible data (e.g. tickets / commits / CommBlog posts / metrics /
etc.)
* jflory7 bee2502 Arrange for some personal hacking to close out Flock
items
* bee2502 jflory7 Work on moving election-specific information from
Flock into ticket #19, share with jkurik after
* commops
* commops New members, make sure you introduce yourself on the CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* dhanesh95
* dhanesh95 Start mailing list discussion on wiki page changes for
Python SIG
* dhanesh95 Make changes to Python SIG pages based on feedback, post
to python-devel mailing list requesting feedback on the rewrites,
explain idea of splitting Python SIG into two FAS groups (python-sig
for interested members, python-packagers for security-related bugs /
pushing to packages git)
* skamath dhanesh95 sumantro Leave vote in ticket #86 for revised
meeting time
* jflory7
* 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 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
* jflory7 bee2502 Arrange for some personal hacking to close out Flock
items
* bee2502 jflory7 Work on moving election-specific information from
Flock into ticket #19, share with jkurik after
* jflory7 Close ticket #86 no sooner than 2016-09-08
* skamath
* skamath File a ticket in Fedora Infra Trac for proposing an official
migration from fedora-infra GitHub organization into Pagure
* skamath Research Bugzilla datagrepper queries for new bug report
tickets
* skamath dhanesh95 sumantro Leave vote in ticket #86 for revised
meeting time
* sumantro
* sumantro a2batic File tickets in Fedora Badges Trac for filing
Bugzilla bugs, for completing release validation testing, and
getting sponsored to the QA group
* skamath dhanesh95 sumantro Leave vote in ticket #86 for revised
meeting time
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jflory7 (329)
* skamath (77)
* dhanesh95 (39)
* zodbot (25)
* mhroncok (18)
* bee2502 (13)
* sumantro (9)
* FranciscoD (9)
* x3mboy (4)
* c0mrad3 (2)
* a2batic (2)
* a2batic_ (2)
* trishnag (1)
* mailga (1)
* commops (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
Dear all,
You are kindly invited to the meeting:
CommOps IRC Meeting on 2016-09-06 from 12:00:00 to 13:30:00 US/Eastern
At fedora-meeting(a)irc.freenode.net
The meeting will be about:
This meeting is for team members of the Community Operations (CommOps) team. The weekly agenda is mostly comprised of the different tasks detailed on the CommOps wiki page, although it is subject to change depending on time and context of what is going around the Fedora Project.
More information can be found on the [wiki page](https://fedoraproject.org/wiki/CommOps).
Source: https://apps.fedoraproject.org/calendar/meeting/4409/
Dear all,
You are kindly invited to the meeting:
Fedora Hubs Weekly Check-in on 2016-09-06 from 10:00:00 to 11:00:00 US/Eastern
At fedora-hubs(a)irc.freenode.net
The meeting will be about:
The Fedora Hubs team meets up once a week to check in on development status of Fedora Hubs, work through issues, and make progress on development. Current developers and anyone interested in developing for Hubs are encouraged to attend.
You can find the source code on http://pagure.io/fedora-hubs
More information available at:
[https://fedoraproject.org/wiki/Fedora_Hubs](https://fedoraproject.org/wiki/…
Source: https://apps.fedoraproject.org/calendar/meeting/3863/
Hey all,
An interesting link I found earlier over the weekend about what seems to
be an on-going research report / analysis into open source communities,
their demographics, and more. A report on the data is in progress, but
for now, a copy of the questionnaire used is available along with dumps
of the raw dataset for importing into R or LimeSurvey.
Thought this could be a useful asset or tool for later learning. :)
http://floss2013.libresoft.es/results.en.html
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
#414: Badges for Community Blog authors
-------------------------------------+-------------------------------------
Reporter: bee2502 | Owner:
Type: New badge | maryshak1996
idea | Status:
Priority: minor | reopened
Keywords: | Resolution:
Has a description: 1 | Has a name:
Artwork status: Proposed | 1
External requirements: | Concept approved (reviewers only):
Triaged (triagers only): 1 | 1
| Badge definition status:
| Approved (badges admins only)
| Manually awarded:
| 1
-------------------------------------+-------------------------------------
Comment (by churchyard):
Replying to [comment:46 maryshak1996]:
> I just attached a zip with .svgs and .pngs for the updates mentioned
above for the whole series
It's not there.
Also, please attach pngs directly and display them in the comment, so it's
easier for everybody involved to see them.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/414#comment:47>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#414: Badges for Community Blog authors
-------------------------------------+-------------------------------------
Reporter: bee2502 | Owner:
Type: New badge | maryshak1996
idea | Status:
Priority: minor | reopened
Keywords: | Resolution:
Has a description: 1 | Has a name:
Artwork status: Proposed | 1
External requirements: | Concept approved (reviewers only):
Triaged (triagers only): 1 | 1
| Badge definition status:
| Approved (badges admins only)
| Manually awarded:
| 1
-------------------------------------+-------------------------------------
Comment (by maryshak1996):
I just attached a zip with .svgs and .pngs for the updates mentioned above
for the whole series
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/414#comment:46>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
Hi all,
I have prepared a patch for aarch64 platform mozjs based on its trunk.
But i also want to push the patch into Fedora next release. What's the
process for doing it?
Thanks