Re: Importing new repositories?
On Thu, 2021-09-23 at 11:57 +, Sharan Foga wrote: > Let's not lose this idea so please create an issue on Kibble Github > repo for your suggestion about being able to join multiple emails > together. We can flag it as a future feature and if we do manage to do > some tidy up of Kibble-1 then we might be able to pick it up. https://github.com/apache/kibble/issues/12 Thanks, Robert
Re: Importing new repositories?
Hi Sharan, Thanks a lot! I guess I was confused that there are views with the same name and I thought I was unable to edit them. Now I see all repos, and I explicitly excluded two sources: - https://github.com/apache/sling-old-svn-mirror.git, which is our old pre-git migration repo. - https://lists.apache.org/list.html?comm...@sling.apache.org, which reflects the Jira/GitHub/Nexus activity and therefore is basically noise. I saw some discussion about the new version of Kibble, are you still receiving enhancement requests for the 'old' one? One thing that really stands out is that people are mapped by email address but we usually get multiple ones and that makes it hard get proper email addresses. I would be happy with a way to manually say per...@apache.org/per...@employer.com/per...@gmail.com are the same. Thanks, Robert On Thu, 2021-09-23 at 10:06 +, Sharan Foga wrote: > Hi Robert > > I have just added the 6 new sling repos to the Kibble demo sources. > I've checked that they are appearing in the list and they are showing > as not yet processed. They should be processed on the new data refresh. > > Any problems or questions then please let me know :-) > > Thanks > Sharan > > On 2021/09/23 09:50:14, Sharan Foga wrote: > > Hi Robert > > > > Thanks for sending this. I have taken a look. > > > > So in the Kibble Demo using the guest@kibbledemo profile I took a > > look at the Sling view that was included there. It said that it had > > 340 sources some of which were not even Sling, so I have deleted that > > view and recreated one that uses sling as a filter. It is now showing > > 338 sources. Remember that anyone can log in using the guest profile > > and change this view so I am guessing that you are referring to and > > using the views created using your own Kibble profile (As I see that > > you have one setup :-). This is personal to you so only you can > > update them. > > > > So now I have been through your list of Sling repos and did a bit of > > a cross check and this this is what I found. > > > > *Sling Repo in Kibble But Not on Your List* > > The following sling repo was not in your list but is is a valid sling > > repo in Kibble that is been imported and aggregated. > > > > - https://github.com/apache/sling-old-svn-mirror.git > > > > If it is in your view and you want to remove it then please go ahead. > > > > *Sling Repos on Your List But Not in Kibble* > > I found the following 6 sling repos in your list that don't yet exist > > in Kibble, so I will add them. > > > > - https://github.com/apache/sling-org-apache-sling-auth-saml2.git > > - > > https://github.com/apache/sling-org-apache-sling-graphql-schema-aggregator.git > > - > > https://github.com/apache/sling-org-apache-sling-jcr-maintenance.git > > - https://github.com/apache/sling-org-apache-sling-scripting-spi.git > > - https://github.com/apache/sling-org-apache-sling-sitemap.git > > - https://github.com/apache/sling-org-apache-sling-thumbnails.git > > > > I will let you know once they are added and remember you will need to > > wait for the refresh for them to be active so hopefully later today > > it should be done. > > > > Thanks > > Sharan > > > > On 2021/09/22 09:47:11, Robert Munteanu wrote: > > > On Wed, 2021-09-22 at 08:25 +, Sharan Foga wrote: > > > > Hi Robert > > > > > > > > If the repos you are talking about are not already in the source > > > > list > > > > then we need to add them manually so I will need the list to do > > > > that. > > > > > > > > Today is a bit of a busy day for me but I can definitely take a > > > > proper > > > > look tomorrow. > > > > > > > > Thanks > > > > Sharan > > > > > > Hi Sharan, > > > > > > Thanks for taking this up! I generated a full list of Sling > > > repositories, see attached. > > > > > > I tried to generate a list of the new repos only by playing with > > > the > > > API, but I only managed to login via PUT /api/session; the cookie > > > that > > > was returned apparently did not allow me to run GET /api/sources . > > > > > > Thanks! > > > Robert > > > > >
Importing new repositories?
Hi, I am trying to gather some data using the kibble.dev instance, which has been going on very nicely for a couple of years, thanks for that! In the Sling project we have quite a number of repositories and I noticed not all are imported. I count 338 in [1] but the 'Sling' view from Kibble only has 330. Can someone please import the missing sling projects and add them to the Sling view? ISTR that it was easy to do a bulk re-add but if that's not the case let me know and I'll generate a list of the missing projects. Thanks! Robert [1]: https://github.com/apache?q=sling-===
Re: Adding more sources to kibble.dev
Hi Sharan, On Wed, 2020-09-23 at 11:36 +, Sharan Foga wrote: > Hi Robert > > I've added your apache email address to the Apache organisation. Have > a try now to see if you can add any sources. Any problems let me > know. :-) That worked, thank you very much! I'll wait until tomorrow to see if all sources have been correctly imported. Thanks, Robert > > Thanks > Sharan > > On 2020/09/23 11:24:35, Sharan F wrote: > > Hi Robert > > > > I will take a quick look now and get back to you. > > > > Thanks > > Sharan > > > > On Wed, 23 Sep 2020, 13:06 Robert Munteanu, > > wrote: > > > > > Hi, > > > > > > I am trying to add some more sources to the kibble.dev instance. > > > I had > > > a user tied to me apache email but apparently that does not work > > > anymore ( or maybe I think I did ... it was some time ago ). > > > > > > I tried to add some sources with the demo user, but I am told > > > > > > You don't have permission to add sources to this organisation. > > > > > > With my freshly created user I not connected to the Apache org. > > > > > > I'd appreciate if someone could look into this - our annual > > > 'Sling & > > > friends' [1] conference starts on Monday and I'd like to present > > > some > > > updated numbers. > > > > > > For reference, I've attached the full repository list, IIRC I > > > don't > > > need to submit the delta. > > > > > > Thanks! > > > > > > Robert > > > > > > [1]: https://adapt.to/2020/en.html > > >
Re: Projects refresh on kibble.dev?
Great. Thanks a lot, Daniel! Robert On Wed, 2019-07-17 at 11:24 +0200, Daniel Gruno wrote: > Update: > > - 24 new repos were added today > - Fixes have been put in place to work around GitHub's rate limits > by > checking said limits and waiting for them to reset, then continuing. > - Additional workarounds for abiding by abuse detection rules have > been > made. > > I am happy to report that as of today, all GitHub Issues/PRs are > properly scanned on a daily basis :) > > > On 10/07/2019 16.25, Robert Munteanu wrote: > > On Wed, 2019-07-10 at 15:48 +0200, Daniel Gruno wrote: > > > On 7/10/19 3:44 PM, Robert Munteanu wrote: > > > > Hi, > > > > > > > > Can anyone please run an import of the new GitHub projects on > > > > https://kibble.dev ? Currently some repositories are missing. > > > > > > I can get around to that this week, sure thing! > > > > Thanks! > > > > > > Also, I see that on [1] some sources have not been synced due > > > > to > > > > "API > > > > rate limit exceeded for user ID 51666742". Does this impact the > > > > analysis of projects on the long run or does it only mean that > > > > it > > > > will > > > > be delayed by some days? > > > > > > That depends...we have nearly 2000 repos on github now, and > > > scanning > > > them all for changes is one of the bottlenecks we're working on > > > (keep > > > in > > > mind, github allows for 5,000 API calls per hour only). It > > > _should_ > > > only > > > mean that some (randomly ordered) github issue/pr scans are > > > delayed > > > for > > > a day or two, but I'll take a look at whether we can somehow > > > avoid > > > this > > > more easily, when time permits. > > > > Thanks for clarifying. For me personally it is perfectly fine to > > get > > data with some delay (1-2-5 days), as I'm not looking at it in real > > time, maybe once every month. > > > > Thanks! > > > > Robert > >
Re: Projects refresh on kibble.dev?
On Wed, 2019-07-10 at 15:48 +0200, Daniel Gruno wrote: > On 7/10/19 3:44 PM, Robert Munteanu wrote: > > Hi, > > > > Can anyone please run an import of the new GitHub projects on > > https://kibble.dev ? Currently some repositories are missing. > > I can get around to that this week, sure thing! Thanks! > > > Also, I see that on [1] some sources have not been synced due to > > "API > > rate limit exceeded for user ID 51666742". Does this impact the > > analysis of projects on the long run or does it only mean that it > > will > > be delayed by some days? > > That depends...we have nearly 2000 repos on github now, and scanning > them all for changes is one of the bottlenecks we're working on (keep > in > mind, github allows for 5,000 API calls per hour only). It _should_ > only > mean that some (randomly ordered) github issue/pr scans are delayed > for > a day or two, but I'll take a look at whether we can somehow avoid > this > more easily, when time permits. Thanks for clarifying. For me personally it is perfectly fine to get data with some delay (1-2-5 days), as I'm not looking at it in real time, maybe once every month. Thanks! Robert
Projects refresh on kibble.dev?
Hi, Can anyone please run an import of the new GitHub projects on https://kibble.dev ? Currently some repositories are missing. Also, I see that on [1] some sources have not been synced due to "API rate limit exceeded for user ID 51666742". Does this impact the analysis of projects on the long run or does it only mean that it will be delayed by some days? Thanks, Robert [1]: https://kibble.dev/organisations.html?page=sources
Re: New demo server, ALL THE PROJECTS!
On Wed, 2019-06-12 at 11:42 +0200, Daniel Gruno wrote: > On 6/12/19 11:39 AM, Robert Munteanu wrote: > > Hi, > > > > On Mon, 2019-06-10 at 17:52 +0200, Daniel Gruno wrote: > > > the dogs and ponies at Quenda have donated a much beefier machine > > > for > > > our tests, with more than a terabyte of super fast NVMe storage > > > and > > > twice the compute capacity, meaning we're going to aim at having > > > the > > > ENTIRE ASF in our demo! This might not work very well at all, but > > > we're > > > going to try! > > > > That is great news :-) . Do you also plan to keep this instance > > periodically updates with new repositories that are created in the > > apache github org? > > The hopeful plan is to keep it up to date with everything we have at > ASF. I will, however, stress that it's a demo, and not a production > system, so there will be no guarantees that it stays up or that the > data > isn't wiped now and then, for science reasons. First and foremost, > it's > meant as a test for developing the software :) All clear on that. I'm probably going a step too far :-) , but are there any plans to set up a production instance? Thanks, Robert
Re: New demo server, ALL THE PROJECTS!
Hi, On Mon, 2019-06-10 at 17:52 +0200, Daniel Gruno wrote: > the dogs and ponies at Quenda have donated a much beefier machine > for > our tests, with more than a terabyte of super fast NVMe storage and > twice the compute capacity, meaning we're going to aim at having the > ENTIRE ASF in our demo! This might not work very well at all, but > we're > going to try! That is great news :-) . Do you also plan to keep this instance periodically updates with new repositories that are created in the apache github org? Thanks, Robert
Re: Password reset not working?
On Wed, 2019-05-01 at 09:13 -0500, Daniel Gruno wrote: > On 01/05/2019 09.05, Sharan Foga wrote: > > Hi Robert > > > > Taking a look at the password reset code, there is nothing behind > > it except a re-display of the index page. I'm setup as Admin but > > cant see anywhere to manage or reset paswords for existing user > > profiles. > > > > Daniel do you have any tips how we can get Robert back up and > > running? > > I don't think the password reset works at all right now :\. > I might have time to make it do stuff within a few days, but for > now, > it'd be best to just use the guest account if needed. Ack, thanks. I'm trying to understand how things can be mode to work in the context of the Sling project. We are trying to include Kibble in our repo creation workflow (we have ~300 github repos, periodically creating some more, maybe 1-2 per month). I think most of the repos are onboarded, but we still need to add some from time to time. What would you suggest that we do whenever we want to include a new repo to Kibble? - use the guest user ( but that has no write privileges IIRC ) - use individual accounts for each PMC member ( do those need 'approval' in some way to get write privileges? ) - share an individual account, e.g. priv...@sling.apache.org - something else Thanks! Robert
Re: Password reset not working?
Hi Sharan, On Sun, 2019-04-28 at 10:45 +, Sharan Foga wrote: > Hi Robert > > Did anyone fix this for you yet? > Nope, not yet :-) Robert > Thanks > Sharan > > On 2019/04/16 13:13:31, Robert Munteanu wrote: > > Hi, > > > > I tried to reset my password on http://demo.kibble.apache.org/ . I > > enter my email (romb...@apache.org) and I just get redirected to > > http://demo.kibble.apache.org/index.html . Nothing reaches my > > inbox. > > > > Can anyone please advise how to solve this? > > > > Thanks, > > > > Robert > > > >
Password reset not working?
Hi, I tried to reset my password on http://demo.kibble.apache.org/ . I enter my email (romb...@apache.org) and I just get redirected to http://demo.kibble.apache.org/index.html . Nothing reaches my inbox. Can anyone please advise how to solve this? Thanks, Robert
Re: API access available?
On Tue, 2018-09-18 at 17:55 +0200, Daniel Gruno wrote: > One thing to note; For GitHub repos, you will need to specify a > user/pass if you want github issues/PRs to be looked at - this can be > an > anonymous account if you like. I'll see if I can't work our regular > kibble user into the repos you added, assuming you did not specify > any user. Interesting, I did not know that (maybe add it as a hint on the page?). I did not specify any user as I saw no need :-) - GitHub repos are public but it would be interesting to see PR information as well. Thanks, Robert
Re: API access available?
On Thu, 2018-09-13 at 16:45 +0200, Daniel Gruno wrote: > On 09/13/2018 04:42 PM, Daniel Gruno wrote: > > On 09/13/2018 04:38 PM, Robert Munteanu wrote: > > > Hi, > > > > > > I am trying to simplify my job of keeping the list of sources up- > > > to- > > > date for the Kibble demo instance. Basically we add git > > > repositories > > > periodically and I want to add them to Kibble as well. > > > > > > I was thinking of using the Kibble API to retrieve the list of > > > sources > > > and checking which of our repositories are not there, so I can > > > easily > > > paste them in Kibble. > > > > It's a bit convoluted at the moment, apologies. > > First, you have to obtain a session cookie by logging in; > > https://demo.kibble.apache.org/apidoc.html#put-api-session > > when you have that cookie, pass it to the API end point you wish to > > use, > > and it should work just fine. > > > > I'll be working later next week on API tokens for use here, it's > > one of > > the things that are still missing. > > > > With regards, > > Daniel. > > > > I should add one important/easy thing here: > > If you want to keep the list of sources up to date with e.g. github, > you > can just PUT a request with all the sources you have, and it will > both > update existing ones and add the ones it doesn't have, there are > checks > against adding duplicates, so only sources that aren't in the DB > would > get added even if you post old sources to the API. > That is nice! Since I'm having some issues with the API (see earlier emails) I used the web form to paste in all Sling repos again. It seems to have worked - the repos are added (though I see not yet processed ) and the old date is still there. One things which threw me off a bit is that even existing repositories now have a status of "Source hasn't been processed yet..." . That looks mostly cosmetic though since the old data is still there. Thanks, Robert
Re: API access available?
On Thu, 2018-09-13 at 16:42 +0200, Daniel Gruno wrote:
> On 09/13/2018 04:38 PM, Robert Munteanu wrote:
> > Hi,
> >
> > I am trying to simplify my job of keeping the list of sources up-
> > to-
> > date for the Kibble demo instance. Basically we add git
> > repositories
> > periodically and I want to add them to Kibble as well.
> >
> > I was thinking of using the Kibble API to retrieve the list of
> > sources
> > and checking which of our repositories are not there, so I can
> > easily
> > paste them in Kibble.
>
> It's a bit convoluted at the moment, apologies.
> First, you have to obtain a session cookie by logging in;
> https://demo.kibble.apache.org/apidoc.html#put-api-session
> when you have that cookie, pass it to the API end point you wish to
> use,
> and it should work just fine.
>
> I'll be working later next week on API tokens for use here, it's one
> of
> the things that are still missing.
I'm trying to set this up but not managing - perhaps there is a flaw in
my code? I'm using something like
$ curl --cookie-jar .cookies -v -X PUT -H "Content-Type: application/json"
https://demo.kibble.apache.org/api/session -d "{ \"email\": \"${1}\",
\"password\": \"${2}\" }"
$ curl -v --cookie .cookies https://demo.kibble.apache.org/api/session
$ rm .cookies
While the first call succeeds, for the second one I get
< HTTP/1.1 403 Authentication failed
< Date: Mon, 17 Sep 2018 16:24:42 GMT
< Server: gunicorn/19.6.0
< Content-Type: application/json
< Transfer-Encoding: chunked
<
{
"code": 403,
"reason": "You must be logged in to use this API endpoint! %s"
}
I can see the cookie being sent and then returned. But If I got my
timezone calculations correctly, the cookie immediately expires
Just now I got
< Set-Cookie: kibble_session=f7dc532d-dcb4-4fa2-ad80-3e8c83a4b0e2; expires=Tue,
17 Sep 2019 16:27:14 GMT
which looks to be 'now'.
Any hints on how to solve this?
Thanks,
Robert
Re: Contributors page tests
On Mon, 2018-09-17 at 10:04 +0200, Daniel Gruno wrote: > > I also see that the contributor is linked to an email address so we > > will > > probably will have people that are contributing under different > > email > > addresses, though not sure if that is an issue at this stage. > > There are, and it's not an easy task to solve. email addresses are > the > best we can reliably guess is a single person. There could be two > Sharans or Daniels, but they would have different email addresses, > so > that's our best guess for what constitutes a person. We should make > some > way of merging people. One suggestions that was floated around when presenting Kibble was the GitHub API - since Kibble can pull data from GitHub it can potentially use that API _if_ a someone defines multiple email aliases for the same account. Thanks, Robert
Re: Possible to exclude directories from analysis?
On Wed, 2018-09-12 at 14:37 +0200, Daniel Gruno wrote: > top posting, yaay! > I have a new server sort of set up now. I'll have infra redirect to > that > one instead, and it'll rebuild most of the database during the night > (and the next night, and...). > > there's a new option, a path filter in the repos tab, which filters > commits, line changes, trends, top contributors etc by paths > affected, > so you can enter either 'jbake' to get everything touching jbake, or > '!jbake' to get everything that doesn't touch those files. > > The CNAME should switch over some time today :) Cool, thanks! I'll give this a shot later. Robert > > With regards, > Daniel. > > PS: We're also switching to elasticsearch 6 with this move, which is > going to be great, as that allows us to test on a modern ES, instead > of > the old 5.x installation we're currently running on. > > On 09/12/2018 12:24 PM, Daniel Gruno wrote: > > On 09/12/2018 12:22 PM, Robert Munteanu wrote: > > > > > > If you look at the sling-site repository at [1] we have the > > > actual > > > documentation under src/main/jbake, with > > > - content being markdown files > > > - templates being ... well ... templates > > > - and assets being static files > > > > > > Some of those static files are generated (javadoc, Maven plugin > > > sites) > > > and should not be recorded by Kiddle. Those are the ones that are > > > problematic, especially since we have a large number of javadocs > > > committed. > > > > > > $ find src/main/jbake/assets/apidocs -type f | wc -l > > > 7127 > > > > > > Those are the ones we'd like excluded, if at all possible. > > > > > > Thanks, > > > > > > Robert > > > > > > [1]: > > > https://github.com/apache/sling-site/tree/master/src/main/jbake > > > > > > > > > > I've added a change to the scanners, so they will put a list of > > files > > changes into each commit object we record. This is likely going to > > require a complete re-scan of all things sling...which in theory > > is > > fine, as I _was_ planning on moving the demo server to a new box > > anyway. > > I'll let y'all know more when I have that worked out in my mind :) > > After the move and re-scan, it should be possible to exclude by > > file paths. > >
API access available?
Hi,
I am trying to simplify my job of keeping the list of sources up-to-
date for the Kibble demo instance. Basically we add git repositories
periodically and I want to add them to Kibble as well.
I was thinking of using the Kibble API to retrieve the list of sources
and checking which of our repositories are not there, so I can easily
paste them in Kibble.
So I tried to access the Kibble API
$ curl -v --netrc https://demo.kibble.apache.org/api/sources
(snip)
* Server auth using Basic with user 'romb...@pache.org'
> GET /api/sources HTTP/1.1
> Host: demo.kibble.apache.org
> Authorization: Basic REDACTED
> User-Agent: curl/7.61.1
> Accept: */*
>
< HTTP/1.1 403 Authentication failed
< Date: Thu, 13 Sep 2018 14:33:51 GMT
< Server: gunicorn/19.6.0
< Content-Type: application/json
< Transfer-Encoding: chunked
<
{
"reason": "You must be logged in to use this API endpoint! %s",
"code": 403
}
Is it possible to get read-only API access to the list of sources? If
not I'll look for something else, but would simplify things for me :-)
Thanks,
Robert
Re: Possible to exclude directories from analysis?
On Wed, 2018-09-12 at 12:05 +0200, Daniel Gruno wrote: > On 09/12/2018 12:00 PM, Robert Munteanu wrote: > > On Sat, 2018-09-08 at 12:54 +0200, Daniel Gruno wrote: > > > On 09/05/2018 08:38 PM, Robert Munteanu wrote: > > > > Hi, > > > > > > > > I'm using the demo Kibble instance to visualise code > > > > contributions > > > > for > > > > the Apache Sling project. One thing I noticed is that Kibble > > > > things > > > > we're 75% HTML, which is not right - we're a Java project. > > > > > > > > I think it's due to the fact that we use gitpubsub and have > > > > registered > > > > our github.com/apache/sling-site repository with kibble. That > > > > repository's master branch holds all the HTML we publish, > > > > including > > > > lots of Javadocs, Maven plug-in documentation, etc. > > > > > > The easiest path would be to simply exclude the sling-site > > > repository > > > in > > > your reports. If you're using a quick filter, instead of > > > filtering > > > on > > > 'sling', you could do a negative lookahead and filter on > > > 'sling(?!-site)' as the quick filter accepts regular expressions. > > > > Thanks for the suggestestion. I ended up excluding the sling-site > > repository completely from the 'Apache Sling' view. It's not ideal > > as > > it does not capture documentation contributions, which are quite > > important as well. > > > > It would be great if in the future we would have a more fine- > > grained > > solution. > > Ideal solutions are rare :) > Could you elaborate on exactly *what* you want to see, and what you > want > to filter away? Some things may be possible, but when you have to do > aggregations on something like 3 million commits in real-time, it > gets > tricky to exclude paths and individual files without throwing a huge > lag > spike into the mix. If you look at the sling-site repository at [1] we have the actual documentation under src/main/jbake, with - content being markdown files - templates being ... well ... templates - and assets being static files Some of those static files are generated (javadoc, Maven plugin sites) and should not be recorded by Kiddle. Those are the ones that are problematic, especially since we have a large number of javadocs committed. $ find src/main/jbake/assets/apidocs -type f | wc -l 7127 Those are the ones we'd like excluded, if at all possible. Thanks, Robert [1]: https://github.com/apache/sling-site/tree/master/src/main/jbake
Re: Feedback Requested from Kibble Demo Projects
On Wed, 2018-09-12 at 12:18 +0200, Daniel Gruno wrote: > On 09/12/2018 12:14 PM, Robert Munteanu wrote: > > 3. I was unable to find what the Pony Factor is. Some documentation > > (inline in the app or in the manual) would be great. > > https://ke4qqq.wordpress.com/2015/02/08/pony-factor-math/ > > We should put a link to that or add the description to the > documentation, yeah. it's basically a risk factor. Thanks for the primer in equine mathematics :-) Robert
Re: Feedback Requested from Kibble Demo Projects
Hi Sharan, (+dev@sling) On Mon, 2018-09-10 at 10:07 +0200, sha...@apache.org wrote: > Hi All > > Thanks very much for being one of the projects that is part of the > Kibble demo instance. We hope that you are making use of the > information > Kibble shows about your project. We have had our demo instance up > and > running for most of this year so now we'd like to get some feedback > from > you about how you are using Kibble. > > Some example questions that we’d be interested in are as follows: > > * How often are you using Kibble and what are you using it for? I for one used it a couple of times to try and assess community health by looking for new contributors. Having 280+ git repos makes it very hard to do so with other tools. > * How does information from Kibble inform decisions or is useful in > other ways? I'm looking mostly at trends - how is the number of contributors evolving? Do we have new people coming in and contributing? > * What questions about your community can you currently not answer > and > what information could Kibble provide to help answer these > questions? Top of my head, that would be: - contributions by non-committers - code, emails - release activity ( can be picked up from Jira or from [VOTE] emails ) > * What problems do you have with using Kibble? 1. Trying to access the 'contributors' tab with the 'Apache Sling' view results in a 'Widget design not found' error for me [1] 2. (Not an issue with Kibble per se) Since we keep adding repositories (~20 are not on Kibble) we would need a way of automating it. I saw that Kibble has an API, but not sure how much work is for us to manage the repositories list ( + the view ). Need to look into it. 3. I was unable to find what the Pony Factor is. Some documentation (inline in the app or in the manual) would be great. - Guess that about covers it. Overall I'm happy Kibble exists I can extract stats about our projects so thanks for that! Robert [1]: https://demo.kibble.apache.org/contributors.html?page=mvp=adb6da82a758f0cc0d3b650b9e839c15c0e0f7d92ff5f074821d7e98
Re: Possible to exclude directories from analysis?
On Sat, 2018-09-08 at 12:54 +0200, Daniel Gruno wrote: > On 09/05/2018 08:38 PM, Robert Munteanu wrote: > > Hi, > > > > I'm using the demo Kibble instance to visualise code contributions > > for > > the Apache Sling project. One thing I noticed is that Kibble things > > we're 75% HTML, which is not right - we're a Java project. > > > > I think it's due to the fact that we use gitpubsub and have > > registered > > our github.com/apache/sling-site repository with kibble. That > > repository's master branch holds all the HTML we publish, including > > lots of Javadocs, Maven plug-in documentation, etc. > > The easiest path would be to simply exclude the sling-site repository > in > your reports. If you're using a quick filter, instead of filtering > on > 'sling', you could do a negative lookahead and filter on > 'sling(?!-site)' as the quick filter accepts regular expressions. Thanks for the suggestestion. I ended up excluding the sling-site repository completely from the 'Apache Sling' view. It's not ideal as it does not capture documentation contributions, which are quite important as well. It would be great if in the future we would have a more fine-grained solution. Thanks, Robert
Possible to exclude directories from analysis?
Hi, I'm using the demo Kibble instance to visualise code contributions for the Apache Sling project. One thing I noticed is that Kibble things we're 75% HTML, which is not right - we're a Java project. I think it's due to the fact that we use gitpubsub and have registered our github.com/apache/sling-site repository with kibble. That repository's master branch holds all the HTML we publish, including lots of Javadocs, Maven plug-in documentation, etc. Is it possible to exclude a certain directory from analysis, to make the statistics more relevant? Thanks, Robert
Re: Request for Participation: The Right Metrics for the Right Project
Hi, On Mon, 2017-11-27 at 19:26 +0100, Daniel Gruno wrote: > Hi there, fellow Apache projects! > > The Apache Kibble project serves as a practical implementation of > metrics deemed to be helpful for open source projects trying to > understand where their project is, was, and is headed. > > As such, we need help in determining which metrics projects either > already use and consider useful for measuring project health or which > metrics they would love to have and use. > > We are looking for projects interested in participating in the Kibble > demo instance ( https://demo.kibble.apache.org/ ) and sending > feedback > to the Kibble project on which parts they find useful, which elements > they find useless and which ideas they would love to see implemented > to > better gauge the health and activity of their project. I would be interesting in gathering information about the Apache Sling project. Now, I'm aware that we might be a bit special, having in access of 250 projects ( canonical listing at [1] ), so I won't be shocked if you reject or delay our inclusion. We are interested in Kibble since we have split our source repositories which makes it hard to generate aggregate statistics of our development activity. For me personally the most important indicators to track would be the number of distinct contributors over the last X months, which is a fair indicator of community engagement. Thanks, Robert [1]: https://github.com/apache/sling-aggregator/blob/master/default.xml
