Participants
- Alexander Sandberg @alexandersandberg
- Dave Verwer @daveverwer
- Jame Dempsey @James_Dempsey
- Kristina Fox @kristina
- Mishal Shah @mishal_shah
- Michael Schinis @mschinis
- Paul Hudson @Paul_Hudson
- Reda Lemeden @kaishin
- Tim Codon @0xTim
- Tim Triemstra @TimTr
- Tom Doron @tomerd
Discussion summary
=> Welcome and introductions 
=> Overview of goals (Swift.org - Swift.org website)
Swift.org website goals include:
- Welcome newcomers with friendly information about Swift
- Help visitors of all skill levels get started developing with Swift
- Document the language, libraries, and best practices
- Announce new features, APIs, and tooling improvements
- Provide a safe, friendly place to interact with fellow Swift developers
- Promote activities occurring anywhere within the community
- Support collaboration and evolution in building the Swift ecosystem
Discussion
- Main goal is to make swift.org into more of a community resource
- Develop a community engagement strategy
- Prioritize cross cutting concerns like diversity, mentoring, and community culture
- Make swift.org into a platform for community members to show case their work and collaborate with others
- use the blog more, e.g show case community success stories
- integration with the forums or other collaboration tools
- Host resources or be a portal for resources that the community cares about
- conferences
- education website and online resources
- documentation of critical tools and libraries
- Domain specific documentation and guides (eg Swift on Server guides)
- Develop content vision and strategy
- Rewarding workflow for “drive-by” bug fixes
- Encourage creation of content by the community
- Interesting challenges:
- What process do we need to adopt to balance concerns about commercial interests (eg commercial conferences, books, blogs, etc) with making useful resources (commercial or not) available and easily found.
- What process do we need to adopt to avoid the impression of “picking winners” when featuring or linking content
- Making the content fresh and engaging
- Develop technical vision for a new version of the website
- Underlying technology would be Swift
- Probably continues to be a static file generator
- Focus is likely to wind down after initial push to release a new website, and shift to community building and content
- Develop UX and UI vision for the a version of the website
- UX/UI ideation in collaboration with Apple designers
- Define technical framework for implementing the vision (CSS, etc)
- Focus is likely to wind down after initial push to release a new website, and shift to community building and content
=> Overview of charter (Swift.org - Swift.org website workgroup (SWWG))
The main goal of the Swift website workgroup is to define a set of processes governing contributions to the Swift.org website and actively guide contributors along the website’s goals as the defined above.
In that capacity, workgroup members review proposals for changes to the website, either in pull requests or ideas posted to the workgroups formal communication channels and provide feedback in effort to integrate these changes in a way that is consistent with the website’s goals.
Workgroup member may also initiate projects to improve different aspects of the Swift.org website including it’s content, information design, UX and UI design, and technical infrastructure. For example, one of the initial workgroup goals is to kick off building a new website, built with Swift and a different information and UX/UI design.
Members of the Swift website workgroup serve at the discretion of the Swift core team and the Swift project lead, who has the ultimate authority over the workgroup decisions.
Discussion
- The workgroup is a steering committee. The main task is to come up with strategies and models to achieve the website goals, then find ways to work with others in the community to implement these strategies.
- Workgroup members are usually the most passionate about the domain and can (usually do) wear multiple hats: Both defining the vision and strategy (workgroup steering role) and initiate and lead project to implement aspects of the strategy (community members).
- Its is common that not everyone on the workgroup is interested in all topics, and folks can choose how to best spend their time
Decisions, and follow up action items
- Admin
- We will meeting every other week for 1h
- Tom to put out a doodle poll to figure out exact time and date
- Next few meetings may run a bit longer as we are in the “ideation chaos” phase, and need to give everyone time to share their vision and goals
- The workgroup will publicly publish meeting notes as forums thread (similar to server workgroup). We first publish them privately for workgroup scrutiny, then publish a public version.
- The workgroup will use a forum thread to capture meeting agenda in the weeks leading up to the next meeting (Tim C. already started one for next meeting, thank you!)
- If you haven’t already, read through the workgroup docs on swift.org: Swift.org - Swift.org website and Swift.org - Swift.org website workgroup (SWWG)
- If interested, come up with a short description of your vision for the website and be prepared to share and discuss with the rest of the workgroup next meeting