Hi Mike

I have responded on the Jira ticket but also responding here too for 
completeness. The new Lucene repo has loaded data but it seems to be stalled on 
the issue load. If you can let me know what issue tracker you are using, I can 
check to see if it needs to be loaded too.

Thanks
Sharan

On 2021/10/17 18:24:03, Sharan Foga <sha...@apache.org> wrote: 
> Hi Mike
> 
> I responded on the Jira ticket but will also add a note here. I have updated 
> the kibble demo to pull in data from https://github.com/apache/lucene at the 
> next data synch. It's currently showing in the list as unsynched but I'll 
> check it tomorrow to see if any data has been brought it in.
> 
> Thanks
> Sharan
> 
> 
> On 2021/10/10 12:59:11, Sharan Foga <sha...@apache.org> wrote: 
> > Hi Mike
> > 
> > Thanks for the report. I will see if I can take a look.
> > 
> > Thanks
> > Sharan
> > 
> > On 2021/10/05 14:35:44, Michael McCandless <luc...@mikemccandless.com> 
> > wrote: 
> > > Hello,
> > > 
> > > I am hoping someone here on the Kibble dev list can help us fix COMDEV-425
> > > <https://issues.apache.org/jira/browse/COMDEV-425>:
> > > 
> > > Over in the Apache Lucene project, as we were drafting our last Board
> > > quarterly report, we noticed that the "Busiest GitHub topics", which seems
> > > to use Kibble in the Apache Reporter tool
> > > <https://svn.apache.org/repos/asf/comdev/reporter.apache.org/trunk>, fails
> > > to include Lucene's github repo (https://github.com/apache/lucene).
> > > 
> > > It is currently using lucene-solr, lucenenet, lucene-site.
> > > 
> > > But since Lucene and Solr have not split development, we need to add 
> > > lucene
> > > into that list as well.  And likely Solr also needs to add "solr" github
> > > repo.
> > > 
> > > I think there must be some Kibble configuration somewhere to fix.  I can
> > > see from kibble.py that the tool loads the stats from
> > > https://demo.kibble.apache.org.  Does anyone know where that configuration
> > > might be?
> > > 
> > > Thanks!
> > > 
> > > Mike McCandless
> > > 
> > > http://blog.mikemccandless.com
> > > 
> > 
> 

Reply via email to