Re: Open Source Gardening - Lucene/Solr relevance?
Thanks for reminding us about this mess. Rather than fix the old Wiki, we should just archive it all and start afresh with a better structured set of community-edited pages (already being discussed elsewhere). Then Alexandre and others can direct their energy towards building a really good New-User experience rather than patching the old ugly wiki. Also the huge amount of open JIRA issues getting shuffled from rev-to-rev is not ideal. Reviewing old inactive JIRAs is something some of us do from time to time, but could definitely need more eyes on that part. The TaskList page could be replaced with some JIRA labeling conventions. Much better to describe wanted tasks and features in JIRAs (with possible sub tasks) than in wiki. We already tried that with the newdev label but I'm afraid it is rather random what issues got that label - another need for gardening. On Wed, Apr 16, 2014 at 5:33 PM, Shawn Heisey s...@elyograg.org wrote: On 4/16/2014 4:14 AM, Alexandre Rafalovitch wrote: I don't normally repost to the mailng lists, but this is better than my own attempts :-) http://words.steveklabnik.com/how-to-be-an-open-source-gardener I would be curious to know how this topic applies to Lucene/Solr. I have a feeling that the old-timers have a particular sequence/process/concept in mind. But, the more recent members may not. Good blog post. We should all be doing it. I try to stay on top of the email that I get from ASF, but there's a lot of it and sometimes work and life take precedence. Specifically, I have - for the first time really - gone through the sections under Solr Development section of the Wiki. I can tell that half of the items there are out of date and obsolete. The other half, I cannot tell (because I am not an old timer/committer). E.g. the ideas on http://wiki.apache.org/solr/TaskList . Some of them must have been implemented, some proven stillborn (Apache Wirr), some point at long abandoned issues. How can we spend 3-5 minutes per issue and triage it into Yes/No (/Maybe?) and into the form that somebody could actually find it (on http://www.codetriage.com/ or similar). I didn't know this existed. That's probably the case for a lot of people. There are likely other pages as well that are horribly out of date. I suspect that they get created by someone who is interested in triage, but later abandoned because that person either lost interest or got consumed by other projects. This one looks much fresher http://wiki.apache.org/solr/HowToContribute : But do we actually still have a separate commit list? I thought this one (dev@) was it. Or, maybe, I just can't tell what's wrong with the page, I am only up to the step 5 on it. And is http://s.apache.org/newdevlucenesolr really used? Probably needs the same triage as before. That wiki page needs updating, like so many others. There is a separate comm...@lucene.apache.org list. I've been subscribed to it since 2010. The dev list gets a copy of every Jira update, but the commits made to svn are logged separately. Most commits do include a SOLR- or LUCENE- identifier. For those, there's an email from svn and one from Jira. The svn-jira link is more important for issue histories than for the email notification, but I do like seeing the email. I don't know if that specific Jira filter gets used. But I do know that when a Solr release is made, every open issue for that specific version is looked at by the release manager. A lot of issues simply get bumped to the next release over and over ... they need more attention than that. We could do better. Please do contribute if you can. I would like to do more, there's just so little time. Thanks, Shawn - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Open Source Gardening - Lucene/Solr relevance?
I don't normally repost to the mailng lists, but this is better than my own attempts :-) http://words.steveklabnik.com/how-to-be-an-open-source-gardener I would be curious to know how this topic applies to Lucene/Solr. I have a feeling that the old-timers have a particular sequence/process/concept in mind. But, the more recent members may not. Specifically, I have - for the first time really - gone through the sections under Solr Development section of the Wiki. I can tell that half of the items there are out of date and obsolete. The other half, I cannot tell (because I am not an old timer/committer). E.g. the ideas on http://wiki.apache.org/solr/TaskList . Some of them must have been implemented, some proven stillborn (Apache Wirr), some point at long abandoned issues. How can we spend 3-5 minutes per issue and triage it into Yes/No (/Maybe?) and into the form that somebody could actually find it (on http://www.codetriage.com/ or similar). This one looks much fresher http://wiki.apache.org/solr/HowToContribute : But do we actually still have a separate commit list? I thought this one (dev@) was it. Or, maybe, I just can't tell what's wrong with the page, I am only up to the step 5 on it. And is http://s.apache.org/newdevlucenesolr really used? Probably needs the same triage as before. I am not complaining here, just think a discussion could be nice. Links to past discussions could be useful as well, even if they are somewhat outdated. Regards, Alex. Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Open Source Gardening - Lucene/Solr relevance?
On 4/16/2014 4:14 AM, Alexandre Rafalovitch wrote: I don't normally repost to the mailng lists, but this is better than my own attempts :-) http://words.steveklabnik.com/how-to-be-an-open-source-gardener I would be curious to know how this topic applies to Lucene/Solr. I have a feeling that the old-timers have a particular sequence/process/concept in mind. But, the more recent members may not. Good blog post. We should all be doing it. I try to stay on top of the email that I get from ASF, but there's a lot of it and sometimes work and life take precedence. Specifically, I have - for the first time really - gone through the sections under Solr Development section of the Wiki. I can tell that half of the items there are out of date and obsolete. The other half, I cannot tell (because I am not an old timer/committer). E.g. the ideas on http://wiki.apache.org/solr/TaskList . Some of them must have been implemented, some proven stillborn (Apache Wirr), some point at long abandoned issues. How can we spend 3-5 minutes per issue and triage it into Yes/No (/Maybe?) and into the form that somebody could actually find it (on http://www.codetriage.com/ or similar). I didn't know this existed. That's probably the case for a lot of people. There are likely other pages as well that are horribly out of date. I suspect that they get created by someone who is interested in triage, but later abandoned because that person either lost interest or got consumed by other projects. This one looks much fresher http://wiki.apache.org/solr/HowToContribute : But do we actually still have a separate commit list? I thought this one (dev@) was it. Or, maybe, I just can't tell what's wrong with the page, I am only up to the step 5 on it. And is http://s.apache.org/newdevlucenesolr really used? Probably needs the same triage as before. That wiki page needs updating, like so many others. There is a separate comm...@lucene.apache.org list. I've been subscribed to it since 2010. The dev list gets a copy of every Jira update, but the commits made to svn are logged separately. Most commits do include a SOLR- or LUCENE- identifier. For those, there's an email from svn and one from Jira. The svn-jira link is more important for issue histories than for the email notification, but I do like seeing the email. I don't know if that specific Jira filter gets used. But I do know that when a Solr release is made, every open issue for that specific version is looked at by the release manager. A lot of issues simply get bumped to the next release over and over ... they need more attention than that. We could do better. Please do contribute if you can. I would like to do more, there's just so little time. Thanks, Shawn - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
