-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Want to add to the upcoming meeting agenda? Here's how #11
Comments
Hi @AramZS, having recently experienced this on Privacy CG, you should be aware that most people aren't able to set labels on issues. I had to personally chase chairs to get an issue noticed in that case. |
Wouldn't be more comfortable for majority if participants could add items with email send to group? We can add some time capp - ex. include only items provided 3 (maybe more?) days before start to make it more comfortable from perspective of preparation. Items send after this capp would be included in agenda of next meeting. So something as flexible as what currently works on Web-Adv but with time constraints. WDYT? |
@AramZS, looking closer at the label issue, it seems like the only way to accomplish this is to use issue templates. It looks like it would be very easy to setup a template for agenda items (and if you want to add me as a editor on this repo, I'd be happy to do it.) |
Given that these meetings are much less frequent, and will be much longer, it seems preferable to have specific issues for each agenda item, which can be used as a specific thread for that agenda item, rather than the mailing thread (which can be more difficult to allow for threads across different topics.) Given that Github issues also get forwarded to the mailing list, using Github to manage the agenda process still keep everyone in the loop. |
@eriktaubeneck Thanks for this feedback! I didn't realize. I believe that the WebAdv Github allows people to freely apply labels, so I'll have to look into how that works. For now I think you've got the right idea and I've added the issue template. I'm open to any changes for additional details if you'd like. |
@lukwlodarczyk I think, especially considering the long timeline, that expecting people to keep up with all emails, keep them organized between meetings, and keep up on every thread, is adding a lot of extra work for a process simplified and made clear and transparent via Github issues. Plus, having a queue of agenda items we can pull off of these issues will allow us to continually move forward, picking agenda items up off the backlog, and not spend any time agenda setting beyond maybe some short prioritization. |
Thanks for setting up the template @AramZS!
I just checked, and I'm unable to add a label, even on an issue that I opened. I believe you are able to add labels in that repo by having push access (I can't see that list, but I do see you'd made commits to that repot, so that's my best guess.) Anyways, probably nothing to figure out, and templates are the way to go! |
I have no idea what the agenda+ and agenda+next labels in this repo mean, as it's not clear that they're being regularly updated between meetings. Does anyone know what is going to be discussed at the pair of meetings next week, June 21/23? It's very difficult to plan out attendance at a long meeting in an inconvenient time zone when I don't know which topics are going to be covered, or which topics have already been covered. |
I didn't make the first day of this week's meeting because I didn't know what the agenda was until too shortly before to plan my time or prep for it. +1 to @martinthomson on another thread that having the agenda set 1 week in advance would make a big difference for preparation of materials, no matter what time zone you're in, but especially because there's always going to be someone for whom the timezone is difficult. |
Open an issue in this repository using the 'Agenda Item template'
Thanks!
[Edited to switch to suggesting people use the issue template, thanks @eriktaubeneck]
The text was updated successfully, but these errors were encountered: