As mentioned above, this is a community project, maintained by volunteers. If you need help with OXID Module Connector, please turn to the boards, to avoid bugging the OMC or the OXIDforge editorial team. If you need help with modules listed in OMC, please find it in either the boards or consider to contact the vendor of this module.
Good news first: for you as a module vendor, your module is and will be completely independent from OXID Module Connector (OMC). All OMC will need is a JSON file (recipe) that defines where to find the most important information as well as how to map your module structure into the folder structure of an OXID eShop installation. Find out how to provide a JSON file.
If you run an OXID based shop to sell your OXID extensions/modules, you might find this tool helpful: OXID Module Connector Generator is an extension that exports the necessary JSON files for OMC that you simply can adapt and send them to the OMC recipe branch via pull request. (Many thanks to @AlphaSys for this module!)
Please note that anyone can add or propose any module of any vendor. However, there’s no general right of acceptance.