Top HN posts
W3C teams have a tendency of scribing everytihng they do, and they're pretty effective at it.
This is not due to individuals being great at scribing: the system is set up such that even new group members will be able to scribe reasonably effectively. It's also set up such that new group members will get that opportunity soon enough.
The main thing is that "anyone can scribe": most teams avoid a designated scribe and instead designate a scribe per meeting and discussion. This works with some of the following additional structure:
- Nobody is expected to scribe and take minutes simultaneously. if the scribe wants to say something, someone else will take over. You pre-agree to who that person will be before the scribe actually says something
- Before the discussion starts, scribe asks for an alternate
- During the discussion, scribe may use chat to say "anyone want to scribe for me when I talk in a bit" and then call out that person before speaking.
- Feature Name:
pattern_types - Start Date: (fill me in with today's date, YYYY-MM-DD)
- RFC PR: rust-lang/rfcs#0000
- Rust Issue: rust-lang/rust#0000
This RFC introduces pattern types, which are subtypes of matchable types that
are statically restricted to a subset of the variants of the original type.
OlderNewer