Hmmm, interesting. Now I can see your dilemma and how my questions were "wrong". So yeah, you gave me the answer I was looking for.
On the other hand, if this is the case than probably the devs themselves should take their time and write a blog post every (other) week shortly describing what they are working on and what is the purpose/aim of that. I mean really, 5-10 sentences wouldn't hurt and take away the time from coding!
I try to give an example: Marek has submitted a lot of code recently for the r300g driver as git shows. But I'm an end user so the git commits don't give me much information on the benefits of the commits. They shouldn't either as that is not the purpose of them. But still, some more insight on a less techie level to what is going would be nice.
Just writing this stuff I realised that most probably it is Phoronix which I am wishing for. Maybe I just got dragged in too deeply into these matters that the flow of information from Michael is not enough...
As a sidenote it is good to be back on the interesting stuff!
On the other hand, if this is the case than probably the devs themselves should take their time and write a blog post every (other) week shortly describing what they are working on and what is the purpose/aim of that. I mean really, 5-10 sentences wouldn't hurt and take away the time from coding!
I try to give an example: Marek has submitted a lot of code recently for the r300g driver as git shows. But I'm an end user so the git commits don't give me much information on the benefits of the commits. They shouldn't either as that is not the purpose of them. But still, some more insight on a less techie level to what is going would be nice.
Just writing this stuff I realised that most probably it is Phoronix which I am wishing for. Maybe I just got dragged in too deeply into these matters that the flow of information from Michael is not enough...
As a sidenote it is good to be back on the interesting stuff!
Comment