CODE OF CONDUCT



  • Applicability and Scope

    This code of conduct applies to all of this community's spaces, including public channels, private channels and direct messages, both online and off. Anyone who violates this code of conduct may be sanctioned or expelled from these spaces at the discretion of the administrators.

    Toward a Welcoming and Safe Environment

    We hope to create an environment in which diverse individuals can collaborate and interact in a positive and affirming way. Examples of behaviour that contributes to creating this sort of environment include:

    • Using welcoming and inclusive language
    • Being respectful of differing viewpoints and experiences
    • Gracefully accepting constructive criticism
    • Focusing on what is best for the overall community
    • Showing empathy towards other community members

    Anti-Harassment Statement

    MakerGram will not tolerate harassment of any kind. Examples of harassment include:

    • Offensive comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, pregnancy status, veteran status, political affiliation, marital status, body size, age, race, national origin, ethnic origin, nationality, immigration status, language, caste, religion or lack thereof, or other identity marker. This includes anti-Indigenous/Nativeness and anti-Blackness.

    • Unwelcome comments regarding a person's lifestyle choices and practices, including those related to food, health, parenting, relationships, drugs, and employment.

    • Deliberate misgendering, using inappropriate pronouns, or use of "dead" or rejected names.

    • Gratuitous or off-topic sexual images or behaviour in spaces where they're not appropriate.

    • Physical contact and simulated physical contact (eg, textual descriptions like "hug" or "backrub") without consent or after a request to stop.

    • Threats of violence.

    • Incitement of violence towards any individual or group, including encouraging a person to commit suicide or to engage in self-harm.

    • Deliberate intimidation.

    • Stalking or following - online or in the physical world.

    • Harassing photography or recording, including logging online activity for harassment purposes.

    • Sustained disruption of discussion.

    • Unwelcome sexual attention.

    • Patterns of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others.

    • Continued one-on-one communication after requests to cease.

    • Deliberate "outing" of any aspect of a person's identity without their consent except as necessary to protect vulnerable people from intentional abuse.

    • Publication of non-harassing private communication.

    • Jokes that resemble the above, such as "hipster racism", still count as harassment even if meant satirically or ironically.

    If you have questions or concerns about these issues please feel free to message an admin or ask for an opportunity to explore the issue with a moderator and volunteers.

    Reporting

    If you are being harassed by a member of our community, notice that someone else is being harassed, or have any other concerns, please contact the administrators via mail at contact@makergram.com. If the person who is harassing you is on the admin team, they will not be involved in handling or resolving the incident.

    The admin team will respond to any complaint as promptly as possible we can. If you do not get a timely response (for example, if no admins are currently online) then please put your personal safety and well-being first, and consider logging out and/or contacting the admins by email at contact@makergram.com.

    This code of conduct applies to our community's spaces, but if you are being harassed by a member of our community outside our spaces, we still want to know about it. We will take all good-faith reports of harassment by our members, especially the administrators, seriously. This includes harassment outside our spaces and harassment that took place at any point in time. The abuse team reserves the right to exclude people from the community based on their past behaviour, including behaviour outside of our spaces and behaviour towards people who are not in this community.

    In order to protect volunteers from abuse and burnout, we reserve the right to reject any report we believe to have been made in bad faith. Reports intended to silence legitimate criticism may be deleted without response.

    Enforcement Process

    Every code of conduct violation report will be treated with seriousness and care. If a member's immediate safety and security is threatened, an individual admin may take any action that they deem appropriate, up to and including temporarily banning the offender from the community. In less urgent situations, at least two admins will discuss the offence and mutually arrive at a suitable response, which will be shared with the offender privately. Whatever the resolution that they decide upon, the decision of the admins involved in a violation case will be considered final.

    We will respect confidentiality requests for the purpose of protecting victims of abuse. At our discretion, we may publicly name a person about whom we've received harassment complaints, or privately warn third parties about them, if we believe that doing so will increase the safety of our members or the general public. We will not name harassment victims without their affirmative consent.

    Consequences

    Participants asked to stop any harassing behaviour are expected to comply immediately. If a participant engages in harassing behaviour, the administrators may take any action they deem appropriate, up to and including expulsion from the community and identification of the participant as a harasser to other members. At the discretion of the admins, or by request, one or more of the parties involved may request to discuss the violation and how to avoid similar situations in the future.

    ~~~~~~~~~~~~~~~~~~~~
    ~~~~~~~~~~~~~~~~~~~~

    Acknowledgement
    This Code of Conduct is adapted from the Community Covenant, version 1.0, available from here. And then edited accordingly.
    License
    Community Covenant by Coraline Ada Ehmke is licensed under a Creative Commons Attribution 4.0 International License. Based on a work at http://community-covenant.net/.

Log in to reply
 

Recent Posts

  • @Suhailjr But I think since it's not a plug and plug play system and it will laying on the PCB for the long term, it might be fine. for me, it's similar to the Intel Edison and the PICO-IMX7 System-on-Module

    dade502a-71f6-4da0-bd7d-0e9a0b602cb0-image.png

    a4b8898f-90d4-4a34-ba5d-81ab76fda904-image.png

    read more
  • @salmanfaris at last they update their design. T
    What you think on the updated connector. I felt like its more fragile and high chance for corottion issue due to humidity for long term use.

    read more
  • Built on the same 64-bit quad-core BCM2711 application processor as Raspberry Pi 4, Compute Module 4 delivers a step-change in performance over its predecessors: faster CPU cores, better multimedia, more interfacing capabilities, and, for the first time, a choice of RAM densities and a wireless connectivity option.

    3094f292-3301-4364-a444-d828f6e77ff8-image.png

    You can find detailed specs here,

    1.5GHz quad-core 64-bit ARM Cortex-A72 CPU VideoCore VI graphics, supporting OpenGL ES 3.x 4Kp60 hardware decode of H.265 (HEVC) video 1080p60 hardware decode, and 1080p30 hardware encode of H.264 (AVC) video Dual HDMI interfaces, at resolutions up to 4K Single-lane PCI Express 2.0 interface Dual MIPI DSI display, and dual MIPI CSI-2 camera interfaces 1GB, 2GB, 4GB or 8GB LPDDR4-3200 SDRAM Optional 8GB, 16GB or 32GB eMMC Flash storage Optional 2.4GHz and 5GHz IEEE 802.11b/g/n/ac wireless LAN and Bluetooth 5.0 Gigabit Ethernet PHY with IEEE 1588 support 28 GPIO pins, with up to 6 × UART, 6 × I2C and 5 × SPI

    31354fad-6332-40e8-b324-53e0aa5dbace-image.png

    Compute Module 4 IO Board
    89a3b68b-bb74-4002-9c2b-d32c2e1450b3-image.png

    The IO board provides:

    Two full-size HDMI ports Gigabit Ethernet jack Two USB 2.0 ports MicroSD card socket (only for use with Lite, no-eMMC Compute Module 4 variants) PCI Express Gen 2 x1 socket HAT footprint with 40-pin GPIO connector and PoE header 12V input via barrel jack (supports up to 26V if PCIe unused) Camera and display FPC connectors Real-time clock with battery backup

    More details:
    https://www.raspberrypi.org/products/compute-module-4/?variant=raspberry-pi-cm4001000, https://www.raspberrypi.org/blog/raspberry-pi-compute-module-4/

    read more
  • 28e1870e-33fe-4791-bc74-05c9d58098da-image.png

    Seeed is currently counting down for the 10 year anniversary of the debut of Grove 🎉. In the past 10 years, we have seen many wonderful projects created by Grove from our user and community. We want to invite you to join us to celebrate the 10 year anniversary of Grove 🤩.

    In the Grove 10 Years Celebration, we’d like to collect the stories of “Grove with You”, which we want to invite our users to share their stories they have with Grove products.

    => What project you’ve made out of Grove?
    => What is your favourite Grove?
    => which one was the first Grove you’ve purchased?

    Seeed encourages you to post and share photos, videos, stories of Grove in the Seeeed Forum, or any other platforms below that you’d like to use.

    The following ways to find us, and tag #grove10 to share the project with us!

    Twitter (@seeedstudio) Instagram (@seeedstudio) or simply email your project to grove10@seeed.cc

    Feel free to be creative in documenting your projects–we will be selecting top 10 most “Grovy” winning entries from the submissions, and the winners will receive a $100 Grove Surprise Pack 😋 as a special gift.

    Looking forward to seeing your projects! 🥳

    read more
  • @kowshik1729 I think that might not get since the platform is not opensource! but they provided everything you need to develop a system with that.

    read more