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

Add Android Workgroup charter and membership list #925

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

marcprux
Copy link

Motivation:

From the discussion at https://forums.swift.org/t/swift-on-android-working-group/77780/25 and in messages with @al45tair, this PR adds the Android WG charter for review by the Core Team and eventual publication to swift.org.

Modifications:

Result:

The Android Workgroup charter and membership will be published to swift.org

@marcprux
Copy link
Author

The Android Workgroup will:

* Coordinate the development of a reference Swift Android SDK
* Improve and maintain Android support for the official Swift distribution, eliminating the need for out-of-tree or downstream forks
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is anybody actually doing this? I think in-tree support is pretty good now, with downstream mostly just applying a few patches, ie nobody is maintaining an actual fork to my knowledge.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed that I don't know of anyone currently doing this. This specific point was requested by the PSG. I suspect – and perhaps one of them might confirm – that the goal is for the official Android SDK to be sufficiently adaptable to multiple Android environments (smartphone, embedded, car, TV. etc.) so as to make it unnecessary for a fork to have be created to support such an environment.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I know, nobody has ever tried Swift on anything other than Android smartphones, so if those other Android environments require more work, nobody has even started on that.

I suggest you change "forks" to "patches", as that more accurately characterizes where the Android platform support is today for the dominant smartphone usecase, ie nobody has needed a fork in awhile.

@al45tair
Copy link
Contributor

@etcwilde You should probably look over this also.

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