Skip to content

Add tips for effective online communication to devguide #9

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

Closed
brettcannon opened this issue Jul 22, 2016 · 8 comments
Closed

Add tips for effective online communication to devguide #9

brettcannon opened this issue Jul 22, 2016 · 8 comments

Comments

@brettcannon
Copy link
Member

Originally from http://bugs.python.org/issue24689

@nilabja-bhattacharya
Copy link
Contributor

I'm a new contributor and I would like to help.

@willingc
Copy link
Collaborator

willingc commented Feb 10, 2017

Hi @nilabja10201992,

Welcome. Rereading the original issue, it looks as if there are two possible actions:

  • Section 12.1 Review mailing list descriptions and add any that are missing. Review the textbox and correct the formatting within the box.

  • Section 12.4 Effective communication tips - A lot has improved since the initial opening of this issue on bugs.python.org. I'm not sure if additional detail is needed on this currently.

PS Sorry everyone for closing the issue/reopening. Hit the wrong key 😞

@willingc willingc reopened this Feb 10, 2017
@louisrawlins
Copy link
Contributor

louisrawlins commented Feb 11, 2017

Hi @willingc and @brettcannon.

Thanks a bunch for your help on the core mentorship list.

I'd like to help with documentation. I'm new to Open-source, but comfortable with Git workflows (once we've established what they are).

@willingc, I could use most help finding documentation updates and discussing what needs doing. Please let me know how (or if) you're assigning tasks to be done from this issue, in particular.

I'm happy to get to work on Section 12.1 and Section 12.4.

For the Section 12.4, let me know what your gauge is for "done" and whether you think this part of the issue is closed. I'm using the thread with you and Ezio for inspiration. I found a quote I liked from Nick Coghlan where he says that

"putting openness, respect and kindness into practice on a public international mailing list that now mixes paid contributors with volunteers is a genuinely hard task that could likely benefit from a few pragmatic tips :)"

Thank you again for your help. I appreciate your support and guidance.

@louisrawlins
Copy link
Contributor

louisrawlins commented Feb 16, 2017

@willingc Wanted to share some thoughts on changed before I commit anything. I've made some changes to help clarify the common Python mailing lists here:

@willingc, in issuecomment-279027021, can you tell me what "Review the textbox and correct the formatting within the box." means? I'm happy to add any lists that should be there. I've only made clarifying updating, so far with a little reordering of topics for new readers.

@nilabja10201992 Sorry for munging your change. It'll get updated better when I commit -- I'm struggling to get the Github Wiki to render all of the reStructuredText properly.

@nilabja-bhattacharya
Copy link
Contributor

@louisrawlins If you feel like to add more changes, it's fine, nothing to be sorry. I made changes which I felt appropriate if you feel more changes are necessary you can surely work on it.
Thank You!

@brettcannon
Copy link
Member Author

@louisrawlins the link you provided didn't seem to work and in the various wiki pages I couldn't find the word "textbox" so I don't know the context of the text you would like more info about.

@louisrawlins
Copy link
Contributor

louisrawlins commented Feb 24, 2017 via email

@willingc
Copy link
Collaborator

Closing as original issue submitter and devguide covers in several places.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants