** Section 1. Per the opening paragraph, isn’t a goal of the Hackathon also
verification and validation of in-flight IETF work? Reference implementations
to foster adoption of IETF work?
** Section 1.
Bring developers and young people into IETF and get them exposed
to and interested in the IETF
Consider “students”, “early career professionals” or “newcomers” instead of or
in addition to “young people.”
** Section 1.
Similarly, while the Hackathon is meant to
attract newcomers and those who do not typically view themselves as
standards people,
Who are “standards people”?
** Section 1.
Group dynamics and blending of skill sets
and perspectives are extremely valuable aspects of IETF Hackathons.
Per “Group dynamics … are extremely valuable …”, can the phrase “group
dynamics” be more specific. Which dynamics is the hackathon trying to foster?
** Section 1.
Examples include, but are
not limited to, interoperability of implementations, proof of
concepts, and tools.
What is a “tool” if not a proof of concept? Is this tooling to support the
standards development process?
** Section 2.2. Editorial.
Initially, we did something similar as part of Bits and Bites
-- The voice in the sentence changed to first-person plural (we).
-- Is there more context to provide on Bits and Bites for those that might not
be familiar.
** Section 2.3
Champions are encouraged to look at the final agenda and determine
time slots best suited to ensure attendance of Code Lounge sessions
as well as any related working group sessions.
The idea of “Code Lounge session” and the “Code Lounge” being open continuously
would benefit from an explanation. Is there an expectation that the champion is
scheduling things during IETF week? I don’t see this scheduling in the roles
and responsibilities section.
** Section 2.4. Editorial.
The IETF [CODE-SPRINT] develops tools that support the work of the
IETF. The Code Sprint existed ...
Using [CODE-SPRINT] after “IETF” is an odd place to put the reference.
Recommend putting it after “Code Sprint” in the second sentence.
** Section 9.1. An additional privacy consideration is the photography
described in Section 7.5. Perhaps mention the lanyard system to opt-out.
eckelcu
commented
2 years ago
COMMENT:
** Section 1. Per the opening paragraph, isn’t a goal of the Hackathon also verification and validation of in-flight IETF work? Reference implementations to foster adoption of IETF work?
** Section 1.
Consider “students”, “early career professionals” or “newcomers” instead of or in addition to “young people.”
** Section 1. Similarly, while the Hackathon is meant to attract newcomers and those who do not typically view themselves as standards people,
Who are “standards people”?
** Section 1. Group dynamics and blending of skill sets and perspectives are extremely valuable aspects of IETF Hackathons.
Per “Group dynamics … are extremely valuable …”, can the phrase “group dynamics” be more specific. Which dynamics is the hackathon trying to foster?
** Section 1. Examples include, but are not limited to, interoperability of implementations, proof of concepts, and tools.
What is a “tool” if not a proof of concept? Is this tooling to support the standards development process?
** Section 2.2. Editorial. Initially, we did something similar as part of Bits and Bites
-- The voice in the sentence changed to first-person plural (we).
-- Is there more context to provide on Bits and Bites for those that might not be familiar.
** Section 2.3 Champions are encouraged to look at the final agenda and determine time slots best suited to ensure attendance of Code Lounge sessions as well as any related working group sessions.
The idea of “Code Lounge session” and the “Code Lounge” being open continuously would benefit from an explanation. Is there an expectation that the champion is scheduling things during IETF week? I don’t see this scheduling in the roles and responsibilities section.
** Section 2.4. Editorial. The IETF [CODE-SPRINT] develops tools that support the work of the IETF. The Code Sprint existed ...
Using [CODE-SPRINT] after “IETF” is an odd place to put the reference. Recommend putting it after “Code Sprint” in the second sentence.
** Section 9.1. An additional privacy consideration is the photography described in Section 7.5. Perhaps mention the lanyard system to opt-out.