fperez
commented
2 years ago First, thanks a lot for proposing this, and for the amazing work the entire Elyra team has done! It's a great contribution to the growing ecosystem of Jupyter tools for various use cases, with impressive functionality.
Now - what follows is just my personal take, not in any way an "official" stance, and I'd be happy to hear other voices. I also want to caveat this with the fact that I don't personally use Elyra, so this is a high-level perspective, and I'd be happy to be corrected on any misconceptions.
That said - my impression is that pulling Elyra in as a core Jupyter project would be a stretch: Jupyter isn't an ML-specific tool (while many people do ML with it), and Elyra is a fairly complex codebase aimed at this particular use case. It takes advantage wonderfully of various aspects of Jupyter, but for example maintaining pieces of it would probably be a tough stretch for any "regular" Jupyter developer who was not part of the Elyra team.
Having said that, as a project, we absolutely want to be a great foundation for projects and communities like Elyra, regardless of how specialized their use cases may be!
So I would ask instead:
- Are there aspects of Elyra that make sense to fold back into existing Jupyter components? If so, are there any barriers to that happening we could lower/remove, or ways in which Jupyter could help the Elyra team better achieve their goals?
- Are there pieces of the Jupyter APIs, protocols, etc. where modifications could be made to help Elyra? If so, those can be discussed (either as narrow PRs or larger scope JEPs if needed).
- Are there other ways, beyond code, where Jupyter could help the Elyra team? For example, regarding community building, visibility, integration, etc - maybe we can find other ways to signal to the broader community how projects like Elyra are part of this "extended ecosystem," and highly valued and important, without assuming a direct maintenance burden?
I think all of the above, from software to community work, are fair game to improve the experience and processes for Elyra users and developers. But for the Jupyter teams, who are already stretched pretty thin, I think it would be a strategically risky stretch to absorb this maintenance and development commitment.
Again - I hope this does not come across in any way as negative towards Elyra or the team: the project is awesome, and the team has been a wonderful citizen of the Jupyter community. But we should find ways to continue building on that track record without necessarily taking on potentially unsustainable responsibilities both towards Elyra and the rest of Jupyter.
davidbrochart
westurner
lresende
We propose to make Elyra an official Jupyter subproject.