#192 [Talk-50] Modularity: modularize or not to modularize?
Closed: Resolved 4 months ago by riecatnor. Opened a year ago by asamalik.

  1. What is your proposal?

The goal of this talk is to provide a higher-level guidance about more complex module packaging, and to set a common ground before discussing this and other topics at the Modularity & packager experience BoF.

I'll have a multiple packaging problems prepared, and demonstrating how Modularity can help with some of them, but also which ones Modularity can't help with. I'll offer existing non-modular solutions to some of the problems as well.

This is a higher-level talk than tooling and making modules, but more detailed and guiding than my previous introductory talks.

  1. 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:

Everyone at FESCo, so:

  • Kevin Fenzi (nirik)
  • Justin Forbes (jforbes)
  • Zbigniew Jędrzejewski-Szmek (zbyszek)
  • Miro Hrončok (churchyard/mhroncok)
  • Owen Taylor (otaylor)
  • Stephen Gallagher (sgallagh)
  • Igor Gnatenko (ignatenkobrain)
  • Aleksandra Fedorova (bookwar)
  • Petr Šabata (psabata)
  1. Is this a…
  • 50 minute Talk

... but I expect the talk to be 15-20 minutes, and a lot of discussion.

The reason I want to have all the discussion here and not just at the BoF I mentioned earlier is that I expect different audiences to be at both sessions. Here, I expect more people coming, mostly learning from each other and looking for answers. In the BoF we'll actually produce some better guidelines, and the audience is expected to be more focused on doing actual changes/enhancements to Modularity itself as opposed to just using it.

  1. Who are you?
  • Name: Adam Samalik
  • FAS ID: asamalik

CC Modularity people: @psabata @sgallagh @langdon @ignatenkobrain @merlinm @ngompa

CC remaining FESCo members: @nirik @jforbes @zbyszek @churchyard @otaylor @bookwar

I'd love to hear feedback from you and even suggestions of problems to solve and demonstrate.

Rather than listen for an hour long talk delivered by one of the interested parties, I'd prefer to gather and discuss this.

@churchyard This is a very good point, my intention is to have a lot of discussion in this session. I would normally go for 25 mins, but because I expect a long discussion, I went for 50 mins. I expect the actual talk to have no more than 15-20 minutes. So don't worry it won't be just me talking for an hour! Let me make that clear in the proposal.

I'll be there (if the talk is accepted).

+1, I'll be there

I am all for discussions, but the talk part with some problem statement is important

and moderation too :)

Metadata Update from @mattdm:
- Issue assigned to mattdm

a year ago

Metadata Update from @mattdm:
- Issue marked as blocking: #223
- Issue tagged with: Talk Accepted

a year ago

This now collides with @ignatenkobrain's automation talk.

@mattdm Looking at the schedule, this talk is at the same time as @sgallagh's Fedora Server talk and @ngompa and @ignatenkobrain's "Improving packaging experience with automation".

I need all three of them to be there for discussion, and also the "Improving packaging experience with automation" feels like it has the same audience. :(

Any chance we could reshuffle that a bit? (I know schedules are hard)

In the case of this conflict, I am afraid I'll miss this. Feel free to talk about this with me any time at Flock.

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

4 months ago

Login to comment on this ticket.