2011/10/13 Henning Brauer <[email protected]>: > it's not as if the tools were broken. > > us moving a lot of the development process that used to happen on > internal mailing lists to tech has helped a little bit with getting > more people to get involved, but it could still be better. > > blaming the shortage of that on the tools is a poor excuse. if we > switched to git today, nothing would change. except that we, the devs, > had to learn and deal with the quirks of a new rcs system. > > -- > Henning Brauer, [email protected], [email protected] > BS Web Services, http://bsws.de, Full-Service ISP > Secure Hosting, Mail and DNS Services. Dedicated Servers, Root to Fully > Managed > Henning Brauer Consulting, http://henningbrauer.com/
I can just speak for my self and I have been a member of misc@ for many years and It's just since the last week I also become a member of tech@. I had not a single clue that it was important testing that was going on in that list and help was needed. I will for sure do my share and help testing diffs but just blaming the commitment of the community is wrong. I think it's a combination of everything, both commitment, tools and information. Jeremie Courreges-Anglas response/behaviour is one typical thing what totally drains our (users) engagement. We hardly not dare to write a single line because there is a little but disturbing kind of people that destroys for all others. One little suggestion, hint or anything that's unorthodox in the spirit of OpenBSD and you get bashed and put in the corner of shame. I just think that the commitment can improve if we also has the right tools. For example, if a developer needs help and I could find all open cases with diffs that need be tested then it would be more easy for me to take that diff, test and then send a response. When the developer has enough input then he/she can close the case. For sure, we can read old threads in the list but does the developer sends a notice when the test is done and no more input is needed? How do we work efficient ? Not only the developers time is important, every single person that are committed to OpenBSDs time is important. I would love to help writing a new bug tracker that could be merged into base but I'm no skilled coder but I have engagement and I want to help testing. I can probably provide server and space but for sure give my own time as a tester of the system. Best regards Johan
