# NoM Community Contribution Guidelines

**URL:** <http://forum.zenon.org/t/nom-community-contribution-guidelines/1319>\
**Category:** Development\
**Created:** [February 27, 2023, 8:30pm UTC](http://forum.zenon.org/t/nom-community-contribution-guidelines/1319 "2023-02-27T20:30:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![0x3639](http://forum.zenon.org/user_avatar/forum.zenon.org/0x3639/32/1651_2.png) [@0x3639](http://forum.zenon.org/u/0x3639)\
**Post date:** [February 27, 2023, 8:30pm UTC](http://forum.zenon.org/t/nom-community-contribution-guidelines/1319/1 "2023-02-27T20:30:36Z")

</div>

As we work through this first wave of community contributions to SYRIUS and go-zenon I hope we can learn from this process and prepare some Community Contribution Guidelines.

@coinselor you found many good examples. Can you share some of the links here in this post. I think @sol found this one. [jon atack - How to Contribute Pull Requests to Bitcoin Core](https://jonatack.github.io/articles/how-to-contribute-pull-requests-to-bitcoin-core)

I hope others can share examples and then someone from the community (other than the guys writing code) can synthesize the information and prepare Community Contribution Guidelines.

We can use the wiki function of the forum and many people can contribute once we have the framework in place.

---

<div class="post-metadata">

**Author:** ![coinselor](http://forum.zenon.org/user_avatar/forum.zenon.org/coinselor/32/2832_2.png) [@coinselor](http://forum.zenon.org/u/coinselor)\
**Post date:** [February 28, 2023, 8:54pm UTC](http://forum.zenon.org/t/nom-community-contribution-guidelines/1319/2 "2023-02-28T20:54:12Z")

</div>

I’ll gather the sources as I create the document for reference. My goal is to provide a little bit more than a skeleton document to set the basic structure in place while making it clear where I think NoM-specific content should be provided/filled in by _actual_ developers. I will try to get it done asap since there is a great need for it. However, this is not a document we can afford to half-ass, so proper research and attention to detail are essential.

On the bright side, it looks like contributing devs are finding some common ground and moving toward some sort of consensus 🙂