Upcoming graduation of KFServing

[Thea Lamkin]

Hi all, 

We wanted to let the Kubeflow contributor community know that kfserving will be graduating from the Kubeflow Project later this year, and will be transferred to an independent GitHub org under the stewardship of the Kubeflow Serving Working Group leads.  

The Kubeflow Project Steering and Serving Working Groups have been closely collaborating to prepare for this new chapter for KFServing and the Kubeflow ecosystem. We're excited to see KFServing's contributor and user communities continue to grow and address a wider set of use cases. We are also eager to use this opportunity to develop a new model for how libraries and apps developed outside of the Kubeflow project can integrate with core Kubeflow APIs and standards (see the recent work around conformance). 

Over the coming weeks, we'll be working to ensure the transfer involves minimal disruption to Kubeflow and KFServing' user and contributor experiences. Project committers will be giving more updates along the way in Kubeflow's and Serving WG's community meetings. 

As we approach the transfer date, the Kubeflow Project Steering Group will provide more detailed updates on KFServing's graduation here. 

Best,

Thea Lamkin, on behalf of the Kubeflow Project Steering Group & Kubeflow Serving Working Groups

[Animesh Singh]

Thanks Thea!

On behalf of the Kubeflow Serving Working Group, we want to say thanks for your stellar efforts towards driving and enabling this, to ensure the KFServing community continues to thrive as it reaches this  graduation! We are grateful for the collaboration and support from Kubeflow Project Steering Group!

Hi all

We will be using the KFServing Community Meeting tomorrow to handle any questions, if you have any!

KFServing Working Group US/EU

Wednesday, September 1⋅9:00 – 10:00am PST

Zoom: https://zoom.us/j/920703993

Thanks,

Animesh and Dan!!

--
You received this message because you are subscribed to the Google Groups "kubeflow-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubeflow-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubeflow-discuss/CAO-yHY8QtD%3Daw6ruqeghs3Yy%2BVosfxrG-AzZS14gAGps7g8%3DEQ%40mail.gmail.com.

[Jeremy Lewi]

Really great to see KFServing continue to grow.

Thank you Thea and the KFServing working group for driving this.

J

To view this discussion on the web visit https://groups.google.com/d/msgid/kubeflow-discuss/CABMfuRvDQEs5shE9%2B8LhEaNhnG5A8P2-NiVaJ-gDqXOAYQuiYA%40mail.gmail.com.

[Malini Bhandaru]

To view this discussion on the web visit https://groups.google.com/d/msgid/kubeflow-discuss/CACijwibXS5UXBt%2BsJrVMP%2BQi0_Viq-MfJknhgpy-izwrXyuUeg%40mail.gmail.com.

[Constantinos Venetsanopoulos]

Hello Thea,

Thank you for your email announcing the changes underway for the KFServing WG and plans to create its own organization. As KFServing contributors, we will work closely with the KFServing WG leads to see how we can keep contributing to kserve and get more involved in the new organization, so we can help the best we can.

I want to follow up on a very critical point that you made in your email:

> Over the coming weeks, we'll be working to ensure the transfer involves minimal disruption to Kubeflow and KFserving's user and contributor experiences.

This effort by all of us is extremely important to the Kubeflow community. Currently, there are a lot of users, companies and independent organizations that use KFServing as part of Kubeflow in production, so we want to ensure that all these parties are still very well supported, and enjoy a seamless experience with this move to kserve. Per the last two KFServing meetings, we know that the new organization is not planning to support previous versions of KFServing, currently in the kfserving repository.

Thus, once the "graduation" and transfer is complete in the following weeks, we would like to propose that we repurpose the current KFServing WG and repo with the purpose of keeping the latest KFServing version supported as an LTS version for at least a year after the transfer is complete. This should be for bug fixes or integration work as other Kubeflow components evolve. All new features should go to the new organization (kserve). Arrikto is planning to provide all the resources required for this effort, but we will encourage anyone interested to get involved with Arrikto in the repurposed WG. The whole idea is to have in place a concrete action plan to achieve the objective you laid out in your email -- ensure that users are happy and that they get the smoothest possible transition to kserve when the time is right for them. We are going to provide these resources in addition to the contributions that we are planning to make to the new org.

We hope that we can work together as we outlined above to ensure the success of all of the customers using Kubeflow today. We will work with the new WG team to solve customer issues and we will get involved in the new era of kserve to bring as much value as we can.

Best,
Constantinos

On Tue, Aug 31, 2021 at 3:02 PM 'Thea Lamkin' via kubeflow-discuss <kubeflow...@googlegroups.com> wrote:

[dan sun]

Hi Constantinos:
     There is not going to be any change in WG and the project mission, except that it's being developed in a new github organization under a new name. The Kubeflow Serving WG intends to support v0.5+ for next 6 months at least and we have also developed and documented the kfserving-> kserve migration process. If you need more information please reach out to us, and we can discuss.

Best
-Dan

To view this discussion on the web visit https://groups.google.com/d/msgid/kubeflow-discuss/CA%2BWLfo7Xguz6V%3DRQpzQbG5kBVHt4ZM%2BEJf1VGfa%2BLVqg3KtrEA%40mail.gmail.com.

[Constantinos Venetsanopoulos]

Hello Dan,

I thought I had understood from Thea's email above, and your description during the follow-up KFServing meeting, but now I'm a bit confused.

My understanding from Thea's email is that KFServing is "graduating from the Kubeflow Project", which means that after the migration is done, it is not going to be governed by the Kubeflow PSG anymore, and thus the current WG either. And I assume that there is going to be a different governing structure in the new org, not adhering to the current Kubeflow governance docs, correct? Isn't this why we are changing the name as well? Else why would we change the name, and make things difficult for users?

Or is the Kubeflow PSG (Google), going to govern at the top level the new GitHub org as well? My understanding was that this isn't the case, and we haven't seen any relevant document or decision about this from Google, correct?

Best,

Constantinos

[Animesh Singh]

Hi Constantinos

What Dan means is that the only immediate change going forward is going to be the change for github repo to be in a new github organization. 

For now, KServe WG Governing leadership remains the same as KFServing WG leadership. Additionally it will be the same biweekly meetings for design discussions and communication.  Also we intend to support KFServing prior version for next six months. Vis a vis actual governance structure for KServe, that's something which will gradually evolve.

We will be publishing a blog soon with more details, and if there are questions after - let's discuss on one of the community meetings.  

Hope this clarifies.

Thanks,

Animesh

To view this discussion on the web visit https://groups.google.com/d/msgid/kubeflow-discuss/CA%2BWLfo4crF9f1kFSBXVrrh9T%3DZtXqEL_HhaEncNdf4d8qQ5LDg%40mail.gmail.com.

[Thea Lamkin]

To follow up on this, the KFServing maintainers will be presenting the transfer plan and answering questions in this evening's community meeting at 5:30PM PT (apologies for the late notice). 

You can access the community calendar for meeting information here: https://calendar.google.com/calendar/u/0/embed?src=kubeflow.org_7l5vnb...@group.calendar.google.com&ctz=America/Los_Angeles

-Thea 

[Constantinos Venetsanopoulos]

Thea,

Unfortunately, this is indeed quite of a late notice for me, since I have other conflicts today, which I can't reschedule. I will go through the recording of the meeting though, and come back with comments/questions.

Thank you,

Constantinos

To view this discussion on the web visit https://groups.google.com/d/msgid/kubeflow-discuss/CAO-yHY9CMOXaAFdVc2vLrKSwo6Z97ko95ju_aTzA_oQK%2BHuEcg%40mail.gmail.com.