René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Strengthen your project with a Code of Conduct","articleBody":"Hello!\n\nI am [Maryblessing Okolie](https://www.linkedin.com/in/maryblessingokolie/), project manager at Contributor Covenant by [Organization for Ethical Source](https://ethicalsource.dev/).\n\nI noticed that your project doesn’t currently have a Code of Conduct (CoC). Having one is an important step in building trust, setting clear expectations, and fostering inclusive collaboration. You can learn more about why a CoC matters here:\n\n- Open Source Guides: [Why you need a code of conduct](https://opensource.guide/code-of-conduct/)\n- GitHub: [About codes of conduct](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)\n- Open Source Conducts: [Codes of Conduct (CoC)](https://opensourceconduct.com/)\n\nWe recently released Contributor Covenant v3.0, the most widely adopted code of conduct in open source, now updated with clearer enforcement guidelines and broader community input: https://www.contributor-covenant.org/ \n\nIf your project doesn’t yet have a designated CoC team, you can start by assigning a trusted maintainer as the first point of contact. This can evolve as your community grows.\n\nWe’re also hosting a Community Call on September 12th, 7pm GMT to share what’s new in version 3, discuss adoption, and answer questions. You’re warmly invited to join. Due to the sensitivity of the discussion and the possibility of spam, I won’t share the Zoom link here in a public repo. Please let me know the best email address to send the official invite to.\n\nBest regards,\nMaryblessing","author":{"url":"https://github.com/Maryblessing","@type":"Person","name":"Maryblessing"},"datePublished":"2025-08-27T20:33:09.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/52/openapi/issues/52"}