#41 Welcome to Fedora @aelnor
Closed: C: Inactive 11 months ago by t0xic0der. Opened 2 years ago by nasirhm.

Hello aelnor! Welcome to Fedora!

Before we begin, please subscribe to the Fedora join mailing list at
fedora-join@lists.fedoraproject.org
.
We use this list for general discussion, and it is also where the community
shares tasks that need help.

Then, could you please introduce yourself (preferably on the list) so that the
community can get to know you? (interests, skills, anything you wish to say
about yourself really)

In the meantime, these links would be a good read. They tell you what the
Free/Open Source community is about, and then they'll introduce you to Fedora:
what Fedora is all about, and what we do, and of course, how we do it:

If you have any questions at all, please ask! We'll use this ticket to keep in
touch! :)


Done :)
I've subscribed to the list and sent my introdution.
I've taken a look at the additional info as well.

Metadata Update from @ankursinha:
- Issue untagged with: C: Introduction requested
- Issue tagged with: S: Introduced myself

2 years ago

I think I still have a couple of questions. It is not clear for how the general roadmap for a rookie like me looks like. Let's take GNOME for example since I've already contributed. The GNOME website has a guidance for those looking to contribute and it leads to a number of open issues tagged as 'good first issue' or something like that.

And it's pretty clear for me how to help fixing those simple minor bugs, make merge requests and so on. What is unclear is how a person that fixes bugs transitions to a person that can help develop features and work on more critical parts? Don't get me wrong, I have nothing against fixing bugs and don't want to jump out and immediately start working on the most critical features that define releases, but I'd like to understand how the path looks like.

The same questions more or less apply to all the projects that have been mentioned. For example what should I do if I'd like to maintain a package but I don't know what packages I can maintain? Should I join the mailing list and start asking these questions there?
And what if I'd like to work on infrastructure: should I start with easyfix bugs and see how it goes?

I think I still have a couple of questions. It is not clear for how the general roadmap for a rookie like me looks like. Let's take GNOME for example since I've already contributed. The GNOME website has a guidance for those looking to contribute and it leads to a number of open issues tagged as 'good first issue' or something like that.

https://fedoraproject.org/easyfix/

And it's pretty clear for me how to help fixing those simple minor bugs, make merge requests and so on. What is unclear is how a person that fixes bugs transitions to a person that can help develop features and work on more critical parts? Don't get me wrong, I have nothing against fixing bugs and don't want to jump out and immediately start working on the most critical features that define releases, but I'd like to understand how the path looks like.

Well, it depends from person to person. You explore the project starting with small/easy fixes. Once you are comfortable with the project i.e understand what the project's overall goal is, how the code is intended to be, how to CI works etc etc, you can start taking bigger tasks. Then comes the point where you know the path and potential of projects (because you are familiar with it?) and may propose a change/feature.
What I am saying is not written in stone.. this is just a way/perspective. You may have a different path for this.
Other way is request as a consumer. Let's say project X achieves task Y but you know that if it could also achieve Z, it could replace 2-3 other tools that can be eliminated. Now then you request that feature and possibly help with that and be involved in development with others.

The same questions more or less apply to all the projects that have been mentioned. For example what should I do if I'd like to maintain a package but I don't know what packages I can maintain? Should I join the mailing list and start asking these questions there?

The best way I can recommend (different people will have different views) is to see what packages are in orphan stage or people who don't want to maintain and you use that (so will like to see it). and same goes for other packages that you want to see in fedora and are not yet packaged.

And what if I'd like to work on infrastructure: should I start with easyfix bugs and see how it goes?

yeah, that sounds like a good idea.
The thing with Infra is that it's comparatively difficult to start (since privileges)
but easy-fixes are the right place to start

And what if I'd like to work on infrastructure: should I start with easyfix bugs and see how it goes?

also, take a look at this doc
https://fedoraproject.org/wiki/Infrastructure_Apprentice

Hello @aelnor
it is a while that this ticket is not updated.
How are you? How it is going?
Did you find something interesting? Do you have any question?

Metadata Update from @alciregi:
- Issue tagged with: C: Progress check 1

2 years ago

Hey @aelnor, it has been a while since we have heard from you. How is it going? Did you find anything interesting to work on? Also, should you have questions or queries - feel free to comment under this ticket and we'd be pleased to answer.

Metadata Update from @t0xic0der:
- Issue tagged with: C: Progress check 2

a year ago

Hi,

It has been a while since the last time we heard from you. I hope you are doing well and I just dropped by to see if you have found something interesting to work on. :-)

We love interacting so please feel free to reach out to us if there are any questions/concerns that you may have regarding how you can contribute to our projects.

According to the "Welcome" workflow, this ticket would be closed if no response is received within two weeks of time. That is, of course, not to say that the doors are closing as you can always come back and continue from wherever you left off previously.

Metadata Update from @t0xic0der:
- Issue tagged with: C: Progress check 3 - Final

a year ago

Metadata Update from @t0xic0der:
- Issue tagged with: S: User unresponsive

11 months ago

Metadata Update from @t0xic0der:
- Issue close_status updated to: C: Inactive
- Issue status updated to: Closed (was: Open)

11 months ago

Login to comment on this ticket.

Metadata