#151 [Talk-50] Improving Packaging Experience with Automation
Closed: Resolved 3 years ago by riecatnor. Opened 4 years ago by ignatenkobrain.

What is your proposal?

We are working on a Fedora Objective about saving packagers’ time with an automation related to building of their packages. That includes but not limited to automatic rebuild of packages on dependency changes, removing manual work on writing changelog both in spec and later in git and doing release bumps on rebuilds.

The talk will be split into 3 smaller parts:

  • Presenting Objective to the audience
  • Comparing workflow of Fedora packagers with other distributions with demo
  • Discussing the objective with audience and asking for a feedback

This talk is about presenting our ideas of how to improve the quality of life for packagers (the lifeblood of our distribution) and getting feedback (in a panel-ish form) about how to further refine and improve the packaging and maintenance experience. This is becoming increasingly important as the way we deliver software is increasing in complexity with things like modules and flatpaks and whatnot.

Who in addition to the speaker needs to be in the room for this to succeed? This could be the audience you need to reach, other participants in the conversation, or other stakeholders.

List each person by their name and FAS ID, as shown below:

Is this a…

  • 50 minute Talk

Anything else we need to know?

We will be using a laptop to present and do a demonstration, so a projector and wired networking for our demo to work would be very helpful.

Who are you?

  • Name: Igor Gnatenko, Neal Gompa
  • FAS ID: @ignatenkobrain, @ngompa
  • IRC Nick, if not FAS ID: ignatenkobrain, Son_Goku/Conan_Kudo/Pharaoh_Atem/King_InuYasha

I would like to attend this talk.

Metadata Update from @mattdm:
- Issue assigned to mattdm

4 years ago

Metadata Update from @mattdm:
- Issue tagged with: Talk Accepted

4 years ago

Metadata Update from @mattdm:
- Issue marked as blocking: #223

4 years ago

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

3 years ago

Login to comment on this ticket.