New maintainer needed

[bkaestner]

I'm not really interested in writing this document anymore. It has been fun at first, but I don't find that much time to continue it lately. Also, it somewhat feels like the lack of official documentation (no documentation on the C# or C++ framework) shouldn't be filled by a third party.

This project was meant as a quick introduction to random test cases in Haskell for @g964, has grown slightly out of proportion, and could probably be a nice reference to new Codewars users. Any interested maintainer may comment on this discussion or write an email.

[DonaldKellett]

@bkaestner may I take part in maintaining the Codex? I just need some information on what to maintain and how. Thanks 😄

[mattcollie]

@bkaestner I am interested also :)

[bkaestner]

may I take part in maintaining the Codex? I just need some information on what to maintain and how.

At this point, maintaining the codex means adding new information and fix old issues. For example, several languages are missing best practices, e.g. #7, #8, #10. With the addition of the new testing framework, a chapter on C++ is necessary.

So basically, maintaining would require you to write new text and check that the old one isn't riddled with errors from time to time.

From an organisational point of view, becoming the maintainer would transfer the ownership of this repository to either of you, or, if you prefer, to a new GitHub organization. Alternatively, I can stay the owner of the repository for a while and accept additional content via pull-request. Depending on the amount of changes you want to contribute, this could be a little bit cumbersome, but gives you a small safety net, since I still audit your changes.

Changes must be committed under the CC-BY-SA 4.0 license (see contributing).

That's basically everything. Get ownership of the repository (or provide pull-requests or become a collaborator), add new content, remove old/invalid content.

[DonaldKellett]

Thanks a lot for the instructions @bkaestner , either way would be fine by me (owner, member, contributor, collaborator, etc.). Just give me a call if you want help with anything Javascript-related (or Ruby-related) regarding the Codex 😄

[bkaestner]

@DonaldKellett You can check the section on JavaScript and whether something's missing. The Ruby section should probably contain at least the same amount of information.