My experience as a wannabe contributor
by Alain Vigne
Hi, I am Alain, FAS: avigne
As discussed today in #fedora-devel, here is some feedback about my
experience trying to join Fedora as a contributor -> packager.
TLDR: Adding a new package and become a Fedora packager is NOT easy.
I am not a computer scientist, but as an Integrated Circuit designer, I am
using eCAD proprietary tools heavily.
With my years of experience, I came up to know how to use Fedora, and I
like this distro because it is reliable, and fairly up to date with
software technologies.
When Fedora FEL spin was alive, I picked up some tools, and slowly learn
how to use them. gEDA, PCB, NGspice, GerbV, etc...
At some point, 2 years ago, I thought Open Source world gave me a lot, it
was time to give back... So I contacted the pcb-rnd project [1], and
started to contribute code around GTK, and GUI aspects of the application.
Naturally, as I am developing with a Fedora system, I thought it could be
nice to have pcb-rnd for Fedora... I had no clue on how to proceed, and
first, I tried to find someone who can do that for me...
Found no one. (I should have known :).
Time passes by, and one day a pcb-rnd Mageia contributor showed me the
.spec file he wrote for Mageia. I was curious about what was behind all
those commands and how this "recipe" (the .spec file) can lead to a package.
So I dug into the documentation (mainly Fedora wiki) learning how to first
build an RPM, then after a successful local "mock", my curiosity was
satisfied. I thought I understood the purpose of those tools (rpmbuild,
rpmlint, mock).
That is when I started to think about contributing this package to Fedora.
"It should be easy, I have the recipe, I just need to find where to
check-in the .spec file..." Easy thought, no ?
Unfortunately, no, this is not easy.
First, there are tons of pages describing the process, and what to do. In
theory the process is well described.
In practice, I got stuck in the "need a sponsor" phase where I think there
is kinda chicken-and-egg problem for a new contributor.
I might detail that, later, if someone is interested in this list.
My feeling today, 6 months after I jumped in the unknown is not very much
positive:
I had to register, open accounts, leave traces on many systems before being
able to .... get nothing at the moment
- Bugzilla
- FAS
- COPR
- mailing list
- Freenode registration
etc...
I feel like someone who has a complicated map under the eyes, walk, try and
error to make sense of the map, up to a point where the map says: next step
is "find a sponsor" and I have no idea how this is being done.
And time passes by... Slowly. I am silently ignored.
Somebody says today : "Do informal reviews [a suggestion on the wiki, but
what can I suggest ? I have no experience ->chicken and egg problem], make
some mails, fill some bugs and you will get noticed".
I think this is the problem: nobody noticed, it seems nobody cares having a
new volunteer.
So, I am concluding: Fedora = too big ship, mainly automated, with a lot of
processes (procedures, way of working) and a community not open to new
contributors [I recall, my experience is only about contributing a new
package], because this is too complicated (which I agree and understand).
That said, I am a patient man, and I have done all this travel not to being
stop by a wall. I spent my life trying to get around, over, across... so
many walls, so, I won't surrender here !
Thanks for reading till that point, and let us open the debate.
Kind regards
Alain
PS: I am French, not EN native speaker, pardon my language if it does not
make sense to you.
[1] http://repo.hu/projects/pcb-rnd/
--
Alain V.
5 years, 6 months
[feedback wanted] Planning Fedora Docs hack-fest targeting user communities
by Justin W. Flory
Hi all,
In today's CommOps meeting, we revisited an old ticket about planning a
Fedora Docs hack-fest, focusing on getting active, knowledgeable users
across Fedora's user communities to contribute and update content in the
Quick Docs repo (also encouraging people from our user communities to
link and reference the official docs).
Please take a look and weigh in on this Fedora Discourse thread (please
don't reply on the mailing lists because it will inevitably exclude
someone from one sub-project or another):
https://discussion.fedoraproject.org/t/fedora-docs-community-contribution...
We learned Fedora Join SIG was talking about similar ideas recently, so
we wanted to prevent duplication of work and see if we can all work
together to make this idea happen.
Thanks!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
5 years, 6 months
Re: [commops] Introducing myself
by Justin W. Flory
On 9/28/18 5:19 AM, Harshit Modi wrote:
> 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.
>
Hi Harshit, welcome to the CommOps list! I think CommOps is a good way
to get an early exposure to the wider Fedora community and how it comes
together.
I've also added CC'd the Fedora Join SIG since they are a great resource
for getting started too.
> 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!
>
Awesome! I definitely think there are ways for you to jump in and get
started. Are you looking for technical / development opportunities, like
some web development? Or are you looking for non-technical work, maybe
blog posts or helping with things like Fedora Appreciation Week?
If you're not sure, this is a good place to look, to get an idea of what
we do:
https://docs.fedoraproject.org/en-US/commops/#what-commops-does
What can we do to help you get started? :) Hoping to see you around the
community!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
5 years, 6 months
Meeting logs for 2018-10-09: ticket updates, release based classroom schedule, pro-active tracking of new contributors
by Ankur Sinha
Hi,
Here are the logs from today's meeting. There are one or two tickets
that need inputs, so if you can please comment on them before the next
meeting, we can make a decision then.
- Feedback needed on new Fedora release schedule based classroom
calendar (https://pagure.io/fedora-join/Fedora-Join/issue/87)
The idea here is that we set ourselves up in sync with the Fedora
releases so that we can plan ahead, organise better, and not compete
with release related tasks/marketing. I've put together a draft
calendar here as a prototype. If you can please go through it and
comment on the ticket, we shall refine it as required:
https://fedoraproject.org/wiki/Classroom/Release_schedule
- In line with this new calendar scheme, we have 8 weeks between
releases where we'd like to have at least 6 sessions in successive
weeks. So, we need to decide which sessions we should try to organise.
There are quite a few options:
https://pagure.io/fedora-join/Fedora-Join/issues?status=Open&tags=classroom
If you can please go through the list and vote (comment as +1), we
shall count votes at the next meeting and pick 6 (+1 or 2 as backup).
Here are the links to the meeting logs, and summary is below. Thank you
for attending, and I shall see you in a week.
https://meetbot-raw.fedoraproject.org/fedora-meeting-3/2018-10-09/fedora-...
https://meetbot.fedoraproject.org/fedora-meeting-3/2018-10-09/fedora-join...
https://meetbot.fedoraproject.org/fedora-meeting-3/2018-10-09/fedora-join...
Here are the action items:
Action Items, by person
-----------------------
* bt0
* dhanesh95 bt0 x3mboy alciregi hellbanger FranciscoD : review
https://pagure.io/fedora-join/Fedora-Join/issue/87 and provide
comments
* bt0 close #65 when recording link has been provided
* dhanesh95
* dhanesh95 bt0 x3mboy alciregi hellbanger FranciscoD : review
https://pagure.io/fedora-join/Fedora-Join/issue/87 and provide
comments
* FranciscoD
* FranciscoD comment on ticket noting agreement
* FranciscoD e-mail devel list to clarify the function of "Trivial"
key word on review tickets
* dhanesh95 bt0 x3mboy alciregi hellbanger FranciscoD : review
https://pagure.io/fedora-join/Fedora-Join/issue/87 and provide
comments
* FranciscoD close #61
* FranciscoD write script to extract information from FAS on
applications to FAS groups
* FranciscoD open new ticket for script and make it block #86
* FranciscoD send out logs and update next_meeting page
* hellbanger
* dhanesh95 bt0 x3mboy alciregi hellbanger FranciscoD : review
https://pagure.io/fedora-join/Fedora-Join/issue/87 and provide
comments
* x3mboy
* dhanesh95 bt0 x3mboy alciregi hellbanger FranciscoD : review
https://pagure.io/fedora-join/Fedora-Join/issue/87 and provide
comments
=========================================
#fedora-meeting-3: Fedora Join 2018-10-09
=========================================
Meeting started by FranciscoD at 17:00:06 UTC.
Meeting summary
---------------
* We will follow this meeting guide:
https://fedoraproject.org/wiki/Meeting:Guide (FranciscoD, 17:00:55)
* The agenda is here:
https://fedoraproject.org/wiki/SIGs/Join/Next_Meeting (FranciscoD,
17:01:05)
* Roll call (FranciscoD, 17:01:12)
* FAS: ankursinha; IRC: FranciscoD; GMT+1; Classrooms, Join,
Packaging, NeuroFedora (FranciscoD, 17:01:51)
* Alberto Rodriguez S; UTC-5;CommOps (Metrics, Community engagement),
DotNet (Testing), Infrastructure(Apprentice), Marketing (Member),
Ambassadors (Member),Fedora-Join(Member) ,Cats (lover) (bt0,
17:01:58)
* New member introductions (FranciscoD, 17:07:08)
* If anyone here is new to Fedora or the team, please introduce
yourselves :) (FranciscoD, 17:07:36)
* Community announcements (FranciscoD, 17:09:40)
* Fedora 29 final freeze:
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
(FranciscoD, 17:10:16)
* Fedora Modularity test day on 2018-10-12:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.or...
(FranciscoD, 17:10:55)
* FPgM's report:
https://communityblog.fedoraproject.org/fpgm-report-2018-40/
(FranciscoD, 17:11:46)
* Tasks from last week (FranciscoD, 17:13:03)
* Logs from last week's meeting:
https://meetbot-raw.fedoraproject.org/fedora-meeting-3/2018-10-02/fedora-...
(FranciscoD, 17:13:12)
* bt0 update https://pagure.io/fedora-join/Fedora-Join/issue/72 with
more information (Script to get last activity of a user): DONE
(FranciscoD, 17:14:05)
* LINK:
https://pagure.io/fedora-join/Fedora-Join/issue/72#comment-535664 ->
comment in question (FranciscoD, 17:14:59)
* AGREED: (hellbanger, 17:16:43)
* AGREED: Use "last seen" and "active" fields of FAS with some date
constraint to measure activity of contributors in script (+4/-0)
(FranciscoD, 17:17:34)
* ACTION: FranciscoD comment on ticket noting agreement (FranciscoD,
17:17:47)
* dhanesh95 FranciscoD finish post and aim to publish in 2 weeks:
PENDING (FranciscoD, 17:18:29)
* dhanesh95 FranciscoD finish post and aim to publish: to be discussed
in meeting on 23rd October. (FranciscoD, 17:21:07)
* FranciscoD e-mail devel list to clarify the function of "Trivial"
key word on review tickets: PENDING, reassigning (FranciscoD,
17:21:42)
* ACTION: FranciscoD e-mail devel list to clarify the function of
"Trivial" key word on review tickets (FranciscoD, 17:22:34)
* s14ck FranciscoD discuss newcomers + classroom after meeting: DONE:
a separate set of sessions for LATAM will be run. More information
at https://pagure.io/fedora-join/Fedora-Join/issue/74 (FranciscoD,
17:23:27)
* FranciscoD send e-mails to ML about tickets that need discussing one
by one: PENDING, needs discussion, reassigning (FranciscoD,
17:23:47)
* FranciscoD work on
https://pagure.io/fedora-join/Fedora-Join/issue/6: (Introduction
template for contributors): PENDING, reassigning (FranciscoD,
17:25:04)
* FranciscoD file ticket proposing zsh classroom session and assign it
to x3mboy : DONE:
https://pagure.io/fedora-join/Fedora-Join/issue/76 (FranciscoD,
17:25:54)
* FranciscoD file ticket for Vim 102 classroom session: DONE:
https://pagure.io/fedora-join/Fedora-Join/issue/77 (FranciscoD,
17:26:13)
* FranciscoD file ticket for Silverblue classroom session: DONE:
https://pagure.io/fedora-join/Fedora-Join/issue/78 (FranciscoD,
17:26:39)
* FranciscoD send out logs and updates next_meeting page etc: DONE
(FranciscoD, 17:27:01)
* FranciscoD close https://pagure.io/fedora-join/Fedora-Join/issue/28:
DONE (Video platform overview) (FranciscoD, 17:27:33)
* hellbanger file ticket about l10n classroom sessions: DONE:
https://pagure.io/fedora-join/Fedora-Join/issue/73 and
https://pagure.io/fedora-join/Fedora-Join/issue/80 (FranciscoD,
17:28:08)
* #73 is about holding more sessions for non English speakers
(FranciscoD, 17:28:30)
* #80 is about a session on l10N 101 (FranciscoD, 17:28:39)
* Pagure tickets (FranciscoD, 17:29:00)
* https://pagure.io/fedora-join/Fedora-Join/issue/87: Release related
Fedora classroom schedule (FranciscoD, 17:29:21)
* ACTION: dhanesh95 bt0 x3mboy alciregi hellbanger FranciscoD : review
https://pagure.io/fedora-join/Fedora-Join/issue/87 and provide
comments (FranciscoD, 17:36:11)
* AGREED: We decide 6 classroom sessions for F29 at next week's
meeting (FranciscoD, 17:43:17)
* https://pagure.io/fedora-join/Fedora-Join/issue/61: Fedora
modularity classroom sessions (FranciscoD, 17:43:59)
* ACTION: FranciscoD close #61 (FranciscoD, 17:46:34)
* ACTION: bt0 close #65 when recording link has been provided
(FranciscoD, 17:46:44)
* https://pagure.io/fedora-join/Fedora-Join/issue/86: Keeping an eye
on contributors looking for sponsorship to various groups
(FranciscoD, 17:47:04)
* ACTION: FranciscoD write script to extract information from FAS on
applications to FAS groups (FranciscoD, 17:54:28)
* ACTION: FranciscoD open new ticket for script and make it block #86
(FranciscoD, 17:57:24)
* ACTION: FranciscoD send out logs and update next_meeting page
(FranciscoD, 17:59:45)
Meeting ended at 18:00:01 UTC.
People Present (lines said)
---------------------------
* FranciscoD (132)
* dhanesh95 (40)
* bt0 (26)
* hellbanger (17)
* zodbot (13)
* x3mboy (0)
--
Thanks,
Regards,
Ankur Sinha "FranciscoD"
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
5 years, 6 months
Ansible linux-system-roles on fedora-join
by Michael DePaulo
Hi everyone,
I'm at AnsibleFest right now, and contributors to both Fedora and Ansible are discussing linux-system-roles:
https://linux-system-roles.github.io
It is upstream to to the rhel-system-roles package in RHEL/CentOS & it officially supports Fedora, although it does not seem to be provided as a package in Fedora. (I will be inquiring about this tomorrow.)
The few fellow Fedora contributors I've talked to (including mattdm) like the idea of listing linux-system-roles on fedora-join after a brief high-level discussion. It could be advertised towards anyone who knows how to write Ansible playbooks/roles (no module writing in Python); a very broad skill set nowadays.
What do people here think?
-Mike
5 years, 6 months
Cleared up ML moderation queue
by Ankur Sinha
Hello,
I've just cleared up the message moderation queue. Most of it was spam,
but a few genuine e-mails did get stuck in there too. I've let them
through now, although I think it's too late for us to follow up on them.
To ensure that we don't let this happen again, we need more people
looking at the moderation queue. It only takes 5 minutes a week. I've
filed a ticket here. If you're OK with being a mailing list moderator,
please comment on the ticket to let us know. I'd like to add 2--3 folks.
https://pagure.io/fedora-join/Fedora-Join/issue/84
--
Thanks,
Regards,
Ankur Sinha "FranciscoD"
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
5 years, 6 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
5 years, 6 months
Meeting logs for 2nd October 2018: task updates, tickets, new ideas, and mentoring
by Ankur Sinha
Hi!
Here are the logs from today's meeting. We went over tasks and had a few
new ideas. We're looking at organising classroom sessions in languages
other than English, for example. We also want to re-start the mentoring
process, and have a classroom calendar that is related to the release
calendar so that we can organise and plan in advance.
See you all next week!
Links:
Logs: https://meetbot.fedoraproject.org/fedora-meeting-3/2018-10-02/fedora-join...
Minutes (text): https://meetbot-raw.fedoraproject.org/fedora-meeting-3/2018-10-02/fedora-...
Minute (HTML): https://meetbot.fedoraproject.org/fedora-meeting-3/2018-10-02/fedora-join...
Action Items, by person
-----------------------
* bt0
* bt0 update https://pagure.io/fedora-join/Fedora-Join/issue/72 with
more information
* dhanesh95
* dhanesh95 FranciscoD finish post and aim to publish in 2 weeks
* FranciscoD
* FranciscoD e-mail devel list to clarify the function of "Trivial"
key word on review tickets
* dhanesh95 FranciscoD finish post and aim to publish in 2 weeks
* s14ck FranciscoD discuss newcomers + classroom after meeting
* FranciscoD send e-mails to ML about tickets that need discussing one
by one
* FranciscoD work on https://pagure.io/fedora-join/Fedora-Join/issue/6
* FranciscoD file ticket proposing zsh classroom session and assign it
to x3mboy
* FranciscoD file ticket for Vim 102 classroom session
* FranciscoD file ticket for Silverblue classroom session
* FranciscoD send out logs
* FranciscoD update next meeting page
* FranciscoD close https://pagure.io/fedora-join/Fedora-Join/issue/28
* FranciscoD comment on the ticket and close it appropriately
* FranciscoD file new ticket and come up with a calender for the F29
release period
* hellbanger
* hellbanger file ticket about l10n classroom sessions
* s14ck
* s14ck Create tickets with classroom session proposals
* s14ck FranciscoD discuss newcomers + classroom after meeting
Meeting summary
---------------
* https://fedoraproject.org/wiki/SIGs/Join/Next_Meeting (FranciscoD,
17:09:00)
* Roll call (FranciscoD, 17:09:06)
* ankursinha: packaging, join, classrooms, NeuroFedora and other misc
community tasks (FranciscoD, 17:09:37)
* Dhanesh B. Sabane, UTC+5:30, CommOps, Join, RPM Packaging, Python
(dhanesh95, 17:09:50)
* Alberto Rodriguez S; UTC-5;CommOps (Metrics, Community engagement),
DotNet (Testing), Infrastructure(Apprentice), Marketing (Member),
Ambassadors (Member),Fedora-Join(Member) ,Cats (lover) (bt0,
17:10:00)
* New member introductions (FranciscoD, 17:11:02)
* If anyone has not attended a meeting before, they can use this
opportunity to introduce themselves to the group :) (FranciscoD,
17:11:25)
* Community announcements (FranciscoD, 17:14:05)
* Fedora tagger and statscache sunset:
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
(FranciscoD, 17:14:41)
* Fedora 29 beta has been released!
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
(FranciscoD, 17:14:56)
* Fedora packaging guidelines have been moved to docs.fp.o:
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
(FranciscoD, 17:15:15)
* Fedora packaging guidelines:
https://docs.fedoraproject.org/en-US/packaging-guidelines/
(FranciscoD, 17:15:28)
* Planned Fedora infra outage on 2018-10-03:
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
(FranciscoD, 17:15:49)
* NeuroFedora is up and running and is looking for contributors:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
(FranciscoD, 17:16:25)
* DNF test day tomorrow:
https://communityblog.fedoraproject.org/dnf-3-5-test-day-2018-10-03/
(FranciscoD, 17:17:03)
* Fedora program managers notes for this week:
https://communityblog.fedoraproject.org/fpgm-report-2018-39/
(FranciscoD, 17:17:20)
* Fedora atomic and cloud test day was yesterday (you can still
participate!):
https://communityblog.fedoraproject.org/fedora-29-atomic-and-cloud-test-d...
(FranciscoD, 17:17:47)
* Hactoberfest is on! https://hacktoberfest.digitalocean.com/
(FranciscoD, 17:18:59)
* chromium-vaapi is coming to fedora :D (hellbanger, 17:20:11)
* Tasks from past week (FranciscoD, 17:21:33)
* Last week's meeting minutes are here:
https://meetbot-raw.fedoraproject.org/fedora-meeting-3/2018-09-25/fedora-...
(FranciscoD, 17:22:07)
* s14ck Create tickets with classroom session proposals: PENDING,
reassigning (FranciscoD, 17:23:42)
* ACTION: s14ck Create tickets with classroom session proposals
(FranciscoD, 17:23:47)
* FranciscoD e-mail devel list to clarify the function of "Trivial"
key word on review tickets: PENDING (waiting on), reassigning
(FranciscoD, 17:24:34)
* https://github.com/fedora-infra/fedora-gather-easyfix/pull/13 -> PR
to add this bit (FranciscoD, 17:25:03)
* ACTION: FranciscoD e-mail devel list to clarify the function of
"Trivial" key word on review tickets (FranciscoD, 17:25:37)
* dhanesh95 FranciscoD finish post and aim to publish in 2 weeks: WIP,
reassigning (FranciscoD, 17:26:20)
* ACTION: dhanesh95 FranciscoD finish post and aim to publish in 2
weeks (FranciscoD, 17:27:50)
* ACTION: s14ck FranciscoD discuss newcomers + classroom after meeting
(FranciscoD, 17:30:24)
* FranciscoD send e-mails to ML about tickets that need discussing one
by one: PENDING, need-info (FranciscoD, 17:30:51)
* ACTION: FranciscoD send e-mails to ML about tickets that need
discussing one by one (FranciscoD, 17:31:32)
* FranciscoD close https://pagure.io/fedora-join/Fedora-Join/issue/5
"Fedora join FAS group membership kinks ": DONE (FranciscoD,
17:32:09)
* I added a new section to the wiki page:
https://fedoraproject.org/wiki/SIGs/Join#Membership (FranciscoD,
17:32:28)
* bt0 file new ticket about datagrepper script to check activity for
membership purposes: DONE (FranciscoD, 17:33:48)
* bt0 filed https://pagure.io/fedora-join/Fedora-Join/issue/72
(FranciscoD, 17:33:54)
* https://pagure.io/fedora-join/Fedora-Join/issue/72 requires
comments! (FranciscoD, 17:34:04)
* ACTION: bt0 update
https://pagure.io/fedora-join/Fedora-Join/issue/72 with more
information (FranciscoD, 17:38:53)
* FranciscoD update https://pagure.io/fedora-join/Fedora-Join/issue/6
summary to clarify that this is for seasoned contributors looking to
join the Join SIG to help: DONE (FranciscoD, 17:39:05)
* Summary of the ticket has been modified to: Join SIG introduction
template for seasoned contributors looking to help out (FranciscoD,
17:39:34)
* ACTION: FranciscoD work on
https://pagure.io/fedora-join/Fedora-Join/issue/6 (FranciscoD,
17:41:06)
* x3mboy work on https://pagure.io/fedora-join/Fedora-Join/issue/7:
WIP, has been assigned to x3mboy (FranciscoD, 17:41:56)
* bt0 follow up on #61 and try to schedule the sessions: DONE, ticket
will be discussed (FranciscoD, 17:42:39)
* FranciscoD send out logs: DONE (FranciscoD, 17:42:57)
* x3mboy file ticket proposing zsh classroom session: PENDING
(FranciscoD, 17:43:14)
* ACTION: file ticket proposing zsh classroom session and assign it to
x3mboy (FranciscoD, 17:43:38)
* x3mboy FranciscoD do second vim classroom session: PENDING
(FranciscoD, 17:43:51)
* ACTION: FranciscoD file ticket proposing zsh classroom session and
assign it to x3mboy (FranciscoD, 17:44:16)
* ACTION: FranciscoD file ticket for Vim 102 classroom session
(FranciscoD, 17:44:37)
* ACTION: FranciscoD file ticket for Silverblue classroom session
(FranciscoD, 17:45:03)
* FranciscoD open new tickets about Infra 101 related classroom
sessions: DONE: https://pagure.io/fedora-join/Fedora-Join/issue/70
(FranciscoD, 17:45:28)
* ACTION: hellbanger file ticket about l10n classroom sessions
(FranciscoD, 17:46:36)
* ACTION: FranciscoD send out logs (FranciscoD, 17:47:19)
* ACTION: FranciscoD update next meeting page (FranciscoD, 17:47:24)
* Pagure tickets (FranciscoD, 17:47:45)
* https://pagure.io/fedora-join/Fedora-Join/issue/28 Classroom v2
video platforms (FranciscoD, 17:49:31)
* AGREED: close https://pagure.io/fedora-join/Fedora-Join/issue/28:
we're happy with jitsi + bluejeans at the moment (FranciscoD,
17:51:01)
* ACTION: FranciscoD close
https://pagure.io/fedora-join/Fedora-Join/issue/28 (FranciscoD,
17:51:06)
* https://pagure.io/fedora-join/Fedora-Join/issue/71: release schedule
oriented organisation of Fedora classroom sessions (FranciscoD,
17:51:30)
* AGREED: We try to come up with a release related calendar for the
classroom: https://pagure.io/fedora-join/Fedora-Join/issue/71
(FranciscoD, 17:54:41)
* ACTION: FranciscoD comment on the ticket and close it appropriately
(FranciscoD, 17:54:51)
* ACTION: FranciscoD file new ticket and come up with a calender for
the F29 release period (FranciscoD, 17:55:22)
* Mentoring related tickets:
https://pagure.io/fedora-join/Fedora-Join/issues?status=Open&tags=mentorship
(FranciscoD, 17:57:26)
Meeting ended at 18:04:41 UTC.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD"
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
5 years, 6 months
