Self-Introduction
by Yajushi Srivastava
Hello Team,
I'm a final year undergraduate, pursuing Computer Science Engineering from
a private college in Jaipur, India. I have been training in Linux System
Administration for over a year. Apart from that, I have been working with
OpenStack, AWS and DevOps technologies like Docker and Ansible.
I have always been a FOSS/OSS enthusiast because I believe in the scenic
genius of Sapiens. It’s crucial for us to collaborate, in order to grow,
and Open Source does just that. It provides us with a liberal way to share
and to know. Despite our possible differences in political ideologies,
beliefs, race and administrative boundaries. We are all bound by our love
of technology.
I have used several Linux distributions, but it’s in Fedora that I found my
haven. I love contributing to Open Source, in whichever way I can. I would
like to take my skills to reach out to as many people as I can, and share
Fedora with them. And, in sharing, I know that I’ll come across essentials
that I may have overlooked in the past.
I believe I am an empathetic and creative person. I love knowing people and
their stories, and I believe that everyone is inspirational and has
limitless potential. I would like to put my skills to use by being a part
of CommOps.
I’m not yet involved with other things in Fedora. But I’d like to be a part
of the Fedora Ambassadors Project. There are several people working on
Linux in and around my city, in one way or the other, but often in
isolation. And, I would like to encourage collaboration and introduce them
to our global community.
I represent Docker’s Jaipur Chapter as the Community Leader, and PyJaipur
(Official Local Python User’s Group) as the Content Management Lead.
I see CommOps as crucial for people involved in Fedora to keep track of the
several projects, making the contribution and collaboration process
feasible. I also appreciate how CommOps connects people with stories beyond
work, through acknowledgement programs and interviews.
I look forward to understanding Community Health Monitoring in detail.
As far as the questions go, a lot IRC lurking may be required. However, it
would be great if somebody could help me get started with my first task.
Thanks.
Yajushi Srivastava
4 years, 11 months
Introducing myself
by Harshit Modi
Hi CommOps Team,
I am Harshit Modi. I am interested in getting involved in the Fedora
community by contributing to the Fedora CommOps. As Fedora CommOps deals
with all other fedora projects, it will provide me good opportunity to work
closely with all the community.
I am current graduate student at UT Arlington with computer science major.
I have 2 years of experience in web development. I have proper knowledge in
web stack and had used many open source technologies. As I move forward in
my career, I want to dig into more in open source projects. And for that I
want to join such project and learn from the highly motivated community.
Fedora is well known in open source world and has diverse fields to work
with. And CommOps has many active contributors and joining them will help
me jump on board and become the part of fedora community. So I am confident
that this opportunity will benefit us both.
Please let me know if you need any additional information. Thanks!
Regards,
Harshit Modi
https://www.linkedin.com/in/harshit-modi/
4 years, 11 months
Easyfix + WhatCanIDoForFedora
by Brian Exelbierd
I started writing this a while ago and never got it fully formed. Rather than let it keep rotting in my drafts folder I wanted to share it and see if it made sense to anyone else.
Warning - rough edges ahead!
---
Conversations with several people have resulted in distilling the following idea:
= EasyFix
== Changing metadata
Modify the table that drives fedoraproject.org/easyfix that is located at https://fedoraproject.org/wiki/Easyfix
The table would now include two additional columns (optional)
Col 1 = existing reference to the issue tracker. We should consider adding gitlab.com support
Col 2 = existing point of contact
Col 3 = category of task (documentation, infrastructure, programming-Haskell, programming-Ruby, etc.)
Col 4 = SIG/WG/etc. this project is related too (Design, Council, KDE, etc.)
== Changing fedoraproject.org/easyfix
Today we show only two categories: Issues from Pagure/Github and Bugzillas
I believe those categories are not the right categories for consumers of the page. Using the new category (col 3) above, we would break things out by the kind of contribution. This would serve to let people browse related tasks more easily and to reduce the overwhelming nature of the current lists.
For BZs we are either going to have to guess based on BZ metadata or leave them lumped together.
= WCIDFF
WCDIFF should be extended to show the categories and groups appropriate for the various endpoints. This way the person who navigates WCDIFF has the option of reading a specific task they could work on right now, if they so desire.
= Marketing/Promotion
The categories give us the opportunity to promote our easyfixes as a great way to join or contribute in a targeted manner. This could come in the form of articles, tweets, or live conference appearances.
What do people think?
regards,
bex
4 years, 11 months
Re: [badges] Event Badges - Policy Discussion
by Justin W. Flory
Hi! I've been thinking about this thread for a while.
This is great feedback and I wonder how we could try to improve the
contributing experience for Fedora Badges. In 2015, an early idea was to
equip CommOps to work with the Design Team on creating and establishing
badge policy and strategy. Perhaps we could revisit this again.
I'd like to figure out where we can begin tracking this feedback and
organize an effort to address some of these.
(One example on my mind is hosting a docs.fedoraproject.org page on
Fedora Badges to explain policy and badge rules. It could also be a "new
home" for the style guide.)
On 8/18/18 9:57 AM, Marie Nordin wrote:
> Hello All!
>
> I am opening up this thread to discuss event badges-- I think it would
> be helpful to brainstorm and finalize some standards/regulations
> regarding event badges with the input from leadership, design, and
> development side. I will do my best to list all the different
> thoughts/issues that have been raised. Please feel free to jump in with
> other points and/or correct if I don't have the latest info.
>
> _*Current policy:*_
> - 1 event badge per event (non Fedora, or Fedora)
> - 3 event badges per Flock
> - attendee
> - contributor
> - party attendee
> - 1 event badge per Fudcon
> - attendee
> - in the past we have also had speaker/organizer badges
>
> _*Common issues we encounter:*_
> - People pointing to older badges and asking why we don't make them any more
> - I actually haven't seen this as much lately, but have in the past
> - People not knowing what or where to find a policy regarding event
> badges. People pose potential badges, and we have to turn them down.
> - From creation/pushing to site aspect, not getting enough notice that
> an event badge is needed, or it gets lost in a sea of update emails
> (best to request an event badge at least 1-1.5 months in advance, so we
> can see & address at a badges meeting (held bi-weekly unless something
> comes up)). Then there is time for gathering of resources (logos),
> creation of artwork, and pushing to site.
>
> _*Outdated badges:*_
> - We have old speaker/organizer badges. Do we want to remove those and
> replace them with the new contributor badges? Would this be too big an
> effort for the outcome?
>
> _*New ideas:*_
> - Fedora meet up badge - IMHO, if we created this it should just be one
> badge overall that is used for multiple events? Or yearly, so "you
> attended a fedora meet up in 2018" I think this is a great idea for
> people who are unable to make it to some of the larger conferences,
> giving them a chance to earn event badges. On the other side, those
> privileged to go to the larger badges will most likely earn these as
> well. https://pagure.io/fedora-badges/issue/641
> - Non-Fedora badges - this idea made by Bex on issue 642. I would be
> interested to hear more about what this would entail and how to
> implement. https://pagure.io/fedora-badges/issue/642
>
> _*More Thoughts:*_
> - Why did we move from speaker/organizer badges to contributor badges?
> Who made this decision and why?
> - A note here is that I am fine with this policy, I am just curious how
> this decision came about, and why it wasn't really finalized
> "officially" and discussed with the badges team as a whole. I think it
> was announced on a badge issue, and we then had to adapt.
>
>
> That is all I have for now. I think it would be great if we had input on
> these thoughts, and any others, from all the people who makes badges
> happen :)
>
> Best,
> - riecatnor
>
>
> _______________________________________________
> Fedora Badges mailing list -- badges(a)lists.fedoraproject.org
> To unsubscribe send an email to badges-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/badges@lists.fedoraproject....
>
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
5 years
[Meeting] [2018-09-26] Discourse migration
by Justin W. Flory
The weekly CommOps meeting came to an end a bit ago. We were low
bandwidth so it was a quick meeting. We covered the following:
* Currently on target for Appreciation Week in November
* Discourse migration beginning next Monday
Thanks everyone for participating – see you around IRC or elsewhere.
= = = = =
Meeting ended Wed Sep 26 16:40:37 2018 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-commops/2018-09-26/commops.2018-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-commops/2018-09-26/commops.2018-...
Log:
https://meetbot.fedoraproject.org/fedora-commops/2018-09-26/commops.2018-...
* * * * *
============================================
#fedora-commops: Fedora CommOps (2018-09-26)
============================================
Meeting started by jwf at 16:08:35 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-commops/2018-09-26/commops.2018-...
.
Meeting summary
---------------
* Agenda (jwf, 16:08:43)
* LINK:
https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/f...
(jwf, 16:08:47)
* (1) Roll call / Q&A (jwf, 16:08:50)
* (2) Announcements (jwf, 16:08:52)
* (3) Action items from last meeting (jwf, 16:08:54)
* (4) Tickets (jwf, 16:08:56)
* (5) Open floor (jwf, 16:08:58)
* Roll call / Q&A (jwf, 16:09:02)
* Name; Timezone; Sub-projects/Interest Areas (jwf, 16:09:04)
* ACTION: commops New members, please introduce yourself on the
CommOps mailing list [
https://docs.fedoraproject.org/en-US/commops/contribute/join/ ]
(jwf, 16:09:08)
* Justin W. Flory; UTC-5; CommOps, D&I Team, Mindshare (for a month
more), Fedora Badges sysadmin (jwf, 16:09:34)
* Ben Cotton; UTC-4; FPgM (bcotton, 16:09:45)
* Announcements (jwf, 16:11:57)
* === "FPgM report: 2018-38" === (jwf, 16:12:04)
* LINK: https://communityblog.fedoraproject.org/fpgm-report-2018-38/
(jwf, 16:12:04)
* This week in Fedora is brought to you in part by bcotton. (jwf,
16:12:04)
* === "Submit a Fedora talk to DevConf.cz 2019" === (jwf, 16:12:46)
* LINK:
https://communityblog.fedoraproject.org/submit-fedora-talk-devconf-cz-2019/
(jwf, 16:12:46)
* The CfP for the DevConf devops conference in Brno, Czech Republic is
now open. Fedora topics welcome! (jwf, 16:12:46)
* === "Announcing the release of Fedora 29 Beta" === (jwf, 16:14:06)
* LINK: https://fedoramagazine.org/announcing-fedora-29-beta/ (jwf,
16:14:11)
* Fedora 29 Beta launched this week! Get a sneak peek into what's
ahead for Fedora and what's planned for the final release next
month. (jwf, 16:14:36)
* Action items from last meeting (jwf, 16:15:35)
* LINK:
https://meetbot.fedoraproject.org/fedora-commops/2018-09-19/commops.2018-...
(jwf, 16:15:38)
* 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 if needed. If no
status, we'll try to get a quick update and move forward. (jwf,
16:15:42)
* === [COMPLETE] "bt0 Write a second contributor story for FAW (due no
later than Monday, 2018-09-24)" === (jwf, 16:15:54)
* === [DELAYED] "jwf Write a CommBlog article summarizing CommOps @
Flock by Wednesday, Sept. 26" === (jwf, 16:16:31)
* ACTION: jwf Write a CommBlog article summarizing CommOps @ Flock by
Wednesday, Oct. 3 (jwf, 16:16:31)
* === [COMPLETE] "jwf Work with bt0 and pingou to configure a new
event to collect and vote on community photos in Nuancier for Fedora
Appreciation Week" === (jwf, 16:17:13)
* We reached out to pingou via email to see if Nuancier can be used
for FAW. Might be a slow response since a major Pagure update
released this week too. (jwf, 16:17:13)
* === [IN PROGRESS] "bt0 Collect info on current Pagure issue tags
used in fedora-commops / fedora-marketing and add proposal as
comment to ticket #168 (by Wednesday, Oct. 3)" === (jwf, 16:17:52)
* ACTION: bt0 Collect info on current Pagure issue tags used in
fedora-commops / fedora-marketing and add proposal as comment to
ticket #168 (by Wednesday, Oct. 3) (jwf, 16:17:53)
* === [COMPLETE] "bcotton File a new CommOps ticket about an editorial
calendar for the CommBlog to prevent editors stepping on toes for
scheduling articles (and other ways to improve awareness of CommBlog
happenings)" === (jwf, 16:18:25)
* === [COMPLETE] "bcotton File a new CommOps ticket about an editorial
calendar for the CommBlog to prevent editors stepping on toes for
scheduling articles (and other ways to improve awareness of CommBlog
happenings)" === (jwf, 16:18:53)
* LINK: https://pagure.io/fedora-commops/issue/184 (jwf, 16:18:53)
* Tickets (jwf, 16:19:47)
* LINK:
https://pagure.io/fedora-commops/issues?status=Open&priority=20
(jwf, 16:19:50)
* Ticket #110: "Fedora Appreciation Week 2018" (jwf, 16:20:34)
* LINK: https://pagure.io/fedora-commops/issue/110 (jwf, 16:20:34)
* LINK:
https://screenshots.firefox.com/xu7fdJ4v3sVLlQYh/etherpad.gnome.org
(jwf, 16:20:34)
* No updates as of now; bt0 and jwf working with pingou for using
Nuancier. dhanesh95 filed tickets for Design and Badges. Still need
a common header for CommBlog posts published during FAW, but may
slip to next month. (jwf, 16:23:38)
* Ticket #178: "Pilot run a CommOps section on
discussion.fedoraproject.org" (jwf, 16:24:34)
* LINK: https://pagure.io/fedora-commops/issue/178 (jwf, 16:24:34)
* LINK: https://discussion.fedoraproject.org/ (jwf, 16:24:34)
* Work to do before Monday, Oct. 1 launch: (1) explicitly announce
transition on list, (2) set up an auto-mailer message for the
mailing list about Discourse, (3) set up / configure the CommOps
subforum with help from sanja (jwf, 16:27:34)
* Fedocal automated email messages need consideration (jwf, 16:31:12)
* ACTION: jwf Send an email announcement to CommOps list to boost
awareness of upcoming Mailman => Discourse migration experiment by
end of day Wednesday, Sept. 26 (jwf, 16:32:29)
* ACTION: jwf Set up auto-email response for new threads on CommOps
list to explain Discourse migration by Sunday, Sept. 30 (jwf,
16:33:01)
* Ticket #168: "Propose a set of Pagure tags than help the onboarding
process" (jwf, 16:34:35)
* LINK: https://pagure.io/fedora-commops/issue/168 (jwf, 16:34:36)
* Next Steps: find the correct place for this docs (CommOps docs??
another repo, a brand new docs page?) (jwf, 16:34:36)
* ACTION: bt0 Update Ticket #168 (Pagure tags ticket) by next meeting
on Wednesday, Oct. 3 (jwf, 16:36:20)
* Open floor (jwf, 16:36:47)
* LINK: https://pagure.io/wordcloudbot (jwf, 16:38:40)
Meeting ended at 16:40:37 UTC.
Action Items
------------
* commops New members, please introduce yourself on the CommOps mailing
list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ]
* jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday,
Oct. 3
* bt0 Collect info on current Pagure issue tags used in fedora-commops /
fedora-marketing and add proposal as comment to ticket #168 (by
Wednesday, Oct. 3)
* jwf Send an email announcement to CommOps list to boost awareness of
upcoming Mailman => Discourse migration experiment by end of day
Wednesday, Sept. 26
* jwf Set up auto-email response for new threads on CommOps list to
explain Discourse migration by Sunday, Sept. 30
* bt0 Update Ticket #168 (Pagure tags ticket) by next meeting on
Wednesday, Oct. 3
Action Items, by person
-----------------------
* bt0
* bt0 Collect info on current Pagure issue tags used in fedora-commops
/ fedora-marketing and add proposal as comment to ticket #168 (by
Wednesday, Oct. 3)
* bt0 Update Ticket #168 (Pagure tags ticket) by next meeting on
Wednesday, Oct. 3
* commops
* commops New members, please introduce yourself on the CommOps
mailing list [
https://docs.fedoraproject.org/en-US/commops/contribute/join/ ]
* bt0 Collect info on current Pagure issue tags used in fedora-commops
/ fedora-marketing and add proposal as comment to ticket #168 (by
Wednesday, Oct. 3)
* jwf
* jwf Write a CommBlog article summarizing CommOps @ Flock by
Wednesday, Oct. 3
* jwf Send an email announcement to CommOps list to boost awareness of
upcoming Mailman => Discourse migration experiment by end of day
Wednesday, Sept. 26
* jwf Set up auto-email response for new threads on CommOps list to
explain Discourse migration by Sunday, Sept. 30
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jwf (127)
* zodbot (11)
* fcommops-tg1 (7)
* bcotton (6)
* nb (2)
* labbott (1)
* bt0 (0)
* commops (0)
* bee2502 (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
5 years
