sebbASF commented on issue #10:
URL: https://github.com/apache/kibble/issues/10#issuecomment-1146890125
Yes, the URLs are OK now
--
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 comme
sharanf commented on issue #14:
URL: https://github.com/apache/kibble/issues/14#issuecomment-1146877297
Hi @esmiralhaibm Yes we are!. If you are interested then come along and join
our mailing list at dev@kibble.apache.org
--
This is an automated message from the Apache Git Service.
To re
sharanf commented on issue #10:
URL: https://github.com/apache/kibble/issues/10#issuecomment-1146876855
Thanks @sebbASF. Hope they are fixed and working now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abov
esmiralhaibm commented on issue #14:
URL: https://github.com/apache/kibble/issues/14#issuecomment-1146859080
> Hi @pbrubaker. The answer to the question is no - not yet :-).
Unfortunately we don't have any active volunteer developers in the community at
the moment so this is why there is a
sebbASF commented on issue #10:
URL: https://github.com/apache/kibble/issues/10#issuecomment-1146841976
The URLs in the previous comment both resolve to
https://github.com/apache/kibble/issues/url which does not lead anywhere useful.
--
This is an automated message from the Apache Git Ser
sharanf commented on issue #10:
URL: https://github.com/apache/kibble/issues/10#issuecomment-1146839642
I started investigating the failed sources. We had around 150 to start with.
It looked like some were caused by default branches with unsual names so I
created an issue in the kibble-scan
sharanf commented on issue #14:
URL: https://github.com/apache/kibble/issues/14#issuecomment-1146837112
Hi @pbrubaker. The answer to the question is no - not yet :-). Unfortunately
we don't have any active volunteer developers in the community at the moment so
this is why there is a lack of
