-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Monthly PyLadies Meeting Notes: Feb 12 @ 16:00 PT #60
Comments
Hi there from Los Angeles :) I'm not going to be able to join tomorrow's meeting. I do have one reservation about moving away from an inbox for I'll be looking for the meeting notes if they get shared out. Thanks for all you do!
|
@godsylla the problem we are suffering from is not enough volunteer hours to manage Right now only @elainewong and @Mariatta are managing the inbox, and these are two PyLadies who are already quite committed in other Python spaces. What is your thought on some documentation and perhaps a PyLadies Intro to Git online set of workshops? |
In pyladies/pyladies#428 I've described all the problems with managing info@ mailbox. I've proposed several solutions. Please share feedback there. |
I think a quick + dirty documentation on how to submit a Git issue is a
good idea.
Also, maybe Marietta and Elaine can weigh in on most commonly asked
questions?
Does it make sense to help draft an FAQ?
Sometimes I'll get forwarded emails that go to the info@pyladies.com inbox
as opposed to direct to la@pyladies.com. So for example, perhaps in the
FAQ, we can have a place on "how to contact your local chapter" or
something to that effect.
…On Wed, Feb 12, 2020 at 8:32 AM Mariatta ***@***.***> wrote:
In pyladies/pyladies#428 <pyladies/pyladies#428>
I've described all the problems with managing info@ mailbox. I've
proposed several solutions. Please share feedback there.
One reason for proposing GitHub Issue is that it is the easiest way to set
up from our perspective.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#60?email_source=notifications&email_token=AHVFVO6LEJDJKBOMGZDUZ5TRCQQCRA5CNFSM4KQMWWXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELRN3AA#issuecomment-585293184>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHVFVO5YQ757XEDMINTTIHTRCQQCRANCNFSM4KQMWWXA>
.
--
Sylvia Tran
e-mail: Sylvi.Tran@gmail.com
|
Yup, please see: pyladies/pyladies#428 (comment) |
@godsylla I've started the FAQ here: https://github.com/pyladies/info/pull/1/files Please review the PR and provide feedback. Thanks. |
This template should be used (edited) the month prior and during the meeting. This will ensure we can address all topics added throughout the month; as well as provide minutes and follow up after the meeting is held.
Initial Details
Meeting Topics
Please add items as needed. If you add a topic please make sure to attend the meeting.
New Business
Old Business: Follow up items from prior meeting:
Action Items and Assignees for Next Meeting
@pyladies/pyladies-global-contributors
@pyladies/pyladies-global-admin
The text was updated successfully, but these errors were encountered: