Seeking Collaborators for CLNDR 2.0

I have been anxious to get working on a new version of CLNDR. It was written a year and a half ago now (!) and the code no longer reflects my standard of quality. It was also written without a clear understanding of which features would be most useful or interesting. I’m ready to try again with a much clearer picture of what it should be and how it should be put together.

Maintaining open source software is fun and interesting, but it’s also a lot of responsibility! I would love to share this process— and the resulting codebase— with at least one other person.

I am 100% on board to share everything from architectural ideas to commit privileges with as many folks as are willing to participate. Here are some thoughts I have about where to go with version 2.0, in no particular order:

• Use browserify to modularize parts of the plugin
• Unit test everything
• Allow the plugin to be used as a node module, allowing initial rendering on the server
• Remove the concept of a month in favor of any interval of time as explored in the intervals branch
• Use _.template internally and remove underscore/lodash dependency
• Optimize!

If you are interested let’s talk about it! I have no expectations about timeline- we could do it in a week or across 6 months. I’d love to hear from some past contributors as well- @jaakon, @Ahrengot, and @dmerrill6 come to mind.

[mikegioia]

@kimroen I just removed it now 😛

[kimroen]

The call to action for this issue on the marketing page could probably be changed or removed at this point! (https://kylestetz.github.io/CLNDR/)