Skip to content
This repository was archived by the owner on Oct 30, 2019. It is now read-only.

Commit 81e1ee0

Browse files
Bastian Gruberyoshuawuyts
Bastian Gruber
authored and
yoshuawuyts
committed
Add notes for february, march and april 2019 (#106)
1 parent 78de022 commit 81e1ee0

File tree

7 files changed

+247
-0
lines changed

7 files changed

+247
-0
lines changed

‎meetings/2019-02-14.md

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
## Working Group Updates
2+
- Status updates
3+
- tide
4+
- docs
5+
- All-hands recap
6+
- Add WG agenda items here…
7+
- Can we get alignment between Tide’s middleware and Tower’s middleware?
8+
- Missing gaps in the ecosystem
9+
10+
## Revamping the structure of the WG
11+
12+
- Initially structured as three “sub” WGs:
13+
- async
14+
- embedded
15+
- web
16+
- Proposed structure
17+
- network foundations (lang/compiler/`std`)
18+
- network ecosystem
19+
20+
## Survey review
21+
22+
- Biggest takeaway: lack of documentation and examples is a major problem in the Rust async world right now
23+
- People also want a “one true framework” / more obvious default choice
24+
- Still lots of gaps in the web ecosystem
25+
- client libraries for message queues
26+
- async database drivers
27+
- Summary post
28+
- aturon wants to review detailed responses to make an “ecosystem TODO list”
29+
30+
## Update on the state of networking
31+
32+
- Rust team All Hands
33+
- 3 sessions on Tide
34+
- mostly introducing people to Tide
35+
- some high-level API review
36+
- CSRF issues
37+
- 3 sessions on async + futures
38+
- No decision yet on final `await` syntax, but some progress on process to get there
39+
- session on futures 1.0 👍
40+
- futures RFC is in FCP
41+
42+
## Tide
43+
44+
- progress has been steady, even in absence of meetings
45+
- API Design notes
46+
- we’d like to explore different API designs outside of extractors
47+
- Tide could move to a more “layered” structure, where each endpoint is `async fn(RequestContext) - > Response`.
48+
- A branch + writeup are planned to explore this direction further
49+
- We’re thinking of moving to a highly iterative approach, where we can release new Tide versions early + often
50+
- Create a split between “core” functionality, and ergonomics that can be layered on top
51+
- The plan will be laid out more concretely in issues/RFCs
52+
53+
## Async
54+
55+
- Concerns about how the process around futures and async/await has progressed — there’s a large disconnect between the public github threads and private discussions amongst team members, which feels bad for everyone
56+
57+
## Middleware ([http-service](https://docs.rs/http-service/0.1.1/http_service/) + [tower](https://docs.rs/tower/0.0.1/tower/))
58+
59+
- Lots of overlap between what these two crates are trying to do
60+
- The http-service crate is intended to be framework-neutral, and collaboration is super important there
61+
- However, there’s a lot of detail work to figure out how to fit this together in a way that works for Tide, Tower, and others

‎meetings/2019-02-21.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
## Working Group Updates
2+
- Recurring meeting slot (poll)
3+
- Finalized to Thu 10AM-11AM CST
4+
- Tide issue triage
5+
- Initial triage on 2019-02-22 10AM - 11AM CST
6+
- Once initial triage is done, recurring triage will occur during the weekly meetings
7+
- Status updates
8+
- tide
9+
- @Aaron T submitted a new PR refactoring the internals of tide to use the new http-service crate
10+
- for http-service, the goals are:
11+
- to provide an interface that is not tied in to any particular framework or server
12+
- to work with futures 0.3 directly
13+
- to avoid generics as much as possible, to keep the type system aspects relatively easy
14+
- WG structure
15+
- `rustasync` will be the umbrella org for the rust asynchronous ecosystem with two major focuses
16+
- One would be the async foundations which overlaps with the compiler team and works to add async features to the languages
17+
- The other will be async ecosystem, which focuses on the broader async ecosystem
18+
- Quoting @yoshua w :
19+
> being about networking, the scope of the async ecosystem WG would also include bindings to platforms, reactors, thread pools, and traits to bind them together
20+
21+
## Office Hours
22+
- Web WG is growing: Can we list the core areas of the “new” WG?
23+
- What is the most urgent area where help is needed? Tide? Core-Crates?
24+
- What other ways are there to help out except PRs?
25+
- What’s the timeline for the first version of Tide and how many people are currently working on it?
26+
- //Maybe an offtopic question: How would you position Rust/Tide vs. NodeJS and Go. What are the arguments you would tell a company/shop to use Rust/Tide instead of Node or Go?
27+
- Get a stable core framework up and running from which point we can start semver versioning.
28+
- The triage meeting happening tomorrow and the triage which will happen during the weekly meeting would be a great entry point for onboarding contributors.
29+
- Mentorship
30+
- Are there any plans for providing mentorship to new contributors?
31+
- Similar to the previous question, the triage meetings would be a great point to start the onboarding of new contributors.
32+
- How would this be structured?

‎meetings/2019-02-28.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
## Working Group Updates
2+
- Status updates
3+
- tide
4+
- Outcome of the triage from last Friday.
5+
- Need to discuss owner structure of crates and who is able to update/publish them.
6+
- Figuring out to make the whole WG as a maintainer of a crate: `cargo owner --add "github:rustasync:maintainers"`
7+
- Merged @Bastian G `http-service-mock` crate
8+
- @V B Looked into session management (mainly Rocket, actix-web and tower-web) and how we could implement it in tide. He also looked into URL generation. Django and Flask are using a stringly typed API, which we want to avoid
9+
- @Sendil K proposed to be able to serve static files (issue)
10+
- Gaps in the ecosystem
11+
- [2019-02-27 Web Ecosystem Gaps](https://paper.dropbox.com/doc/2019-02-27-Web-Ecosystem-Gaps--AbDiGEkEgke46uLrPDgEOn6ZAg-1DSQhREQVJYGirBelosBY)
12+
- Going through the survey points. This document is a great starting point for anyone who wants to contribute to the ecosystem
13+
- Creating a guide like tokio doc-blitz
14+
- Crates could be linked to [AreWeWebYet](http://www.arewewebyet.org/)?
15+
- Discussion of how to point to the next priority to work on and where to share progress. Libraries are not synced with the latest progress (like futures 0.3) and people are waiting for things to finalize and stabilize
16+
- Update areweasyncyet to point to which futures version is supported
17+
- Link areweasyncyet to async-book
18+
- Summary of the discussion: “we have a consensus that for now we should't engage in building a new list, we shouldn't put out a call for implementations, but we should start making futures 0.3/1.0 projects more discoverable”
19+
- Async WG transition updates
20+
- wg-net site
21+
- rust-lang.org (team repo)
22+
- Discord channel, wg-net repo and website still need to be moved to the new org structure. @Aaron T is needed for this because of admin rights
23+
- Discrod channel should be under “domain working groups” in the future, but needs to be clarified. @yoshua w is coordinating it.
24+
- Joint meeting with async foundation wg is planned, and more check ins in the future
25+
- Blog post or primer on how to get involved with the group with details
26+
27+
## Office Hours
28+
- Extractor or Resource download option for the tide ([PR]( https://github.com/rustasync/tide/pull/126))
29+
- PR is stalled, suggestion to treat static file serving as a separate concern and implement it into the middleware

‎meetings/2019-03-07.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
## Working Group Updates
2+
- Status updates
3+
- tide
4+
- Core idea is to create the “smallest” core API as possible
5+
- The goals are:
6+
- Taking care of http-related concerns at “signature” level
7+
- Working with application types instead of http types
8+
- Current downsides of the extractor setup are dealing with wrapper types, some magic impls of the Endpoint trait which makes it overall hard to use and understand
9+
- @Aaron T is working on revamp to make it easier to use and understand
10+
- The goal is to write endpoints directly and extract data within the body instead of having various Endpoint impls for extractor arguments
11+
- Extractions (could) happen inside the endpoint body instead of getting passed as parameters. However, the seperation of http and application would weaken
12+
- Using attribute macros to extract parameters to keep the function bodies “app native”
13+
- @Aaron T will write up a lengthy proposal for this change (proposal). Generally great feedback from the working group
14+
- wg transition
15+
- We have rustasync GitHub handle
16+
- We fixed the blog and the urls
17+
- Still missing: rust-lang.org, discord and twitter, rustasync
18+
- Website: @yoshua w
19+
- Twitter: @Aaron T
20+
- Discord: @Aaron T
21+
- rustasync: Will be an issue on GitHub
22+
- Need to give access rights to team members to transition ownership from private crate to rustasync
23+
- arewewebyet
24+
- Looking for maintainers and doing active curation within the team
25+
- Probably takes 10 minutes a week to keep it updated and curated
26+
- Long term vision: AWWY could be a key role in communicating, together with the working group and areweasync yet
27+
- areweasyncyet
28+
- Constant updates, need to get upsuper joining the next meeting
29+
- [2019 roadmap](https://github.com/rustasync/team/issues/96)
30+
- Read it and give feedback 😉
31+
- 6 week sprints
32+
- WASM WG is starting with 6 week sprint cycles (again)
33+
- Use this also for our working group to plan work in terms of time and setting goals
34+
- Having a road map according to the 6 week cycle
35+
- Creating an issue with first thoughts - [https://github.com/rustasync/team/issues/96](https://github.com/rustasync/team/issues/96)
36+
- Issue triage (org | tide)
37+
- No time left, first point on the agenda for next meeting

‎meetings/2019-03-14.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
## Working Group Updates
2+
- Status updates (10 mins)
3+
- tide
4+
- Updates on the [route-match algorithm](https://github.com/rustasync/tide/issues/141).
5+
- areweasyncyet
6+
- Upsuper won’t make it to the meetings because of time difference. Goals would be to add a bit automation to keep things updated. Not much plans otherwise, so suggestions are welcome.
7+
- arewewebyet
8+
- A few curation PRs to prune unmaintained crates, steady progress
9+
- List of all “are we xy yet” is at the MozillaWiki: https://wiki.mozilla.org/Areweyet
10+
- romio + juliex
11+
- Moving both repos to the org soon, have to find the time to do that
12+
- async foundations
13+
- http://smallcultfollowing.com/babysteps/blog/2019/03/01/async-await-status-report/
14+
- Discord and twitter still need to be updated; time is (as always) very limited
15+
- In talks to schedule a regular checkin meeting wit the async foundations WG
16+
- asnyc foundation WG also open to have sprints
17+
- 6 week sprints (25 mins)
18+
- https://github.com/rustasync/team/issues/96
19+
- Helpful to define metrics (“we support X after this sprint”…)
20+
- After the sprint we want to have a small and well defined example app
21+
- The tide rewrite should have been merged
22+
- Finished and stabilized the “core” (PR/issue need to define what exactly is included in the core)
23+
- Generally raising concerns about the direction of the WG and tide, which will be talked at another time (https://github.com/rust-lang/rfcs/pull/2657#issuecomment-471643874)
24+
- The extractor interface change needs to happen in this sprint as well, which is a blocker for future work on the middleware
25+
- Another sprint goal is to come up with a websockets design
26+
- Issue triage ([org](https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Arustasync) | [tide](https://github.com/rustasync/tide/issues/))(25 mins)
27+
- https://github.com/rustasync/tide/issues/152
28+
- Logging vs Tracing: Logging prio 1
29+
- Solution (and talked about previously) was to use a log middleware create which just calls the log macros instead of setting up a logger
30+
- Moving session management (https://github.com/rustasync/tide/issues/9) to the core
31+
- Proposed “documentation” label
32+
33+
## Office Hours
34+
- No office hours this week.

‎meetings/2019-03-28.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
## Working Group Updates
2+
- Status updates
3+
- tide
4+
- Discussions around @Aaron T PR about the big rewrite. Some concerns about declerative vs. imperative and passing the whole state in every route. Examples should clarify the concerns soon.
5+
- areweasyncyet
6+
- maintenance mode and just needs updates whenever features are getting stabilized
7+
- arewewebyet
8+
- PR with updated WASM topic
9+
- We still need to figure out access writes to close the currently 11 open PRs Fixed
10+
- Changing engine from jekyll to cobalt, but not a priority right now
11+
- Cleanup is still in progress
12+
- romio + juliex
13+
- @yoshua w put out a new release for both last week
14+
- Juliex now as a thread pool initialization hook; useful for setting up TLS
15+
- Romio exposes new contructors (like TryFrom<std::netTcpListener>
16+
- https://github.com/yoshuawuyts/async-ready
17+
- https://github.com/yoshuawuyts/async-datagram
18+
- Issue triage (org | tide)
19+
- skip because of the blocking rewrite PR which needs to be merged first
20+
- Other WG agenda items
21+
- Start putting async-book and futures on the weekly agenda
22+
- Brainstorm async-book chapter ideas so people can pick them up and write about them
23+
- Disucssions around keeping track of async realted topics; hard to keep track of what’s floating around

‎meetings/2019-04-04.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
## Six-Week Sprint
2+
- End date: 2019-05-02 (six weeks)
3+
- Sprint goals
4+
5+
## Working Group Updates
6+
- Status updates
7+
- futures
8+
- Transition to 0.3 is mostly done
9+
- Cleanup the “disabled” parts of the code base still needs to happen
10+
- AsyncSeek trait still needs to be added (besides other features)
11+
- Getting more users to try it out is a key to figure out what is still missing
12+
- There are still a few broken doc links which need to be fixed
13+
- romio + juliex
14+
- Not much happened in the last week
15+
- A new bug was filed (link) and being triaged
16+
- async rust book
17+
- Hold off until Futures are stabilized (Just the Futures API, not all of AsyncRead, AsyncWrite etc.)
18+
- This might happen soon though
19+
- arewewebyet
20+
- WASM topic updated
21+
- All current PRs are merged
22+
- Current focus: content
23+
- Next topic will be infrastructure tasks
24+
- tide
25+
- @Aaron T will finish up the blocking rewrite PR asap
26+
- Other improvements (endpoint errors) will be outlined in a GitHub issue
27+
- Nested apps will be discussed in a future PR
28+
- Issue triage (org | tide)
29+
- Add WG agenda items here…
30+
- Add http-service to future agendas
31+
- Lets start each meeting with the Sprint Goals/Roadmap

0 commit comments

Comments
 (0)