#7 Welcome to Vipin
Closed: C: Inactive 3 years ago by nasirhm. Opened 4 years ago by alciregi.

Vipin got in touch with us on telegram.
He stated that he has a "good command on Jenkins so If we have any CI or automation work please let me know". So infrastructure team could be a good path, isn't it?
He will create a FAS account soon.


Hello Everyone,
My name is Vipin, I am from Rajasthan(India), I have done my graduation from Matsya University, I connect to a community DGPLUG during my college days and from there I got to know about the Opensource world. I am familiar with a few technologies (Jenkins, Python, Shell) and I am using Fedora since 4 years.

Thanks

Hello Everyone,
My name is Vipin, I am from Rajasthan(India), I have done my graduation from Matsya University, I connect to a community DGPLUG during my college days and from there I got to know about the Opensource world. I am familiar with a few technologies (Jenkins, Python, Shell) and I am using Fedora since 4 years.
Thanks

Hi @kumarvipinyadav : it's great to meet you! Welcome to Fedora, again!

Have you been looking around the community to see if anything interests you? We do have CI based on jenkins: https://fedoraproject.org/wiki/Jenkins@infra The work here would be to help administer the jenkins set up, which the infrastructure team would do.

On the other hand, if you are interested in using Jenkins, you could look into maintaining packages for Fedora---lots of python there: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers

What do you think? Or are you interested in developing applications using Python? The infrastructure team maintains lots of tools, most of which are python based. They do need some help, with fedocal for example. Take a look at the updates provided here:

https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/MEDDGWOW4KNHFKSXWD7LOROESSUVXIXM/

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

4 years ago

Sure I will go through the above links and let you know :smile:

Sure I will go through the above links and let you know 😄

Great, please feel free to comment with any questions/comments whenever you need to. We'll be following the tickets (and receive e-mail notifications etc.), so we will be able to reply when needed.

Hi @kumarvipinyadav : how are you doing? Did you have a chance to look through the links yet? What do you think?

How can we help?

PS: this is progress check 2/3. If we get to 3 progress checks without receiving a reply, the ticket will be closed as "inactive".

Metadata Update from @ankursinha:
- Issue untagged with: C: Progress check 1
- Issue tagged with: C: Progress check 2, I: Development

4 years ago

Metadata Update from @sash713:
- Issue assigned to kumarvipinyadav

4 years ago

Metadata Update from @alciregi:
- Issue tagged with: S: Subscribed

4 years ago

I have gone through URLs but they are related to building new projects or to fix python packages and I am still not familiar with building packages and all, I was thinking of converting Jenkins freestyle jobs into Pipeline jobs and make or Jenkins Infrastructure as code. Then it would be easy to manage jobs and changing them.

I have gone through URLs but they are related to building new projects or to fix python packages and I am still not familiar with building packages and all, I was thinking of converting Jenkins freestyle jobs into Pipeline jobs and make or Jenkins Infrastructure as code. Then it would be easy to manage jobs and changing them.

Right. As pointed out above, I know Fedora uses Jenkins for CI, but I've not heard of the community developing it. Jenkins has its own upstream development team and it merely deployed by the infrastructure team:

https://jenkins-fedora-infra.apps.ci.centos.org/
https://fedoraproject.org/wiki/Jenkins@infra

So I don't know if there's anything there to be done that's Jenkins related.

If you're looking to develop Jenkins, you should perhaps look at the upstream project here. They are also community based, and they'd have tasks that you can work on:

https://jenkins.io/participate/

So, to clarify: Fedora is a downstream Linux distribution. We take software from developers and build it so that users have easy access to it. We only develop tools required for this and other community work. We do not develop all the software that we provide. No Linux distribution does that---we're all downstream.

The closest you'll get to Jenkins in Fedora is:

Volunteering for communities isn't really "Oh, this is what I want to do, where can I do it?". It's more "I have these skills---how can I help?". So, the community has certain requirements, and you have certain skills. The idea is that you apply your skills, and learn the little bit more required to do what is needed by the community. Not the other way around: the community does not create new tasks that you can do with your skills.

Does that make sense? What do you think?

how have you been? We haven't known about you for a long time? Have you look at the link provide before about jenkins and infra TEAM? have you had any problems? Have you found any interesting to cooperate on according to your skills?

PS: this is progress check 2/3. If we get to 3 progress checks without receiving a reply, the ticket will be closed as "inactive".

Metadata Update from @hhlp:
- Issue untagged with: C: Progress check 2
- Issue tagged with: C: Progress check 3 - Final

4 years ago

Hi, Yes I look at the links, I don't have any problem and There are lot of interesting things, but I am good at writing Pipelines on Jenkins. And we do have Jenkins Jobs there But I can't see the configuration of them so not sure they are Freestyle or scripted. So not sure I can help in that section or not rest of the things are beyond my skills.

Hi @kumarvipinyadav

I understand what you're saying. Volunteering at communities works slightly differently. We do not go to the communities saying "this is what we can do---do you need this?", instead, we go to the communities asking "where can we help with these skills?". Now your jenkins pipeline writing skill is far too specific for most communities, so that particular skill will be rarely used. However, this implies you have a general knowledge of continuous integration, and advanced technical skills, which means you can do lots of other things that the community needs help with. You may have to learn a few new processes and tools, but for someone with your knowledge, that shouldn't be an issue.

Basically, in short: we all have our focus areas but we learn extra skills so that we can help the community in related tasks. We don't come in with skills and limit our tasks to those particular set of skills only. We evolve to fit with the community, not the other way around.

The infra folks manage jenkins. I do not know if they need anyone writing pipelines---things are already set up. If that's all you're interested in working on, you should e-mail the infra team and see if there's anything to be done. I'd suggest branching out a bit, though :)

https://fedoraproject.org/wiki/Infrastructure

Metadata Update from @ankursinha:
- Issue untagged with: C: Progress check 3 - Final
- Issue tagged with: S: Getting to know Fedora

4 years ago

okay, I will polish skills and try to learn a few more things and get back :)
by that time we can close the ticket.
And thanks for the guidelines.

Hey @kumarvipinyadav , we haven't heard from you in a while, Did you find something interesting to cooperate on ? or have you had any problems ?

P.S : I'm marking this ticket as C: Progress Check 1 , Once we hear back from you, I would love to update the ticket.

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

3 years ago

Hey @kumarvipinyadav, we haven't heard from you in a while, we hope you are fine.

P.S.: I'm marking this ticket as C: Progress Check 2 , Once we hear back from you, we would like to update this ticket.

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

3 years ago

Hi, all good thanks for asking, So I read about brew and koji the tools used to make RPMs of source code but these things are completely different from the work I do so they are taking time.
So you can mark the ticket as Progress check 3 or close it because I am not sure how much time it will take me to prepare for it and to learn how things work in a community. Once I learn all the things will come back.

Hey @kumarvipinyadav , It's been quite some time we haven't heard from you, Did you find something interesting to cooperate on ? or have you had any problems ?

I'm marking this ticket as C: Progress Check 3 and would be closing the issue , Once we hear back from you on other platforms, we would love to update it accordingly.

Hey @kumarvipinyadav If we don’t get a response in the next 7 days, we’ve not seen activity and we’ll have no choice but to close the ticket.

Closing the ticket is only a formal and operational to ask, then if you like, you can get in touch again with us using the various communication channels.

Metadata Update from @nasirhm:
- Issue untagged with: C: Progress check 2
- Issue tagged with: C: Progress check 3 - Final

3 years ago

Hey @kumarvipinyadav It's been quite some time we've heard back from you, We hope things are good at your side, I'm closing this ticket as C: Inactive. Please re-open the ticket whenever you wish and you can continue your journey into Fedora where you left off.

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

3 years ago

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

2 years ago

Login to comment on this ticket.