Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial support for visionOS #1083

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

pdiaz
Copy link

@pdiaz pdiaz commented Dec 22, 2024

Description

This is adding support for visionOS. No other platforms should be affected.

Type of Change

  • New feature
  • Bug fix
  • Documentation

Checks

  • Changes support all platforms (Android, iOS, Linux, macOS, tvOS)
  • Breaks existing functionality
  • Implementation is completed, not half-done
  • Is there another PR already created for this feature/bug fix

Tests

How are these changes verified? Please provide test instructions.
Also list any relevant details about your test configuration.

@pdiaz
Copy link
Author

pdiaz commented Jan 23, 2025

Do you need any more details to review and approve this?

@tanersener
Copy link
Collaborator

@pdiaz We had to retire the project. None of open PRs will be reviewed. See the main README.

@pdiaz
Copy link
Author

pdiaz commented Jan 23, 2025

It seems that I totally missed that notice. Thanks anyway! Will there any "designated" fork from which a community may continue forward?

@tanersener
Copy link
Collaborator

I wish there were, but so far nobody has expressed interest in maintaining the project.

If anyone does take up the responsibility, I’d be happy to include a link to their fork in the project README to help the community stay connected.

@CodeWithTamim
Copy link

@tanersener I wish to maintain the android project cause my app is running using it

@tanersener
Copy link
Collaborator

@CodeWithTamim It's great to see someone willing to keep the project going. I can add a link to your fork on the project page, but there should be something new there, like a release, so users have a reason to check it out.

@CodeWithTamim
Copy link

@CodeWithTamim It's great to see someone willing to keep the project going. I can add a link to your fork on the project page, but there should be something new there, like a release, so users have a reason to check it out.

I can migrate the Android part of the code from Java to Kotlin, leveraging modern Kotlin features like coroutines for better async handling, which aligns with modern Android development. I’ll also sync it with the latest FFmpeg features. Would that be okay?

@tanersener
Copy link
Collaborator

@CodeWithTamim Let me be clear: FFmpegKit is an open-source project. You are free to fork it, modify it, and implement new features. You don’t need our approval, nor do we dictate what you do with your fork. Many developers are already doing this.

Right now, people are asking if there’s an alternative, and my answer is that I don’t know of one.

What I’m saying is, if you create a maintained fork, I can add a link to it in the main README to direct users there. That way, when FFmpegKit stops working on April 1st, they’ll have a place to go.

The real question is: is your fork ready for other developers to use? That should be your main focus right now.

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

Successfully merging this pull request may close these issues.

3 participants