= phenomenon = Different products may wish to have different (public) services available by default.
= reason = The different products have different target use-cases. It will likely make sense for them to provide different default services (carefully evaluated for security vs. convenience).
= recommendation = FESCo should approve a blanket permission for the Product WGs to decide on the suitability of starting a service by default without having to come to FESCo every time.
Should there be a requirement for those to be tracked by each product in some organized fashion?
Replying to [comment:1 jwboyer]:
That is a perfectly reasonable request. Yes, I'd say that we should probably all share a Wiki page listing the services approved by the WGs.
I'm not optimistic about our ability to keep wiki pages in sync with reality. What if we point to the rpm with the presets as the authoritative documentation, possibly with asking for the changelog to refer to list or ticket discussion for each service?
I think we agree that we want it tracked. I'm not sure this ticket is the right forum for deciding on implementation.
The more important question is whether FESCo feels comfortable ceding decisions on default services to the Working Groups.
I am +1, to be clear.
Adding meeting keyword.
FESCo grants WG's the right to decide default services (+6,0,0)
Most folks seemed to like that the tracking be in the preset files that are actually used (wherever they end up). devel list to figure that out.
Login to comment on this ticket.