-
Notifications
You must be signed in to change notification settings - Fork 60
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
Create AllCoreDevs Notes & Summaries.md #25
Conversation
For us to track who is responsible for producing the summaries for which CoreDev call
I am not sure if we necessarily need a summary tracker for AllCoreDevs Notes. Note taking task is already taken care at ECH PM repo as issue #. Guideline says that summary should be posted within 24 hrs and transcript within a week and in my experience, it is being taken care. If someone is interested in sharing immediately after the meeting; are welcome to share. This decision can be managed through internal communication. The need of calendar or tracker for that, I am not so sure. |
@timbeiko I believe this is very helpful - if Brett or others continue to do the summary, great, but we need a backup plan and imo this works |
@mariapaulafn so you think having this on the repo vs. coordinating on Gitter is beneficial? What do you think @DBrettRobertson? |
I think both are needed - some of us have a lot on our plates :) |
IMHO it would be easiest for the Note Taker of the AllCoreDevs call to do the summary as well. If we really want to track who is doing it, why don't we just track the Note Taker? For two reasons:
Please note that the Note Taking bounty for AllCoreDevs calls is public and people simply apply to do it and get accepted based on their application. We can always share the bounty across all channels as a backup. WDYT? |
I agree it is probably easier for the notetaker to do a summary and submit it for review as a PR, as Brett did for the last call. I don't want to create yet-another channel of comms if it isn't useful. @mariapaulafn you were most in favor of this. WDYT of @CPSTL's comment above? If you agree, I would just close and delete this PR. |
Sure, i agree - ill do my part and post on social media and magicians |
For us to track who is responsible for producing the summaries for which CoreDev call