Hey folks, If there are people willing to contribute to Apache Kibble it may be good to revisit the proposal for 2.0 version [1]. It's not very deep but as far as I remember the kibble-1 code required a lot of love and work. I did some refactoring a while ago but it seemed more reasonable to potentially start from scratch.
[1] https://lists.apache.org/thread/q2p5g7vgqh463n9k969990txg6k2ry6w On Mon, 14 Apr 2025 at 10:34, Kallidis, Georg <georg.kalli...@fu-berlin.de> wrote: > Hi Sharan, hi Sebb, > > Sharan did summarize it very well IMO. I might add that kibble-1 and > kibble-scanners projects are tightly coupled. > > When I started last year I investigated first in what might be the future > kibble, but I wanted just to understand first the running code, before I > could do this and actually wanted to understand the output of the reporter > tool. > > That was my intent and the starting point for me. I then ended up to test > kibble-1 and kibble-scanners, which was quite fun! The last thing I did, > was submitting a pull request with some basic project environment settings > (toml) to allow for a release, which required some changes in the module > structure (which might break current envrionments). > > What might be next, is to create a kibble-1 release together with > kibble-scanner and to truly tell the world, that kibble github repo is > still a working draft, which might need much more to do IMO and a much more > active community. Nevertheless thinking about next steps here for kibble > "future", it should be broken down into smaller pieces .. ? > > How I might contribute? Though I am a more casual python developer, who > happened to get this done by chance in the last couple of months in 2024, I > am nevertheless currently in two other Apache (Java) PMCs with also quite > some stuff ahead to do as well - that said, I truly could not find much > time this year to continue developing in kibble. I might assist in > releasing it, but it might or might not take some time .. > > A different issue is of course to align the Git repo with the SVN > repository, either this should be done after the release or before - ? > > Best regards, Georg > > " All the communication we put out there said the Kibble-1 repo was no > longer being developed and then things went quiet - so to try and some > activity off I suggested that rather than starting from scratch - perhaps > we could do a release of the code we have running as the demo while rethink > our approach for what to do next. > We got a few contributions to Kibble-1 from Georg who had done a test > install and thought that we might be able to move forward with the > Kibble-1 codebase with some fixes. > So the working codebase is in Kibble-1." > > ------------------------------------------------------------ > > -----Ursprüngliche Nachricht----- > Von: sharanf <sha...@apache.org> > Gesendet: Sonntag, 13. April 2025 17:30 > An: dev@kibble.apache.org; sebb <seb...@gmail.com> > Betreff: Re: Final appeal to anyone willing to help develop Kibble > > Hi Sebb > > See some responses inline. > > On 4/13/25 15:56, sebb wrote: > > On Sun, 13 Apr 2025 at 14:23, Sharan <sha...@apache.org> wrote: > >> Hi All > >> > >> We've been struggling to get any real progress or work started on the > >> project so am making a final appeal to anyone is willing to come > >> onboard as a potential committer or PMC member to help develop the > >> project. It's been a while since we had any community activity. I've > >> tried to keep things moving by responding to queries and questions > >> but I'm not a developer so cannot answer any technical or code > >> related questions. This means that we don't have any way to help or > >> mentor any potential new code contributors. > >> > >> From my side - I am taking a break from ASF activities for while > >> due to personal reasons and so won't be able to continue oversight > >> of Kibble as needed by the board so it be good to find others willing > >> to take over, review where are, plan and then help move the project > forward. > >> > >> If we can't sustainably keep Kibble going then we need to seriously > >> think about starting a vote to take the project to the attic. It's an > >> unfortunate situation but it's where we are. > >> > >> Please respond if you are willing to help keep Kibble alive. > > I have looked at it a couple of times, but cannot fathom where > > development is supposed to be happening. > > The most recent changes have been to Kibble-1, but that repo says that > > it is obsolete. > > Thanks for looking! > > What happened was that we cleared down the repo and moved everything to > Kibble-1 in preparation for starting the rewrite for the Kibble repo but > then nothing was really started. All the communication we put out there > said the Kibble-1 repo was no longer being developed and then things went > quiet - so to try and some activity off I suggested that rather than > starting from scratch - perhaps we could do a release of the code we have > running as the demo while rethink our approach for what to do next. > > We got a few contributions to Kibble-1 from Georg who had done a test > install and thought that we might be able to move forward with the > Kibble-1 codebase with some fixes. > > So the working codebase is in Kibble-1. > > > > > Also, this email is just going to the developer list, which does not > > have a large subscription. > > > > Maybe consider an email to some ASF Python projects? > > Also dev@community, since I believe reporter.a.o make use of Kibble? > > I did reach out to the ASF Tooling team to see if Kibble could be > interesting for them to take over as it does can provide project wide > statistics (It probably needs a bit of a tidy up to pickup any incubating > or new projects) > > An SVN repo of an earlier version of Kibble was used to create some of the > stats for the reporter.a.o tool - so I don't think it's looking at the > Kibble-1 repo (unless the SVN repo has been moved). The thing I'm not sure > about is whether the reporter tool uses the same DB as Kibble does to pull > the data from as the Kibble scanners run everyday so the data would be > there already to read if needed. > > If I get a chance I will try and post something to the comdev list. > > Thanks > > Sharan > > > > >> Thanks > >> Sharan > >> > >> > >> > >> > >> >
