On pe, 20 touko 2022, Leo O via FreeIPA-users wrote:
Hello Alexander,
oh that's a pity. I would have expected that there are at least some notes, maybe some technical explanations about such general things, anything which helps to speed up the process and not making a newcomer having to read the source code. I mean, it looks like FreeIPA isn't a small project, it is used by Red Hat IDM, somewhere in Fedora and as community FreeIPA. I really expected more than an almost non existing documentation and/ or really outdated pdfs. What can you do with the best application of the world if "nobody knows how to set it up for their needs" to exagerate that statement a bit ;) Hope there are plans to improve on that in the near future, I would say that's more important than new features. Lot's of tests and documentation for the win. Anyways, thanks for the quick reply, I still think this is a great software package which could reach way more projects, teams, businesses, github stars etc. with just having a better documentation.
There is no such thing as 'just having a better documentation' for what is effectively a development process. One needs to understand that one and reading source code is the best way to do that right now. There are plenty of comments in ipalib/*, ipapython/*, ipaserver/plugins/* and in related places, code and git commit messages are the developer documentation at this point. Documentation writers aren't developers themselves, with very little exceptions, and cannot replace developers in writing that knowledge base.
There is always a balance between fixing bugs and working full time on producing a documentation you are asking for. Having large number of customer- and community-driven deployments sometimes skews priorities towards more realistic tasks.
You are welcome to contribute to developer documentation as you go through a journey to discover how to extend IPA. It certainly will be beneficial to everyone.