Korona wrote:
I don't know if we need a strict rule -- some rule of thumb should be sufficient. The screenshot thread is not spammed either.
I'd suggest some recommendation on the length of posts. I think posts should give some context but not be too long. After all, neither "I implemented an IDT." nor full page posts with technical details would be desirable. I think we should encourage posts to state some context like "This weekend, I implemented an IDT. I encountered problems X and Y. It took me a while to figure out that Z in my code was wrong but the qemu debugger helped me to find this issue. Thanks to the IDT support, I also implemented a keyboard driver; I can now use the arrow keys move my ASCII art unicorn around the screen."
I like the context and problems encountered. I was thinking it should be focused on one meaty feature, examples include (follow up questions in brackets)
- modified scheduler to facilitate priorities (why did you go with X over Y, I had problems while implementing Z how did you overcome that)
- the idt example and really getting into how you debugged it
- got the first piece of SMP support in place (how are you planning on managing Z down the road)
Then go into these were my problems, fun/interesting things I learned in the process, things I'd like to revisit or do differently.
Note that this isnt a hard format, but the examples are just there to show how its one thing that could bring up a few posts. Not so much a blogpost of here's everything I did last week. But that's just my thoughts, I'm open to ideas.