I am currently hacking around, and noticed that there is no real "howto hack". There is also several points in which code architecture might be improved a lot (yes, it takes lot of time and does not add featires, but I think that it would ease improvements and reduce bugs).
I intend to take some time to do so, but I have several questions to avoid wasting my and your time:
* is cpp11 allowed? cpp14?
* is it ok to remove commented code? It just slows reading the code and pollutes the diffs.
* any coding standard? It seems that there are globally followed rules, but can't really guess them all from source.
* is there is any kind ofAPI or ABI stability to keep? Maybe something network related?
* would it be ok to split manuslly those f*****g long lines that are everywhere? What would be the ideal max width (remember, splitting a screen to see 2 files is damn useful)?
* with a defined codestyle, it could be possible to add a git hook to checkthat they are followed, which would avoid code quality regressions. Would it be ok?
* few things could be imported or exported from/into libs, I am thinking about the (mathematical) vector genric class, for example. What would be the requirements?
* errors are sometimes managed with exceptions (not inheriting std::exception, too) and sometimes with nullchecks. I think it would be good to uniformize that, but to which direction? Anddo you agreewith this?
Finally, I have noticed the point about copyrights of contributions. I am notagainst cc0, but I must admit I prefer cc-by, which is roughly BSD-3 clauses. Itdoes not cost to name contributors, right?
![Wink ;)](./images/smilies/icon_wink.png)
I will probably have several other questions, but let those come in the discussion
![Smile :)](./images/smilies/icon_smile.png)