An important characteristic of working on Open Source is that we work in the open and that everything is shared. People that participate to GSoC will learn and experiment this way of communicating and working.
I receive several invites for private conversations on Gitter.
I prefer to avoid these 1:1 conversations. Please ask your questions or make your points publicly: there is no stupid question, others will benefit for the question and the answer, and there are no secrets to hide.
I understand that required to communicate publicly is difficult, gives you the impression to be in danger, and looks weird. This is probably completely new to many but it is part of the GSoC teaching and the ways of OSS.
You can mention me directly in public messages (and remind me if you didn't get the expected answer). But I will not get into private conversation. Thank you for your understanding.
Although we are quite early in GSoC2023, a lot of members of this channel are wondering how is works, how to prepare, and many other questions.
We are preparing an online session where we will answer as many question as we can. (The session will recorded if you aren't available at that time). We plan to have that first session begin December.
Stay tuned. We will announce this session on various channels.
In the meantime, read all the available documentation, on the GSoC, or on the Jenkins.io site (sub-projects menu). Of particular interest are the recommendations for contributors (https://www.jenkins.io/projects/gsoc/students/)
And of course, get confortable with java development, read Jenkins documentation, install your own server and experiment. And look at some beginner issues and try to contribute to learn the process. We'll come back on this during our online session.
There is our list of open newbie friendly issues: https://issues.jenkins.io/issues/?jql=labels%20%3D%20newbie-friendly
You can search there for the keyword test
Sure @shraddha761 . https://github.com/jenkinsci/gitlab-plugin is a plugin that is looking for someone to adopt it. https://www.jenkins.io/doc/developer/tutorial-improve/ is a tutorial of steps that can improve a plugin through a series of small, useful pull requests. If that list is complete, then there is a Google Doc that lists many more ideas at https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit#heading=h.hvd0nm6pz5o4
This chat channel contains many other suggestions of ways that new contributors can help.
You can look in here: https://github.com/jenkinsci/lockable-resources-plugin we still need support and few issues for beginners https://github.com/jenkinsci/lockable-resources-plugin/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22. In that case I would do my best to support you.
See the suggestions at https://www.jenkins.io/events/hacktoberfest/#where-to-contribute for good starter ideas
Many others available in the history of this chat channel
Do you think I can pick some documentation good first issues too?
I would like to work on this one: jenkinsci/lockable-resources-plugin#322
The only description the issue contains is:
please show example with Declarative syntax
This is not quite descriptive for me :(
I understand what
declarative syntax is. But I do not know what examples it speaks of?
I would recommend looking into jenkins declarative syntax. It's a core part of pipelines and jenkins now.
The current examples in readme.md are scripted syntaz
I have commented my doubt on Github: https://github.com/jenkinsci/lockable-resources-plugin/issues/322#issuecomment-1321034547