> And if we did manage to get a few more active people then we might also be > able to help Comdev out with the reporter tool since it uses and some of > the Kibble code but in an SVN repo.
Hi Sharan, I just realized the PRs in kibble-1 and kibble-scanners are merged. Thanks!! I'll check it soon .. What I prepared before .. I will give here some feedback, what I have learned about Kibble the last weeks. ------------------------ INFRA-26246 pointed me to COMDEV to Kibble I have now finished tests and updates. Most of I needed to do to get it installed with ElasticSearch 8 was successfully. I still get some index update errors, which might be due to EL7/8 update (kibble-1 code still supports EL6), which I could try to fix in kibble-scanner soon (either updating the PR pull/10 or opening a new PR). Actually the results of my first bug issue might more trivial. In COMDEV kibble (demo) installation just a lot of repos (about 500?!) did not run for more than 5000 hours. Why? Of course, some failures occur, e.g. for https://github.com/apache/lucene-site.git because git remote prune origin seems to be needed (?) Some repos are showing an error "Could not read from remote repository", that is, they do not exist any more (?) I think, this had been previously reported here: https://github.com/apache/kibble/issues/10 and I would suspect this is a recurring issue. --------------- About what Kibble 2.0 might become .. I found some important code changes in the pipeline: - unmerged branch from Dec 2020: https://github.com/apache/kibble-1/commits/2.0/ - a document from February 2021 (in dev@kibble.apache.org: https://lists.apache.org/thread/q2p5g7vgqh463n9k969990txg6k2ry6w - unmerged PR (Mai/June 2021) https://github.com/apache/kibble/pull/8 In my eyes the PR seems to be quite the best next step to proceed (including a docker image), the document the mindset behind. The first unmerged branch was apparently a first step, which could be revisited, but would need more work. Nevertheless what seems to be true: - Keep on to bugfix and improve kibble-1 and kibble-scanner to provide a reliable production-ready version. - Nevertheless try to understand Kibble 2.0 more and if capacities are available proceed there also. IMO Kibble-1 could be maintained with smaller adaptions due to EL (database) changes and other fixes. Kibble 2.0 is envisioned as starting with an OpenAPI based FastAPI server (reading the document above), but since 2021 work has stopped :( --------------- Releases One important accomplishment for kibble-1 would be to allow for a release. Some considerations have been done in the kibble mailing list and in the document above.There is already mentioned to ship kibble as python package - pypi may be the best build and release ASF does support it (?) (incubating) and has already some preliminary information about this: https://incubator.apache.org/guides/distribution.html#pypi Quite a lot of project are already to find in pypi: https://pypi.org/search/?q=apache- That is a build system might be introduced and then a release might be not done!? --------------- Pre-Commit I found some information about this in kibble and kibble-1. When running this in kibble-1 a lot of files would be updated.. This is quite important, but needs more documentation and might have also its caveats for e.g windows systems. It could also done as a build step, or other kind of action .. -------------- Generally If a PR is merged some tests should be done? As a first step, as PyTest environment is still missing from kibble-1, which might be changed easily. Jenkins (cibuilds) builds might be used as well after a build system is available .. Best regards, Georg On 2024/11/14 13:34:56 Sharan F wrote: > Hi Georg > > Our project is struggling to get people involved and you seem like someone > who might be interested in being part of the community and help maintain > Kibble. > > Would you be interested in that as we need active people to move the > project forward? > > For example we have never made a release and we did discuss fixing up > Kibble-1 and the scanners as a release since we haven't made any progress > with the redesign. > > And if we did manage to get a few more active people then we might also be > able to help Comdev out with the reporter tool since it uses and some of > the Kibble code but in an SVN repo. > > Anyway - let me know your thoughts. > > Thanks > Sharan
