Il giorno mer 9 feb 2022 alle ore 16:39 赵井达 <[email protected]> ha
scritto:

> Hi, I am the head of the oVirt China User Community, which is founded and
> maintained by a non-profit organization. Our site: www.cnovirt.com.
>

Hi, a huge welcome to the user mailing list!




> First of all, thanks to the oVirt community for providing such an
> excellent open source project. We hope this project can continue
> forever.Our community currently has 1000+ registered users and an online
> communication group of 500+ enthusiasts.
>
> The work we have done so far:
> 1. Share the oVirt tutorial in Chinese.
> 2. Answer the questions in the use of oVirt. (Due to language problems,
> these users cannot directly participate in the maillist)
> 3. The oVirt mirror site has been established:
> http://mirror.massclouds.com/ovirt/, which is convenient for users in
> China to obtain and update software packages.
> 4. Publish and maintain oVirt desktop client software opencc,
> https://github.com/cnovirt/opencc-ovirt-pro,
> https://gitee.com/cnovirt/opencc-ovirt-pro.
> 5. Publish and maintain the offline version, merge the engine rpm into the
> node and remove the dependency on the external network during deployment.
> An iso image of the engine is made to facilitate independent deployment.
>
> We plan to contribute to the community in the following ways:
> 1. Collect user questions and feedback bugs to the community.
> 2. Try to participate in bug fixes.
> 3. Submit some code, such as oVirt's support for arm architecture and
> loongarch.
> 4. Participate in the preparation of Chinese version documents.
>

Looking forward to collaborating with the Chinese community!
+Avital Pinnick <[email protected]> a heads up we need to organize the
docs to be able to accept contributions in different languages if not
already able to accept contributions in that direction.




>
>
>
> --
> Jingda Zhao
>
> 发件人:"Sandro Bonazzola" <[email protected]>
> 发送日期:2022-02-07 15:54:30
> 收件人:"Nathanaël Blanchet" <[email protected]>,"Sanja Bonic" <
> [email protected]>
> 抄送人:"Thomas Hoberg" <[email protected]>,"oVirt Users" <[email protected]>
> 主题:[ovirt-users] Re: RHGS and RHV closing down: could you please put that
> on the home page?
>
>
>
> Il giorno sab 5 feb 2022 alle ore 13:30 Nathanaël Blanchet <
> [email protected]> ha scritto:
>
>> Can anybody from redhat confirm what is supposed here, all my staff
>> depends on the future of ovirt. How can we help to maintain this project
>> alive if redhat dev are not implicated anymore? I may donate some hardware
>> or is it unuseful?
>>
>
> Looks like this is being asked on several channels so I guess I'll end up
> writing a blog post or add some statement on the oVirt home page.
> Anyway, let me reiterate the message:
>
> This has been discussed publicly (
> https://lists.ovirt.org/archives/list/[email protected]/message/VIYHOW3WDR6N4APWIXQQONVHNXT3LK5L/
> )
> As a product, Redhat Virtualization has a different lifecycle than
> oVirt which is a community project.
> What will be the future of oVirt project depends on how the community will
> be shaping it.
> As members of the Red Hat team working on the oVirt project we are
> actively doing whatever we can to ensure that the project will survive
> after we'll stop working on it in the future.
> - We are moving the development to public platform (GitHub)
> - We are changing our release process to ship oVirt builds via widely
> supported community systems like Fedora COPR and CentOS CBS.
> - We started a peering program helping whoever would like to start having
> an active role in oVirt community trying to make the onboarding as easy as
> possible (
> https://lists.ovirt.org/archives/list/[email protected]/message/QQVZHTFBF7NVI67PYW2EY2HV5FSIBVF3/
> )
> - We actively reached out to Rocky Linux, Alma Linux and Oracle,  trying
> to engage them (CentOS is already engaged providing Community Build System
> for Virtualization SIG).
> So, what will be the future of the oVirt project depends on how the
> community will be shaping it. You're welcome to contribute to shaping this
> future! https://ovirt.org/develop/
>
> Up to now:
> - We have one person who reached out being interested to the peering
> program, Maithreyi Gopal  (
> https://lists.ovirt.org/archives/list/[email protected]/message/TSSE7U36UQTEGEBPWLUAETCGV4XOYLOL/
> ) and she's been peered with @Sanja Bonic <[email protected]> .
> - Rocky Linux replied they were discussing within the Foundation meeting
> about oVirt but I didn't got the result of the discussion yet.
> - Oracle replied they are looking to get a list of OLVM developers that
> can join the peering program in October 2021 but nobody reached out so far.
> - I don't remember I have seen any reply from Alma so far.
> - Tried to reach out to oVirt China http://www.cnovirt.com/ as they seems
> to ship a rebuild of oVirt targeting Chinese speaking users without any
> success
>
> That said, no : oVirt is not dead. oVirt 4.5 is being developed actively
> and it has 566 bugzilla tickets targeting it:
> https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovirt-4.5.0%20
> and 242 of them have been already handled.
>
>
>
>
>> Le 5 févr. 2022 11:31, Thomas Hoberg a écrit :
>>
>>
>> Please have a look here:
>> https://access.redhat.com/support/policy/updates/rhev/
>>
>> Without a commercial product to pay the vast majority of the developers,
>> there is just no chance oVirt can survive (unless you're ready to take
>> over). RHV 4.4 full support ends this August and that very likely means
>> that oVirt won't receive updates past July (judging by how things happened
>> with 4.3).
>>
>> And those will be CI tested against the Stream Beta not EL8 including
>> RHEL.
>>
>> Only with a RHV support contract ($) you will receive service until 2024
>> and with extended support ($$$) until 2026.
>>
>> oVirt is dead already. They have known since October. They should have
>> told us last year.
>> _______________________________________________
>> Users mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/[email protected]/message/ZPQ7DO75CVINFKDWXTSH6D2KM67L5FI4/
>> _______________________________________________
>> Users mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/[email protected]/message/DDYD27NS5QB5LIJJ3UQXKVKLLN3MYBYB/
>>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA <https://www.redhat.com/>
>
> [email protected]
> <https://www.redhat.com/>
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
>
> _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/[email protected]/message/PNYE27QDRA64HJVZYVPHJXMDSFMVFC7V/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA <https://www.redhat.com/>

[email protected]
<https://www.redhat.com/>

*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/NHESSFY6YVE7ZV5G5FNVLRQBBDOAERLU/

Reply via email to