-
Notifications
You must be signed in to change notification settings - Fork 258
Add Windows Workgroup #1222
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
base: main
Are you sure you want to change the base?
Add Windows Workgroup #1222
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| - name: Saleem Abdulrasool | ||
| handle: compnerd | ||
| github: compnerd | ||
| affiliation: The Browser Company of New York | ||
| chair: true | ||
|
|
||
| - name: Alastair Houghton | ||
| handle: al45tair | ||
| github: al45tair | ||
| affiliation: Apple (Swift) | ||
|
|
||
| - name: Carl Peto | ||
| handle: carlos4242 | ||
| github: carlpeto | ||
| affiliation: Apple (Swift) | ||
|
|
||
| - name: Charles Zablit | ||
| handle: c_zablit | ||
| github: charles-zablit | ||
| affiliation: Apple (LLDB) | ||
|
|
||
| - name: Clinton Nkwocha | ||
| handle: clintonpi | ||
| github: clintonpi | ||
| affiliation: Apple (Standard Library/Foundation) | ||
|
|
||
| - name: Doug Schaefer | ||
| handle: dschaefer2 | ||
| github: dschaefer2 | ||
| affiliation: Apple (SwiftPM) | ||
|
|
||
| - name: Mohamed Hegazy | ||
| handle: mhegazy | ||
| github: mhegazy | ||
| affiliation: The Browser Company of New York |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,77 @@ | ||
| --- | ||
| layout: page | ||
| title: Windows Workgroup | ||
| --- | ||
|
|
||
| The Windows workgroup is a team that promotes the use of Swift for developing Windows applications. | ||
|
|
||
| ## Charter | ||
|
|
||
| The goal of the Windows workgroup is to maintain Swift support for Windows, allowing users to develop Windows applications using the Swift language and its associated tools. | ||
|
|
||
| The Windows workgroup will: | ||
|
|
||
| * Improve and maintain Windows support for the official Swift distribution. | ||
| * Recommend enhancements to core Swift packages such as Foundation and Dispatch to work better with Windows idioms | ||
| * Make recommendations to the Swift Project about the direction of future Windows support in Swift | ||
| * Identify and recommend best practices for bridging between Swift and the Windows API, and for shipping Swift libraries with Windows applications | ||
| * Improve and maintain support for debugging Swift applications on Windows | ||
| * Advise and assist with adding support for Windows to various community Swift packages | ||
|
|
||
| ## Communication | ||
|
|
||
| The Swift Windows workgroup uses the [Swift Windows forum](https://forums.swift.org/c/platform/windows/67) for general discussions. It can also be contacted privately by messaging [@windows-workgroup](https://forums.swift.org/g/windows-workgroup) on the Swift Forums. | ||
|
|
||
| ## Membership | ||
|
|
||
| Membership in the Windows workgroup is open to anyone who wishes to contribute. Members communicate with each other over regular video calls and on the Swift forums. | ||
|
|
||
| The Windows workgroup adheres to the Swift code of conduct. If community members have any concerns about the adherence of the workgroup or one of its members to the code of conduct, they should contact a member of the Swift Core Team. | ||
|
|
||
| The Platform Steering Group selects one member of the Windows 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. | ||
|
|
||
| Where the workgroup is uncertain of or unable to agree on the way forward, members may raise issues to the relevant Steering Group(s) for consideration. Significant decisions should be made following the usual Swift Evolution process to allow for community participation and Steering Group oversight. | ||
|
|
||
| The core members of the Windows workgroup are: | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think that we should be following the C++ WG model, and not have explicit membership lists or the distinction of "core" vs "non-core" members.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We discussed this in the Platform Steering Group meeting. The alternatives are:
We definitely don't want to do (3). I'd suggested (2) partly because I didn't realise the aliases had public member lists, but partly also because I thought it would be useful as a way for people to see that there was an increasing effort being put into support for Swift and its ecosystem on Windows (I'm not sure (1) quite gets us that, but it is at least more transparent than I had originally realised). Personally, I still like (2). I know @compnerd prefers (1). Happy to leave the final decision up to Core Team. |
||
|
|
||
| {% assign people = site.data['windows-workgroup'].members | sort: "name" %} | ||
| <ul> | ||
| {% for person in people %} | ||
| <li>{{ person.name }} | ||
| {%- if person.chair -%} | ||
| (Chair) | ||
| {% endif %} | ||
| {%- 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> | ||
|
|
||
| Core members have no additional rights or responsibilities, but are generally people who work on Swift for Windows as part of their day-to-day jobs; they are listed here solely to provide stable points of contact for the workgroup. If you would like to be added to the list of core members, please reach out to a current core member, or send a request to the [Windows workgroup](https://forums.swift.org/g/windows-workgroup) directly. | ||
|
|
||
| ## Meetings | ||
|
|
||
| The Windows workgroup meets biweekly on Wednesday at 9am PST (U.S. Pacific Time). | ||
|
|
||
| Workgroup meetings are meant for open discussion and any Swift community member may attend by sending a message to [@windows-workgroup](https://forums.swift.org/new-message?groupname=windows-workgroup) beforehand to request an invite. | ||
|
|
||
| ## 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 Windows support library projects. | ||
| * Discuss ideas on the Swift Forums. You can create new topics in the [Windows](https://forums.swift.org/c/platform/windows/67) category, or add the windows tag to any topic. | ||
| * Develop new tools to aid the Windows experience or improve existing ones. | ||
| * Provide feedback to the members of the Windows workgroup directly by sending a message to [@windows-workgroup](https://forums.swift.org/new-message?groupname=windows-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 Windows workgroup’s regular video meetings. Send a message to [@windows-workgroup](https://forums.swift.org/new-message?groupname=windows-workgroup) to request access. | ||
Uh oh!
There was an error while loading. Please reload this page.