weave
weave copied to clipboard
weaveworks
Opening up development of Weave Net
To those of you who responded in the discussion of #3939, thanks a lot for your ideas and offers of help so far! :sparkling_heart:
Weaveworks wants to open up the development of Weave Net and in order to bring interested folks together, get to know each other and discuss ideas, we would like to arrange a meeting soon. :calendar:
If you are interested in joining, please comment on this issue, so we can let you know when it's going to happen, or give you a ping for a doodle we've set up. Thanks a lot everyone in advance!
CCing @monadic and @kingdonb
Hi folks, we'll target in a meeting in the last week of JUNE 2022. I'll choose a time for the community meeting, which will likely be around 7am Pacific / 3pm UK.
Great -- here is the Meeting URL to join
Weave Net community meeting Wednesday, August 10 · 4:00 – 4:40pm UK (8am US Pacific)
Google Meet joining info Video call link: https://meet.google.com/ydc-wwtn-xye Or dial: (GB) +44 20 3910 5019 PIN: 732 425 366# More phone numbers: https://tel.meet/ydc-wwtn-xye?pin=1413075876243
Next meeting 31 August!
weave net open meeting Wednesday, August 31 · 4:00 – 4:50pm Google Meet joining info Video call link: https://meet.google.com/fjy-msnk-fcq Or dial: (GB) +44 20 3956 9319 PIN: 208 155 944# More phone numbers: https://tel.meet/fjy-msnk-fcq?pin=2035335265953
So the next steps:
- we have a core group of 3 people who want to move the community forward
- we want to get this to 10 or more
- weaveworks will support as much as possible - our only asks are "goes into CNCF" and we are all good community members!
-alexis
Which of the following do we need most at this point?
- Regular maintenance, release publishing, documentation updates, pull request curation, regressions against newer library versions etc.
- Further development, feature additions etc.
- Creation of new processes and structures to make the project more suitable for community participation and CNCF inclusion.
I think that, at this point, (1) is most important - just to keep weave net where it is. Maybe interested community members can begin by sharing some of that responsibility.
Sorry I missed the meeting. Mistimed it by one hour because of a silly timezone mistake.
Which of the following do we need most at this point?
- Regular maintenance, release publishing, documentation updates, pull request curation, regressions against newer library versions etc.
- Further development, feature additions etc.
- Creation of new processes and structures to make the project more suitable for community participation and CNCF inclusion.
I think that, at this point, (1) is most important - just to keep weave net where it is. Maybe interested community members can begin by sharing some of that responsibility.
Sorry I missed the meeting. Mistimed it by one hour because of a silly timezone mistake.
1 is the most important!
I would agree (1). Triage on issues, fix high priority ones, also update dependencies.
thank you to @rajch @nathanejohnson and others for help and enthusiasm so far
this is the PLAN
- we shall make a community document that states the goals for the next 6-12 months
- priority is maintenance and regaining momentum as a self-sustaining community
- we shall have a monthly open community meeting online to discuss and vote on a PUBLIC ROADMAP which will lay out near term priorities, how to help etc
- step one is that I shall work on this with @rajch @nathanejohnson who will post link below so that others can help
- overall aim is to get to X new maintainers by time (some time in 2023) to be determined
- governance will aim to cede more control as trust builds up until the project is governed by a strong community
- ex maintainers have offered to help with this process
next public meeting will be 28 Sep at 4pm UK // 8am Pacific
--alexis
I have written up a basic outline for the roadmap here. Just broad headings, with a few points that I thought of. If the structure is okay, I shall continue to fill it in.
The Google doc is public editable. Feel free to jump in.
Some things that we can do/should do with the aim of CNCF inclusion:
- Start gathering a list of adopters (people or projects that are using weave net right now). See here for a definition of "adopter".
- Consider the CNCF IP Policy.
Full details about the graduation process can be found here.
I've been disconnected for a bit. Did the public meeting on 28th September happen? What did I miss?
Proposal for new install endpoint
The recommended method for installing weave used to be this:
kubever=$(kubectl version | base64 | tr -d '\n')
kubectl apply -f https://cloud.weave.works/k8s/net?k8s-version=$kubever
This would redirect to the simpler url:
https://cloud.weave.works/k8s/vX.YZ/net.yaml
which would generate a manifest appropriate to the version of kubernetes. In the current release of weave (2.8.1), there are four possible manifests: weave-daemonset-k8s-1.8.yaml, weave-daemonset-k8s-1.9.yaml, weave-daemonset-k8s-1.11.yaml, and weave-daemonset-k8s.yaml. The last one was added recently, and the documentation was updated to use that from the release, like this:
kubectl apply -f https://github.com/weaveworks/weave/releases/download/v2.8.1/weave-daemonset-k8s.yaml
I propose that the community create and maintain an endpoint like the old https://cloud.weave.works/k8s one, to ensure that the endpoint remains the same for potential future releases of both weave and kubernetes. This could re-use the old weave cloud code, or be a fresh implementation.
I can take this up if other people think this is a good idea.
Is anyone going to Kubecon NA? Perhaps we could meetup if there are a few of us going?