Code Of Conduct
The Mycological, foraging, mushroom and science community is made up of members from around the globe with a diverse set of skills, personalities, and experiences, and The Humble Fungus is a representative of that diversity. It is through these differences that our community experiences great successes and continued growth. When you're working with members of The Humble Fungus community, this Code of Conduct will help steer your interactions and keep The Humble Fungus & mycology a positive, successful, and growing community.
Members of the Humble Fungus community are open, considerate, and respectful. Behaviors that reinforce these values contribute to a positive environment, and include:
- Being open. Members of the community are open to collaboration, whether it's on discussions, debates, experiments, methods, or approaches, problems, or otherwise.
- Focusing on what is best for the community. We're respectful of the processes set forth in the community, and we work within them.
- Acknowledging time and effort. We're respectful of the volunteer, scientific, and citizen science efforts that permeate the Humble Fungus community. We're thoughtful when addressing the efforts of others, keeping in mind that often times the labor was completed simply for the good of the community.
- Being respectful of differing viewpoints and experiences. We're receptive to constructive comments and criticism, as the experiences and skill sets of other members contribute to the whole of our efforts.
- Showing empathy towards other community members. We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views.
- Being considerate. Members of the community are considerate of their peers -- other mycologists, scientists, growers, farmers -- everyone.
- Being respectful. We're respectful of others, their positions, their skills, their commitments, and their efforts.
- Gracefully accepting constructive criticism. When we disagree, we are courteous in raising our issues.
- Using welcoming and inclusive language. We're accepting of all who wish to take part in our activities, fostering an environment where anyone can participate and everyone can make a difference.
Every member of our community has the right to have their identity respected. The Humble Fungus community is dedicated to providing a positive experience for everyone, regardless of age, gender identity and expression, sexual orientation, disability, physical appearance, body size, ethnicity, nationality, race, or religion (or lack thereof), education, or socio-economic status.
Examples of unacceptable behavior by participants include:
- Harassment of any participants in any form
- Deliberate intimidation, stalking, or following
- Logging or taking screenshots of online activity for harassment purposes
- Publishing others' private information, such as a physical or electronic address, without explicit permission
- Violent threats or language directed against another person
- Incitement of violence or harassment towards any individual, including encouraging a person to commit suicide or to engage in self-harm
- Creating additional online accounts in order to harass another person or circumvent a ban
- Sexual language and imagery in online communities or in any conference venue, including talks
- Insults, put downs, or jokes that are based upon stereotypes, that are exclusionary, or that hold others up for ridicule
- Excessive swearing
- Unwelcome sexual attention or advances
- Unwelcome physical contact, including simulated physical contact (eg, textual descriptions like "hug" or "backrub") without consent or after a request to stop
- Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others
- Sustained disruption of online community discussions, in-person presentations, or other in-person events
- Continued one-on-one communication after requests to cease
- Other conduct that is inappropriate for a professional audience including people of many different backgrounds
- Any violation of local law
Community members asked to stop any inappropriate behavior are expected to comply immediately.
No weapons are allowed at Humble Fungus events. Weapons include but are not limited to explosives (including fireworks), guns, and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon.
The exception to the above weapons policy is for all outdoor foraging / camping or similar events requiring those things. If you have questions about this, please contact Humble Fungus staff.
Firearms are not allowed on any event, outing or space.
If a participant or customer engages in behavior that violates this code of conduct, the Humble Fungus team may take any action they deem appropriate, including warning the offender or expulsion from the community and community events with no refund of event tickets. The full list of consequences for inappropriate behavior is listed in the Enforcement Procedures below.
Thank you for helping make this a welcoming, friendly community for everyone.
This Code of Conduct applies to all Humble Fungus public / private events, foraging events, meetups, speaking engagements and company spaces (offices, labs, camps).
Summary of processes
When the Humble Fungus staff receives a report of a possible Code of Conduct violation, it will:
- Acknowledge the receipt of the report.
- Evaluate conflicts of interest.
- Call a meeting of employees & community leaders without a conflict of interest.
- Evaluate the reported incident.
- Propose a behavioral modification plan.
- Propose consequences for the reported behavior.
- Vote on behavioral modification plan and consequences for the reported person.
- Contact online community administrators/moderators to approve the behavioral modification plan and consequences.
- Follow up with the reported person.
- Decide further responses.
- Follow up with the reporter.
Acknowledge the report
Reporters should receive an emailed acknowledgment of the receipt of their report within 24 hours.
Conflict of interest policy
Examples of conflicts of interest include:
- The reporter or reported person is your manager
- You have a romantic or platonic relationship with either the reporter or the reported person. It's fine to participate if they are an acquaintance.
- The reporter or reported person is your metamour. (This is a term used in the poly community; the short definition is here, and a longer description is here).
- The reporter or reported person is your family member
- The reporter or reported person is your direct client
- The reporter or reported person is someone you work closely with. This could be someone on your team or someone who works on the same project as you.
- The reporter or reported person is a maintainer who regularly reviews your contributions
Committee members do not need to state why they have a conflict of interest, only that one exists. Other work group members should not ask why the person has a conflict of interest.
Anyone who has a conflict of interest will remove themselves from the discussion of the incident, and recluse themselves from voting on a response to the report.
Evaluating a report
- Is this a Code of Conduct violation? Is this behavior on our list of inappropriate behavior? Is it borderline inappropriate behavior? Does it violate our community norms?
- Did this occur in a space that is within our Code of Conduct's scope? If the incident occurred outside the community, but a community member's mental health or physical safety may be negatively impacted if no action is taken, the incident may be in scope. Private conversations in community spaces are also in scope.
- Did this incident occur in a private conversation or in a public space? Incidents that all community members can see will have more negative impact.
- Does this behavior negatively impact a marginalized group in our community? Is the reporter a person from a marginalized group in our community? How is the reporter being negatively impacted by the reported person's behavior? Are members of the marginalized group likely to disengage with the community if no action was taken on this report?
- Does this incident involve a community leader? Community members often look up to community leaders to set the standard of acceptable behavior.
- Does this incident include sexual harrasment?
- Does this pose a safety risk? Does the behavior put a person's physical safety at risk? Will this incident severely negatively impact someone's mental health?
- Is there a risk of this behavior being repeated? Does the reported person understand why their behavior was inappropriate? Is there an established pattern of behavior from past reports?
Reports which involve higher risk or higher impact may face more severe consequences than reports which involve lower risk or lower impact.
Propose a behavioral modification plan
The work group will determine a concrete behavioral modification plan that ensures the inappropriate behavior is not repeated. The work group will also discuss what actions may need to be taken if the reported person does not agree to the behavioral modification plan.
What follows are examples of possible behavioral modification plans for incidents that occur in online spaces under the scope of this Code of Conduct. This behavioral modification list is not inclusive, and the Python Software Foundation Code of Conduct work group reserves the right to take any action it deems necessary.
- Requiring that the reported person not use specific language
- Requiring an employee to take unpaid time off during internal employee review
- Requiring that the reported person not join in on specific types of discussions
- Requiring that the reported person not send private messages to a community member
- Requiring that the reported person not join specific communication channels
- Removing the reported person from event speaking and coordination
- Removing a volunteer from their duties and responsibilities
- Removing a person from leadership of relevant organizations
- Removing a person from membership of relevant organizations
What follows are examples of possible consequences to an incident report. This consequences list is not inclusive, and the Python Software Foundation Code of Conduct work group reserves the right to take any action it deems necessary.
Possible private responses to an incident include:
- Nothing, if the behavior was determined to not be a Code of Conduct violation
- A verbal or emailed warning
- A final warning
- Temporarily removing the reported person from the community spaces
- Permanently removing the reported person from the community spaces
- Publishing a public account of the incident
- Halting fulfillment of orders or removal from paid events without refund
Follow up with the reported person
The Humble Fungus staff will work with online community members and leaders to draft a response to the reported person. The email should contain:
- A description of the person's behavior in neutral language
- The negative impact of that behavior
- A concrete behavioral modification plan
- Any consequences of their behavior
The work group should not state who reported this incident. They should attempt to anonymize any identifying information from the report. The reported person should be discouraged from contacting the reporter to discuss the report. If they wish to apologize to the reporter, the work group can accept the apology on behalf of the reporter.
Follow up with the reporter
A person who makes a report should receive a follow up email stating what action was taken in response to the report. If the work group decided no response was needed, they should provide an email explaining why it was not a Code of Conduct violation. Reports that are not made in good faith (such as "reverse sexism" or "reverse racism") may receive no response.
The follow up email should be sent no later than one week after the receipt of the report. If deliberation or follow up with the reported person takes longer than one week, the work group should send a status email to the reporter.
Each report should be assigned a code name, using an online random phrase generator. The code name should be used in the document's title. Only committee members without a conflict of interest should have access to the report documentation.
Report documents should include:
- A summary of a verbal report, or the text of an emailed report. Use neutral, non-judgmental words to describe the behavior. Where possible, separate out the behavior of the reported person and the impact on the reporter.
- A summary of committee discussions, including whether the report is in scope
- Proposed behavioral modification plan
- Proposed consequences for the reported behavior
- A summary of verbal discussions, or the text of email discussions with community moderators, administrators, registration, or other event organizers about the proposed consequences and behavioral modification plan
- A summary of verbal discussions, or the text of email discussions with the reported person
- The text that was sent to follow up with the reporter
All discussion summaries should include dates that they took place.
There are some common privacy pitfalls to online tools like Google Docs. Make sure to always share the document with committee members who don't have a conflict of interest, rather than turning link sharing on. This prevents people outside of the committee from accessing the documents.
Another common issue is that when a folder is shared with the whole committee, even if a person doesn't have edit or view access to an individual report, they can still see the document's title. This can give information away, such as the person who made the report. Some communities use initials in the report title instead. That can still reveal information, and it makes it hard to talk about report status in public spaces (such as an event). The committee may want to assign a code name to each report, and reference that name in the report title and status spreadsheet. You can use an online random phrase generator to create the code name.
When on-boarding new members & staff, they should be provided with a list of names of people who have been reported in a Code of Conduct incident. The new committee member should state whether they have any conflicts of interest with reviewing documentation for those cases. If not, they will be given edit access to the report documents.
This Code of Conduct and Enforcement Procedures are based on the Python Community Code of Conduct.
- The PyCon Code of Conduct is licensed under a Creative Commons Attribution 3.0 Unported License.
- Ada Initiative's guide titled "Conference anti-harassment/Responding to Reports" is licensed under a Creative Commons Attribution 3.0 Unported License
- Audrey Eschright of Safety First PDX provided the impact vs risk assessment framework, which is licensed under a Creative Commons Attribution Share-Alike 3.0 Unported License by Audrey Eschright of Safety First PDX
- Code of Conduct template was created by Otter Tech and is licensed under a Creative Commons Attribution 3.0 Unported License