-
Notifications
You must be signed in to change notification settings - Fork 207
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
marcprux
wants to merge
2
commits into
swiftlang:main
Choose a base branch
from
marcprux:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+125
−0
Draft
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
- name: Abe White | ||
handle: aabewhite | ||
github: aabewhite | ||
affiliation: | ||
|
||
- name: Andrew Druk | ||
handle: andriydruk | ||
github: andriydruk | ||
affiliation: | ||
|
||
- name: Finagolfin | ||
handle: finagolfin | ||
github: finagolfin | ||
affiliation: | ||
|
||
- name: Jason Foreman | ||
handle: threeve | ||
github: threeve | ||
affiliation: | ||
|
||
- name: Joannis Orlandos | ||
handle: Joannis_Orlandos | ||
github: Joannis | ||
affiliation: | ||
|
||
- name: Luke Howard | ||
handle: lukeh | ||
github: lhoward | ||
affiliation: | ||
|
||
- name: Marc Prud’hommeaux | ||
handle: marcprux | ||
github: marcprux | ||
affiliation: | ||
|
||
- name: Robbert Brandsma | ||
handle: obbut | ||
github: obbut | ||
affiliation: | ||
|
||
- name: Saleem Abdulrasool | ||
handle: compnerd | ||
github: compnerd | ||
affiliation: | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,77 @@ | ||
--- | ||
layout: page | ||
title: Android Workgroup | ||
--- | ||
|
||
The Android Workgroup is a team that promotes the use of Swift for developing Android applications. | ||
|
||
## Charter | ||
|
||
The main goal of the Android Workgroup is to add and maintain Android as an officially supported platform for the Swift language. | ||
|
||
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 | ||
* Recommend enhancements to core Swift packages such as Foundation and Dispatch to work better with Android idioms | ||
* Work with the PSG to officially define platform support levels generally, and then working towards achieving official support of a particular level for Android | ||
* Determine the range of supported Android API levels and architectures for Swift integration | ||
* Develop [continuous integration](https://www.swift.org/documentation/continuous-integration/) for the [main Swift repository](https://ci-external.swift.org/job/oss-swift-RA-linux-ubuntu-24.04-android-arm64/) that adds Android checks for pull requests | ||
* Identify and recommend best practices for bridging between Swift and Android's Java SDK and packaging Swift libraries with Android apps | ||
* Develop support for debugging Swift applications on Android | ||
* Advise and assist with adding support for Android to various community Swift packages | ||
|
||
## Communication | ||
|
||
The Swift Android workgroup uses the [Swift Android forum](https://forums.swift.org/c/development/android) for general discussions. It can also be contacted privately by messaging [@android-workgroup](https://forums.swift.org/g/android-workgroup) on the Swift Forums. | ||
|
||
If any significant decisions are reached during one of the workgroup’s regular meetings, a member will post about them in the Forums within one week. The outcome of each proposal review will be announced by its review manager in a separate thread dedicated to that proposal. | ||
|
||
## Membership | ||
|
||
Membership in the Android Workgroup is contribution-based and expected to evolve over time. Adding new members and removing inactive ones is subject to a vote by the existing members and requires unanimous agreement. Membership is limited to ten members in total to keep the group small enough to be effective. A cap of two members per company is in place to avoid over-representation. | ||
|
||
The Core Team selects one member of the workgroup as the chair. The chair has no special authority over the workgroup, but they are responsible for ensuring its smooth functioning, including by: | ||
|
||
* organizing and leading regular meetings, | ||
* ensuring that the workgroup communicates effectively with the community, and | ||
* coordinating meetings between workgroup representatives and other Swift workgroups or teams when necessary. | ||
|
||
If you would like to join the workgroup, send a message to [@android-workgroup](https://forums.swift.org/new-message?groupname=android-workgroup) on the Forums and you will be invited to the next available group meeting to discuss it more. See Community participation for examples of ways to contribute and demonstrate your interest to the group. | ||
|
||
Workgroup members will try to make a decision independently by consensus whenever possible, and will raise issues to the Core Team when there are particular challenges with reaching consensus on significant decisions. | ||
|
||
The current members of the Android Workgroup are: | ||
|
||
{% assign people = site.data['android-workgroup'].members | sort: "name" %} | ||
<ul> | ||
{% for person in people %} | ||
<li>{{ person.name }} | ||
{%- if person.affiliation -%} | ||
, {{ person.affiliation }} | ||
{% endif %} | ||
{% if person.handle %} | ||
(<a href="https://forums.swift.org/u/{{person.handle}}/summary">@{{person.handle}}</a>) | ||
{% endif %} | ||
</li> | ||
{% endfor %} | ||
</ul> | ||
|
||
## Meetings | ||
|
||
The Android Workgroup meets biweekly on Wednesday at 2:00PM ET (US Eastern Time). The meetings take place in the weeks with the [odd week numbers](http://www.whatweekisit.org/). | ||
|
||
Many workgroup meetings are meant for open discussion and any Swift community member may attend by sending a message to [@android-workgroup](https://forums.swift.org/new-message?groupname=testing-workgroup) beforehand to request an invite. Some meetings are reserved for private discussion by group members, for example to make a decision on a proposal under review. | ||
|
||
## Community Participation | ||
|
||
Everyone is welcome to contribute in the following ways: | ||
|
||
* Participating in design discussions. | ||
* Asking or answering questions on the forums. | ||
* Reporting or triaging bugs. | ||
* Submitting pull requests to any of the Android support library projects. | ||
* Discuss ideas on the Swift Forums. You can create new topics in the [Android](https://forums.swift.org/c/development/android/115) category, or add the android tag to any topic. | ||
* Develop new tools to aid the Android experience or improve existing ones. | ||
* Provide feedback to the members of the Android Workgroup directly by sending a message to [@android-workgroup](https://forums.swift.org/new-message?groupname=android-workgroup) on the Forums. The workgroup chair brings outstanding issues and topics to the workgroup to discuss during regular meetings. The workgroup decides the actions for the issues. | ||
* Join the Android Workgroup’s regular video meetings. Send a message to [@android-workgroup](https://forums.swift.org/new-message?groupname=android-workgroup) to request access, since calls are easier to manage when kept to a relatively small number of participants. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.