Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

README: Add migration guide to libvlcsharp #645

Merged
merged 1 commit into from
May 19, 2020

Conversation

mfkl
Copy link
Contributor

@mfkl mfkl commented May 19, 2020

No description provided.

@jeremyVignelles jeremyVignelles merged commit 2f28a71 into ZeBobo5:develop May 19, 2020
@mfkl mfkl deleted the docs/add-migration-guide branch May 19, 2020 08:55
@ZeBobo5
Copy link
Owner

ZeBobo5 commented May 19, 2020

😪 Is it the end of my oldest open sourced project... ? Not enough time to manage it, despite help from @jeremyVignelles and you, @mfkl... Thanks to you for all 🙏 Hope to have time to contribute on LibVLCSharp. More particularly to manage options, WPF, WinUI and any more coming 😁

@jeremyVignelles
Copy link
Collaborator

Hi @ZeBobo5.
I understand your feeling, but it's not the end of your project, it's its retirement.
It did serve well for many years, and helped many of us use VLC inside our apps. As it was the best libVLC binding available in its time, you should be proud of yourself.
Now, usages have evolved, and evolving both LibVLCSharp and Vlc.DotNet would be a waste of time, and you know that maintaining an open source project like this one takes time.
I'm working closely with @mfkl, full-time employee at VideoLabs, on LibVLCSharp to improve the library while I am making the transition at work. It was a fantastic opportunity to maintain this project, that allowed me to meet the great folks of VideoLAN, and get a better understanding of how video works. Thanks a lot for that @ZeBobo5 !

I will keep on maintaining this project for as long as I can, but will transition my efforts to LibVLCSharp. As you said, great things are coming to the .NET ecosystem 🙂

@jbkempf
Copy link

jbkempf commented May 20, 2020

@ZeBobo5 could you please mail me? We have things to send to you!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants