UPDATE:
I've started to work on a website for this project I've got a lot of information and it's spread out in my repo in such a way I don't think may people can find it. To that end I've started to organise it and I'm trying out some SSG so I can use gitlab pages.
Any suggestions for missing or hard to find documentation that I could make more clear? I'm also thinking to start a mini dev blog for the project. Not sure that it will be helpful or not but sometimes people report problems here and sometimes there are issues and it might be a good idea to have them all in one place with so comments I don't know this is just a thought it might be a bad idea but good documentation is a good idea.
This would be an example of something that could go into the dev blog. I'm looking at why I should have the daemon support both the old firmware and the new firmware. Once the code is compiled does it make sense to check what hardware firmware in use each time? It seems like it would be faster to have that set at compile time. How many people move there installs between systems? I would keep auto detect for those that do but it makes sense to include a way to skip the auto detect and have a setting or compile option.
I've started to work on a website for this project I've got a lot of information and it's spread out in my repo in such a way I don't think may people can find it. To that end I've started to organise it and I'm trying out some SSG so I can use gitlab pages.
Any suggestions for missing or hard to find documentation that I could make more clear? I'm also thinking to start a mini dev blog for the project. Not sure that it will be helpful or not but sometimes people report problems here and sometimes there are issues and it might be a good idea to have them all in one place with so comments I don't know this is just a thought it might be a bad idea but good documentation is a good idea.
This would be an example of something that could go into the dev blog. I'm looking at why I should have the daemon support both the old firmware and the new firmware. Once the code is compiled does it make sense to check what hardware firmware in use each time? It seems like it would be faster to have that set at compile time. How many people move there installs between systems? I would keep auto detect for those that do but it makes sense to include a way to skip the auto detect and have a setting or compile option.
Statistics: Posted by DarkElvenAngel — Wed Mar 13, 2024 3:49 am