contribute to the Fedora
by Suraj Rajendra Patil
hello there,
my name is suraj patil im a newbie to the open source world. im very passionate and enthusiastic person to work with the fedora and open source
i want to add one blog regarding how to use ll (long-list) command please help for this
warm & regards
Suraj patil
5 years, 1 month
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, 1 month
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, 1 month
Meeting logs: 25th September 2018: Tasks from last week, ticket updates, introduction templates
by Ankur Sinha
Hello!
Here are the logs from today's meeting:
minutes(html): https://meetbot.fedoraproject.org/fedora-meeting-3/2018-09-25/fedora-join...
minutes(text): https://meetbot-raw.fedoraproject.org/fedora-meeting-3/2018-09-25/fedora-...
logs: https://meetbot.fedoraproject.org/fedora-meeting-3/2018-09-25/fedora-join...
The next meeting will be in 1 week, on 2nd of October. The action items
are below, and the summary of the meeting at the end of this e-mail. See
you next Tuesday!
Action Items, by person
-----------------------
* bt0
* bt0 file new ticket about datagrepper script to check activity for
membership purposes
* bt0 follow up on #61 and try to schedule the sessions
* 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
* FranciscoD send e-mails to ML about tickets that need discussing one
by one
* FranciscoD close https://pagure.io/fedora-join/Fedora-Join/issue/5
* 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
* FranciscoD send out logs
* x3mboy FranciscoD do second vim classroom session
* FranciscoD open new tickets about Infra 101 related classroom
sessions
* s14ck
* s14ck Create tickets with classroom session proposals
* x3mboy
* x3mboy work on https://pagure.io/fedora-join/Fedora-Join/issue/7
* x3mboy file ticket proposing zsh classroom session
* x3mboy FranciscoD do second vim classroom session
Meeting summary
---------------
* Roll call (FranciscoD, 17:03:13)
* FranciscoD: ankursinha---Fedora Join/Classroom, packaging,
NeuroFedora and a few other tidbits (FranciscoD, 17:03:46)
* New member introductions (FranciscoD, 17:04:51)
* If this is your first meeting, please introduce yourself---what are
your interests, what you'd like to do, what help can we provide?
(FranciscoD, 17:05:26)
* Community announcements (FranciscoD, 17:06:02)
* Fedora 29 beta has been released:
https://fedoramagazine.org/announcing-fedora-29-beta/ (FranciscoD,
17:06:28)
* Today is Java test day:
https://communityblog.fedoraproject.org/test-day-java-81011/
(FranciscoD, 17:06:57)
* Fedora program managers latest report:
https://communityblog.fedoraproject.org/fpgm-report-2018-38/
(FranciscoD, 17:07:13)
* Submit a talk to Devconf.cz:
https://communityblog.fedoraproject.org/submit-fedora-talk-devconf-cz-2019/
(FranciscoD, 17:07:49)
* Fedora appreciation week is coming up in November:
https://communityblog.fedoraproject.org/fedora-appreciation-week-2018/
(FranciscoD, 17:08:12)
* Gnome 3.30 is coming to Fedora 29:
https://fedoramagazine.org/gnome-3-30-released-coming-fedora-29/
(FranciscoD, 17:09:08)
* Tasks from past week (FranciscoD, 17:11:01)
* The last meeting was 2 weeks ago. Minutes are here:
https://meetbot.fedoraproject.org/teams/fedora-join/fedora-join.2018-09-1...
(FranciscoD, 17:11:31)
* s14ck Create tickets with classroom session proposals (FranciscoD,
17:11:47)
* Our tickets are at: https://pagure.io/fedora-join/Fedora-Join/issues
(FranciscoD, 17:12:18)
* Pagure got a facelift! (FranciscoD, 17:12:32)
* Classroom related tickets are here:
https://pagure.io/fedora-join/Fedora-Join/issues?status=Open&tags=classroom
(FranciscoD, 17:13:25)
* ACTION: s14ck Create tickets with classroom session proposals
(FranciscoD, 17:14:29)
* FranciscoD update #61 to say "Next round of modularity classroom
sessions": DONE (FranciscoD, 17:15:14)
* This is the main ticket for modularity related sessions:
https://pagure.io/fedora-join/Fedora-Join/issue/61 (FranciscoD,
17:15:26)
* FranciscoD make other tickets block #61: DONE (FranciscoD,
17:15:46)
* FranciscoD e-mail devel list to clarify the function of "Trivial"
key word on review tickets: PENDING (FranciscoD, 17:16:10)
* ACTION: FranciscoD e-mail devel list to clarify the function of
"Trivial" key word on review tickets (FranciscoD, 17:17:55)
* FranciscoD e-mail dukebarman to check up: DONE (FranciscoD,
17:18:09)
* dukebarman has said he's slightly busy at the moment and will get
started when he can find some time. I've removed his temporary
membership and closed the ticket too. (FranciscoD, 17:18:40)
* FranciscoD go over draft post: DONE (FranciscoD, 17:19:04)
* FranciscoD e-mailed dhanesh95 feedback yesterday. dhanesh95 is
making changes. (FranciscoD, 17:19:31)
* dhanesh95 FranciscoD finish post and aim to publish before next
meeting: PENDING (FranciscoD, 17:19:39)
* ACTION: dhanesh95 FranciscoD finish post and aim to publish in 2
weeks (FranciscoD, 17:19:59)
* dhanesh95 figure out a way to make draft public: DONE (FranciscoD,
17:20:09)
* FranciscoD update wiki page with information about badges from
https://pagure.io/fedora-join/Fedora-Join/issue/33: DONE
(FranciscoD, 17:21:16)
* FranciscoD added:
https://fedoraproject.org/wiki/Classroom#Badges_for_instructors
(FranciscoD, 17:21:24)
* In short, if a session happens in #fedora-classroom, instructors get
badges automatically. BUT, if it happens over jitsi or bluejean etc,
we must open a ticket requesting a badge to be manually given to
them. (FranciscoD, 17:21:59)
* FranciscoD close https://pagure.io/fedora-join/Fedora-Join/issue/33:
DONE (FranciscoD, 17:22:28)
* FranciscoD send e-mails to ML about tickets that need discussing one
by one: PENDING (FranciscoD, 17:22:52)
* ACTION: FranciscoD send e-mails to ML about tickets that need
discussing one by one (FranciscoD, 17:23:26)
* FranciscoD send out logs: DONE (FranciscoD, 17:23:39)
* FranciscoD update next meeting page: DONE (FranciscoD, 17:23:47)
* Pagure tickets (FranciscoD, 17:24:16)
* We go over tickets tagged "next-meeting":
https://pagure.io/fedora-join/Fedora-Join/issues?status=Open&tags=next-me...
(FranciscoD, 17:24:54)
* FAS group membership kinks:
https://pagure.io/fedora-join/Fedora-Join/issue/5 (*three* years
old!) (FranciscoD, 17:27:53)
* AGREED: proposed guidelines are OK (+4/-0) (FranciscoD, 17:32:22)
* ACTION: FranciscoD close
https://pagure.io/fedora-join/Fedora-Join/issue/5 (FranciscoD,
17:32:31)
* ACTION: bt0 file new ticket about datagrepper script to check
activity for membership purposes (FranciscoD, 17:33:43)
* Join SIG introduction template:
https://pagure.io/fedora-join/Fedora-Join/issue/6 (FranciscoD,
17:34:32)
* LINK: https://pagure.io/fedora-commops/issue/166 (bt0, 17:39:19)
* ACTION: 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 (FranciscoD, 17:41:55)
* https://pagure.io/fedora-join/Fedora-Join/issue/6 asssigned to
FranciscoD (FranciscoD, 17:42:40)
* https://pagure.io/fedora-join/Fedora-Join/issue/7: Prospective
contributor introduction template (FranciscoD, 17:46:40)
* ACTION: x3mboy work on
https://pagure.io/fedora-join/Fedora-Join/issue/7 (FranciscoD,
17:50:17)
* x3mboy bt0 FranciscoD finish templates and discuss what's common and
how they should be made available to the community (FranciscoD,
17:50:41)
* Modularity classroom sessions
https://pagure.io/fedora-join/Fedora-Join/issue/61 (FranciscoD,
17:51:10)
* ACTION: bt0 follow up on #61 and try to schedule the sessions
(FranciscoD, 17:52:03)
* Open floor (FranciscoD, 17:55:06)
* ACTION: FranciscoD send out logs (FranciscoD, 17:57:05)
* ACTION: x3mboy file ticket proposing zsh classroom session
(FranciscoD, 17:57:21)
* ACTION: x3mboy FranciscoD do second vim classroom session
(FranciscoD, 17:57:37)
* ACTION: FranciscoD open new tickets about Infra 101 related
classroom sessions (FranciscoD, 17:58:12)
Meeting ended at 18:01:24 UTC.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD"
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
5 years, 2 months
Meetings logs for 11th September 2018: ticket updates, EasyFix discussion and more!
by Ankur Sinha
Hello!
We had our weekly meeting earlier. We discussed the many tickets we have
on our Pagure project instance. Here are the links to the logs:
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-3/2018-09-11/fedora-join...
Minutes (text): https://meetbot-raw.fedoraproject.org/fedora-meeting-3/2018-09-11/fedora-...
Full logs: https://meetbot.fedoraproject.org/fedora-meeting-3/2018-09-11/fedora-join...
Minutes are pasted below for your convenience. Please do take a look at
the action items at the end of the summary. There's much work to be
done, and we can always use more hands! :)
Meeting summary
---------------
* https://fedoraproject.org/wiki/SIGs/Join/Next_Meeting (FranciscoD,
17:05:32)
* Roll call (FranciscoD, 17:05:45)
* Please introduce yourself and give a little summary of your
interests :) (FranciscoD, 17:06:01)
* Ankur Sinha, ankursinha: Fedora Join/Classroom, Packaging,
NeuroFedora (FranciscoD, 17:06:26)
* Alberto Rodriguez S; UTC-5;CommOps (Metrics, Community engagement),
DotNet (Testing), Infrastructure(Apprentice), Marketing (Member),
Ambassadors (Member), Fedora-join (Member),Cats (lover) (bt0,
17:06:51)
* New member introductions (FranciscoD, 17:11:02)
* If this is your first IRC meeting, please introduce yourself in more
detail if you wish (FranciscoD, 17:11:23)
* Community announcements (FranciscoD, 17:15:06)
* Today is virtualization test day:
https://fedoraproject.org/wiki/Test_Day:2018-09-11_Virtualization
(FranciscoD, 17:15:29)
* Python 2 is no longer with us in Fedora 30:
https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal
(FranciscoD, 17:16:13)
* Fedora 29 Beta Release readiness meeting is on Thursday 2018-09-13
at 1900UTC https://fedoraproject.org/wiki/Releases/29/Schedule
(FranciscoD, 17:17:24)
* The meeting will be in #fedora-meeting-1 (FranciscoD, 17:17:50)
* Latest FPgM report is here:
https://communityblog.fedoraproject.org/fpgm-report-2018-36/
(FranciscoD, 17:19:28)
* Tickets (FranciscoD, 17:20:51)
* https://pagure.io/fedora-join/Fedora-Join/issues -> This is where
our tickets are (FranciscoD, 17:21:03)
* https://pagure.io/fedora-join/Fedora-Join/issue/63: A monthly
"easyfix day" (FranciscoD, 17:21:59)
* FranciscoD proposes we discuss this next week so that everyone has a
chance to comment (FranciscoD, 17:23:12)
* AGREED: https://pagure.io/fedora-join/Fedora-Join/issue/63 to be
discussed next week when everyone has had a chance to comment on it
(+6/-0) (FranciscoD, 17:26:12)
* https://pagure.io/fedora-join/Fedora-Join/issue/61 Next round of
classroom sessions (FranciscoD, 17:26:37)
* https://pagure.io/fedora-join/Fedora-Join/issue/65 -> Classroom
sessions about modularity (FranciscoD, 17:28:37)
* ACTION: s14ck Create tickets with classroom session proposals
(FranciscoD, 17:31:32)
* Remember to update the classroom wiki page once we know how many
modularity sessions we have (FranciscoD, 17:32:19)
* ACTION: FranciscoD update #61 to say "Next round of modularity
classroom sessions" (FranciscoD, 17:32:47)
* ACTION: FranciscoD make other tickets block #61 (FranciscoD,
17:33:01)
* https://pagure.io/fedora-join/Fedora-Join/issue/60 -> Add "trivial"
review tickets to easyfix list also (FranciscoD, 17:33:52)
* https://github.com/fedora-infra/fedora-gather-easyfix/pull/13
(FranciscoD, 17:34:26)
* ACTION: FranciscoD e-mail devel list to clarify the function of
"Trivial" key word on review tickets (FranciscoD, 17:36:01)
* https://pagure.io/fedora-join/Fedora-Join/issue/45 -> Temporary
member dukebarman (FranciscoD, 17:37:14)
* We need to check if dukebarman has been added to other groups so
that we can remove the temporary membership (FranciscoD, 17:38:06)
* ACTION: FranciscoD e-mail dukebarman to check up (FranciscoD,
17:40:36)
* https://pagure.io/fedora-join/Fedora-Join/issue/45 -> revisit next
week (FranciscoD, 17:40:48)
* AGREED: FranciscoD e-mail dukebarman about inactivity (+6/-0)
(FranciscoD, 17:41:12)
* https://pagure.io/fedora-join/Fedora-Join/issue/55 -> Write commblog
explaining how easyfix works (FranciscoD, 17:41:56)
* ACTION: FranciscoD go over draft post (FranciscoD, 17:42:57)
* ACTION: dhanesh95 FranciscoD finish post and aim to publish before
next meeting (FranciscoD, 17:43:16)
* ACTION: dhanesh95 figure out a way to make draft public
(FranciscoD, 17:49:58)
* https://pagure.io/fedora-join/Fedora-Join/issue/55 -> revisit next
week (FranciscoD, 17:50:22)
* https://pagure.io/fedora-join/Fedora-Join/issue/33 -> Badge series
for classroom instructors (FranciscoD, 17:50:49)
* ACTION: FranciscoD update wiki page with information about badges
from https://pagure.io/fedora-join/Fedora-Join/issue/33
(FranciscoD, 17:53:32)
* https://pagure.io/fedora-join/Fedora-Join/issue/33 - badges for
classroom instructors: FIXED (FranciscoD, 17:53:49)
* ACTION: FranciscoD close
https://pagure.io/fedora-join/Fedora-Join/issue/33 (FranciscoD,
17:54:33)
* Remember to mention badges in the posts announcing the new classroom
sessions (FranciscoD, 17:56:19)
* Open floor (FranciscoD, 17:59:14)
* ACTION: FranciscoD send e-mails to ML about tickets that need
discussing one by one (FranciscoD, 17:59:52)
* We need comments on mentoring related tickets:
https://pagure.io/fedora-join/Fedora-Join/issues?status=Open&tags=mentorship
(FranciscoD, 18:00:43)
* HELP: Join SIG voice their opinions on tickets to help with faster
resolution (dhanesh95, 18:00:57)
* ACTION: FranciscoD send out logs (FranciscoD, 18:02:29)
* ACTION: FranciscoD update next meeting page (FranciscoD, 18:02:40)
* ACTION: FranciscoD end meeting (FranciscoD, 18:02:52)
Meeting ended at 18:02:57 UTC.
Action Items
------------
* s14ck Create tickets with classroom session proposals
* FranciscoD update #61 to say "Next round of modularity classroom
sessions"
* FranciscoD make other tickets block #61
* FranciscoD e-mail devel list to clarify the function of "Trivial" key
word on review tickets
* FranciscoD e-mail dukebarman to check up
* FranciscoD go over draft post
* dhanesh95 FranciscoD finish post and aim to publish before next
meeting
* dhanesh95 figure out a way to make draft public
* FranciscoD update wiki page with information about badges from
https://pagure.io/fedora-join/Fedora-Join/issue/33
* FranciscoD close https://pagure.io/fedora-join/Fedora-Join/issue/33
* FranciscoD send e-mails to ML about tickets that need discussing one
by one
* FranciscoD send out logs
* FranciscoD update next meeting page
* FranciscoD end meeting
Action Items, by person
-----------------------
* dhanesh95
* dhanesh95 FranciscoD finish post and aim to publish before next
meeting
* dhanesh95 figure out a way to make draft public
* dukebarman
* FranciscoD e-mail dukebarman to check up
* FranciscoD
* FranciscoD update #61 to say "Next round of modularity classroom
sessions"
* FranciscoD make other tickets block #61
* FranciscoD e-mail devel list to clarify the function of "Trivial"
key word on review tickets
* FranciscoD e-mail dukebarman to check up
* FranciscoD go over draft post
* dhanesh95 FranciscoD finish post and aim to publish before next
meeting
* FranciscoD update wiki page with information about badges from
https://pagure.io/fedora-join/Fedora-Join/issue/33
* FranciscoD close https://pagure.io/fedora-join/Fedora-Join/issue/33
* FranciscoD send e-mails to ML about tickets that need discussing one
by one
* FranciscoD send out logs
* FranciscoD update next meeting page
* FranciscoD end meeting
* s14ck
* s14ck Create tickets with classroom session proposals
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* FranciscoD (138)
* dhanesh95 (35)
* zodbot (30)
* bt0 (27)
* hellbanger (15)
* s14ck (15)
* fdelapena (5)
* x3mboy_ (0)
* dukebarman (0)
* linuxmodder (0)
--
Thanks,
Regards,
Ankur Sinha "FranciscoD"
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
5 years, 2 months