Add the 2024 SSWG update blog post #576
Merged
+96
−1
Conversation
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
Co-authored-by: Franz Busch <privat@franz-busch.de>
Co-authored-by: Franz Busch <privat@franz-busch.de>
add survey wording
Co-authored-by: Franz Busch <privat@franz-busch.de>
Co-authored-by: Franz Busch <privat@franz-busch.de>
Co-authored-by: Franz Busch <privat@franz-busch.de>
Co-authored-by: Franz Busch <privat@franz-busch.de>
Co-authored-by: Franz Busch <privat@franz-busch.de>
Co-authored-by: Franz Busch <privat@franz-busch.de>
Joannis
requested review from
cthielen,
TimTr,
tkremenek and
tomerd
as code owners
MahdiBM
reviewed
Mar 2, 2024
ktoso
reviewed
Mar 4, 2024
ktoso
reviewed
Mar 4, 2024
| For example, while the majority of respondents already use Swift Concurrency, there remain challanges in some areas with adoption. | ||
| Among the highlights that shaped our goals for the next year were: a huge interest in standardized tooling for e.g. swift-format, as well as sourcekit-lsp and various IDEs. | ||
|
|
||
| We highly encourage you to have a look at the full [SSWG Community Survey 2024 Report](http://TODO), over on the Swift forums! |
There was a problem hiding this comment.
TODO: When we're ready to post I will make the forums post and then we merge the blog
ktoso
reviewed
Mar 4, 2024
finagolfin
reviewed
Mar 12, 2024
cthielen
requested changes
Mar 19, 2024
|
|
||
| # Ecosystem | ||
|
|
||
| Last year, we've seen seven new packages enter the SSWG incubation process. A tremendous amount of work has been done on these packages, showing how rapidly the ecosystem is expanding. |
There was a problem hiding this comment.
Anything to say about the incubation process in general?
|
|
||
| In preparation for Swift 6, we'll be looking at the impact of the strict concurrency checking across the server ecosystem. We are planning to enable strict checking on every incubated package and make each package compile warning free under the strict checking rules. | ||
|
|
||
| ## Adoption of Structured Concurrency |
There was a problem hiding this comment.
Repeating my comment above, this feels like a perennial goal. How can this be better framed in terms of progress, work to be done, etc.?
There was a problem hiding this comment.
@Joannis how about we state this as sswg maintained libs being expressed in surface APIs in concurrency concepts. Compatibility with service lifecycle etc?
|
|
||
| In addition, we're looking to connect developers by organising online user group meetings. We're currently planning the first Swift Server User Group meeting, with our goal being three or four meetings per year going forward. | ||
|
|
||
| Finally, we're seeing a new edition of the [Swift Server Conference](https://serversideswift.info) in 2024, which will be hosted in London. |
There was a problem hiding this comment.
Should be the proper name of the conference, e.g. "ServerSide.swift".
There was a problem hiding this comment.
Any concluding thoughts?
* Projects and members update * Update acceptance date
Joannis
requested review from
0xTim,
alexandersandberg,
daveverwer,
dempseyatgithub,
parispittman,
kaishin,
shahmishal and
federicobucchi
as code owners
cthielen
force-pushed
the
jo/update-sswg
branch
from
68cae8b
to
9936aeb
Compare
|
@Joannis @FranzBusch @ktoso I took an editorial pass - could you take a look and make sure the links I added are correct? Also, the link to the forums post will need to be added. Lastly, I had a little rebasing trouble, so please take a look to make sure I didn't lose any commit. Otherwise, how about 3/28/24 at 10a Pacific for publishing? |
Joannis
commented
Mar 27, 2024
| We've analyzed the responses to help direct the workgroup's efforts, as well as provide visibility into how the ecosystem is doing. For example, while the majority of respondents already use Swift Concurrency, there remain challenges in some areas with adoption. | ||
| We also learned that there is a lot of interest in standardized tooling such as `swift-format` and `sourcekit-lsp`, and interest in building out support for various IDEs. | ||
|
|
||
| You can read the full [SSWG Community Survey 2024 Report](http://TODO) over on the Swift forums. |
There was a problem hiding this comment.
Placing a marker for @ktoso here
|
@cthielen looks good to me |
shahmishal
reviewed
Mar 28, 2024
|
|
||
| The SSWG has continued to focus on growing the ecosystem by [incubating packages](/sswg/incubation-process.html) and providing guidance to package authors. We've seen a lot of new, in-development, and improved packages in the last year. | ||
|
|
||
| By participating in the [Google Summer of Code](https://www.swift.org/gsoc2024/), we were able to provide [swift-memcache-gsoc](https://github.com/swift-server/swift-memcache-gsoc), which makes it easier to communicate with Memcached servers. The wire protocol and higher-level connection APIs are done, with connection pools and key sharding on the roadmap. |
There was a problem hiding this comment.
Suggested change
| By participating in the [Google Summer of Code](https://www.swift.org/gsoc2024/), we were able to provide [swift-memcache-gsoc](https://github.com/swift-server/swift-memcache-gsoc), which makes it easier to communicate with Memcached servers. The wire protocol and higher-level connection APIs are done, with connection pools and key sharding on the roadmap. | |
| By participating in the [Google Summer of Code](/gsoc2024/), we were able to provide [swift-memcache-gsoc](https://github.com/swift-server/swift-memcache-gsoc), which makes it easier to communicate with Memcached servers. The wire protocol and higher-level connection APIs are done, with connection pools and key sharding on the roadmap. |
|
|
||
| ### Marketing Swift on the Server | ||
|
|
||
| Marketing Swift on the Server is a big focus area for 2024. With the introduction of the redesigned navigation of the [Swift.org](https://swift.org/) website, we'll be better able to showcase Swift on the Server. |
There was a problem hiding this comment.
Suggested change
| Marketing Swift on the Server is a big focus area for 2024. With the introduction of the redesigned navigation of the [Swift.org](https://swift.org/) website, we'll be better able to showcase Swift on the Server. | |
| Marketing Swift on the Server is a big focus area for 2024. With the introduction of the redesigned navigation of the [Swift.org](/) website, we'll be better able to showcase Swift on the Server. |
|
@swift-ci please test |
cthielen
approved these changes
Mar 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.