On Mon, Nov 7, 2016 at 4:13 AM, Jan Kurik <jku...@redhat.com> wrote: > For the Fedora 26 timeframe, we will lock down the users who can > submit to the MBS to a small number of Modularity WG members. This is > not ideal, but the thought is that we want to limit the amount of spam > that the MBS will impose on the production koji instance - we don't > want to interfere with the general release of Fedora 26. >
Is the intention then that users will be able to install modules on their system and have things work within the Fedora 26 timeframe, or would that not be possible until Fedora 27, assuming nothing slips? It seems like that would require at least one other change proposal (probably a system-wide one). I ask as someone who's aware that Modularity is being worked on but not too clear on what it's actually going to wind up looking like and how my system / our package collection is going to change as a result. By which I mean, I understand the goal and basic concept (split packages into higher level units), but I'm iffy on the implementation details, and if we're at the point where things are going to start getting deployed in upcoming releases I'd like to read more about them. A lot of the wiki pages on modularity [1] seem to be focused on "why is modularity a good idea" or "how do I contribute to modularity projects", but neither of these is quite what I'm looking for. Is there a "Fedora Modularity for current developers" writeup somewhere? (by which I mean "Fedora developers" in general). Ben Rosser [1] https://fedoraproject.org/wiki/Modularity
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
