#99 Outreachy proposal: Support repo overrides in rpm-ostree
Closed: fixed 2 years ago by siddharthvipul1. Opened 3 years ago by jlebon.

This is a proposed project for Outreachy. Note that once this ticket is approved you will have to register as a mentor on the Outreachy page and enter this information again. Many of these questions are based on the application on the Outreachy website.

One-line name

Support repo overrides in rpm-ostree

Short title for this internship project proposal

Add support for rpm-ostree package overrides coming from remote yum repos.

Longer description of project

Today, rpm-ostree support overrides from locally downloaded RPM files. For example:

rpm-ostree override replace kernel.rpm

This works great, but is limiting. There are many situations where one would rather have an RPM override from yum repos, the same way one would usually simply yum install on a traditional system.

We want to teach rpm-ostree this ability. The command-line UX would be similar, for example:

rpm-ostree override replace kernel

Except that rpm-ostree would look for the specified package(s) in enabled yum repos.

Rough timeline/milestones

Week 1-2: Ramp up and set up developer environment.
Week 3-4: Finalize approach of implementation.
Week 5-9: Work on implementation, iterate based on feedback from mentors.
Week 10-12: Stretch goals based on interest. Some ideas include better overrides integration with COPR, Bodhi, and/or Koji, and writing a fedmag blog post about the new feature.

License of the project

GPLv2+ and MIT

Longevity (How long has the team accepted contributions)

The rpm-ostree project has been around for 8 years.

Community size

The rpm-ostree project is used in multiple Fedora variants (Fedora Silverblue, Fedora CoreOS, and Fedora IoT), as well as Red Hat Enterprise Linux CoreOS, the base platform for OCP.

How will this project benefit Fedora

Several Fedora editions use rpm-ostree, this will allow their users to more easily test and contribute to parts of the OS.

Project website

https://coreos.github.io/rpm-ostree/

Project repo

https://github.com/coreos/rpm-ostree

Where can an applicant find application tasks?

Here :)
And at https://github.com/coreos/rpm-ostree/.

IRC

freenode/#fedora-coreos

Skills required including what level and if they are optional

C/C++ and Rust - the project is slowly converting more code to Rust and that's preferred.


There will be three co-mentors.

Questions from the top level Outreachy Program for the mentor application (Jonathan Lebon):
- How long have you been contributing to the community: 7 years
- What is your current role: CoreOS engineer at Red Hat
- Have you mentored for a three-month internship program before: I haven't.
- Have you read the mentor page and understand the process of being a mentor: yes
- Are you available for 5 hours a week during the internship period: yes
- Are you available for 5-10 hours a week during the application period: yes
- Are you aware you need to sign a mentor contract: yes

Questions from the top level Outreachy Program for the mentor application (Timothée Ravier):
- How long have you been contributing to the community: 2 years
- What is your current role: CoreOS engineer at Red Hat
- Have you mentored for a three-month internship program before: yes
- Have you read the mentor page and understand the process of being a mentor: yes
- Are you available for 5 hours a week during the internship period: yes
- Are you available for 5-10 hours a week during the application period: yes
- Are you aware you need to sign a mentor contract: yes

Questions from the top level Outreachy Program for the mentor application (Colin Walters):
- How long have you been contributing to the community: 8 years
- What is your current role: CoreOS engineer at Red Hat
- Have you mentored for a three-month internship program before: no
- Have you read the mentor page and understand the process of being a mentor: yes
- Are you available for 5 hours a week during the internship period: yes
- Are you available for 5-10 hours a week during the application period: yes
- Are you aware you need to sign a mentor contract: yes


Thanks a lot @jlebon!
Love the project and I am really looking forward to it.
Can you please provide a rough timeline in what you expect interns to work/achieve?
This helps interns clarify requirement and road map and often help mentors+coordinators recognize "How we measure success of this project"

Thanks @siddharths , added a section with a rough timeline.

Metadata Update from @siddharthvipul1:
- Issue tagged with: Outreachy, project-idea

3 years ago

@jlebon, hey! can you sign up for outreachy account and submit the project there?
we will accept it after @riecatnor's +1
Deadline is March 7th, so please get it in there before that day :)

I am Siddharth Sharma, not the Siddharth you are looking for. Please
contact the concerned person to get the correct FAS information. Thank You.

On Fri, Mar 5, 2021 at 11:02 AM Jonathan Lebon pagure@pagure.io wrote:

jlebon added a new comment to an issue you are following:
Hi @siddharths, we've submitted the proposal: https://www.outreachy.org/outreachy-may-2021-internship-round/communities/fedora/support-repo-overrides-in-rpm-ostree/cfp/ .

To reply, visit the link below or just reply to this email
https://pagure.io/mentored-projects/issue/99

I am Siddharth Sharma, not the Siddharth you are looking for.

Yup sorry! Was a bit too fast with the auto-complete. :)

hi @jlebon,

  • The deadline for Fedora mentors to select their intern is May 10th. Do not communicate intern selection with applicants until the interns are announced on the alums page at May 17 at 4pm UTC

  • When the selected interns are announced, we will do an Intern introduction blogpost on the Fedora community blog and plan a social hour with all the mentors and interns (all within first 2 weeks of selection). This keeps the community informed of the efforts and coming work, and gives interns a chance to meet and greet peers other than just the "work" part

  • Outreachy program expects Interns to write/blog their work somewhere (can be their own blog), we would like to take summary of the work and publish a combined work of all interns in a community blog every 2-3 weeks. I will be sending an email to all the students and mentors with this info once selection is out.

I want to thank you once again for coming up with the project and mentoring the intern

Metadata Update from @siddharthvipul1:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata