= Questions/Requested Information
Packager experience with modularity hasn't been all that great so far. People working on various parts of it are aware of some gaps but we need a) more user stories from the actual world, and b) find some way forward together where the "obvious" fix isn't practical or possible.
This is a half a day long birds of feather session with some modularity representatives. Packagers, users, release engineers, and pretty much everyone is welcome to contribute.
List each person by their name and FAS ID, as shown below:
No specific needs.
/cc @asamalik @langdon @sgallagh @mohanboddu @kevin @ignatenkobrain @ngompa @jmracek @dmach
I hope this would be useful, especially if we can identify specific pain points and how to solve them in a backwards-compatible manner.
It could be useful, I'm not sure what we'd be doing though. This also kind of aligns with what @ignatenkobrain and I are doing for #151.
You'd be doing the most important thing, bringing ideas :)
I think that bringing all our ideas, opinions, and experiences together, and combining them to a shared vision that we all understand and that ideally works for all of us, would be quite beneficial.
And potentially writing it down in a short, effective way, maybe with some guiding principles that would help us dealing with potential future issues would be even better.
A huge +1 to this!
+1
I would like to attend this talk.
Metadata Update from @mattdm: - Issue assigned to mattdm
Metadata Update from @mattdm: - Issue marked as blocking: #223 - Issue tagged with: Talk Accepted
We should figure out module retirement and fix it (or come up with a design for it and plan the work) during this session
Metadata Update from @riecatnor: - Issue close_status updated to: Resolved - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.