Packit support for OBS

[dcermak]

Project Title:

Packit support for OBS

Description:

Packit is a CI system that builds rpms out of upstream projects. Currently it only supports building rpms in COPR and Koji. It would be beneficial for packit to gain support to build in OBS, as it would give access to more distributions and would allow packit to send submissions to openSUSE.

Deliverable:

• Implement support for the packit CLI to build on OBS (finish OBS build support packit/packit#2067)
• Add support for the packit server to build on OBS

stretch goals:

• implement support for sending submit requests on OBS via packit

Mentor:

@dcermak
@lachmanfrantisek

Skills:

• Python knowledge
• packaging rpms is beneficial

Skill Level:

Medium to Hard

Project Size:

Large Sized Project (350 hours)

Get started:

• get acquainted with OBS and the OBS API
• learn the basics of building RPMs in COPR, koji and OBS
• give packit a try

[johnathankahn]

Hey @dcermak
what will be the selection criteria ? what weightage will contributions hold ?

[ddemaio]

@johnathan2709 I'm answering for @dcermak as an admin for GSoC for our organization. As a mentoring organization, openSUSE evaluates and ranks submitted proposals based on our capacity and the slots Google allocates to us. Once we submit these rankings, our involvement is minimal. Mentor discussions and project considerations influence these rankings, but the final selection is beyond our control. A good bit of advice would be to engage with possible mentors and write a good proposal with detailed solutions, timelines and make sure to ask questions so your proposal is clearly understood by possible mentors.

[johnathankahn]

@ddemaio

As you are an project admin, I want to bring to your notice that three candidates have already commenced work on the project idea #186. However, what is troubling is that these candidates were seemingly added to a private Slack channel by Bryan Gartner(@bwgartner) approximately two months ago, without any public announcement or engagement.

It appears that these candidates have been receiving mentorship and guidance solely within this private Slack channel, completely bypassing any public channels of communication. This raises questions about the fairness of the mentorship process and suggests that there might be preferential treatment towards these candidates, potentially due to personal connections with the mentor(s).

It won't be outrageous to say that these candidates have already been selected as a mentee unofficially. It is disheartening to learn that while some candidates are receiving exclusive mentorship and support, others who are equally deserving and enthusiastic about contributing to the project are left no chance.

I strongly urge the OpenSUSE project team to review and rectify this situation to ensure fairness and equal opportunity for all candidates. I have also raised a concern regarding this to the GSOC admins.

I won't be expecting a reply but please look into this matter seriously, for the sake of keeping open source "open".

[ddemaio]

Thank you for the information @johnathan2709 I'll bring this up as a topic of discussion for all the mentors this year in our next meeting/communications. Issue #186 you mention has been around for a few years now and some mentees are now mentors. Both openSUSE and GSoC encourage mentorship to continue even after GSoC. I know Bryan has always been very helpful for those who have asked to be mentored. The means of communication for mentoring is for the parties involved to decide; slack, email, etc. Nevertheless, I will have the conversation and please know that I'm the one pressing the final submit button for the rankings after thoroughly discussing all the proposals with the team of mentors representing all the projects we have listed. We'll ensure the selection process is reviewed and discussed to ensure fairness and that steps are taken to make the mentorship process is seen as more inclusive and transparent.

[abhi-bhatra]

Hi @johnathankahn
Each year Bryan selects new candidates, not the repeating one. Also, the slack channel is open for all. Once, you show your interest in the project. Mentors add everyone to the slack. Every community in GSOC had their communication channel. So, SUSE uses slack, within slack community, anyone and everyone can come, contribute, share their work, and join the community call.
I think you have misunderstood, as selection criteria is completely unbiased. I was part of AEEW-GSOC in 2022, and after that I was still in the slack channel, but not as a GSOC contributor, instead, helping new contributors to start doing contribution. I join community calls regularly, just because I enjoy learning from Ann, Terry and Bryan. And assisting new contributors to getting started with Open Source.
I suggest you that first, you can show your interest in any idea, then comment down on how you can contribute. Once, you show your interest, you will be added to channel, where you can attend community calls and understand more about the idea. Ex-Contributors might also join the call, but for assisting and helping others, not to guarantee their selection.