> There has been some sporadic discussions around the idea of pulling certain
> plugins into core at some point. I am sending this email along to spur a
> more centralized discussion around this issue. For example, the idea has
> been floated around to pull foreman-tasks into core or that the new remote
> execution work might be pulled into the core at some point. I think there
> are potentially three interpretations of 'pulled into core':
> 1) Making a plugin a hard dependency of Foreman
> 2) Literally merging the plugin's code into Foreman's as a singular code
> 3) Keeping the plugin as an engine, but maintaining it as a single code
> base (e.g. an engines/ directory)
With the foreman-tasks, as well as the remote execution, my assumption is
the evolution: from the hard-dependency to merging it directly to the core.
The benefit of not having the plugin in the core is possibility
to have faster release cycles: rolling the versions in the plugin, and keeping
the plugin compatible with multiple versions is somehow easier, than having
that in the core and backporting to multiple versions.
The ultimate goal, however, is to get the code merged into the core, to have
more maintenance power over it.
> The initial questions that come to my mind around this are:
> 1) What do we actually mean by pulling a plugin into core?
> 2) When does a plugin get pulled into Foreman core? e.g. What is the
> criteria for such?
The criteria for foreman-takss (and remote execution) are one of these:
a) multiple other plugins use it for their work, so it's extending
the platform itself - this is the foreman-tasks case
b) the core is using the functionality of the plugin: this should be the
case for both foreman-tasks (using that for async operations) and
remote_execution (using that for the puppet run and finish scripts).
> 3) What are the expectations (e.g. maturity, infrastructure testing setup)
> for a plugin that gets 'pulled into core' ?
The unit test coverage is one of the biggest requirements I'm aware of.
----- Original Message -----
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an
email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/d/optout.