Adam, Your second email sounds more like code monitoring than ownership. Is that more of what you had in mind?
As far as whether these constraints are considered a policy or an obligation for other committers, I guess we'd have to vote on that. I don't think we have anything setup (yet) to allow individuals to create obligations for others. Actually, even if we vote on something that creates obligations for others what can we really do about it? I guess we can get into commit wars, but that's about it. We don't have men with guns, or cages to put people in, or even people who write threatening letters for a living. As a labour saving device you might consider putting some information in these files themselves so people have a chance to collaborate with you on this, and you don't have to worry so much about watching it, especially a year or two from now when this thread has faded from even our fondest dreams. Useful information might include the coverage status, where the tests are, how to run and test for coverage, etc (I think all of these would be one-liners in the file). -David On Mar 14, 2010, at 10:40 PM, Adam Heath wrote: > So, with the recent threads we've participated in, I've decided to > announce a decision of mine. > > Any class that I have added test cases that have gotten to 100% > coverage, I have decided to take ownership of. Any change that is > done to such a class *must* have a test case that keeps the coverage > at 100%. This doesn't mean that the code will automatically work > perfectly all the time. But if something *is* added that makes the > coverage fall below 100%, it means the class is *not* fully tested, > and that is a big problem. On Mar 14, 2010, at 10:55 PM, Adam Heath wrote: > Anil Patel wrote: >> Adam, >> Thanks for hard work. I am sure people in community respect your effort and >> will co-operate. > > This decision of mine doesn't preclude others from doing work in these > classes. But I will be watching these classes like a hawk, and would > greatly appreciate anyone that wants to change them try to keep the > coverage up if they do so.
