some comments were queued up as review comments
Ulf: I already addressed a number of the smaller ones
Gunnar: prefer a group discussion on the more fundamental topics
Ulf: certainly more to discuss but think it is better to merge now and raise those issues
Gunnar: fine with broad strokes and further refinement as subsequent changes
Ted: I agree with your comment Gunnar that subscribe doesn't make as much sense on REST requests. regarding filter returning too much results, there is risk of developer requesting too much in any query interface
Gunnar: I would like to see improvement on decisions on call
scope for BG will basically be formalizing VSSo that EURECOM will bring over, Best Practices for apps in-vehicle and several aspects of data handling in the cloud, a joint task force with Spatial Data on the Web Interest Group on additional ontologies - we will have a draft one for routing from OGC public soon, and the graph project
Magnus: depends on the scope of the best practices
Ted: some of the in-vehicle and offboarding best practices will come from a telematics security assurance grant project between US DOT Volpe, Colorado State, MIT, UL and Geotab
Magnus: ITS and their station to
station communication is nearby
... looking forward to more details
... my interest area is in-vehicle and toward external
endpoint
Gunnar: makes sense to look more
widely about the needs in this space
... routing data model makes sense to me more than memory
footprint etc for in-vehicle apps
Magnus: AutoSAR meeting f2f
monthly and 5G group every few months
... I feel we have good progress during our f2f meetings and
wonder if we should change the frequency
Ted: maybe with a third day - more hands on hackathon than just discussing topics
Ulf: I agree. it is not only
working methods, we have had other sorts of problems
... somewhat converging
Gunnar: in github it is possible
to enable project management support
... we agreed on prioritizing certain tickets but not
formalized
... we can visually see which issues will be discussed on a
given day
... I noticed in the kanban board issues and PR are treated the
same
... in some cases they are redundant and you do not need a
separate ticket
Ulf: it sounds like a good idea, is it easy to get into?
Gunnar: we can use it to manage
what will be our group call agenda
... this aligns with Peter's desired organization
... my proposal is to use kanban and try to avoid duplicating
issues and pull requests
Ulf: I assume it easy to revert and stop using this tool
Magnus: it looks easy to create
one and just tried it
... think repo owner needs to do it
Ted: I can look into it
Magnus: let's try it
https://github.com/w3c/strategy/projects/2 -> W3C strategy funnel
Magnus: you can edit and add
columns as you go
... I'm afraid to add blocked column in this group...
Magnus: setup to run as a docker
right now, geared to localhost
... it would be nice (hint, hint) to have someone host an
instance soon
Ulf: Ted replied he is somewhat prejudiced against docker
Ted: docker are great for quick easy evaluation. I kind of have a pet peeve against running them on a public server, you are dependent on docker image maintainer keeping up with security updates, have to be careful to preserve your custom configuration on image updates, etc.
Magnus: when docker builds image it updates and downloads the dependencies
Gunnar: it is possible to have
these tied to underlying OS and auto update
... possible to cron rebuild and restart container but that
depends on docker base images
... on the other hand you gain security in being inside a
docker container
... docker falling out of fashion somewhat to other
containers
Magnus: like which?
Gunnar: podman
... it is learning from mistakes of early docker issues. docker
too are keeping up
Ted: happy to host as is Gunnar, I can be persuaded to relax on docker
Magnus: choose golang or docker tool setup
Ulf: agree with that
Magnus: I would be happy for someone to clone repo and try it out, working on my computer but not others
Ulf: I will try
Gunnar: I can too and put on a public IP