Thanks for the response Shawn ! In relation to this : "I feel fairly sure that most of them are unwilling to document their skills. If information like that is documented, it might saddle a committer with an obligation to work on issues affecting those areas when they may not have the free time available to cover that obligation. "
I understand your point. I was referring to pure Lucene/Solr modules interest/expertise more than skills but I get that "it might saddle a committer with an obligation to work on issues affecting those areas when they may not have the free time available to cover that obligation." It shouldn't transmit an obligation ( as no contributor operates under any SLA but purely passion driven ) but it might be a "suggestion" . I was thinking to some way to avoid such long standing Jiras. Let's pick this issue as an example. >From the little of my opinion I believe it is quite useful. The last activity is from 22/May/17 15:23 and no committer commented after that. I would assume that committers with interest or expertise on Learning To Rank or Grouping initially didn't have free time to evaluate the patch and then maybe they just forgot. Having some sort of tagging based on expertise could at least avoid the "forget" part ? Or the contributor should viralize the issue and get as much "votes" from the community as possible to validate an issue to be sexy ? Just thinking loudly, it was just an idea ( and I am not completely sure it could help) but I believe as a community we should manage a little bit better contributions, of course I am open to any idea and perspective. Cheers ----- --------------- Alessandro Benedetti Search Consultant, R&D Software Engineer, Director Sease Ltd. - www.sease.io -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
