Packages in each distributions are quite different. Why do we actually spend maintainers’ time on dealing with these things? I will go through differences in each ecosystem (Python, Ruby, Rust, …) between Fedora and other closest distributions and then we will discuss and try to find out what ideas are good, bad and figure out plan how to get to the future with same packaging across the world.
List each person by their name and FAS ID, as shown below:
My latop has HDMI and USB-C outputs. Required cables would be much appreciated.
ignatenkobrain
figure out plan to do exactly what?
I think @akien and @hellcp would definitely be interested in this too.
@churchyard basically how to proceed further. Whatever we decide is good in a packaging of distro X for ecosystem Y, we need to figure out how to make all distros to follow that pattern.
I can pitch in for Python, sure.
I'm not available to go to Flock, and sorry I am not a meeting person. Not sure what I could bring to the table, my knowledge of other distributions is extremely limited as I've stopped distro-hopping years ago. I don't know their process for package management. Last time I've checked, OpenSUSE Go packaging was fairly limited. I think we have the more advanced/complex one with the most unbundling than any other distro. It would be great if we could come with a common ground, but if that means reworking our macros stack I'm not really interested. Debian seems to have a solid team but I know nothing about their process and it seems hardly compatible with ours.
Also, @mcepl may be interested, as he's a SUSE Python guy now..
@ngompa I have suggested exactly this as a panel for this year PyConCZ. Unfortunately, the proposal was not accepted. Not sure whether I want to go to Budapest though.
Sounds interesting, I'll be there!
Metadata Update from @mattdm: - Issue assigned to mattdm
Given the abstract, should we change the title of this to focus specifically on collaboration for packaging?
Metadata Update from @mattdm: - Issue marked as blocking: #223 - Issue tagged with: Talk Accepted
@mattdm good idea, please change it.
cool. changed in the draft schedule.
Metadata Update from @riecatnor: - Issue close_status updated to: Resolved - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.