Re: Draft Kibble Board Report

[Sharan Foga]

Hi 

Just to let you all know that I found and corrected a small typo and then 
posted the report.

Thanks
Sharan

On 2024/05/05 17:34:53 sharanf wrote:
> Hi All
> 
> Our board report is due in a few days so I've prepared an initial draft. 
> Please feel free to take a look and let me have any feedback or updates. 
> I'll aim to finalise and post it to the board agenda by the 8th May.
> 
> Thanks
> Sharan
> 
> 
> 
> -
> 
> ## Description:
> The mission of Apache Kibble is the creation and maintenance of software
> related to an interactive project activity analyzer and aggregator
> 
> ## Project Status:
> Current project status: Dormant, low activity
> Issues for the board: None
> 
> ## Membership Data:
> Apache Kibble was founded 2017-10-18 (7 years ago)
> There are currently 15 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 8:7.
> 
> Community changes, past quarter:
> - No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
> - No new committers. Last addition was Kaxil Naik on 2021-02-21.
> 
> ## Project Activity:
> The project has not yet made a release.
> 
> There has been low activity since our last report. Some minor changes have
> been made to the website and some of its links. We have also started 
> reviewing
> some of the old PRs that were submitted and merging those that are still
> relevant.
> 
> We have also started an initial thread on the mailing lists focussed on
> updating our install documentation to align to the previous Kibble -1 
> version
> as we received another request about the documentation not referring to the
> current Kibble repo.
> 
> ## Community Health:
> The community is small community and we do need a common focus to drive 
> more
> engagement. We are continuing to take small steps around the 
> documentatio neffort
> and also trying to open up for discussions and ideas about a possible 
> roadmap
> and future of the project.
> 
> 

Re: Buildbot Job Missing for Rebuilding Kibble Website?

[Sharan Foga]

Hi All

A quick update - merging the html files does work :-)

I've merged a PR from a contribution we got a few years ago adds a description 
of the various repos we have and an outline of how they all work.

tps://kibble.apache.org/docs/downloads.html 

For Kibble - the next generation - I've included a note that it is in progress 
and we are working on a roadmap to re-design and re-write it.

Thanks
Sharan

On 2024/04/01 09:46:25 sharanf wrote:
> Hi All
> 
> Reading through our old website readme docs - any changes to the source 
> markdown files are picked up and regenerated by a buildbot job. I merged 
> some minor changes yesterday and they are not showing up on the website. 
> Investigating a further I dont see any buildbot jobs for our website 
> rebuild from the infra links. https://github.com/apache/infrastructure-bb2
> I will follow up to see what's not happening! (in the meantime - I can 
> see if merging the locally generated html files solves the issue)
> 
> Thanks
> Sharan
> 

Re: [I] Configuring and Priming the Kibble Instance [kibble]

[Sharan Foga]

FYI - have responded to this on Github pointing them to the Kibble-1 and 
Kibble-Scanners repos.

On 2024/02/16 10:33:24 "sufiyan-ahmed (via GitHub)" wrote:
> 
> sufiyan-ahmed opened a new issue, #21:
> URL: https://github.com/apache/kibble/issues/21
> 
>
>
>**Description:**
>
>
>**Reproduction steps:**
>
>**Actual result:**
>
>
>**OS:**
>
>MacOS
>**Logs:**
>
>
>**Other:**
>
>
> 
> 
> -- 
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
> 
> To unsubscribe, e-mail: dev-unsubscr...@kibble.apache.org.apache.org
> 
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
> 
> 

RE: Draft Kibble Board Report

[Sharan Foga]

Hi All

Just to let you know that the report has been posted.

Thanks 
Sharan

On 2024/02/11 14:16:47 sharanf wrote:
> That looks a bit messy so let's try it again:
> 
> Hi All It's report time again.
> 
> Unfortunately over the last quarter we haven't had any real activity. 
> I'll post a separate message on my thoughts on how we can try to improve 
> that. In the mean time I've drafted our quarterly board report. (See below).
> 
> Happy to get any comments, feedback or updates to the draft over the 
> next couple of days - and will aim to finalise and post it to the board 
> meeting calendar on 14th February.
> 
> Thanks
> Sharan
> 
> 
> ==
> 
> ## Description:
> The mission of Apache Kibble is the creation and maintenance of software
> related to an interactive project activity analyzer and aggregator
> 
> ## Project Status:
> Current project status: Dormant, low activity
> Issues for the board: None
> 
> ## Membership Data:
> Apache Kibble was founded 2017-10-18 (6 years ago)
> There are currently 15 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 8:7.
> 
> Community changes, past quarter:
> - No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
> - No new committers. Last addition was Kaxil Naik on 2021-02-21.
> 
> ## Project Activity:
> The project has not yet made a release.
> 
> There has been no activity since our last report and our mailing lists
> have been quiet. It was hoped that we could begin to kick off some 
> activity in
> the previous quarter but this has not happened.
> 
> ## Community Health:
> We are a small community and perhaps just need to start something rather 
> than
> taking on a large activity such as a complete codebase rewrite (which 
> was our
> planned intention).  We are probably losing potential contributors due to
> incomplete documentation so kicking off a small activity such as 
> cleaning up our
> existing documentation could be a way of gathering more community
> participation. By mid to late March I should have more free cycles to begin
> that documentation tidy up work and we will see what results that brings.
> 
> 
> 
> 
> On 2024/02/11 14:12:13 sharanf wrote:
>  > HI All It's report time again. Unfortunately over the last quarter we
>  > haven't had any real activity. I'll post a separate message on my
>  > thoughts on how we can try to improve that. In the mean time I've
>  > drafted our quarterly board report. (See below). Happy to get any
>  > comments, feedback or updates to the draft over the next couple of days
>  > - and will aim to finalise and post it to the board meeting calendar on
>  > 14th February. Thanks Sharan == ## Description: The mission of
>  > Apache Kibble is the creation and maintenance of software related to an
>  > interactive project activity analyzer and aggregator ## Project Status:
>  > Current project status: Dormant, low activity Issues for the board: None
>  > ## Membership Data: Apache Kibble was founded 2017-10-18 (6 years ago)
>  > There are currently 15 committers and 13 PMC members in this project.
>  > The Committer-to-PMC ratio is roughly 8:7. Community changes, past
>  > quarter: - No new PMC members. Last addition was Michał Słowikowski on
>  > 2021-05-03. - No new committers. Last addition was Kaxil Naik on
>  > 2021-02-21. ## Project Activity: The project has not yet made a release.
>  > There has been no activity since our last report and our mailing lists
>  > have been quiet. It was hoped that we could begin to kick off some
>  > activity in the previous quarter but this has not happened. ## Community
>  > Health: We are a small community and perhaps just need to start
>  > something rather than taking on a large activity such as a complete
>  > codebase rewrite (which was our planned intention). We are probably
>  > losing potential contributors due to incomplete documentation so kicking
>  > off a small activity such as cleaning up our existing documentation
>  > could be a way of gathering more community participation. By mid to late
>  > March I should have more free cycles to begin that documentation tidy up
>  > work and we will see what results that brings.
>  >
> 

Re: Draft Kibble Board Report

[Sharan Foga]

Hi All

I've posted this as our board report.

Thanks
Sharan

On 2023/11/10 15:08:22 sharanf wrote:
> HI All
> 
> I've drafted our quarterly board report. (See below).
> 
> We've had no real activity since the previous and I think if we cant get 
> some work started in the next quarter then we may need to seriously 
> start thinking about an Attic discussion. I sincerely hope we don't get 
> to that stage but I wanted to be frank with the board as to the current 
> status of the project.
> 
> Happy to get any comment, feedback or updates to the draft.
> 
> Thanks
> Sharan
> 
> 
> 
> ## Description:
> The mission of Apache Kibble is the creation and maintenance of software
> related to an interactive project activity analyzer and aggregator
> 
> ## Project Status:
> Current project status: Dormant, low activity
> Issues for the board: None
> 
> ## Membership Data:
> Apache Kibble was founded 2017-10-18 (6 years ago)
> There are currently 15 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 8:7.
> 
> Community changes, past quarter:
> - No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
> - No new committers. Last addition was Kaxil Naik on 2021-02-21.
> 
> ## Project Activity:
> The project has not yet made a release.
> 
> There has been no activity since our last report.
> 
> ## Community Health:
> The community is small and our contributors have had no free cycles to kick
> off any of the suggested work. I'd like to see if we can get around to
> starting some activities in the next quarter and if not then we may need to
> seriously start thinking about an Attic discussion.
> 
> 
> 

Re: Draft Kibble Board Report

[Sharan Foga]

Hi All

A quick update to let everyone know that this draft was submitted as our board 
report.

Thanks
Sharan

On 2023/08/13 19:12:01 sharanf wrote:
> Hi All
> 
> I've drafted a board report for the quarter.
> Please take a look and let me know if you have any feedback, comments or 
> updates.
> 
> Thanks
> Sharan
> 
> 
> --
> 
> 
> ## Description:
> The mission of Apache Kibble is the creation and maintenance of software
> related to an interactive project activity analyzer and aggregator
> 
> ## Project Status:
> Current project status: Ongoing, low activity
> Issues for the board: None
> 
> ## Membership Data:
> Apache Kibble was founded 2017-10-18 (6 years ago)
> There are currently 15 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 8:7.
> 
> Community changes, past quarter:
> - No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
> - No new committers. Last addition was Kaxil Naik on 2021-02-21.
> 
> ## Project Activity:
> The project has not yet made a release.
> 
> We've had a couple more contributions [1][2]. One has been merged and the
> other is still open pending review.
> 
> We have also had a discussion [3] on whether to clear down the current 
> Kibble
> Github repo in preparation to restart development from scratch. The plan 
> is to
> move the current main branch into a new side branch so that we can pick
> up and use specific features we may want to incorporate into the new  Kibble
> main branch.
> 
> ## Community Health:
> The community remains fairly small but we have seen some new people 
> turning up
> either as users trying out an install or as documentation contributors. 
> We are
> trying to actively engage with the new people to see if that sparks interest
> in the project.
> 
> I hope that once the holiday season is over we will be able to start working
> on getting the new main branch setup.
> 
> [1] https://s.apache.org/hqvdk
> [2] https://s.apache.org/2sqcn
> [3] https://s.apache.org/n7tip
> 

Re: [DISCUSS] Clearing Down the Kibble Github Repo

[Sharan Foga]

That's sounds like a practical way forward. And I see there is already an empty 
nextgen branch

Also if we are going to keep the history and the PR improves what we have -  I 
dont see any reason not to merge it before we start any of the new stuff. 

Thanks
Sharan

On 2023/07/10 20:05:59 Daniel Gruno wrote:
> On 2023-07-10 22:02, sharanf wrote:
> > Hi All
> > 
> > When we separated out the repos into Kibble-1 and Kibble the plan was to 
> > start again from scratch. Some work was done in the new Kibble repo but 
> > that has been stalled for quite a while. I know Daniel has some ideas 
> > for either kickstarting some new work but that could mean clearing down 
> > the Kibble repo once again.
> > 
> > We don't have a working version on things in the Kibble repo as its 
> > Kibble-1 that is the working version. I've also seen that we are getting 
> > some PRs Inlcuding this one (https://github.com/apache/kibble/pull/17) 
> > coming through on the Kibble repo that are more documentation focussed 
> > changes.
> > 
> > So I'd like to discuss whether we continue to merge these PRs or decide 
> > to clear the Kibble repo down and begin again.
> > 
> > What do people think?
> 
> I think, if the aim is to sort of start afresh, perhaps the best 
> compromise there is to move the current main branch to the side (rename 
> it, keep its history) and make a new main branch from scratch.
> 
> And yeah, I do have some WIP stuff that grabs ideas and prototypes from 
> both old and newer kibble code, I should polish it up and commit, when 
> time allows :)
> 
> > 
> > Thanks
> > Sharan
> 
> 

Re: Draft Kibble Board Report

[Sharan Foga]

Hi All

Thanks for the feedback and I'll post this as our report.

Thanks
Sharan

On 2023/06/13 15:16:48 Daniel Gruno wrote:
> Looks good to me.
> 
> Well aware (painfully aware?) of the low activity, and I do have some 
> prototypes almost ready to start pushing, along with some basic CI 
> testing. I am currently trying to figure out the best approach here, but 
> will follow up in a separate thread.
> 
> 
> On 2023-06-11 21:11, sharanf wrote:
> > Hi All
> > 
> > See below - I've put together a draft board report for the quarter. 
> > Please take a look and let me know if you have any feedback, comments or 
> > updates.
> > 
> > Thanks
> > Sharan
> > 
> > 
> > 
> > ## Description:
> > The mission of Apache Kibble is the creation and maintenance of software
> > related to an interactive project activity analyzer and aggregator
> > 
> > ## Project Status:
> > Current project status: Ongoing, low activity.
> > Issues for the board: None.
> > 
> > ## Membership Data:
> > Apache Kibble was founded 2017-10-17 (6 years ago)
> > There are currently 15 committers and 13 PMC members in this project.
> > The Committer-to-PMC ratio is roughly 8:7.
> > 
> > Community changes, past quarter:
> > - No new PMC members. Last addition was Michał Słowikowski on 2021-05-02.
> > - No new committers. Last addition was Kaxil Naik on 2021-02-21.
> > 
> > ## Project Activity:
> > The project has not yet made a release.
> > 
> > Very little activity again during the quarter and still trying to find free
> > cycles to work on a release of previous Kibble version and a roadmap for 
> > what
> > the new Kibble could look like.
> > 
> > We've had a documentation contribution [1] from a new contributor and also
> > some interest from someone trying out an install [2].
> > 
> > ## Community Health:
> > The community is small and we know that we need to start focussing on 
> > building
> > it up to be more sustainable but we first need to have work on defining the
> > project vision and roadmap of where we want the project to go. I still 
> > think
> > putting out a Kibble-1 release will help separate the previous version from
> > the new one that we'd like to build.
> > 
> > [1] https://github.com/apache/kibble/pull/16
> > [2] https://s.apache.org/zm5ej
> > 
> 
> 

Re: Kibble Demo Down?

[Sharan Foga]

Hi All

The demo is back up. Daniel fixed an issue with java not running.

Thanks
Sharan

On 2023/03/14 20:54:17 sharanf wrote:
> HI All
> 
> I think the Kibble demo is down. I tried to login and it's not going 
> through. Confession - I did a software update on the VM at the weekend 
> but once that was done I did check that the Kibble folders were still 
> there. Taking a look on the VM today I cant see the Kibble folder at all 
> in the directory structure so none of the jobs are running.
> 
> Daniel - are you doing any maintenance etc? Otherwise we might need to 
> do a reinstall.
> 
> Thanks
> Sharan
> 

Re: Draft Board Report

[Sharan Foga]

Hi All

As I've had no feedback on this - I will post this as our report-

Thanks
Sharan

On 2023/01/29 15:16:00 sharanf wrote:
> Hi All
> 
> I've created a draft for our upcoming board report (extremely early this 
> time :-) as am heading to FOSDEM!. Please take a look and let me have 
> any feedback or comments.
> 
> Thanks
> Sharan
> 
> ---
> 
> ## Description:
> The mission of Apache Kibble is the creation and maintenance of software
> related to an interactive project activity analyzer and aggregator
> 
> ## Issues:
> There are no issues requiring board attention.
> 
> ## Membership Data:
> Apache Kibble was founded 2017-10-18 (5 years ago)
> There are currently 15 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 8:7.
> 
> Community changes, past quarter:
> - No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
> - No new committers. Last addition was Kaxil Naik on 2021-02-21.
> 
> ## Project Activity:
> Another quiet quarter with no real activity.
> 
> Still awaiting some free cycles to begin assessing the proposals around
> re-structuring the codebase.
> 
> The project has not yet made a release. Doing a release based on the 
> existing
> codebase has been previously discussed [1] and could be a way to create an
> upgrade path for existing users as well as creating a distinct separation
> between the existing codebase and any potential new work.
> 
> ## Community Health:
> No real traffic on the mailing lists this quarter. With the main holiday
> season over we are hoping to get some activity started, even if small steps
> during the next quarter.
> 
> [1] https://s.apache.org/7ql2h
> 
> 

Re: Kibble Board Report Due

[Sharan Foga]

Thanks for the update Daniel and sure feel free to come back with some ideas!

On 2023/01/29 14:41:38 Daniel Gruno wrote:
> On 1/29/23 15:05, sharanf wrote:
> > Hi All
> > 
> > Our board report is due soon so I will work on drafting something. I 
> > know it's been another quiet quarter for the project but we have had 
> > some significant holidays as part of it. As we move further in 2023 
> > let's see how we can start taking some small steps to generate some 
> > meaningful project activity.
> > 
> > Thanks
> > Sharan
> 
> Hi Sharan,
> 
> I am having some "unofficial" brainstorming chats with some other 
> interested folks (some are on the kibble project, some are not (yet?)) 
> about how to best turn the proposed roadmap into something more 
> tangible, and it is my hope that it'll result in some basic scaffolding 
> in the coming weeks.
> 
> I will note that these conversations are not for defining a new 
> direction or such - that will always be brought to the mailing list in 
> some form or the other - but rather just some informal chats about how 
> one could syntactically approach some of the goals set out in the 
> roadmap from November last year.
> 
> This will probably end up resulting in some prototype code that we can 
> look at and discuss wherever applicable (mailing lists, issues/PRs etc).
> 
> There are also a few yet-to-be-answered questions about the repository 
> layout for this, but I have not gotten that far yet :)
> 
> With regards,
> Daniel.
> 

Re: Draft Board Report

[Sharan Foga]

Hi All 

No additional feedback received so I will submit this as our report.

Thanks
Sharan

On 2022/09/15 11:44:21 sharanf wrote:
> Hi All
> 
> I've created a draft for our board report. Please take a look and let me 
> have any feedback or comments.
> 
> Thanks
> Sharan
> 
> 
> 
> ## Description:
> The mission of Apache Kibble is the creation and maintenance of software
> related to an interactive project activity analyzer and aggregator
> 
> ## Issues:
> There are no issues requiring board attention.
> 
> ## Membership Data:
> Apache Kibble was founded 2017-10-18 (5 years ago)
> There are currently 15 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 8:7.
> 
> Community changes, past quarter:
> - No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
> - No new committers. Last addition was Kaxil Naik on 2021-02-21.
> 
> ## Project Activity:
> DevLake Collaboration
> We were contacted by Apache DevLake (incubating)[1] as their community is
> working on similar tools to Kibble but for different use cases.They
> requested information and gave us the opportunity to present Kibble
> to their community and answer any questions. [2].As a result we have a few
> people accessing the Kibble-1 repo and asking questions around setting 
> it up.
> We have also added DevLake sources to Kibble so they can see and monitor 
> their
> own community statistics. We will continue to collaborate with DevLake
> 
> RoadMap Reboot
> A conversation has started to discuss how we could reboot the
> roadmap for Kibble development [3]. We should hopefully be able to provide
> more details on the progress of this in our next report.
> 
> PMC Roll Call
> The project has had low activity for a while so we wanted to
> check that the project still have sufficient oversight from the PMC. A> roll
> call was performed and was successful
> 
> ## Community Health:
> Our mailing list activity is low but we have been able to respond to the
> requests we have received. We are a small community that is looking to 
> grow so
> hope the collaboration with DevLake can help provide some opportunities to
> improve that.
> 
> [1] https://s.apache.org/9yklq
> [2] https://s.apache.org/ejgb5
> [3] https://s.apache.org/po6s8
> 
> 

Re: Potential Collaboraton with Apache DevLake

[Sharan Foga]

Hi All

A quick update on this:

I had the call with Hezheng Yin from DevLake and it was interesting to see the 
similarities between the projects. DevLake is written in Go and Kibble in 
Python but the general design is similar. Their focus is more DevOps related 
where they are looking at various use cases and ours is more community 
focussed. Even so we are exploring ways to perhaps share knowledge and 
collaborate. As a next step Hezheng is keen to talk to Daniel to find out more 
about the Kibble technical details. Let's hope we can get something moving 
again for Kibble :-)

And I have been invited to speak at the next DevLake community meeting on 18th 
August. https://lu.ma/01lv9yy0

So let's see how it goes!

Thanks
Sharan


On 2022/07/27 16:58:04 sharanf wrote:
> Hi All
> 
> I've been contacted by Hezheng Yin from the Apache DevLake community 
> https://devlake.apache.org/ to see if we 
> can find any synergies for potential collaboration. Both projects are 
> interested in gathering, aggregating and visualising metrics so perhaps 
> we could leverage each other's communities.
> 
> I'm looking to organise a chat with Hezheng to get a demo of DevLake and 
> find out about their roadmap. I'll report back to the list once I have 
> more details.
> 
> Thanks
> Sharan
> 

Re: Investigate and tidy up failing Kibble Demo sources

[Sharan Foga]

Hi All

An update - the list of failing repos has been reduced to around 90 now. I'll 
keep running through to see what can be fixed.

Thanks
Sharan

On 2022/03/20 16:45:26 Sharan Foga wrote:
> Hi All
> 
> I've down a first run through of the errors list targeting an error of not 
> finding the default branch. In a lot of cases the git repo was empty or didnt 
> exist so I have removed the sources. However I did find a few repos that had 
> default branches but the error was still being generated.
> 
> I've created an issue in the Kibble-Scanners repo with details of the repos 
> that do have default branches but the name of the branch is sometimes unusual 
> 
> https://github.com/apache/kibble-scanners/issues/7
> 
> I will keep running through the error list and if someone with some coding 
> experience can take a look through to see what the problem could be on the 
> default branch not being recognised by the scanners ..that would be great.
> 
> Thanks
> Sharan
> 
> On 2022/03/20 13:03:01 sharanf wrote:
> > Hi All
> > 
> > I took a look at the Kibble demo and see that we have over 150 rows in 
> > the source list that are failing to load for various reasons. It may be 
> > that it's an old directory that is no longer in use and we haven't 
> > removed it from our list - so I will start taking a look through them 
> > and start tidying them up.
> > 
> > Thanks
> > Sharan
> > 
> 

Re: Why my website updates didnt work

[Sharan Foga]

Yippee - it worked!

On 2022/03/19 16:03:52 sharanf wrote:
> Hi All
> 
> I finally got around to taking a look at why my last pull request to 
> update the website list about Who We Are didn't work. I did a checkout 
> of the site and followed the instructions to build the site. I was a 
> little confused because  there looks to be a difference to what is 
> displayed on our active site versus the code I checked out.
> 
> My understanding is that :
> 
>  1. we need to do changes in source directory markdown files
>  2. run the generate.py in the markdown source directory to the html
> files in the content directory
>  3. go to the content directory and run the simple http server to check
> things display correctly
>  4. if everything looks good - commit it and create a pull request :-)
> 
> So now I realised my mistake in updating the html files directly in the 
> content directory html file instead of the source directory markdown 
> files. Let's see if I can get it to work this time :-)
> 
> Thanks
> Sharan
> 
> 

Re: Investigate and tidy up failing Kibble Demo sources

[Sharan Foga]

Hi All

I've down a first run through of the errors list targeting an error of not 
finding the default branch. In a lot of cases the git repo was empty or didnt 
exist so I have removed the sources. However I did find a few repos that had 
default branches but the error was still being generated.

I've created an issue in the Kibble-Scanners repo with details of the repos 
that do have default branches but the name of the branch is sometimes unusual 

https://github.com/apache/kibble-scanners/issues/7

I will keep running through the error list and if someone with some coding 
experience can take a look through to see what the problem could be on the 
default branch not being recognised by the scanners ..that would be great.

Thanks
Sharan

On 2022/03/20 13:03:01 sharanf wrote:
> Hi All
> 
> I took a look at the Kibble demo and see that we have over 150 rows in 
> the source list that are failing to load for various reasons. It may be 
> that it's an old directory that is no longer in use and we haven't 
> removed it from our list - so I will start taking a look through them 
> and start tidying them up.
> 
> Thanks
> Sharan
> 

Re: Draft Kibble Board Report

[Sharan Foga]

Thanks Sebb - good catch! 

On 2022/02/13 14:49:54 sebb wrote:
> "... as our currently we ..." => "as currently we" ?
> 
> On Sun, 13 Feb 2022 at 14:02, sharanf  wrote:
> >
> > Hi All
> >
> > I've created a draft for our quarterly board report (please see below).
> > I've left it a little late this time so will need to file it asap.
> >
> > Thanks
> > Sharan
> >
> >
> > =
> >
> >
> > ## Description:
> > The mission of Apache Kibble is the creation and maintenance of software
> > related to an interactive project activity analyzer and aggregator
> >
> > ## Issues:
> > There are no issues requiring board attention.
> >
> > ## Membership Data:
> > Apache Kibble was founded 2017-10-18 (4 years ago)
> > There are currently 15 committers and 13 PMC members in this project.
> > The Committer-to-PMC ratio is roughly 8:7.
> >
> > Community changes, past quarter:
> > - No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
> > - No new committers. Last addition was Kaxil Naik on 2021-02-21.
> >
> > PLEASE NOTE:The project has not yet made a release.
> >
> > ## Project Activity:
> > There has been pretty much no activity this quarter. We are a small
> > community
> > and had hoped that the New Year would help kick off some activity but it
> > hasn't happened yet.
> >
> > A good place to start some project activity is on tidying up the
> > installation
> > and setup documentation as our currently we have two Kibble code
> > repositories
> > [1][2] (Kibble and Kibble-1) and they may be causing confusion to any
> > potential
> >   users.
> >
> > ## Community Health:
> > The low email traffic confirms the lack of activity for the quarter. It is
> > getting more important for us to engage with and motivate the community to
> > become more active. We hope that working on the documentation work will
> > trigger some user feedback that will help kick start more activity.
> >
> > [1] https://s.apache.org/4gbje
> > [2] https://s.apache.org/xvqpu
> 

Re: DRAFT Kibble Board Report

[Sharan Foga]

Hi All

I've had no additional community feedback so will submit this report.

Thanks
Sharan

On 2021/11/09 17:38:11 sharanf wrote:
> Hi All
> 
> Our quarterly board report is due this month so I have created an 
> initial draft. Please take a look and let me have any comments or 
> suggested changes.
> 
> Thanks
> Sharan
> 
> 
> =
> 
> ## Description:
> The mission of Apache Kibble is the creation and maintenance of software
> related to an interactive project activity analyzer and aggregator
> 
> ## Issues:
> There are no issues requiring board attention.
> 
> ## Membership Data:
> Apache Kibble was founded 2017-10-18 (4 years ago)
> There are currently 15 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 8:7.
> 
> Community changes, past quarter:
> - No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
> - No new committers. Last addition was Kaxil Naik on 2021-02-21.
> 
> ## Project Activity:
> There has been limited activity this quarter with only a few brief
> discussions. Work on the new version has stalled with the last commit 
> done in
> March. As we do have active users a discussion was started about the
> possibility of making a release for the previous Kibble version [1] but
> nothing has been progressed on this yet.
> 
> We have also had a report about incorrect Github stats for Apache Lucene 
> since
> it has split from Apache Solr [2]. It was initially thought this could be
> linked to configuration but it looks like there may be more work needed 
> to fix
> it.
> 
> Even though we don't have a large issue list [3]- not all have been 
> responded
> to and some have been open for a while so this could be an area where we 
> could
> definitely focus on.
> 
> ## Community Health:
> The decrease in email traffic confirms the low activity. We need to engage
> more with the community and find ways to improve. Hopefully working on the
> open issues which also include improving the documentation and setup
> instructions will trigger some activity and user feedback.
> 
> [1] https://s.apache.org/q99he
> [2] https://s.apache.org/jcefe
> [3] https:/github.com/apache/kibble/issues
> 
> 

Re: Help configuring Kibble for Apache Reporter tool for Lucene?

[Sharan Foga]

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  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  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  
> > 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
> > > 
> > 
> 

Re: [GitHub] [kibble] timshen opened a new issue #13: There is no setup/requirements.txt file

[Sharan Foga]

Hi All

I didn't think we have created any installation instructions yet for the new 
Kibble and the existing instructions apply to Kibble-1.  This could that be the 
reason why this problem is being reported.

Thanks
Sharan

On 2021/10/11 03:17:11, GitBox  wrote: 
> 
> timshen opened a new issue #13:
> URL: https://github.com/apache/kibble/issues/13
> 
> 
>
>
>**Description:**
>In document 
> https://apache-kibble.readthedocs.io/en/latest/setup.html#installing-the-server,
>  a step is mentioned for installing the server. 
>"pip install -r setup/requirements.txt", but after cloning the code, I 
> couldn't file the requirements.txt file.
>
>**Reproduction steps:**
>
>1. Execute the commands:
>git clone https://github.com/apache/kibble.git /var/www/kibble
>cd /var/www/kibble
>pip install -r setup/requirements.txt
>
>
>**Actual result:**
>No setup/requirements.txt is found
>
>**OS:**
>Ubuntu 18.04.5 LTS 
>
>**Logs:**
>NA
>
>**Other:**
>NA
>
> 
> 
> -- 
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
> 
> To unsubscribe, e-mail: dev-unsubscr...@kibble.apache.org
> 
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
> 
> 
> 

Re: Help configuring Kibble for Apache Reporter tool for Lucene?

[Sharan Foga]

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  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  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
> > 
> 

Re: Help configuring Kibble for Apache Reporter tool for Lucene?

[Sharan Foga]

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  wrote: 
> Hello,
> 
> I am hoping someone here on the Kibble dev list can help us fix 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
> , 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
> 

Re: [DISCUSSION] How hard would it be to create a Kibble release?

[Sharan Foga]

Hi Tomek

Thanks for the feedback. My thought would be to make it as simple as possible. 

I'll wait a few more days to see if anyone else has any other comments to add.

Thanks
Sharan

On 2021/09/24 17:33:44, Tomasz Urbaszek  wrote: 
>  Hey Sharan,
> 
> > how hard would it be to create a release?
> 
> For Kibble-1, cutting out a release in terms of ASF should be pretty easy
> (create release tag in Github, prepare sources, verify and vote). For the
> old version we should probably also release kibble-scanners. Tricky part
> can be if we would like to add some convenience packages (for example to
> make Kibble pip installable) as this would require some additional work.
> 
> Cheers,
> Tomek
> 
> On Thu, 23 Sept 2021 at 14:18, Sharan Foga  wrote:
> 
> > Hi All
> >
> > A while ago I responded to a question from the ASF about the date of our
> > last release [1] and the answer was that Kibble has never done one. Kibble
> > was created as a TLP so bypassed Incubator where we would have had to
> > create at least one. We have interest in the project from within Apache,
> > also from CHAOSS saying that we can be apply to become a reference software
> > that implements some of their metrics (which I think will give the project
> > some great visibility!). We also have some users out there - I know
> > specifically of Project Jupyter.
> >
> > With no release information - it can be difficult for existing and new
> > users to have a stable base to explore the project from. We do have our
> > Live Demo but I have no idea whther the version that is running is changing
> > as we update the code or is several months / years old. My point here is
> > that without having a release as a benchmark we could be missing things.
> >
> > Anyway my question is as in the subject line is - how hard would it be to
> > create a release? Could we use Kibble-1 since we already have the code that
> > is currently being run for the demo?
> >
> > If that is too hard then another option could be to do some sort of basic
> > release of the new Kibble -  bearing in mind that we will have a mismatch
> > between the demo functionality and what we call our release. I am not sure
> > what is feasible so am opening this discussion up to the community to get
> > some feedback.
> >
> > So I am happy to hear people's thoughts, suggestions and creative ideas of
> > how we could look at approaching this.
> >
> > Thanks
> > Sharan
> >
> > [1]  https://s.apache.org/l6z4n
> >
> 

Re: Importing new repositories?

[Sharan Foga]

Great. Thanks Robert.

On 2021/09/23 15:45:50, Robert Munteanu  wrote: 
> On Thu, 2021-09-23 at 11:57 +0000, 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
> 
> 

[DISCUSSION] How hard would it be to create a Kibble release?

[Sharan Foga]

Hi All

A while ago I responded to a question from the ASF about the date of our last 
release [1] and the answer was that Kibble has never done one. Kibble was 
created as a TLP so bypassed Incubator where we would have had to create at 
least one. We have interest in the project from within Apache, also from CHAOSS 
saying that we can be apply to become a reference software that implements some 
of their metrics (which I think will give the project some great visibility!). 
We also have some users out there - I know specifically of Project Jupyter.

With no release information - it can be difficult for existing and new users to 
have a stable base to explore the project from. We do have our Live Demo but I 
have no idea whther the version that is running is changing as we update the 
code or is several months / years old. My point here is that without having a 
release as a benchmark we could be missing things.

Anyway my question is as in the subject line is - how hard would it be to 
create a release? Could we use Kibble-1 since we already have the code that is 
currently being run for the demo?

If that is too hard then another option could be to do some sort of basic 
release of the new Kibble -  bearing in mind that we will have a mismatch 
between the demo functionality and what we call our release. I am not sure what 
is feasible so am opening this discussion up to the community to get some 
feedback.

So I am happy to hear people's thoughts, suggestions and creative ideas of how 
we could look at approaching this.

Thanks
Sharan

[1]  https://s.apache.org/l6z4n

Re: Importing new repositories?

[Sharan Foga]

Hi Robert

That's great! And good to know you are getting more familiar with things. 

On the old vs new kibble, we did discuss no longer supporting the older version 
but as I say that is currently our users only main reference, so most 
suggestions etc will come from the experience of using what we already have.

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.

Thanks
Sharan

On 2021/09/23 11:18:03, Robert Munteanu  wrote: 
> 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
> > > > 
> > > 
> 
> 
> 

ApacheCon Presentation and Other Thoughts

[Sharan Foga]

Hi All

A quick update. I did the Community Health Reporting talk on Tuesday at 
ApacheCon and as part of that I went through a bit of a demo of Kibble. We got 
some good feedback and also some questions about the features that are not 
consistently working such as the mood analysis. Chris Dutz from PLC4X was 
really keen to what their mood analysis looked like - so I think it would be 
good to take a look at it. 

Other people were also keen to start looking at Kibble and I did highlight that 
we are looking to build the community and also keen to get ideas for how we 
could develop it further.

One key message I got from Owen O'Malley's talk was about making sure that we 
have good instructions about how to install and use the software. (I know we 
have 2 versions but it's the old one that is being used for the demo so I'd 
like to spend some time working on closing that gap).

Marton Elek did a great presentation on why Bus Factor and Pony Factor were not 
the only measure of community sustainability and contribution. He put together 
a fast prototype that looked at the 'long tail' of contributions rather than 
the top contributors. I asked if he would make it availble to us here at Kibble 
and if we could take the idea and perhaps develop or integrate as a potential 
new Kibble feature ... and he was happy for us to do that. Once I get a link to 
the repo annd presentation I will post it. Also remember that all ApacheCon 
presentations will be published on the ASF Youtube Channel.

Another thing that Marton highlighted was around the community activity times.. 
and we have something similar already in Kibble on the code repository 
statistics screen. We show a time of day when project activity happens. Marton 
used it like a quiz, he showed the activity chart and we had to guess the 
project it came from.. that was enlightening as well as fun!

There are a few Superset talks that I was hoping to catch and I think there is 
another one today so hopefully will get to see that.

As always I am happy to receive any other feedback or comments on everything I 
have mentioned here.

Thanks
Sharan

Re: Importing new repositories?

[Sharan Foga]

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
> > 
> 

Re: Importing new repositories?

[Sharan Foga]

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 +0000, 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
> 

Re: Where is Kibble issue tracker?

[Sharan Foga]

Done and I hope I haven't broken anything! :-)

On 2021/09/23 07:47:39, Sharan Foga  wrote: 
> Brilliant! Thanks Sebb I will take a look and have a go at it now.
> 
> On 2021/09/22 08:59:17, sebb  wrote: 
> > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
> > 
> > On Wed, 22 Sept 2021 at 09:21, Sharan Foga  wrote:
> > >
> > > Hi Sebb
> > >
> > > I'm not ignoring you - I am just not sure how to get is setup so once I 
> > > find out I will do.
> > >
> > > Thanks
> > > Sharan
> > >
> > > On 2021/09/10 22:19:52, sebb  wrote:
> > > > On Fri, 10 Sept 2021 at 20:12, Sharan Foga  wrote:
> > > > >
> > > > > Hi Sebb
> > > > >
> > > > > Thanks. Yes there are a few things that we need to look at and fix 
> > > > > and we are trying to kickstart some community activity. We are using 
> > > > > Issues on Github as our issue tracker.  Here is the current link
> > > > >
> > > > > https://github.com/apache/kibble/issues
> > > > >
> > > > > We do have an kibble-website repo but I cant see any issues on there 
> > > > > yet ;-)
> > > >
> > > > AFAICT that's because it has not been set up with an issue tracker.
> > > >
> > > > If that is intentional, then it would help to point to the main issue
> > > > tracker in the README.
> > > >
> > > > If not, then please set it up.
> > > >
> > > > > https://github.com/apache/kibble-website
> > > > >
> > > > > We do also have some issues sitting in the previous repos that we 
> > > > > probably need to move or at least make visible.
> > > > >
> > > > > https://github.com/apache/kibble-1/issues
> > > > > https://github.com/apache/kibble-scanners/issues
> > > > >
> > > > > Thanks
> > > > > Sharan
> > > > >
> > > > > On 2021/09/10 12:03:45, sebb  wrote:
> > > > > > There are some problems on the website that need fixing.
> > > > > >
> > > > > > One such is:
> > > > > > - I could not find any links to an issue tracker for Kibble on the 
> > > > > > website.
> > > > > >
> > > > > > Sebb
> > > > > >
> > > >
> > 
> 

Re: Where is Kibble issue tracker?

[Sharan Foga]

Brilliant! Thanks Sebb I will take a look and have a go at it now.

On 2021/09/22 08:59:17, sebb  wrote: 
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
> 
> On Wed, 22 Sept 2021 at 09:21, Sharan Foga  wrote:
> >
> > Hi Sebb
> >
> > I'm not ignoring you - I am just not sure how to get is setup so once I 
> > find out I will do.
> >
> > Thanks
> > Sharan
> >
> > On 2021/09/10 22:19:52, sebb  wrote:
> > > On Fri, 10 Sept 2021 at 20:12, Sharan Foga  wrote:
> > > >
> > > > Hi Sebb
> > > >
> > > > Thanks. Yes there are a few things that we need to look at and fix and 
> > > > we are trying to kickstart some community activity. We are using Issues 
> > > > on Github as our issue tracker.  Here is the current link
> > > >
> > > > https://github.com/apache/kibble/issues
> > > >
> > > > We do have an kibble-website repo but I cant see any issues on there 
> > > > yet ;-)
> > >
> > > AFAICT that's because it has not been set up with an issue tracker.
> > >
> > > If that is intentional, then it would help to point to the main issue
> > > tracker in the README.
> > >
> > > If not, then please set it up.
> > >
> > > > https://github.com/apache/kibble-website
> > > >
> > > > We do also have some issues sitting in the previous repos that we 
> > > > probably need to move or at least make visible.
> > > >
> > > > https://github.com/apache/kibble-1/issues
> > > > https://github.com/apache/kibble-scanners/issues
> > > >
> > > > Thanks
> > > > Sharan
> > > >
> > > > On 2021/09/10 12:03:45, sebb  wrote:
> > > > > There are some problems on the website that need fixing.
> > > > >
> > > > > One such is:
> > > > > - I could not find any links to an issue tracker for Kibble on the 
> > > > > website.
> > > > >
> > > > > Sebb
> > > > >
> > >
> 

Re: Importing new repositories?

[Sharan Foga]

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

On 2021/09/21 21:06:28, Robert Munteanu  wrote: 
> 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: Where is Kibble issue tracker?

[Sharan Foga]

Hi Sebb

I'm not ignoring you - I am just not sure how to get is setup so once I find 
out I will do.

Thanks
Sharan

On 2021/09/10 22:19:52, sebb  wrote: 
> On Fri, 10 Sept 2021 at 20:12, Sharan Foga  wrote:
> >
> > Hi Sebb
> >
> > Thanks. Yes there are a few things that we need to look at and fix and we 
> > are trying to kickstart some community activity. We are using Issues on 
> > Github as our issue tracker.  Here is the current link
> >
> > https://github.com/apache/kibble/issues
> >
> > We do have an kibble-website repo but I cant see any issues on there yet ;-)
> 
> AFAICT that's because it has not been set up with an issue tracker.
> 
> If that is intentional, then it would help to point to the main issue
> tracker in the README.
> 
> If not, then please set it up.
> 
> > https://github.com/apache/kibble-website
> >
> > We do also have some issues sitting in the previous repos that we probably 
> > need to move or at least make visible.
> >
> > https://github.com/apache/kibble-1/issues
> > https://github.com/apache/kibble-scanners/issues
> >
> > Thanks
> > Sharan
> >
> > On 2021/09/10 12:03:45, sebb  wrote:
> > > There are some problems on the website that need fixing.
> > >
> > > One such is:
> > > - I could not find any links to an issue tracker for Kibble on the 
> > > website.
> > >
> > > Sebb
> > >
> 

Re: Where is Kibble issue tracker?

[Sharan Foga]

Hi Sebb

Thanks. Yes there are a few things that we need to look at and fix and we are 
trying to kickstart some community activity. We are using Issues on Github as 
our issue tracker.  Here is the current link

https://github.com/apache/kibble/issues 

We do have an kibble-website repo but I cant see any issues on there yet ;-)

https://github.com/apache/kibble-website

We do also have some issues sitting in the previous repos that we probably need 
to move or at least make visible.

https://github.com/apache/kibble-1/issues
https://github.com/apache/kibble-scanners/issues

Thanks
Sharan

On 2021/09/10 12:03:45, sebb  wrote: 
> There are some problems on the website that need fixing.
> 
> One such is:
> - I could not find any links to an issue tracker for Kibble on the website.
> 
> Sebb
> 

Re: It's Board Report Time!

[Sharan Foga]

Hi All

I will post this draft as our board report today.

Thanks
Sharan

On 2021/08/07 13:44:59, Sharan Foga  wrote: 
> Hi All
> 
> Please see below for my draft for our board report. Please let me have any 
> feedback or suggested updates / changes (especially if there is anything 
> important that I may have missed :-)
> 
> Thanks
> Sharan
> 
> -
> 
> ## Description:
> The mission of Apache Kibble is the creation and maintenance of software 
> related to an interactive project activity analyzer and aggregator
> 
> ## Issues:
> There are no issues requiring board attention at this time.
> 
> ## Membership Data:
> Apache Kibble was founded 2017-10-18 (4 years ago)
> There are currently 15 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 8:7.
> 
> Community changes, past quarter:
> - No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
> - No new committers. Last addition was Kaxil Naik on 2021-02-21.
> 
> ## Project Activity:
> In response to the board feedback on our previous report - the project has not
> yet made a release [1]
> 
> Since the last report some work was started on the next version of Kibble but
> that has now slowed possibly due to the holiday season.
> 
> Community Metrics is a key theme in the ApacheCon@Home Community track and
> there will be a Kibble related talk that will give users and projects a basic
> overview of how to use Kibble and which metrics could be useful.
> 
> We have had bug report regarding incorrect installation instructions so will
> work to be working to correct this.
> 
> ## Community Health:
> Activity has been slow with very little discussions happening. The large
> decrease in mailing list traffic confirms this. We are trying to work on ways
> to build interest in the project and grow the community.
> 
> A new community member has recently joined [2] and is interested in helping
> with community engagement and growth.
> 
> [1] https://s.apache.org/oudkp
> [2] https://s.apache.org/hgi0v
> 
> On 2021/08/04 18:51:23, Sharan Foga  wrote: 
> > Hi All
> > 
> > Our quarterly board report is due this month so I will work on putting 
> > something together and and then post it here for any community feedback.
> > 
> > Thanks
> > Sharan
> > 
> 

Re: It's Board Report Time!

[Sharan Foga]

Hi All

Please see below for my draft for our board report. Please let me have any 
feedback or suggested updates / changes (especially if there is anything 
important that I may have missed :-)

Thanks
Sharan

-

## Description:
The mission of Apache Kibble is the creation and maintenance of software 
related to an interactive project activity analyzer and aggregator

## Issues:
There are no issues requiring board attention at this time.

## Membership Data:
Apache Kibble was founded 2017-10-18 (4 years ago)
There are currently 15 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.

Community changes, past quarter:
- No new PMC members. Last addition was Michał Słowikowski on 2021-05-03.
- No new committers. Last addition was Kaxil Naik on 2021-02-21.

## Project Activity:
In response to the board feedback on our previous report - the project has not
yet made a release [1]

Since the last report some work was started on the next version of Kibble but
that has now slowed possibly due to the holiday season.

Community Metrics is a key theme in the ApacheCon@Home Community track and
there will be a Kibble related talk that will give users and projects a basic
overview of how to use Kibble and which metrics could be useful.

We have had bug report regarding incorrect installation instructions so will
work to be working to correct this.

## Community Health:
Activity has been slow with very little discussions happening. The large
decrease in mailing list traffic confirms this. We are trying to work on ways
to build interest in the project and grow the community.

A new community member has recently joined [2] and is interested in helping
with community engagement and growth.

[1] https://s.apache.org/oudkp
[2] https://s.apache.org/hgi0v

On 2021/08/04 18:51:23, Sharan Foga  wrote: 
> Hi All
> 
> Our quarterly board report is due this month so I will work on putting 
> something together and and then post it here for any community feedback.
> 
> Thanks
> Sharan
> 

It's Board Report Time!

[Sharan Foga]

Hi All

Our quarterly board report is due this month so I will work on putting 
something together and and then post it here for any community feedback.

Thanks
Sharan

Incorrect Installation Instructions

[Sharan Foga]

Hi All

I just saw the Github comment about a user trying to install Kibble-1 and 
Kibble and the installation instructions were not working. I think it is 
important that we look at correcting this as this so that people can use the 
software - even if everything isnt working.

The earliest I can take a look at it is the weekend so if anyone can take a 
look before then please let me know.

Thanks
Sharan

[DISCUSSION] How can we Grow our Community?

[Sharan Foga]

Hi All

We have a small community and our mailing list has been fairly quiet over the 
summer. We need to discuss how we can get more people involved. How can we 
promote and grow our community? Let's use this discussion thread to come up 
with some ideas and strategies that we can work on together. 

We may also get some interest from people as a result of the ApacheCon Asia 
talks as I mentioned Kibble and I included  a demo of Kibble-1 as part of the 
presentation.

Thanks
Sharan

Re: Kibble Related Talks at ApacheCon

[Sharan Foga]

Hi Dianjin

Thanks very much for your email and welcome to the Kibble community :-)

We are definitely happy to have whatever contribution you can give and it's 
great to hear that you have the skills we need to help us with community 
building.

I will start a separate thread and where we can discuss in more details, some 
strategies we can use.

Thanks
Sharan

On 2021/07/22 03:00:48, Dianjin Wang  wrote: 
> Hi Sharan,
> 
> Thanks for letting us know. Looking forward to your great talk. Now I work
> as one community manager at StreamNative, I am good at community building
> and marketing, so I would like to contribute to Kibble if possible.
> 
> Best,
> Dianjin Wang
> 
> 
> On Thu, Jul 22, 2021 at 2:49 AM Sharan Foga  wrote:
> 
> > Hi All
> >
> > A quick note to let you know that my talk Community Health Reporting 101
> > has been accepted for both ApacheCon Asia and ApacheCon@Home. The main
> > focus will be showing some of the views and statistics people can use from
> > the Kibble-1 demo.
> >
> > I will also see if I can get some potential new contributors interested as
> > I know we need to work on community building.
> >
> > Thanks
> > Sharan
> >
> 

Community Health and Metrics Theme on ApacheCon Community Track

[Sharan Foga]

Hi All

One of the themes in the Community Track at ApacheCon@Home in September is 
around community health and metrics. If you take a look at the schedule 

https://www.apachecon.com/acah2021/tracks/community.html

You will find a few talks that are really interesting to what our community 
does and is looking to do. There is a talk about an alternative metric for bus 
factor (I know we have been using Pony Factor instead but it would be good to 
hear what a potential new suggestion could be!)

There is a talk from Apache Superset about how to quantify the growth and 
evolution of an open source community. (Doesn't that sound a little familiar?) 
And there is another Superset talk about using dashboard. So some more really 
good talks to see and perhaps a chance to link up with the Superset community 
and see how we might be able to work together!

We also have a talk based on the exploration of social and technical work 
happening in the Apache Incubator community - so once again something that 
could be interesting and relevant to what we want Kibble to achieve.

So please take a look at the Community track schedule and see if you can catch 
these talks.

Thanks
Sharan

Kibble Related Talks at ApacheCon

[Sharan Foga]

Hi All

A quick note to let you know that my talk Community Health Reporting 101 has 
been accepted for both ApacheCon Asia and ApacheCon@Home. The main focus will 
be showing some of the views and statistics people can use from the Kibble-1 
demo.

I will also see if I can get some potential new contributors interested as I 
know we need to work on community building.

Thanks
Sharan

Setting Up Github Project Board for Kibble Foundations work

[Sharan Foga]

Hi All

So as Tomek mentioned in his post [1] - we can track our potential release 
versions using the milestones functionality. We can use the project board 
functionality to help us manage and group the different pieces of work.

Tomek mentioned 4 areas [2] that we could use as a high level grouping to 
organise the work. These were Foundations, Additional Critical Data Sources, 
API and UI, each of which build on each other. So let's start with setting up a 
board for the first one - the Apache Kibble Foundations work: 

Suggested objectives so far are:

1, Setup up scanner for a limited set of datasources (E.g If we fix this at 2 
then we could have Github and Jira)
2. Make data accessible via a Database (From our call I think we are starting 
with Elasticsearch - is this still valid?)
3. Setup some basic metrics (We need to decide how basic this is - maybe it's 
simply number of records or aggregations or we can take a look at Kibble-1 and 
select something simple but useful)
4. Linking Apache Superset as a dashboard (We need to do some investigation of 
how to integrate this and also connect with the Superset community to see if 
they will be willing to help us in this effort)

We need to break these down into more detailed tasks and the plan is that we 
can see more easily what the key areas we need to focus on. If we find things 
are not working the we can adjust and evolve as needed.

Happy to get any suggestions for any of the points mentioned above as well as 
other comments or feedback.

Thanks
Sharan

[1]  https://s.apache.org/a9b6r
[2]  https://s.apache.org/02xud

Re: Have we ever made a Kibble release?

[Sharan Foga]

Excellent! :-)

On 2021/05/23 14:29:43, Kaxil Naik  wrote: 
> Yup, this is what we do at Apache Airflow too.
> 
> And I did the same for the recently released Apache Airflow Helm Chart.
> 
> Example:
> https://lists.apache.org/x/thread.html/rd2a0a6386c22bb0942c28746d59d105adc0364715c15ea772e23e105@%3Cdev.airflow.apache.org%3E
> 
> I have releasing Airflow versions from past 3 or so years, so have good
> experience with ASF guidelines around it.
> 
> Regards,
> Kaxil
> 
> 
> 
> On Sun, May 23, 2021, 15:24 Sharan Foga  wrote:
> 
> >
> >
> > On 2021/05/23 14:15:32, Kaxil Naik  wrote:
> > > Yeah, as far as I know we don't have a release. For Kibble 2 we can
> > release
> > > Python wheel/binary artifacts.
> >
> > I know there is some discussion going on about binary artifacts and Apache
> > releases as generally Apache releases need to be source code, though they
> > have been supplemented with binary artifacts. We just need to make sure we
> > adhere to the current policy.
> >
> > Thanks
> > Sharan
> >
> > >
> > > Regards,
> > > Kaxil
> > >
> > > On Sun, May 23, 2021, 15:10 Tomasz Urbaszek 
> > wrote:
> > >
> > > > As far as I know Apache Kibble was never released. I would propose
> > > > using Github milestones to track future releases of new Kibble:
> > > > https://github.com/apache/kibble/milestone/1
> > > >
> > > > Tomek
> > > >
> > > > On Sun, 23 May 2021 at 16:00, Sharan Foga  wrote:
> > > > >
> > > > > Hi All
> > > > >
> > > > > Thanks to all who helped review our Board report. We got some
> > feedback
> > > > comment to include details of our last release in our next report. I've
> > > > been searching through our mailing archives and can't find any details
> > or
> > > > Vote of the project ever doing a release.
> > > > >
> > > > > If this is the case then we need to think about planning one as part
> > of
> > > > our roadmap.
> > > > >
> > > > > Thanks
> > > > > Sharan
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> 

Re: Have we ever made a Kibble release?

[Sharan Foga]

On 2021/05/23 14:15:32, Kaxil Naik  wrote: 
> Yeah, as far as I know we don't have a release. For Kibble 2 we can release
> Python wheel/binary artifacts.

I know there is some discussion going on about binary artifacts and Apache 
releases as generally Apache releases need to be source code, though they have 
been supplemented with binary artifacts. We just need to make sure we adhere to 
the current policy.

Thanks
Sharan

> 
> Regards,
> Kaxil
> 
> On Sun, May 23, 2021, 15:10 Tomasz Urbaszek  wrote:
> 
> > As far as I know Apache Kibble was never released. I would propose
> > using Github milestones to track future releases of new Kibble:
> > https://github.com/apache/kibble/milestone/1
> >
> > Tomek
> >
> > On Sun, 23 May 2021 at 16:00, Sharan Foga  wrote:
> > >
> > > Hi All
> > >
> > > Thanks to all who helped review our Board report. We got some feedback
> > comment to include details of our last release in our next report. I've
> > been searching through our mailing archives and can't find any details or
> > Vote of the project ever doing a release.
> > >
> > > If this is the case then we need to think about planning one as part of
> > our roadmap.
> > >
> > > Thanks
> > > Sharan
> > >
> > >
> > >
> > >
> >
> 

Re: Have we ever made a Kibble release?

[Sharan Foga]

On 2021/05/23 14:09:47, Tomasz Urbaszek  wrote: 
> As far as I know Apache Kibble was never released. I would propose
> using Github milestones to track future releases of new Kibble:
> https://github.com/apache/kibble/milestone/1

+1 

> 
> Tomek
> 
> On Sun, 23 May 2021 at 16:00, Sharan Foga  wrote:
> >
> > Hi All
> >
> > Thanks to all who helped review our Board report. We got some feedback 
> > comment to include details of our last release in our next report. I've 
> > been searching through our mailing archives and can't find any details or 
> > Vote of the project ever doing a release.
> >
> > If this is the case then we need to think about planning one as part of our 
> > roadmap.
> >
> > Thanks
> > Sharan
> >
> >
> >
> >
> 

Have we ever made a Kibble release?

[Sharan Foga]

Hi All

Thanks to all who helped review our Board report. We got some feedback comment 
to include details of our last release in our next report. I've been searching 
through our mailing archives and can't find any details or Vote of the project 
ever doing a release.

If this is the case then we need to think about planning one as part of our 
roadmap.

Thanks
Sharan

Re: [DISCUSSION] Kibble Roadmap

[Sharan Foga]

Hi Tomek

Thanks for the feedback. I've included some comments inline.

On 2021/05/12 08:37:56, Tomasz Urbaszek  wrote: 
> > 1) How far do we support Kibble-1 while the new Kibble is being developed?
> 
> To be honest I think we as a project don't have enough capacity to
> both maintain old Kibble and build new. The old code is hard to read,
> not to mention to change. I tried it a few times.

Good point. 

What I am trying to uncover here is about setting a common understanding and 
expectation about what we will and wont do.

We need to send a consistent message to people that either uncover problems or 
bugs to Kibble-1 while the new Kibble is under construction.

Do we allow people to report their issue and then use that list as a cross 
check to make sure that the issue is eitherno longer relevant or has been fixed 
in the new Kibble?

> 
> > 2) What can we do we ensure that the Kibble dependency in 
> > reporter.apache.org tool continues to be supported?
> 
> I think once we have a new working Kibble (together with tests
> ensuring data quality) we should integrate it into reporter tool - how
> I don't know yet. Until that time we reporter should be ok with old
> Kibble.

This sounds reasonable. The reporter tool is working well as it is and we are 
only getting comments around clarifications on how the metrics are calculated.

> 
> > 3) How do we plan for the development of the new Kibble?
> 
> Not sure but I would say we should just do it. Once we have some base
> on which multiple people can work then we can split the work and so
> on. There was no decision if we want to use REST or Graph QL so the
> API part is still undefined (thuse I put it out after 1 milestone in
> my proposal). But we seemed to be aligned to use Elasticsearch for
> database, so the first step is definitely to define some basic classes
> and interfaces around it.

Just doing it has always been the way :-). I don't the big picture yet and was 
thinking of putting together something high level that is easy to follow so the 
information is open and clear for anyone who wants to contribute. Maybe it is 
as simple as creating the Github Kanban board and a Wiki page link... 

> 
> > 4) What can we do to grow Kibble usage and the community?
> 
> Apart from active community we need well-structured project with
> enough documentation and developer tools to make onboarding smooth and
> easy.
> 

Another good point and I'd be happy to spend some on the documentation.

Thanks
Sharan

> Thanks,
> Tomek
> 
> On Mon, 10 May 2021 at 21:32, Sharan Foga  wrote:
> >
> > Hi Tomek
> >
> > I think this is a great start. I was thinking about Kibble from a few other 
> > perspectives too especially around questions or problems that we might want 
> > to solve.
> >
> > 1) How far do we support Kibble-1 while the new Kibble is being developed?
> > 2) What can we do we ensure that the Kibble dependency in 
> > reporter.apache.org tool continues to be supported?
> > 3) How do we plan for the development of the new Kibble? (And I think you 
> > have some good responses for this in your message)
> > 4) What can we do to grow Kibble usage and the community? (One of the 
> > things I'd like to include here is CHAOSS and getting Kibble setup as an 
> > implementation of some their metrics...)
> >
> > My understanding is that first three each have different repos so perhaps 
> > we could think about managing the roadmap at that level..
> >
> > I will have a bit more time later this week - so let me see if I can refine 
> > or iterate on this a bit more.
> >
> > Thanks
> > Sharan
> >
> >
> > On 2021/05/02 16:33:04, Tomasz Urbaszek  wrote:
> > > +1 for using Github issues and projects for managing/tracking - it
> > > works pretty well in Apache Airflow.
> > >
> > > Also I'm definitely in favour of defining a roadmap. I think top level
> > > points on such a roadmap should correspond to some big milestones we
> > > would like to achieve as a community but they also should be small
> > > enough to make executing possible. If I may suggest some starting
> > > point I would say:
> > > bit more
> > > 1. Apache Kibble foundations - we have scanners for few data sources
> > > and some basic metrics. Data is accessible via underlying database +
> > > Apache Superset as dashboard
> > > 2. Crucial data sources - more scanners, covering all required data
> > > sources (ASF crucial ones). At this point we should have quite good
> > > documentation and understanding of the data we are collecting allowing
> > > us for better decision making for next 

Re: Apache Kibble 2.0

[Sharan Foga]

Hi Tomek

Thanks for working on this.

I like the idea.  From the first time we had the demo running and showed the 
list of possible sources - someone immediately asked about adding one that we 
didn't have, so I think making adding them in a simple yet flexible way will be 
a good thing!

Thanks
Sharan

On 2021/05/22 13:50:55, Tomasz Urbaszek  wrote: 
> Finally I started working on new Kibble:
> https://github.com/apache/kibble/pull/8
> 
> I would like to propose introducing the following new concepts in new Apache 
> Kibble:
> 
> 1. DataSource - Github, Gitlab, Jira etc. - each data source would be a 
> python package that would include logic for getting data from the external 
> source as well as some metric and authentication mechanisms. 
> 
> 2. DataType - in case of Github: issues, PRs, commits etc - each DataSource 
> can define its own data types. Single data type should define methods for 
> getting relevant data and way to persist them in Kibble - this would replace 
> the concept of scanners.
> 
> Why? In this way Apache Kibble main aim and value would be building a 
> framework for collecting projects information and serving them in useful, 
> aggregated way. Having such a framework would make adding new data sources as 
> simple as plug and play, thus allowing easy extension and possibility to 
> build custom data source.
> 
> Let me know what do you think. I will definitely try to play with this idea 
> in my PR.
> 
> Thanks,
> Tomek
> 
> 
> 
> On 2021/03/22 19:49:28, Fourat ZOUARI  wrote: 
> > Hey Sharan,
> > 
> > I've already commented on some parts of the doc and to date, it seems
> > fine/sufficient for kicking off the project, more reflections may come over
> > through the process.
> > 
> > I suggest we have a kanban board on gh containing all pending tasks as a
> > projection for the project.
> > 
> > Fourat
> > 
> > 
> > On Mon, Mar 22, 2021 at 7:10 PM Sharan Foga  wrote:
> > 
> > > Hi All
> > >
> > > Does anyone have any feedback on the work Tomek has done around this so
> > > far? Are people happy with the suggestions or do you have anything else in
> > > mind?
> > >
> > > Thanks
> > > Sharan
> > >
> > > On 2021/03/06 14:39:43, Tomasz Urbaszek  wrote:
> > > > Hey all,
> > > >
> > > > I'm wondering if anyone had time to review those documents?
> > > >
> > > > Maybe we should start developing new Kibble and do the decision making
> > > > as we go to avoid overhead of excessive planning?
> > > >
> > > > Cheers,
> > > > Tomek
> > > >
> > > >
> > > > On Sat, 27 Feb 2021 at 18:43, Tomasz Urbaszek 
> > > wrote:
> > > > >
> > > > > After thinking a bit I think we may consider using Graph QL instead of
> > > REST... I know that Daniel mentioned that we may consider using GQL and 
> > > now
> > > (after doing some brainstorming) I think I start understand why. The only
> > > thing I'm afraid is that GQL has a steep learning curve and it may make it
> > > harder to grow the community and develop the app. But I'm not sure if this
> > > should block us from using GQL.
> > > > >
> > > > > T.
> > > > >
> > > > > On Sat, 27 Feb 2021 at 17:07, Tomasz Urbaszek 
> > > wrote:
> > > > >>
> > > > >> Hi all,
> > > > >>
> > > > >> I prepared a draft of Open API specification that we may use to build
> > > new Kibble API:
> > > > >> https://app.swaggerhub.com/apis/turbaszek/kibble/1.0.0
> > > > >>
> > > > >> My idea was that inside single kibble deployment, there can be many
> > > organizations and each organization has its own users and configured
> > > scanners.
> > > > >>
> > > > >> So this proposal basically has 3 CRUD endpoints for organizations,
> > > users and scanners. And additionally there's the crucial
> > > /organization/{organization_id}/scanners/{scanner_id}/data endpoint which
> > > returns data collected by a given scanner for a given organization.
> > > > >>
> > > > >> The data returned by this endpoint is an object containing an array
> > > of data points (the real data) and additional information about the
> > > structure of a single data point. This makes the response little ambiguous
> > > but it gives us a big elasticity - each scanner can return data 

Re: [DISCUSSION] Kibble Roadmap

[Sharan Foga]

Hi Tomek

I think this is a great start. I was thinking about Kibble from a few other 
perspectives too especially around questions or problems that we might want to 
solve.

1) How far do we support Kibble-1 while the new Kibble is being developed? 
2) What can we do we ensure that the Kibble dependency in reporter.apache.org 
tool continues to be supported?
3) How do we plan for the development of the new Kibble? (And I think you have 
some good responses for this in your message)
4) What can we do to grow Kibble usage and the community? (One of the things 
I'd like to include here is CHAOSS and getting Kibble setup as an 
implementation of some their metrics...)

My understanding is that first three each have different repos so perhaps we 
could think about managing the roadmap at that level..

I will have a bit more time later this week - so let me see if I can refine or 
iterate on this a bit more.

Thanks
Sharan


On 2021/05/02 16:33:04, Tomasz Urbaszek  wrote: 
> +1 for using Github issues and projects for managing/tracking - it
> works pretty well in Apache Airflow.
> 
> Also I'm definitely in favour of defining a roadmap. I think top level
> points on such a roadmap should correspond to some big milestones we
> would like to achieve as a community but they also should be small
> enough to make executing possible. If I may suggest some starting
> point I would say:
> bit more
> 1. Apache Kibble foundations - we have scanners for few data sources
> and some basic metrics. Data is accessible via underlying database +
> Apache Superset as dashboard
> 2. Crucial data sources - more scanners, covering all required data
> sources (ASF crucial ones). At this point we should have quite good
> documentation and understanding of the data we are collecting allowing
> us for better decision making for next steps.
> 3. Kibble API - we have an extensible API that allows users access the
> data collected by our scanners. The API can be used for data sources
> management (for example for configuring credentials).
> 4. Kibble UI - there's an web app that can be used for accessing the data.
> 
> What do you think?
> 
> Cheers,
> Tomek
> 
> On Sat, 10 Apr 2021 at 18:48, Sharan Foga  wrote:
> >
> > Hi All
> >
> > In one of the previous threads [1]  the suggestion was made to look at 
> > setting up a kanban board on Github to track the pending tasks. Are people 
> > happy to get one of these setup?
> >
> > In addition, I'm thinking whether it might be good to create a high level 
> > roadmap and make it visible so it is clear and we can all see where we want 
> > to achieve. It could also help explaining to newcomers about what is 
> > happening with Kibble and what our next milestone will be.
> >
> > What do people think?
> >
> > Thanks
> > Sharan
> >
> > [1] https://s.apache.org/xzk6s
> 

Re: It's Board Report Time!

[Sharan Foga]

Thanks for the feedback. I will submit it!

On 2021/05/10 11:29:30, Kaxil Naik  wrote: 
> Looks good to me too, thanks Sharan
> 
> On Fri, May 7, 2021 at 10:00 PM Tomasz Urbaszek 
> wrote:
> 
> > Thanks Sharan for putting this together! Looks good to me
> >
> > Thanks,
> > Tomek
> >
> > On Fri, 7 May 2021 at 19:38, Sharan Foga  wrote:
> > >
> > > Hi All
> > >
> > > Here is my initial draft for the report and all feedback welcome!
> > >
> > > Please let me know if you think there is something important that I've
> > missed.
> > >
> > > Thanks
> > > Sharan
> > >
> > > -
> > >
> > > ## Description:
> > > The mission of Apache Kibble is the creation and maintenance of software
> > > related to an interactive project activity analyzer and aggregator
> > >
> > > ## Issues:
> > > There are no issues requiring board attention at this time.
> > >
> > > ## Membership Data:
> > > Apache Kibble was founded 2017-10-18 (4 years ago)
> > > There are currently 15 committers and 13 PMC members in this project.
> > > The Committer-to-PMC ratio is roughly 8:7.
> > >
> > > Community changes, past quarter:
> > > - Michał Słowikowski was added to the PMC on 2021-05-03
> > > - Tomasz Urbaszek was added to the PMC on 2021-05-03
> > > - Kaxil Naik was added as committer on 2021-02-21
> > >
> > > ## Project Activity:
> > > Since the last report we have welcomed a new committer, a new PMC Chair
> > and
> > > two new PMC members.
> > >
> > > A new git Kibble repo has been created for the code rewrite and the
> > existing
> > > repo has been renamed Kibble-1. Current users are being re-directed to
> > > Kibble-1 as this is the code source for the Kibble demo.
> > >
> > > Progress has been slow but we hope to kick off activity again by working
> > on a
> > > roadmap that will help focus the work. We have had some discussions on
> > some
> > > potential features of vendor neutrality [3] that could be interesting.
> > Also
> > > confirmed was the importance of Kibble as crucial part of the ASF
> > > reporter.apache.org tool [4]
> > >
> > > We have received a potential bug report [1] which we are looking into. A
> > > Kibble talk [2] has also been submitted for ApacheCon@Home as a basic
> > > introduction for projects looking for information about their community.
> > >
> > > ## Community Health:
> > > While development activity has been slow, discussions have been more
> > active
> > > this quarter as we were waiting on the new repo to be created. Now that
> > it is
> > > - we need to focus on having a clear roadmap that can be communicated
> > within
> > > the community.
> > >
> > > It's good to see that our mailing list activity has increased this
> > quarter
> > > mainly due to the discussions around planning the re-write.
> > >
> > > [1] https://s.apache.org/vgnbe
> > > [2] https://s.apache.org/rbx97
> > > [3] https://s.apache.org/a5iux
> > > [4] https://s.apache.org/9tr8h
> > >
> > > On 2021/05/07 16:44:11, Sharan Foga  wrote:
> > > > Hi All
> > > >
> > > > Our quarterly board report is due this month so I will work on putting
> > something together and and then post it here for any community feedback.
> > > >
> > > > Thanks
> > > > Sharan
> > > >
> >
> 

Re: It's Board Report Time!

[Sharan Foga]

Hi All

Here is my initial draft for the report and all feedback welcome!

Please let me know if you think there is something important that I've missed.

Thanks
Sharan 

-

## Description:
The mission of Apache Kibble is the creation and maintenance of software 
related to an interactive project activity analyzer and aggregator

## Issues:
There are no issues requiring board attention at this time.

## Membership Data:
Apache Kibble was founded 2017-10-18 (4 years ago)
There are currently 15 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.

Community changes, past quarter:
- Michał Słowikowski was added to the PMC on 2021-05-03
- Tomasz Urbaszek was added to the PMC on 2021-05-03
- Kaxil Naik was added as committer on 2021-02-21

## Project Activity:
Since the last report we have welcomed a new committer, a new PMC Chair and
two new PMC members.

A new git Kibble repo has been created for the code rewrite and the existing
repo has been renamed Kibble-1. Current users are being re-directed to
Kibble-1 as this is the code source for the Kibble demo.

Progress has been slow but we hope to kick off activity again by working on a
roadmap that will help focus the work. We have had some discussions on some
potential features of vendor neutrality [3] that could be interesting. Also
confirmed was the importance of Kibble as crucial part of the ASF
reporter.apache.org tool [4]

We have received a potential bug report [1] which we are looking into. A
Kibble talk [2] has also been submitted for ApacheCon@Home as a basic
introduction for projects looking for information about their community.

## Community Health:
While development activity has been slow, discussions have been more active
this quarter as we were waiting on the new repo to be created. Now that it is
- we need to focus on having a clear roadmap that can be communicated within
the community.

It's good to see that our mailing list activity has increased this quarter
mainly due to the discussions around planning the re-write.

[1] https://s.apache.org/vgnbe
[2] https://s.apache.org/rbx97
[3] https://s.apache.org/a5iux
[4] https://s.apache.org/9tr8h

On 2021/05/07 16:44:11, Sharan Foga  wrote: 
> Hi All
> 
> Our quarterly board report is due this month so I will work on putting 
> something together and and then post it here for any community feedback.
> 
> Thanks
> Sharan
> 

It's Board Report Time!

[Sharan Foga]

Hi All

Our quarterly board report is due this month so I will work on putting 
something together and and then post it here for any community feedback.

Thanks
Sharan

[ANNOUNCE] Please welcome Michal Slowikowski as a new PMC Member

[Sharan Foga]

Hi Everyone

I'd like to announce that the PMC has invited Michal to become a member of the 
PMC and once again I am happy to confirm that he has accepted.

Michal has a positive attitude and has been active and collaborative, which are 
key strengths in helping our project grow and evolve. 

Please join me in welcoming Michal and congratulating him on his new role.

Thanks
Sharan

[ANNOUNCE] Please welcome Tomasz Urbaszek as a new PMC Member

[Sharan Foga]

Hi Everyone

I'd like to announce that the PMC has invited Tomek to become a member of the 
PMC and I am happy to confirm that he has accepted.

We are keen to grow the project and Tomek has shown his enthusiasm and 
motivation to help us move the project forward.

Please join me in congratulating Tomek on his new role.

Thanks
Sharan

Re: Kibble Talk for ApacheCon?

[Sharan Foga]

Hi All

Here is what I submitted.. and feedback is always welcome :-)

Thanks
Sharan

---

Community Health Reporting 101

Do you know if your community is growing or shrinking? Is your project centred 
around a core of 2 or 3 main contributors? 

Community health isn't only about ensuring releases are made or that code is 
being committed regularly. The health of an open source community is similar to 
our own personal health - there are symptoms that indicate when we are not well.

In this presentation, I will talk about some of the simple and basic insights 
projects can gain by taking a look at their Apache Kibble statistics that are 
freely available and accessible to every ASF project.

Come along and learn about how to find simple indicators that can tell you if 
your project is looking healthy and sustainable.

--


On 2021/05/01 14:58:22, Sharan Foga  wrote: 
> Hi All
> 
> I will submit something before the CFP closes on Monday. If anyone is 
> interested in co-presenting then please let me know. 
> 
> The topic will be 'Community Health Reporting' as suggested by Daniel!
> 
> Thanks
> Sharan
> 
> On 2021/04/23 15:56:15, Sharan Foga  wrote: 
> > Good point.  'Community Health Reporting' has a very nice ring to it. And 
> > in essence that is what we are doing here...
> > 
> > 
> > On 2021/04/23 15:41:22, Daniel Gruno  wrote: 
> > > On 23/04/2021 17.37, Sharan Foga wrote:
> > > > Hi All
> > > > 
> > > > I think it could good to submit a Kibble talk for ApacheCon. It would 
> > > > be based on Kibble-1 as that is where we have all the Apache project 
> > > > data.
> > > > 
> > > > A lot of projects may not be aware of Kibble, what it show them and how 
> > > > they can use it to understand what is and has been happening in their 
> > > > community.
> > > > 
> > > > There could be 2 possible angles
> > > > 
> > > > 1) Kibble 101 for beginners - go through the basics of and maybe open 
> > > > it up to the audience to look at their projects
> > > > 
> > > > 2) How PMCs could use Kibble to help them understand how their 
> > > > community is made up, are they attracting new committers, are people 
> > > > staying, are they attracting new contributors and do they have non 
> > > > coding contributors whose contributions may not have been recognised etc
> > > 
> > > I think a "community health reporting 101" would be a welcome addition 
> > > to the conference!
> > > 
> > > > 
> > > > I know the CFP closing date is coming up pretty quickly but would be 
> > > > good to get some feedback. What do people think?
> > > > 
> > > > Thanks
> > > > Sharan
> > > > 
> > > 
> > > 
> > 
> 

Re: Kibble Talk for ApacheCon?

[Sharan Foga]

Hi All

I will submit something before the CFP closes on Monday. If anyone is 
interested in co-presenting then please let me know. 

The topic will be 'Community Health Reporting' as suggested by Daniel!

Thanks
Sharan

On 2021/04/23 15:56:15, Sharan Foga  wrote: 
> Good point.  'Community Health Reporting' has a very nice ring to it. And in 
> essence that is what we are doing here...
> 
> 
> On 2021/04/23 15:41:22, Daniel Gruno  wrote: 
> > On 23/04/2021 17.37, Sharan Foga wrote:
> > > Hi All
> > > 
> > > I think it could good to submit a Kibble talk for ApacheCon. It would be 
> > > based on Kibble-1 as that is where we have all the Apache project data.
> > > 
> > > A lot of projects may not be aware of Kibble, what it show them and how 
> > > they can use it to understand what is and has been happening in their 
> > > community.
> > > 
> > > There could be 2 possible angles
> > > 
> > > 1) Kibble 101 for beginners - go through the basics of and maybe open it 
> > > up to the audience to look at their projects
> > > 
> > > 2) How PMCs could use Kibble to help them understand how their community 
> > > is made up, are they attracting new committers, are people staying, are 
> > > they attracting new contributors and do they have non coding contributors 
> > > whose contributions may not have been recognised etc
> > 
> > I think a "community health reporting 101" would be a welcome addition 
> > to the conference!
> > 
> > > 
> > > I know the CFP closing date is coming up pretty quickly but would be good 
> > > to get some feedback. What do people think?
> > > 
> > > Thanks
> > > Sharan
> > > 
> > 
> > 
> 

New Kibble PMC Chair

[Sharan Foga]

Hi All

A quick note to let you know that I have been recently been elected as the new 
PMC Chair for Kibble. (Huge thanks to Rich Bowen as the outgoing Chair who has 
been taking care of the project since it's been a TLP!)

I'd really like to explore and see how we can make the project and community 
grow so I plan to be a bit more active in moving the project forward as we work 
on the roadmap for the new version, as well as supporting Kibble-1... so watch 
out for a few more posts from me :-)

Thanks
Sharan

Re: Kibble Talk for ApacheCon?

[Sharan Foga]

Good point.  'Community Health Reporting' has a very nice ring to it. And in 
essence that is what we are doing here...


On 2021/04/23 15:41:22, Daniel Gruno  wrote: 
> On 23/04/2021 17.37, Sharan Foga wrote:
> > Hi All
> > 
> > I think it could good to submit a Kibble talk for ApacheCon. It would be 
> > based on Kibble-1 as that is where we have all the Apache project data.
> > 
> > A lot of projects may not be aware of Kibble, what it show them and how 
> > they can use it to understand what is and has been happening in their 
> > community.
> > 
> > There could be 2 possible angles
> > 
> > 1) Kibble 101 for beginners - go through the basics of and maybe open it up 
> > to the audience to look at their projects
> > 
> > 2) How PMCs could use Kibble to help them understand how their community is 
> > made up, are they attracting new committers, are people staying, are they 
> > attracting new contributors and do they have non coding contributors whose 
> > contributions may not have been recognised etc
> 
> I think a "community health reporting 101" would be a welcome addition 
> to the conference!
> 
> > 
> > I know the CFP closing date is coming up pretty quickly but would be good 
> > to get some feedback. What do people think?
> > 
> > Thanks
> > Sharan
> > 
> 
> 

Potential Leap Year Bug Report from Justin McLean

[Sharan Foga]

Hi All

I am posting this here so we have a record of it.

Justin McLean posted a note in our Slack Channel that there seems to be a dip 
in the statistics every 4 years. He was wondering if it is a leap year bug.

To replicate

1) Login to Kibble demo
2) Click on Engagement
3) Click Contributor Retention 
4) Look at the graph for email retention

I took a look and can replicate it. The dips do seem to be starting around the 
1st March on 4 leap years 2004, 2008, 2012, 2016 and there is currently the 
beginning of a dip in 2020.

Next step will be to take a look at the data and calculation.

Thanks
Sharan

Kibble Talk for ApacheCon?

[Sharan Foga]

Hi All

I think it could good to submit a Kibble talk for ApacheCon. It would be based 
on Kibble-1 as that is where we have all the Apache project data.

A lot of projects may not be aware of Kibble, what it show them and how they 
can use it to understand what is and has been happening in their community.

There could be 2 possible angles 

1) Kibble 101 for beginners - go through the basics of and maybe open it up to 
the audience to look at their projects

2) How PMCs could use Kibble to help them understand how their community is 
made up, are they attracting new committers, are people staying, are they 
attracting new contributors and do they have non coding contributors whose 
contributions may not have been recognised etc

I know the CFP closing date is coming up pretty quickly but would be good to 
get some feedback. What do people think?

Thanks
Sharan

[DISCUSSION] Kibble Roadmap

[Sharan Foga]

Hi All

In one of the previous threads [1]  the suggestion was made to look at setting 
up a kanban board on Github to track the pending tasks. Are people happy to get 
one of these setup?

In addition, I'm thinking whether it might be good to create a high level 
roadmap and make it visible so it is clear and we can all see where we want to 
achieve. It could also help explaining to newcomers about what is happening 
with Kibble and what our next milestone will be.

What do people think?

Thanks
Sharan

[1] https://s.apache.org/xzk6s

Re: Apache Kibble 2.0

[Sharan Foga]

Hi All

Does anyone have any feedback on the work Tomek has done around this so far? 
Are people happy with the suggestions or do you have anything else in mind?

Thanks
Sharan

On 2021/03/06 14:39:43, Tomasz Urbaszek  wrote: 
> Hey all,
> 
> I'm wondering if anyone had time to review those documents?
> 
> Maybe we should start developing new Kibble and do the decision making
> as we go to avoid overhead of excessive planning?
> 
> Cheers,
> Tomek
> 
> 
> On Sat, 27 Feb 2021 at 18:43, Tomasz Urbaszek  wrote:
> >
> > After thinking a bit I think we may consider using Graph QL instead of 
> > REST... I know that Daniel mentioned that we may consider using GQL and now 
> > (after doing some brainstorming) I think I start understand why. The only 
> > thing I'm afraid is that GQL has a steep learning curve and it may make it 
> > harder to grow the community and develop the app. But I'm not sure if this 
> > should block us from using GQL.
> >
> > T.
> >
> > On Sat, 27 Feb 2021 at 17:07, Tomasz Urbaszek  wrote:
> >>
> >> Hi all,
> >>
> >> I prepared a draft of Open API specification that we may use to build new 
> >> Kibble API:
> >> https://app.swaggerhub.com/apis/turbaszek/kibble/1.0.0
> >>
> >> My idea was that inside single kibble deployment, there can be many 
> >> organizations and each organization has its own users and configured 
> >> scanners.
> >>
> >> So this proposal basically has 3 CRUD endpoints for organizations, users 
> >> and scanners. And additionally there's the crucial 
> >> /organization/{organization_id}/scanners/{scanner_id}/data endpoint which 
> >> returns data collected by a given scanner for a given organization.
> >>
> >> The data returned by this endpoint is an object containing an array of 
> >> data points (the real data) and additional information about the structure 
> >> of a single data point. This makes the response little ambiguous but it 
> >> gives us a big elasticity - each scanner can return data in different 
> >> formats. This proposal does not have any filters or aggregation options 
> >> which we definitely would like to add.
> >>
> >> Please let me know what you think! I'm really open to any suggestion ;)
> >>
> >> Cheers,
> >> Tomek
> >>
> >> On Mon, 22 Feb 2021 at 21:10, Fourat ZOUARI  wrote:
> >>>
> >>> Thx Sharan !
> >>>
> >>> I am excited to discover the great work done on kibble, the project
> >>> addresses the need to visualize information around raw source code
> >>> repositories and this is something i've been working on for some years 
> >>> now,
> >>> i'm willing to contribute with my experience to this project, as a user 
> >>> and
> >>> as a developer.
> >>>
> >>>
> >>> On Sun, Feb 21, 2021 at 10:55 AM Sharan Foga  wrote:
> >>>
> >>> > Hi Fourat
> >>> >
> >>> > Welcome to the community! It is great to see you here and thanks very 
> >>> > much
> >>> > for your contribution :-)
> >>> >
> >>> > Thanks
> >>> > Sharan
> >>> >
> >>> > On 2021/02/20 22:07:36, Fourat ZOUARI  wrote:
> >>> > > Hi Tomek, Sharan, Added some suggests to the doc
> >>> > >
> >>> > > Thx, Fourat
> >>> > >
> >>> > >
> >>> > > On Sat, Feb 20, 2021 at 1:53 PM Tomasz Urbaszek 
> >>> > > wrote:
> >>> > >
> >>> > > > Thanks Sharan!
> >>> > > >
> >>> > > > I already prepared the project structure together with some 
> >>> > > > automation
> >>> > > > (pre-commits, CI, etc) on my fork:
> >>> > > > https://github.com/turbaszek/kibble
> >>> > > >
> >>> > > > Best,
> >>> > > > Tomek
> >>> > > >
> >>> > > >
> >>> > > > On Sat, 20 Feb 2021 at 09:57, Sharan Foga  wrote:
> >>> > > > >
> >>> > > > > Hi Tomek
> >>> > > > >
> >>> > > > > Great initiative! I will take a look.
> >>> > > > >
> >>> > > > > I am still waiting on feedback from infra regarding the repo 
> >>> > > > &g

Looking at Vendor Neutrality

[Sharan Foga]

Hi All

At Apachecon@Home last year Myrle Krantz did a talk on Vendor Neutrality with 
some suggestions on how it could be measured. At the time we talked about 
seeing if we could somehow see if it could made into a potential new feature 
for Kibble. 

I reached out the Myrle recently and she sent me a copy of her thesis on Vendor 
Neutrality which I will go through. If anyone is interested in taking a look at 
it then please let me know and I'll load it onto our wiki. 

Something that is perhaps similar could be the CHAOSS metrics around 
organisational diversity which Kibble-1 initially tried to capture as the Meta 
Pony factor - but I know it wasn't complete implementation.

I'll read Myrle's paper and see what I can find, and will also take another 
look at the CHAOSS metrics to see where we are.

Thanks
Sharan

What's Next for the Refactor?

[Sharan Foga]

Hi All

It's been a quiet couple of weeks as the ASF Annual General Meeting has taken 
up some of my time. It's over now so let's see how we can move forward.

- The new repo is up and running
- There are no outstanding PRs or issues yet on the new repo.
- So lets discuss what happens next?

Thanks
Sharan

Is Kibble being used in reporter.apache.org tool?

[Sharan Foga]

Hi All

Some of the stats that are being used in the reporter.apache.org tool look like 
or are very similar to the stats coming from Kibble. Does anyone know if Kibble 
is the main source?

I was trying to find the reporter tool source code and found this in Github 
repo under Comdev

https://github.com/apache/comdev-reporter 

but I also saw a note that Daniel had created or updated the tool with a new 
wizard https://s.apache.org/if8b6

Have I got the correct repo for the reporter tool source?

As we go through the Kibble rewrite we need to understand where we have 
anything dependent on our existing solution (Kibble-1) , so we can plan a 
strategy for updating it if necessary.

Thanks
Sharan

Re: Renaming Existing kibble Repo to kibble-old

[Sharan Foga]

Hi All

The rename is done and a new blank repo is created! Let's get moving :-)

Thanks
Sharan

On 2021/02/09 20:07:55, Sharan Foga  wrote: 
> Hi Tomek
> 
> I am separating this out as a new thread as I think it got lost in the 
> previous discussion.  So has anything happened regarding this?
> 
> I took a quick look and I don't have access to the repo settings to do the 
> rename so maybe it is something we need to ask infra to do as the apache 
> organisation owner. 
> 
> Thanks
> Sharan
> 
> 
> -
> 
> 
> From: Tomasz Urbaszek 
> Subject: Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021
> Date: 2021/01/16 11:30:56
> List: dev@kibble.apache.org
> 
> Hi folks,
> 
> I created a 2.0 branch in apache/kibble (just for sanity sake if we would
> like to reuse some code) and I restored the main branch to some commit
> before breaking the refactor.
> 
> Can someone of you rename apache/kibble -> apache/kibble-old and then
> create apache/kibble repo (as discussed earlier)? I don't have the right to
> rename repo.
> 
> Cheers,
> Tomek
> 

Re: Renaming Existing kibble Repo to kibble-old

[Sharan Foga]

Hi All

Thanks for your patience. I pinged Infra on their slack channel yesterday again 
about this ticket but looks like they haven't had time to action this yet. I 
will check again tomorrow.

Thanks
Sharan

On 2021/02/21 10:37:44, Sharan Foga  wrote: 
> Hi All
> 
> The Jira for the repo rename is still in progress. I followed up with Infra 
> yesterday so hopefully it can get done soon.
> 
> Thanks
> Sharan
> 
> On 2021/02/09 20:07:55, Sharan Foga  wrote: 
> > Hi Tomek
> > 
> > I am separating this out as a new thread as I think it got lost in the 
> > previous discussion.  So has anything happened regarding this?
> > 
> > I took a quick look and I don't have access to the repo settings to do the 
> > rename so maybe it is something we need to ask infra to do as the apache 
> > organisation owner. 
> > 
> > Thanks
> > Sharan
> > 
> > 
> > -
> > 
> > 
> > From: Tomasz Urbaszek 
> > Subject: Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021
> > Date: 2021/01/16 11:30:56
> > List: dev@kibble.apache.org
> > 
> > Hi folks,
> > 
> > I created a 2.0 branch in apache/kibble (just for sanity sake if we would
> > like to reuse some code) and I restored the main branch to some commit
> > before breaking the refactor.
> > 
> > Can someone of you rename apache/kibble -> apache/kibble-old and then
> > create apache/kibble repo (as discussed earlier)? I don't have the right to
> > rename repo.
> > 
> > Cheers,
> > Tomek
> > 
> 

Re: Renaming Existing kibble Repo to kibble-old

[Sharan Foga]

Hi All

The Jira for the repo rename is still in progress. I followed up with Infra 
yesterday so hopefully it can get done soon.

Thanks
Sharan

On 2021/02/09 20:07:55, Sharan Foga  wrote: 
> Hi Tomek
> 
> I am separating this out as a new thread as I think it got lost in the 
> previous discussion.  So has anything happened regarding this?
> 
> I took a quick look and I don't have access to the repo settings to do the 
> rename so maybe it is something we need to ask infra to do as the apache 
> organisation owner. 
> 
> Thanks
> Sharan
> 
> 
> -
> 
> 
> From: Tomasz Urbaszek 
> Subject: Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021
> Date: 2021/01/16 11:30:56
> List: dev@kibble.apache.org
> 
> Hi folks,
> 
> I created a 2.0 branch in apache/kibble (just for sanity sake if we would
> like to reuse some code) and I restored the main branch to some commit
> before breaking the refactor.
> 
> Can someone of you rename apache/kibble -> apache/kibble-old and then
> create apache/kibble repo (as discussed earlier)? I don't have the right to
> rename repo.
> 
> Cheers,
> Tomek
> 

Re: Apache Kibble 2.0

[Sharan Foga]

Hi Fourat

Welcome to the community! It is great to see you here and thanks very much for 
your contribution :-)

Thanks
Sharan

On 2021/02/20 22:07:36, Fourat ZOUARI  wrote: 
> Hi Tomek, Sharan, Added some suggests to the doc
> 
> Thx, Fourat
> 
> 
> On Sat, Feb 20, 2021 at 1:53 PM Tomasz Urbaszek 
> wrote:
> 
> > Thanks Sharan!
> >
> > I already prepared the project structure together with some automation
> > (pre-commits, CI, etc) on my fork:
> > https://github.com/turbaszek/kibble
> >
> > Best,
> > Tomek
> >
> >
> > On Sat, 20 Feb 2021 at 09:57, Sharan Foga  wrote:
> > >
> > > Hi Tomek
> > >
> > > Great initiative! I will take a look.
> > >
> > > I am still waiting on feedback from infra regarding the repo rename so
> > will follow up on that  again today as it would be good to get started with
> > the new version.
> > >
> > > And yes - interesting to see popularity increasing :-)
> > >
> > > Thanks
> > > Sharan
> > >
> > > On 2021/02/20 08:11:10, Tomasz Urbaszek  wrote:
> > > > Hi all,
> > > >
> > > > I drafted some proposal of Kibble 2.0 design decisions:
> > > > https://s.apache.org/kibble-2-0
> > > >
> > > > This is a google docs - I found those much easier to work with than
> > > > confluence. But once we have something that we accept I will move it
> > > > to cwiki.
> > > >
> > > > Please feel free to add all your ideas and concerns!
> > > >
> > > > I think the crucial point (not covered in doc) is to decide if we want
> > > > to reuse the existing Kibble database or not. In my opinion, breaking
> > > > backward compatibility may improve development speed.
> > > >
> > > > And as an interesting fact I think Kibble is getting interestingly
> > "popular":
> > > > https://imgur.com/JssRETL
> > > >
> > > > Cheers,
> > > > Tomek
> > > >
> >
> 

Announcing a New Committer Kaxil Naik

[Sharan Foga]

Hi All

The Kibble PMC has invited Kaxil Naik to become a committer on the project and 
we are happy to announce that he has accepted.

Please join me in congratulating Kaxil on his new role.

Thanks
Sharan
On behalf of the Apache Kibble PMC

Re: Apache Kibble 2.0

[Sharan Foga]

Hi Tomek

Great initiative! I will take a look.

I am still waiting on feedback from infra regarding the repo rename so will 
follow up on that  again today as it would be good to get started with the new 
version.

And yes - interesting to see popularity increasing :-)

Thanks
Sharan

On 2021/02/20 08:11:10, Tomasz Urbaszek  wrote: 
> Hi all,
> 
> I drafted some proposal of Kibble 2.0 design decisions:
> https://s.apache.org/kibble-2-0
> 
> This is a google docs - I found those much easier to work with than
> confluence. But once we have something that we accept I will move it
> to cwiki.
> 
> Please feel free to add all your ideas and concerns!
> 
> I think the crucial point (not covered in doc) is to decide if we want
> to reuse the existing Kibble database or not. In my opinion, breaking
> backward compatibility may improve development speed.
> 
> And as an interesting fact I think Kibble is getting interestingly "popular":
> https://imgur.com/JssRETL
> 
> Cheers,
> Tomek
> 

Potential New Contributor

[Sharan Foga]

Hi All

I had a query in our slack channel from a potential new contributor Fourat so 
have told them to introduce themselves here on the mailing list - so hopefully 
they will :-)

Thanks
Sharan

Re: Renaming Existing kibble Repo to kibble-old

[Sharan Foga]

Hi All

No worries. I've just responded to a comment from Gavin about the rename. He 
has asked why we just don't delete everything and do a push. I've told him that 
we said that we would pick and choose what to bring over from the old into the 
new - so still need to old code available. We also have some existing and 
working user installs on the code we have  now. 

I'll be tracking the Jira ticket and everyone please feel free to monitor it 
too.

Thanks
Sharan

On 2021/02/10 01:14:59, Tomasz Urbaszek  wrote: 
> Thanks Sharan for opening the jira ticket!
> 
> I had quite few things on my head in last few weeks but once the
> ticket is resolved I'm happy to configure pre-commits and Github
> Actions to assure that we build new Kibble using best practices 
> 
> Best wishes,
> Tomek
> 
> On Tue, 9 Feb 2021 at 21:36, Michał Słowikowski
>  wrote:
> >
> > Hi Sharan,
> >
> > Thank you. :)
> >
> > We could move with Kibble somehow.
> > I think we should move our action points from our latest and the only one 
> > call to GitHub issues.
> > Break more complex tasks into smaller and easier.
> >
> > Right know we have branch 2.0 made by Tomek.
> >
> > Should we cherry-pick something to that branch Sorry but I did have 
> > opportunity to take a look at 2.0 branch :(
> >
> > Best
> > Michal
> >
> >
> > > On 9 Feb 2021, at 21:19, Sharan Foga  wrote:
> > >
> > > Hi All
> > >
> > > Infra jira ticket created 
> > > https://issues.apache.org/jira/browse/INFRA-21411
> > >
> > > Thanks
> > > Sharan
> > >
> > >> On 2021/02/09 20:11:45, Sharan Foga  wrote:
> > >> OK I will file one and post the details here so people can track it.
> > >>
> > >> Thanks
> > >> Sharan
> > >>
> > >>> On 2021/02/09 20:08:59, Daniel Gruno  wrote:
> > >>> On 09/02/2021 21.07, Sharan Foga wrote:
> > >>>> Hi Tomek
> > >>>>
> > >>>> I am separating this out as a new thread as I think it got lost in the 
> > >>>> previous discussion.  So has anything happened regarding this?
> > >>>>
> > >>>> I took a quick look and I don't have access to the repo settings to do 
> > >>>> the rename so maybe it is something we need to ask infra to do as the 
> > >>>> apache organisation owner.
> > >>>
> > >>> yeah, renames require a jira ticket, I believe. Feel free to file one :)
> > >>>
> > >>>>
> > >>>> Thanks
> > >>>> Sharan
> > >>>>
> > >>>>
> > >>>> -
> > >>>>
> > >>>>
> > >>>> From: Tomasz Urbaszek 
> > >>>> Subject: Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021
> > >>>> Date: 2021/01/16 11:30:56
> > >>>> List: dev@kibble.apache.org
> > >>>>
> > >>>> Hi folks,
> > >>>>
> > >>>> I created a 2.0 branch in apache/kibble (just for sanity sake if we 
> > >>>> would
> > >>>> like to reuse some code) and I restored the main branch to some commit
> > >>>> before breaking the refactor.
> > >>>>
> > >>>> Can someone of you rename apache/kibble -> apache/kibble-old and then
> > >>>> create apache/kibble repo (as discussed earlier)? I don't have the 
> > >>>> right to
> > >>>> rename repo.
> > >>>>
> > >>>> Cheers,
> > >>>> Tomek
> > >>>>
> > >>>
> > >>>
> > >>
> 

Re: Renaming Existing kibble Repo to kibble-old

[Sharan Foga]

Hi All

Infra jira ticket created https://issues.apache.org/jira/browse/INFRA-21411

Thanks
Sharan

On 2021/02/09 20:11:45, Sharan Foga  wrote: 
> OK I will file one and post the details here so people can track it.
> 
> Thanks
> Sharan
> 
> On 2021/02/09 20:08:59, Daniel Gruno  wrote: 
> > On 09/02/2021 21.07, Sharan Foga wrote:
> > > Hi Tomek
> > > 
> > > I am separating this out as a new thread as I think it got lost in the 
> > > previous discussion.  So has anything happened regarding this?
> > > 
> > > I took a quick look and I don't have access to the repo settings to do 
> > > the rename so maybe it is something we need to ask infra to do as the 
> > > apache organisation owner.
> > 
> > yeah, renames require a jira ticket, I believe. Feel free to file one :)
> > 
> > > 
> > > Thanks
> > > Sharan
> > > 
> > > 
> > > -
> > > 
> > > 
> > > From: Tomasz Urbaszek 
> > > Subject: Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021
> > > Date: 2021/01/16 11:30:56
> > > List: dev@kibble.apache.org
> > > 
> > > Hi folks,
> > > 
> > > I created a 2.0 branch in apache/kibble (just for sanity sake if we would
> > > like to reuse some code) and I restored the main branch to some commit
> > > before breaking the refactor.
> > > 
> > > Can someone of you rename apache/kibble -> apache/kibble-old and then
> > > create apache/kibble repo (as discussed earlier)? I don't have the right 
> > > to
> > > rename repo.
> > > 
> > > Cheers,
> > > Tomek
> > > 
> > 
> > 
> 

Re: Renaming Existing kibble Repo to kibble-old

[Sharan Foga]

OK I will file one and post the details here so people can track it.

Thanks
Sharan

On 2021/02/09 20:08:59, Daniel Gruno  wrote: 
> On 09/02/2021 21.07, Sharan Foga wrote:
> > Hi Tomek
> > 
> > I am separating this out as a new thread as I think it got lost in the 
> > previous discussion.  So has anything happened regarding this?
> > 
> > I took a quick look and I don't have access to the repo settings to do the 
> > rename so maybe it is something we need to ask infra to do as the apache 
> > organisation owner.
> 
> yeah, renames require a jira ticket, I believe. Feel free to file one :)
> 
> > 
> > Thanks
> > Sharan
> > 
> > 
> > -
> > 
> > 
> > From: Tomasz Urbaszek 
> > Subject: Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021
> > Date: 2021/01/16 11:30:56
> > List: dev@kibble.apache.org
> > 
> > Hi folks,
> > 
> > I created a 2.0 branch in apache/kibble (just for sanity sake if we would
> > like to reuse some code) and I restored the main branch to some commit
> > before breaking the refactor.
> > 
> > Can someone of you rename apache/kibble -> apache/kibble-old and then
> > create apache/kibble repo (as discussed earlier)? I don't have the right to
> > rename repo.
> > 
> > Cheers,
> > Tomek
> > 
> 
> 

Renaming Existing kibble Repo to kibble-old

[Sharan Foga]

Hi Tomek

I am separating this out as a new thread as I think it got lost in the previous 
discussion.  So has anything happened regarding this?

I took a quick look and I don't have access to the repo settings to do the 
rename so maybe it is something we need to ask infra to do as the apache 
organisation owner. 

Thanks
Sharan


-


From: Tomasz Urbaszek 
Subject: Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021
Date: 2021/01/16 11:30:56
List: dev@kibble.apache.org

Hi folks,

I created a 2.0 branch in apache/kibble (just for sanity sake if we would
like to reuse some code) and I restored the main branch to some commit
before breaking the refactor.

Can someone of you rename apache/kibble -> apache/kibble-old and then
create apache/kibble repo (as discussed earlier)? I don't have the right to
rename repo.

Cheers,
Tomek

Re: Triage role for contributors

[Sharan Foga]

Ok let me see what I can do.


On 2021/02/09 19:33:10, Kaxil Naik  wrote: 
> No feedback yet, still waiting.
> 
> On Tue, Feb 9, 2021 at 7:32 PM Sharan Foga  wrote:
> 
> > Hi Kaxil
> >
> > Did you get any feedback on this or are you still waiting?
> >
> > Thanks
> > Sharan
> >
> > On 2021/01/08 21:59:58, Kaxil Naik  wrote:
> > > I can help with some Issue Triage too in the current repo and what will
> > > become the Kibble version2 repo.
> > >
> > > My Github username: kaxil (https://github.com/kaxil/)
> > >
> > > Regards,
> > > Kaxil
> > >
> > > On 2020/10/11 18:22:33, Sharan Foga  wrote:
> > > > +1 from me :-)>
> > > >
> > > > Thanks>
> > > > Sharan>
> > > >
> > > > On 2020/10/11 18:21:35, Sharan Foga  wrote: >
> > > > > Hi All>
> > > > > >
> > > > > In order to request this role for Tomek, we need to show community
> > > approval for the triage role and also reference it in the Infra Jira
> > ticket
> > > request.>
> > > > > >
> > > > > So please can you respond if you support giving Tomek a triage role.>
> > > > > >
> > > > > Thanks>
> > > > > Sharan>
> > > > > >
> > > > > On 2020/10/11 16:45:56, Sharan Foga  wrote: >
> > > > > > Hi Tomek>
> > > > > > >
> > > > > > Thanks for volunteering to help with triage. I took a look at the
> > > kibble github repo and I dont have authority to grant access. It sounds
> > > like a request to infra so I will request it for you.>
> > > > > > >
> > > > > > Thanks>
> > > > > > Sharan>
> > > > > > >
> > > > > > On 2020/10/11 11:37:35, Tomasz Urbaszek  wrote:
> > >
> > > > > > > Hello,>
> > > > > > > >
> > > > > > > Quite recently Github introduced a new repository access level
> > > called>
> > > > > > > "triage role":>
> > > > > > > https://infra.apache.org/github-roles.html>
> > > > > > > >
> > > > > > > As described on that page:>
> > > > > > > > It is a good role for people who are interested in supporting
> > and
> > > contributing to the project, but who are not ready to be Committers.>
> > > > > > > >
> > > > > > > I would like to ask you if it would be possible to grant me this
> > > role.>
> > > > > > > I'm happy to manage the issues and PRs and ping people for
> > > reviews.>
> > > > > > > My Github handle is: turbaszek>
> > > > > > > >
> > > > > > > Best wishes,>
> > > > > > > Tomek>
> > > > > > > >
> > > > > > >
> > > > > >
> > > >
> > >
> >
> 

Re: Triage role for contributors

[Sharan Foga]

Hi Kaxil

Did you get any feedback on this or are you still waiting?

Thanks
Sharan

On 2021/01/08 21:59:58, Kaxil Naik  wrote: 
> I can help with some Issue Triage too in the current repo and what will
> become the Kibble version2 repo.
> 
> My Github username: kaxil (https://github.com/kaxil/)
> 
> Regards,
> Kaxil
> 
> On 2020/10/11 18:22:33, Sharan Foga  wrote:
> > +1 from me :-)>
> >
> > Thanks>
> > Sharan>
> >
> > On 2020/10/11 18:21:35, Sharan Foga  wrote: >
> > > Hi All>
> > > >
> > > In order to request this role for Tomek, we need to show community
> approval for the triage role and also reference it in the Infra Jira ticket
> request.>
> > > >
> > > So please can you respond if you support giving Tomek a triage role.>
> > > >
> > > Thanks>
> > > Sharan>
> > > >
> > > On 2020/10/11 16:45:56, Sharan Foga  wrote: >
> > > > Hi Tomek>
> > > > >
> > > > Thanks for volunteering to help with triage. I took a look at the
> kibble github repo and I dont have authority to grant access. It sounds
> like a request to infra so I will request it for you.>
> > > > >
> > > > Thanks>
> > > > Sharan>
> > > > >
> > > > On 2020/10/11 11:37:35, Tomasz Urbaszek  wrote: >
> > > > > Hello,>
> > > > > >
> > > > > Quite recently Github introduced a new repository access level
> called>
> > > > > "triage role":>
> > > > > https://infra.apache.org/github-roles.html>
> > > > > >
> > > > > As described on that page:>
> > > > > > It is a good role for people who are interested in supporting and
> contributing to the project, but who are not ready to be Committers.>
> > > > > >
> > > > > I would like to ask you if it would be possible to grant me this
> role.>
> > > > > I'm happy to manage the issues and PRs and ping people for
> reviews.>
> > > > > My Github handle is: turbaszek>
> > > > > >
> > > > > Best wishes,>
> > > > > Tomek>
> > > > > >
> > > > >
> > > >
> >
> 

Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021

[Sharan Foga]

Hi Kaxil

I have copied the meeting notes onto the Kibble Wiki for reference  

https://cwiki.apache.org/confluence/display/KIBBLE/Kibble+Development+Call%3A+7th+January+2021
 

with a link to this thread.

Thanks
Sharan

On 2021/01/08 21:52:32, Kaxil Naik  wrote: 
> Hi all,
> 
> Here are the notes from our Kibble dev call from yesterday. Please feel
> free to add anything I have missed.
> 
> *Attendees:*
> 
>- Kaxil Naik
>- Tomek Urbaszek
>    - Michał Słowikowski
>- Sharan Foga
>- Daniel Gruno
> 
> 
> Here is the summary of the call.
> 
>- *Kibble v2*:
>   - Rewrite the implementation from Scratch for v2 to improve code and
>   to cater for new ideas
>   - Cherrypick / copy any code from the current Repo
>   - New repo allows us to work with a TDD approach. The current repo
>   does not have tests.
>   - *Supporting more DBs*
>   - For now, we would just support Elasticsearch.
>   - Supporting just one DB allows us to maintain it in a better way
>   - Would be good to find some kind of ORM to talk to Elasticsearch
>   which will allow static Schema and use Class attributes instead
> of dealing
>   with dicts
>   - *Migration*
>   - Make migration tool or make whatever we build new as
>   backwards-compatible so that we don’t need to re-scan all the
> data for ASF
>   Kibble -- which can take aleast a week if started from scratch.
>   (contains 50million records)
>- *Scanners*
>   - Build Base Scanner for v2 that will allow easily creating new
>   Scanners and encourage more contributions
>   - Write docs around how to build a new scanner inheriting
>   *BaseScanner*
>   - Some of the new Scanners that users have requested are:
>  - Gitlab
>  - Social Media Scanners: Twitter, Discord, Slack
>   - Create a Github Issue template for Scanners so users can request
>   new Scanners
>- *Dashboard*
>   - Do a POC to see if Apache Superset can replace our current UI
>- Make Apache Superset or the existing UI optional as some Users just
>   rely on the API
>   - That will allow us to focus on the CORE (Scanner, Server and ES)
>   -
>   - What happens to the PR that introduces breaking changes??
>  - We should not merge that PR until it is a breaking change,
>  instead we should make the PR backwards compatible
>  - Or wait until next major release (assign appropriate Github
>  Milestone)
> 
> 
> Let me know if anyone has any thoughts on any of the items listed above.
> 
> Best regards,
> Kaxil
> 

Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021

[Sharan Foga]

Hi Tomek

Good question! 

Whichever way we start at some point (now or in the future) we will probably 
want the new repo to be eventually called apache/kibble. 

No real preference just some thoughts.. if we rename the existing repo to 'old' 
then at least people know we are working on something new and will go look for 
it.  Having kibble and kibble-2 around at the same time might be confusing 
especially since there will probably be activity on both.

Thanks
Sharan


On 2021/01/10 13:53:51, Tomasz Urbaszek  wrote: 
> Thanks Kaxil for the notes!
> 
> Should we create a new repo called something like apache/kibble-2 or should
> we rename existing one to apache/kibble-old and then create a new, fresh
> apache/kibble?
> 
> Best,
> Tomek
> 
> On Fri, Jan 8, 2021 at 10:55 PM Kaxil Naik  wrote:
> 
> > Please ignore the last bullet around "breaking changes" -- I mixed that up
> > with the Airflow Dev call summary ;)
> >
> > Regards,
> > Kaxil
> >
> > On Fri, Jan 8, 2021 at 9:52 PM Kaxil Naik  wrote:
> >
> > > Hi all,
> > >
> > > Here are the notes from our Kibble dev call from yesterday. Please feel
> > > free to add anything I have missed.
> > >
> > > *Attendees:*
> > >
> > >- Kaxil Naik
> > >- Tomek Urbaszek
> > >- Michał Słowikowski
> > >- Sharan Foga
> > >- Daniel Gruno
> > >
> > >
> > > Here is the summary of the call.
> > >
> > >- *Kibble v2*:
> > >   - Rewrite the implementation from Scratch for v2 to improve code
> > >   and to cater for new ideas
> > >   - Cherrypick / copy any code from the current Repo
> > >   - New repo allows us to work with a TDD approach. The current repo
> > >   does not have tests.
> > >   - *Supporting more DBs*
> > >   - For now, we would just support Elasticsearch.
> > >   - Supporting just one DB allows us to maintain it in a better way
> > >   - Would be good to find some kind of ORM to talk to Elasticsearch
> > >   which will allow static Schema and use Class attributes instead of
> > dealing
> > >   with dicts
> > >   - *Migration*
> > >   - Make migration tool or make whatever we build new as
> > >   backwards-compatible so that we don’t need to re-scan all the data
> > for ASF
> > >   Kibble -- which can take aleast a week if started from scratch.
> > >   (contains 50million records)
> > >- *Scanners*
> > >   - Build Base Scanner for v2 that will allow easily creating new
> > >   Scanners and encourage more contributions
> > >   - Write docs around how to build a new scanner inheriting
> > >   *BaseScanner*
> > >   - Some of the new Scanners that users have requested are:
> > >  - Gitlab
> > >  - Social Media Scanners: Twitter, Discord, Slack
> > >   - Create a Github Issue template for Scanners so users can request
> > >   new Scanners
> > >- *Dashboard*
> > >   - Do a POC to see if Apache Superset can replace our current UI
> > >- Make Apache Superset or the existing UI optional as some Users just
> > >   rely on the API
> > >   - That will allow us to focus on the CORE (Scanner, Server and ES)
> > >   -
> > >   - What happens to the PR that introduces breaking changes??
> > >  - We should not merge that PR until it is a breaking change,
> > >  instead we should make the PR backwards compatible
> > >  - Or wait until next major release (assign appropriate Github
> > >  Milestone)
> > >
> > >
> > > Let me know if anyone has any thoughts on any of the items listed above.
> > >
> > > Best regards,
> > > Kaxil
> > >
> >
> 

Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021

[Sharan Foga]

Good meeting and thanks for the notes Kaxil!

On 2021/01/08 21:55:13, Kaxil Naik  wrote: 
> Please ignore the last bullet around "breaking changes" -- I mixed that up
> with the Airflow Dev call summary ;)
> 
> Regards,
> Kaxil
> 
> On Fri, Jan 8, 2021 at 9:52 PM Kaxil Naik  wrote:
> 
> > Hi all,
> >
> > Here are the notes from our Kibble dev call from yesterday. Please feel
> > free to add anything I have missed.
> >
> > *Attendees:*
> >
> >    - Kaxil Naik
> >- Tomek Urbaszek
> >- Michał Słowikowski
> >- Sharan Foga
> >- Daniel Gruno
> >
> >
> > Here is the summary of the call.
> >
> >- *Kibble v2*:
> >   - Rewrite the implementation from Scratch for v2 to improve code
> >   and to cater for new ideas
> >   - Cherrypick / copy any code from the current Repo
> >   - New repo allows us to work with a TDD approach. The current repo
> >   does not have tests.
> >   - *Supporting more DBs*
> >   - For now, we would just support Elasticsearch.
> >   - Supporting just one DB allows us to maintain it in a better way
> >   - Would be good to find some kind of ORM to talk to Elasticsearch
> >   which will allow static Schema and use Class attributes instead of 
> > dealing
> >   with dicts
> >   - *Migration*
> >   - Make migration tool or make whatever we build new as
> >   backwards-compatible so that we don’t need to re-scan all the data 
> > for ASF
> >   Kibble -- which can take aleast a week if started from scratch.
> >   (contains 50million records)
> >- *Scanners*
> >   - Build Base Scanner for v2 that will allow easily creating new
> >   Scanners and encourage more contributions
> >   - Write docs around how to build a new scanner inheriting
> >   *BaseScanner*
> >   - Some of the new Scanners that users have requested are:
> >  - Gitlab
> >  - Social Media Scanners: Twitter, Discord, Slack
> >   - Create a Github Issue template for Scanners so users can request
> >   new Scanners
> >- *Dashboard*
> >   - Do a POC to see if Apache Superset can replace our current UI
> >- Make Apache Superset or the existing UI optional as some Users just
> >   rely on the API
> >   - That will allow us to focus on the CORE (Scanner, Server and ES)
> >   -
> >   - What happens to the PR that introduces breaking changes??
> >  - We should not merge that PR until it is a breaking change,
> >  instead we should make the PR backwards compatible
> >  - Or wait until next major release (assign appropriate Github
> >  Milestone)
> >
> >
> > Let me know if anyone has any thoughts on any of the items listed above.
> >
> > Best regards,
> > Kaxil
> >
> 

Re: Dev Call to discuss future Roadmap for Apache Kibble in 2021

[Sharan Foga]

Hi All

Happy New Year!

Posting this as a reminder that the call is planned for tomorrow :-)

Thanks
Sharan

On 2020/12/24 17:33:40, Kaxil Naik  wrote: 
> Let's do it then :) -- Looks like Thursday - Jan 7, 2021 at 2-3 PM GMT is
> suitable for all those who replied on Doodle.
> 
> Call Link: https://meet.apache.org/BetterHalvesSenseAround
> Event:
> https://calendar.google.com/event?action=TEMPLATE=NGwxYzlxajMzNmo0ZGloNW9mZm8xbDMzNzAga2F4aWxAYXN0cm9ub21lci5pbw=kaxil%40astronomer.io
> 
> Regards,
> Kaxil
> 
> On Mon, Dec 21, 2020 at 9:26 AM Daniel Gruno  wrote:
> 
> > Good initiative :), I've put my availability in the doodle.
> >
> > I'm leaning towards a complete refactoring/rewrite, a "kibble v2" where
> > we use the general architecture/design of Kibble but write the python
> > logic from scratch.
> >
> > On 20/12/2020 22.55, Kaxil Naik wrote:
> > > Hi folks,
> > >
> > > I was talking to Daniel and Tomek on Slack that it would be awesome to
> > have
> > > a DEV call to discuss the future of Apache Kibble.
> > >
> > > I am one of the committer, PMC Member and Release Manager of the Apache
> > > Airflow project. I organized regular dev calls for Airflow until we
> > > released Airflow 2.0 last week. And it really helped with aligning the
> > > goals, scoping the items for the release etc.
> > >
> > > I really think this would also be useful for Apache Kibble. I recently
> > > started contributing to Kibble (commits
> > > ) and looks like
> > it
> > > needs more love and a bit of refactor. Whether we want to refactor
> > existing
> > > codebase or start fresh can be discussed on the call.
> > >
> > > I propose let's start with one call and then we will see if a regular
> > call
> > > is needed or we can do async.
> > >
> > > Following is the link of the doodle I created, please add a vote to what
> > > day and time suits you best in the new year.
> > >
> > > Doodle: https://doodle.com/poll/g39kwv6e87gcvfst
> > >
> > > Let me know what you all think.
> > >
> > > Regards,
> > > Kaxil
> > >
> >
> >
> 

Re: [LAZY CONSENSUS] Rename Default Branch from Master to Main

[Sharan Foga]

Thanks Tomek for you help on this done!

On 2020/10/19 17:43:00, Sharan Foga  wrote: 
> Hi All
> 
> Just for info - here is a link to the infra issue 
> https://issues.apache.org/jira/browse/INFRA-20997 for the rename.
> 
> Thanks
> Sharan
> 
> 
> 
> On 2020/10/17 14:21:21, Sharan Foga  wrote: 
> > Hi Everyone
> > 
> > I'll organise getting this rename done (probably with help from infra as I 
> > don't want to break anything!)
> > 
> > Thanks
> > Sharan
> > 
> > On 2020/10/11 16:55:38, Sharan Foga  wrote: 
> > > Hi All
> > > 
> > > Many projects have renamed their default branch from master.[1] We still 
> > > have a master branch so would like to rename this to 'main'. Tomek has 
> > > already created an issue [2]
> > > 
> > > I'd like to use lazy consensus [3] for this decision so please respond to 
> > > this message only if you disagree with renaming the default branch from 
> > > 'master' to 'main'
> > > 
> > > Thanks
> > > Sharan
> > > 
> > > [1] https://github.com/github/renaming
> > > [2] https://github.com/apache/kibble/issues/45
> > > [2] http://community.apache.org/committers/lazyConsensus.html
> > > 
> > 
> 

Announcing a New Committer Michał Słowikowski

[Sharan Foga]

Hi All

The Kibble PMC has invited Michał Słowikowski as new committer to the project 
and are happy to announce that he has accepted.

Welcome and congratulations Michał!

Thanks
Sharan

Re: [DISCUSS] Restructure the Apache Kibble project

[Sharan Foga]

Hi Tomek

Thanks for the initiative and ideas!

Anything that makes things simpler or easier is OK with me :-)  and 
consolidating things seems like a good idea. I am guessing that a lot of the 
changes would probably be behind the scenes rather than at the user end - right?

On the wishlist - I saw a talk by Myrle at ApacheCon@Home and she had done some 
initial work linking contributions to affiliation and I mentioned seeing if 
that could be something we could look at including into Kibble. I think we 
tried to do it with Meta Pony Factor but dont think it is complete. Anyway lots 
of ideas to keep us going!

Thanks
Sharan


On 2020/10/18 14:28:33, Tomasz Urbaszek  wrote: 
> Hello all,
> 
> I would like to propose a few things that I think are worth considering:
> 
> 1. Merge all three repositories (kibble, kibble-scanners,
> kibble-docker) into one. In this way I think we may simplify
> development, dependency management, and distribution. Our project is
> rather small and increasing places needing management probably won't
> help.
> 
> 2. Once we have the API server and scanner in one repo we can make
> Kibble a python package. This will not only simplify installation and
> setup but also may help us create a nice CLI to manage all components
> (setup, server, scanners). By doing this users will be able to run
> something like `kibble server` or `kibble scanners ponymail`.
> 
> 3. Rewrite kibble API server to use a framework (for example FastAPI
> which supports OpenAPI specs). This point is probably the hardest one
> to implement as it will require adding tests to preserve compatibility
> with kibble ui.
> 
> What do you think? Do you have anything that you would love to see in
> Apache Kibble? :)
> 
> Cheers,
> Tomek
> 

Announcing a New Committer Tomasz Urbaszek

[Sharan Foga]

Hi All

The Kibble PMC has invited Tomasz Urbaszek as new committer to the project and 
are happy to announce he has accepted.

Congratulations Tomek!

Thanks
Sharan

Re: [LAZY CONSENSUS] Rename Default Branch from Master to Main

[Sharan Foga]

Hi All

Just for info - here is a link to the infra issue 
https://issues.apache.org/jira/browse/INFRA-20997 for the rename.

Thanks
Sharan



On 2020/10/17 14:21:21, Sharan Foga  wrote: 
> Hi Everyone
> 
> I'll organise getting this rename done (probably with help from infra as I 
> don't want to break anything!)
> 
> Thanks
> Sharan
> 
> On 2020/10/11 16:55:38, Sharan Foga  wrote: 
> > Hi All
> > 
> > Many projects have renamed their default branch from master.[1] We still 
> > have a master branch so would like to rename this to 'main'. Tomek has 
> > already created an issue [2]
> > 
> > I'd like to use lazy consensus [3] for this decision so please respond to 
> > this message only if you disagree with renaming the default branch from 
> > 'master' to 'main'
> > 
> > Thanks
> > Sharan
> > 
> > [1] https://github.com/github/renaming
> > [2] https://github.com/apache/kibble/issues/45
> > [2] http://community.apache.org/committers/lazyConsensus.html
> > 
> 

Re: [LAZY CONSENSUS] Rename Default Branch from Master to Main

[Sharan Foga]

Hi Everyone

I'll organise getting this rename done (probably with help from infra as I 
don't want to break anything!)

Thanks
Sharan

On 2020/10/11 16:55:38, Sharan Foga  wrote: 
> Hi All
> 
> Many projects have renamed their default branch from master.[1] We still have 
> a master branch so would like to rename this to 'main'. Tomek has already 
> created an issue [2]
> 
> I'd like to use lazy consensus [3] for this decision so please respond to 
> this message only if you disagree with renaming the default branch from 
> 'master' to 'main'
> 
> Thanks
> Sharan
> 
> [1] https://github.com/github/renaming
> [2] https://github.com/apache/kibble/issues/45
> [2] http://community.apache.org/committers/lazyConsensus.html
> 

Re: Triage role for contributors

[Sharan Foga]

+1 from me :-)

Thanks
Sharan

On 2020/10/11 18:21:35, Sharan Foga  wrote: 
> Hi All
> 
> In order to request this role for Tomek, we need to show community approval 
> for the triage role and also reference it in the Infra Jira ticket request.
> 
> So please can you respond if you support giving Tomek a triage role.
> 
> Thanks
> Sharan
> 
> On 2020/10/11 16:45:56, Sharan Foga  wrote: 
> > Hi Tomek
> > 
> > Thanks for volunteering to help with triage. I took a look at the kibble 
> > github repo and I dont have authority to grant access. It sounds like a 
> > request to infra so I will request it for you.
> > 
> > Thanks
> > Sharan
> > 
> > On 2020/10/11 11:37:35, Tomasz Urbaszek  wrote: 
> > > Hello,
> > > 
> > > Quite recently Github introduced a new repository access level called
> > > "triage role":
> > > https://infra.apache.org/github-roles.html
> > > 
> > > As described on that page:
> > > > It is a good role for people who are interested in supporting and 
> > > > contributing to the project, but who are not ready to be Committers.
> > > 
> > > I would like to ask you if it would be possible to grant me this role.
> > > I'm happy to manage the issues and PRs and ping people for reviews.
> > > My Github handle is: turbaszek
> > > 
> > > Best wishes,
> > > Tomek
> > > 
> > 
> 

Re: Triage role for contributors

[Sharan Foga]

Hi All

In order to request this role for Tomek, we need to show community approval for 
the triage role and also reference it in the Infra Jira ticket request.

So please can you respond if you support giving Tomek a triage role.

Thanks
Sharan

On 2020/10/11 16:45:56, Sharan Foga  wrote: 
> Hi Tomek
> 
> Thanks for volunteering to help with triage. I took a look at the kibble 
> github repo and I dont have authority to grant access. It sounds like a 
> request to infra so I will request it for you.
> 
> Thanks
> Sharan
> 
> On 2020/10/11 11:37:35, Tomasz Urbaszek  wrote: 
> > Hello,
> > 
> > Quite recently Github introduced a new repository access level called
> > "triage role":
> > https://infra.apache.org/github-roles.html
> > 
> > As described on that page:
> > > It is a good role for people who are interested in supporting and 
> > > contributing to the project, but who are not ready to be Committers.
> > 
> > I would like to ask you if it would be possible to grant me this role.
> > I'm happy to manage the issues and PRs and ping people for reviews.
> > My Github handle is: turbaszek
> > 
> > Best wishes,
> > Tomek
> > 
> 

[LAZY CONSENSUS] Rename Default Branch from Master to Main

[Sharan Foga]

Hi All

Many projects have renamed their default branch from master.[1] We still have a 
master branch so would like to rename this to 'main'. Tomek has already created 
an issue [2]

I'd like to use lazy consensus [3] for this decision so please respond to this 
message only if you disagree with renaming the default branch from 'master' to 
'main'

Thanks
Sharan

[1] https://github.com/github/renaming
[2] https://github.com/apache/kibble/issues/45
[2] http://community.apache.org/committers/lazyConsensus.html

Re: Triage role for contributors

[Sharan Foga]

Hi Tomek

Thanks for volunteering to help with triage. I took a look at the kibble github 
repo and I dont have authority to grant access. It sounds like a request to 
infra so I will request it for you.

Thanks
Sharan

On 2020/10/11 11:37:35, Tomasz Urbaszek  wrote: 
> Hello,
> 
> Quite recently Github introduced a new repository access level called
> "triage role":
> https://infra.apache.org/github-roles.html
> 
> As described on that page:
> > It is a good role for people who are interested in supporting and 
> > contributing to the project, but who are not ready to be Committers.
> 
> I would like to ask you if it would be possible to grant me this role.
> I'm happy to manage the issues and PRs and ping people for reviews.
> My Github handle is: turbaszek
> 
> Best wishes,
> Tomek
> 

Kibble tidyup on Github

[Sharan Foga]

Hi All

Some work is in progress to help improve and tidy up the Kibble Github setup. 
Thanks very much to Michal and Tomek for leading this effort. This includes 
things such as:

- Setting up a better issue reporting template to capture more information 
- Removing merge commits to enable a cleaner commit log

One other point to note is that we still have a 'master' branch. Many projects 
have already renamed their default branch and Github will be changing the 
default to 'main' so we will need to rename this at some point. I know that we 
still have some older pull requests so will probably need to review these 
before applying the branch name change.

Thanks
Sharan

Re: [DISCUSSION] Setting up Pre-Commit

[Sharan Foga]

Hi All

As there has been no negative feedback against this idea - let's move forward 
to put something in place. I see that Michal has already started a pull request 
conversation so please feel free to comment while the work is in process.

Thanks
Sharan

On 2020/10/06 21:02:51, Tomasz Urbaszek  wrote: 
> Hello all,
> 
> I heartily support pre-commits. It's an amazing framework that vastly
> automates code/content quality checking. We are using it in Apache
> Airflow where it helps us a lot.
> 
> Cheers,
> Tomek
> 
> 
> On Tue, Oct 6, 2020 at 9:58 PM Sharan Foga  wrote:
> >
> > Hi All
> >
> > Michal one of our new contributors has suggested setting up 
> > https://pre-commit.com/ as a first step in putting in place some checks for 
> > formatting and syntax to help with code quality.
> >
> > You can see the conversation in the github issue 
> > https://github.com/apache/kibble/issues/27
> >
> > I think this could be a very good way to get things started so would be 
> > willing to support this. What do others think?
> >
> > Thanks
> > Sharan
> >
> 
> 
> -- 
> 
> Tomasz Urbaszek
> Polidea | Software Engineer
> 
> M: +48 505 628 493
> E: tomasz.urbas...@polidea.com
> 
> Unique Tech
> Check out our projects!
> 

[DISCUSSION] Setting up Pre-Commit

[Sharan Foga]

Hi All

Michal one of our new contributors has suggested setting up 
https://pre-commit.com/ as a first step in putting in place some checks for 
formatting and syntax to help with code quality.

You can see the conversation in the github issue 
https://github.com/apache/kibble/issues/27

I think this could be a very good way to get things started so would be willing 
to support this. What do others think?

Thanks
Sharan

Re: Failed Sources in Kibble Demo: No Default Branch Found

[Sharan Foga]

Hi 

Just for the record I will be removing the following sources from Kibble demo 
as they have empty repositories:

https://github.com/apache/apachecon-site.git
https://github.com/apache/attic-tuscany-js.git
https://github.com/apache/commons-testrepo.git
https://github.com/apache/couchdb-fauxton-server.git
https://github.com/apache/couchdb-javascript-tests.git
https://github.com/apache/couchdb-query-server-spidermonkey.git
https://github.com/apache/fineract-cn-docker-scripts.git
https://github.com/apache/fineract-cn-integration-tests.git
https://github.com/apache/flex-asjs.git
https://github.com/apache/flex-falcon.git
https://github.com/apache/flex-tourjs.git
https://github.com/apache/flex-typedefs.git
https://github.com/apache/flink-libraries.git
https://github.com/apache/hadoop-downstream-tests.git
https://github.com/apache/incubator-pinot-private.git
https://github.com/apache/incubator-sdap-doms.git
https://github.com/apache/infrastructure-docker.git
https://github.com/apache/mynewt-nfc.git
https://github.com/apache/opennlp-corpus.git
https://github.com/apache/tajo-site.git

Thanks
Sharan

On 2020/10/05 18:39:09, Sharan Foga  wrote: 
> 
> Hi All
> 
> I saw that we have a few sources that are failing to process in the Kibble 
> demo. I have extracted the list and an going through them. The first error I 
> am working on is the 
> 
> "Could not sync with source
> Exception: No default branch was found in this repository"
> 
> I haven't been through the complete list yet but so far I have come across 2 
> things. Some of the sources are pointing to empty repositories (so in this 
> case the error is valid.. nothing there the sync). For these I will delete 
> the sources from the list.
> 
> The second case I am coming across are sources that have a different name for 
> the default branch (e.g develop or 1994-merge, etc) so am wondering if this 
> is something related the renaming of the master branches in Github. For these 
> I am not sure what to do - so wondering if we need to do any code or setup 
> change to pick these up.
> 
> Thanks
> Sharan
> 
> 

Failed Sources in Kibble Demo: No Default Branch Found

[Sharan Foga]

Hi All

I saw that we have a few sources that are failing to process in the Kibble 
demo. I have extracted the list and an going through them. The first error I am 
working on is the 

"Could not sync with source
Exception: No default branch was found in this repository"

I haven't been through the complete list yet but so far I have come across 2 
things. Some of the sources are pointing to empty repositories (so in this case 
the error is valid.. nothing there the sync). For these I will delete the 
sources from the list.

The second case I am coming across are sources that have a different name for 
the default branch (e.g develop or 1994-merge, etc) so am wondering if this is 
something related the renaming of the master branches in Github. For these I am 
not sure what to do - so wondering if we need to do any code or setup change to 
pick these up.

Thanks
Sharan

Re: New Contributor Pull Request to extend gitignore files

[Sharan Foga]

Thanks Daniel.

If you haven't done it already, I will merge it.

Thanks
Sharan

On 2020/10/05 17:45:17, Daniel Gruno  wrote: 
> On 05/10/2020 19.38, Sharan Foga wrote:
> > Hi All
> > 
> > We have a first time contributor who has submitted a change to extend the 
> > gitignore files.
> > 
> > https://github.com/apache/kibble/pull/33
> > 
> > It has no conflcts but I don't know what the consequences of the change so 
> > please can someone take a look and review it to see if it is OK to merge.
> 
> Looks fine to me.
> 
> > 
> > Thanks
> > Sharan
> > 
> 
> 

Creating a Personal Login for the Kibble Demo

[Sharan Foga]

Hi All

While adding Robert to the Kibble demo user list, I realised that most people 
seem to be using the Kibble guest login. This is OK if they want to look around 
but if they are wanting to create their own views etc, then it is a lot easier 
to do that under your own personal login.

At the moment the only people that have a personal login on the demo is myself 
and Robert, so if  you would like to have your own personal Kibble login for 
the demo then please do the following:

1. Click the sign up button at the Kibble login page and create a login
2. Send a note to the mailing list with the email address you signed up with so 
that we can add it to the default Apache organisation in Kibble

We used to have quite a few people in the Kibble demo user list, but perhaps 
that got reset at the last update.

Thanks
Sharan