On Tue, Nov 13, 2012 at 6:01 PM, Steffen Schwigon wrote: > > > >> Ok, I generally understand your rationale, so even if I'm not convinced, > >> let's continue: how would you proceed after you have opened tickets on > >> all dependent modules? > > > > then I will track what happens. probable replies: > > 1. STFU. I don't care > > 2. I looked on the problem and it does not affect my module on my target > > platforms. so, I don't care > > 3. Pinging Test::Class author, and getting him to fix it > > 4. Pinging T::C author, got a comaint and fixed it myself > > 5. ticket ignored > > Hm, in IT this is called a Distributed Denial of Service attack. > > Distributed Request for Service? DRoS?
> You already have your use-case: Test::Class does not work for you. So > let's continue to analyze this single case: > > - What did you already try to help the author? > A ticket was created, with a patch. > - Why did your help not resolve the issue? > Ticket was ignored. > - What else can you do? Or, > what are your reasons you can not do more? > I can ask for comaint. Sorry, won't do that anymore. I already took over two modules, and it is a lot of hard work to learn and maintain somebody's else code. I can contribute a patch, but no more. > - What are the author's reasons he cannot solve the issue? > I don't know. the ticket was ignored. > - Will more quantity solve the quality issue? Why will it? > Maybe an author will be motivated enough to push so it will be fixed? Maybe Test::Class author will see that there are a lot of people that are concerned about the his module failing to install that he will fix it himself? Then scale up the thinking to all CPAN: > > - What is the calculated criteria or barrier before auto-generating > tickets? > If a module have test failures and was released more then a month ago, I think that we can generate tickets. > - Will every author have the same reasons for not solving issues, so > that there is indication the same approach will help the other > author's, too? > I don't understand the question. > - Will this automation-approach scale-up to a huge bi-directionally > connected matrix of several thousand authors and users? > - How do you automatically track and close these multi-thousands of > automatically generated tickets? > I only need to open and track them, not close. Shmuel.
