Hi all,
The PR proposes to integrate Arquillian
Smart Testing as experimental features into Che, so users will get the ability to enable/disable the capabilities provided by the plugin.
While this contribution is substantial, we don't really have a process for what's going or what's not going into our base distribution and I think it is a great opportunity to discuss it.
Arquillian Smart Testing, is a Red Hat influenced tech - while we appreciate the contribution, we, as a community, should integrate it into Che base distribution, only if we think it will bring value to Che.
Another aspect is once the plugin will be integrated into Che's base distribution, it will have to be maintained. It could be maintained with the help of the contributor, but we need to feel confortable enough with having the plugin into our codebase.
In theory, a plugin like this should be delivered independently from Che base distribution. The plugin could have its own release cycles and be installed/uninstalled by the end-users through a plugin marketplace. While this is definitely our target and we are making progress on it, we are not yet there. And until we have a plugin marketplace, we don't have a great alternative for this kind of plugin: it either goes into the base distribution of Che or it will not be very easy for the Che community to benefit from it.
I'd like to open the discussion on how we determine whether we should or should not add a plugin into our base distribution and if we think Arquillian Smart Testing should go into Che's base distribution.
My proposal would be:
- we open a discussion on che-dev mailing list during a week or so,
- once the period is over, we proceed by a community vote.
Thoughts?
Thanks!
Stévan.
