...
Minutes
- Aaron Birkland walks through task list
- Josh on implementation section: good to move ahead with implementation tasks without having completed all the design work first. Since design is very abstract, simplifying assumptions present in implementation could serve as a 2nd phase proof of concept to help solidify design ideas.
- Observations and concerns over API-X performance on Fedora could be discussed with the performance/scalability community at one of their meetings. Nick Ruest encourages adding the topic to the next performance/scaling meeting’s agenda. Latency issues had been in discussion with the community before
- Latency/memory leak investigation task may be aided by some tools Andrew Woods has license key for; get in touch with him for more details.
- Nick Ruest wondered about the approach for CLAW investigation, suggested a side call might be appropriate.
- The person who takes the github issue will be the point person but agreed that having a point person
- CLAW working group’s weekly tech calls on Wednesday to be used for such discussion.
- Nick Ruest will make it a point to read over the document (tasks list?) very well and look out for potential overlap so that duplicated effort can be avoided, experiences can be shared
- Design/development for next two weeks
- Aaron Birkland in-progress for some tasks on list, will reflect this when github issues created
- SD&B scope, service invocation model seem particularly high priority design tasks to finalize
- Integration testing setup also fairly high priority, can be done now
- Make sure that any code intended for OSGi deployment is tested in OSGi runtime (e.g. pax exam, docker+Karaf)
- Docker would be great for ITs that involve non-java code (e.g. a php script)
- Make sure that any code intended for OSGi deployment is tested in OSGi runtime (e.g. pax exam, docker+Karaf)
- Joshua Westgard volunteered for wiki gardening.
- Aaron Birkland to enter in tasks, then folks can comment/prioritize in github
- Body URI substitution results promising
- go-proxy (written in go) quick 'n easy for trying things like this out.
- Aaron Birkland writing a doc explaining the motivation for this as an API-X function, and how to avoid needing this in the first place.