Document all functions

[ndmitchell]

I currently disable the complete Haddock doc check because lots of things fail. I should fix the docs and enable it.

[Neppord]

@ndmitchell where do i start to help with this?

[ndmitchell]

Thanks for the offer. Did you see the warning at https://github.com/ndmitchell/bake#readme?

Warning: This project is not actively developed - you are likely to be better of using something more complete (if you do want to use it, consider forking it and taking it over).

If you are interested in doing stuff, and have the inclination to take over, I recommend forking it and taking it over, otherwise I'd just let it quietly rot...

[Neppord]

Thanks! I did see it i just dont know how to take over, i havent been able to start a build yet. And there is a lot of info and todo in your github issues, that dont follow over in a fork.

May i ask why bake is abonden? Before finding bake i had planed to build something similar my self.

Something with pretested integration, and with sane defaults. I want to simplify companies Continuous Delivery pipeline and the maintenance of the infrastructure needed.

How did bake fail, did you find something better? In that case maybe i want to use that instead :p.

Is there a design flaw that i should be aware of.

Thanks for taking your time to answer, even when the project is inactive!

[ndmitchell]

Very reasonable questions, and ones that anyone wanting to look at Bake should be aware of, so I wrote a blog post answering them: https://neilmitchell.blogspot.co.uk/2018/05/the-end-of-bake.html. Let me know if there are any remaining questions. I haven't found anything better, but everywhere I've worked since has used Jenkins, which has been adequate at best.

I don't think the issues in GitHub are that valuable - but agree that figuring out how to build is a necessary first step before forking :)