-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
"Code of Conduct" and "Reporting Guidelines" #1346
Comments
It's ok to keep this open. It will just take feedback from @conda-forge/core to move forward |
Yup. I second that this is a very good idea! |
Great idea! |
Yep. We needed that recently and struggled to find it! BTW, we follow NumFOCUS CoC and we report to them. You'll find more info on their page. |
Hello, @kathatherine and @beckermr hope this text finds you well! To clarify, Since the Reporting Guidelines is covered under the code of conduct I believe that it isn't supposed to be added? |
Hi there! my name is Prachi Nandi and I am an aspiring Outreachy intern, I am so excited and gripped to contribute to Conda forge. To begin with, it will be my pleasure to work on the issue opened by me last year which I wanted to work on., so can I work on this issue? also, I would like to enquire, exactly at present are we supposed to prepare a draft of the Code of Conduct for Readme.md by taking reference from NumFOCUS Code of Conduct / Governance section of conda-forge docs? Thank you! |
Yes the readme in this repo. |
Outreachy applications have started again. As usual, folks tend to not notice the other PRs and make their own. Please don't worry about it. |
You sure...? There is one more: #1646. |
@beckermr is it okay to provide them feedback? I wasn't aware these were part of applications and I offered feedback to two PRs. Happy to avoid that, just let me know if there are restrictions or procedures you'd like the community to follow. Thanks! @leofang, I think it is fine; in fact, it is a good thing :) |
Feel free to find another issue. |
@ngam helpful comments are appreciated. Remember that outreachy applicants are typically new to our community. Please be patient as they get aquatinted with our tools and processes. |
I meant to say it'd be nice if someone can help coordinate. Even applicants' time is valuable and we shouldn't duplicate their effort. |
Hello Mentor, I am called Fad from Cameroon. I am an Outreachy Applicant for the March 2022 cohort. I am very much interested in the project. |
We're doing our best @leofang. Feel free to join us. |
Okay, Thanks! @beckermr |
Hello Mentor, I am called Austin Tawe from Cameroon. I am an Outreachy Applicant for the March 2022 cohort. I am very much interested in the project. |
Please see our interns gitter channel for some instructions. |
Hi I am Rufaida Ali an outreachy applicant is it possible to contribute to this project?. please guide me |
Hi! Please see our intern gitter channel for some introduction. |
Hello everyone! I am Shivani Parihar, an outreachy applicant. I am from India. |
Feel free to find another issue. |
|
Hi This is Saad, I am an Outreachy aspirant. Looking forward to contribute :) |
Hello everyone, I am Tracy an Outreachy applicant from Uganda. I have seen PRs related to this issue, should I work on this issue or continue to another one? |
Either way is fine! |
Add copy functionality to the steps of command to setup dev environment Fixes:#conda-forge#1346
making it specific to conda-forge Fixes:#conda-forge#1346
Hello everyone I am Lukong Anne from Cameroon looking forward to contributing to the community. |
@prachi237 I think it is a good idea to do add the code of conduct to the readme file, as you said adding it in brief. |
Hello, I am harshita and I would like to work on this issue Thanks in advance :) |
Hi, @harshita214. You don't need to be assigned any issues during the Outreachy application period for conda-forge. You can work on this issue if you want to (we are using this issue in particular as an easy one to start with), but you are welcome to create a PR for any docs issue you would like to work on and let us know about it in the conda forge interns chat. |
I was reading the conda-forge docs, In the Governance section I found the code of conduct, but what I feel is we must link the code of conduct or can write them in brief and add in the readme.md file. Any contributor who would be visiting the page will be reading the readme.md file first and they shd be well aware of the code of conduct and reporting guidelines, and the consequences incase that is violated.
Not sure if this can be implemented, but I would like to know ur views on this
The text was updated successfully, but these errors were encountered: