Comments (8)
Proposal:
- Drop the Materials section (but add Agenda section per issue #53).
- After the meeting, generate a Meeting Record section with space for links to minutes, slides, and recordings. Include a link inline to documentation about how to edit this section.
from tpac-breakouts.
Updated "how to update a session:
https://github.com/w3c/tpac-breakouts/wiki/Good-Practices-for-Session-Chairs#how-to-update-a-session
This includes a link that can be used when the "Meeting Record" section of the issue is added:
https://github.com/w3c/tpac-breakouts/wiki/Good-Practices-for-Session-Chairs#add-meeting-record-information-after-the-breakout
from tpac-breakouts.
One thing I had overlooked is that we need to store the link to the calendar entry in that "Meeting Record" section (useful for people but also for tooling so that it can tell which entry to update) as soon as that calendar entry gets created, meaning before the meeting.
from tpac-breakouts.
What if we move things around a bit and create a new Attend this Session
section that has the following information:
- Who can attend
- Link to calendar entry
- Info about IRC
(and anything else related to attendance).
from tpac-breakouts.
So far, the sections remain directly linked to the form we use to propose a session. Through that form, we cannot ask about two pieces of information (who can attend and what IRC channel to use) and then hope that GitHub will restructure the responses as a list into a single "Attend this Session" section.
Now, we already run updates on the issue description and re-serialize it, so it's totally possible to have a job that runs when a user creates an issue and reformats the description according to a new structure. A bit painful though (code needs to understand two structures instead of one).
from tpac-breakouts.
Through that form, we cannot ask about two pieces of information (who can attend and what IRC channel to use) and then hope that GitHub will restructure the responses as a list into a single "Attend this Session" section.
I had hoped it would be possible to get subsections in YAML. I infer from your comment that won't work. And I see from the syntax description that markdown is not submitted.
from tpac-breakouts.
I've updated the documentation based on our discussion today. I now anticipate there will be two injected sections:
- One for the calendar (to be created as soon as the session has been scheduled)
- One for "Meeting Materials" (to be created around the time of the meeting or shortly afterwards).
In addition, we did the following:
- Tweak the template to add a "Logistics" section for IRC.
from tpac-breakouts.
OK, code should now be aligned with the documentation. The link to the calendar will appear in a dedicated section labeled "Link to calendar".
from tpac-breakouts.
Related Issues (20)
- IRC: check responses from bots HOT 1
- IRC: channel operator rights HOT 4
- Drop Agenda link? HOT 4
- Set up buddy program for first-time facilitators
- Make clearer (via template) how to manage minutes, slides, cal links HOT 1
- Need tools to ease/automate copying of slides and minutes to w3.org HOT 1
- Should Project be in private repo? HOT 2
- Tools to process recordings (clipping, upload to streaming service)
- Checklist for copying info to a new TPAC repo HOT 1
- Email improvements HOT 1
- Use more neutral mechanism to remove issue author from the list of session chairs HOT 1
- Fix video recording policy due to realities of presentations HOT 3
- Need more instruction on available tooling for TPAC breakouts HOT 1
- Include track icons in github data HOT 1
- For videos, align page formatting with other pages
- Provide track labels, along with icons in a more machine-friendly way, for use in TPAC pages
- Move TPAC breakouts tools to separate package HOT 1
- Automate calendar updates HOT 1
- Add support for plenary session HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tpac-breakouts.