Skip to content
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

Improve feedbackability #626

Merged
merged 5 commits into from May 31, 2019
Merged

Conversation

StanczakDominik
Copy link
Member

Closes #624

@StanczakDominik
Copy link
Member Author

If the proposed changes are alright, I'll also add them to docs (CONTRIBUTING is probably the best place). I'll do the website in parallel.

I still need to take care of the feedback box - will do later.

@codecov
Copy link

codecov bot commented May 27, 2019

Codecov Report

Merging #626 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master    #626   +/-   ##
======================================
  Coverage    96.5%   96.5%           
======================================
  Files          52      52           
  Lines        4551    4551           
======================================
  Hits         4392    4392           
  Misses        159     159
Impacted Files Coverage Δ
plasmapy/__init__.py 46.15% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 24113f1...1253d8d. Read the comment docs.

@StanczakDominik
Copy link
Member Author

If the proposed changes are alright, I'll also add them to docs (CONTRIBUTING is probably the best place). I'll do the website in parallel.

I still need to take care of the feedback box - will do later.

@StanczakDominik
Copy link
Member Author

PlasmaPy/plasmapy.github.io#27 does the same thing for the website

@StanczakDominik
Copy link
Member Author

https://docs.google.com/forms/d/e/1FAIpQLSdT3O5iHZrLJRuavFyzoR23PGy0Prfzx2SQOcwJGWtvHyT2lw/viewform?usp=sf_link proposed feedback poll: I will still have to add interested people as collaborators (I don't think we have a shared plasmapy gmail account or anything, do we? perhaps it would be a good idea to have one?)

@StanczakDominik StanczakDominik added this to the v0.2.0 milestone May 30, 2019
If you have any questions, the quickest way to get a response is to ask
on our
[Matrix](https://riot.im/app/#/room/#plasmapy:matrix.org)/[Gitter](https://gitter.im/PlasmaPy/Lobby)
channel. For a slower response, you may also contact Nick Murphy at
<namurphy@cfa.harvard.edu> and Drew Leonard at
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That reminds me that we need to set up a main email address for PlasmaPy, though no need to worry about that right now.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just noticed your comment above. Hm...we do have a plasmapy-dev list that we rarely use. Maybe it could go there. Alternatively, we could create an email list that is primarily for the Coordinating Committee.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is plasmapy-dev the same thing as the google groups thing at https://groups.google.com/forum/#!forum/plasmapy ? Either way, that probably wouldn't work unless it has an associated email address (which I haven't been able to find if it exists). The way this works is that I can add people (via email addresses) to collaborators and those people can then see the responses.

Ideally, we'd eventually automate crossposting those to GitHub or the mailing list.

README.md Show resolved Hide resolved
@StanczakDominik
Copy link
Member Author

Thanks for the review! I'll add this info to a paragraph in the doc index, then merge it.

@namurphy namurphy added the docs PlasmaPy Docs at http://docs.plasmapy.org label May 30, 2019
@StanczakDominik StanczakDominik merged commit 5fe15de into PlasmaPy:master May 31, 2019
@StanczakDominik StanczakDominik deleted the feedback branch May 31, 2019 07:40
rocco8773 pushed a commit to rocco8773/PlasmaPy that referenced this pull request Jun 11, 2019
* README

* Improved readme

* add feedback form link

* Add communication info to documentation
@StanczakDominik StanczakDominik restored the feedback branch June 19, 2019 11:00
@StanczakDominik StanczakDominik deleted the feedback branch June 19, 2019 11:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs PlasmaPy Docs at http://docs.plasmapy.org
Projects
Development

Successfully merging this pull request may close these issues.

Improve ways for community to give feedback
2 participants