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
> 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.
> 2) What can we do we ensure tha
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 depe
+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 sho
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
