...
| Time | Item | Who | Notes |
|---|---|---|---|
| 1min | meeting start | group | |
| 20 15 min | Productization Update | Riko Eksteen, Espen Overbye | Update from the productization task force 20 |
| 10 | Mono-repo Update | Riko Eksteen, Espen Overbye, Former user (Deleted) | Implications for on-going work
What form of permissioning will be need across the different folders? |
| 15 min | General Meeting (Technical Steering Committee) Questions | group | Rob raised some good questions about the general meeting focus and structure. Let's discuss: (from Rob) I wanted to get a discussion going, which maybe we can pick up at the next PMC meeting, about the purpose, viability, and intent of the FDC3 general meeting in the long term. In the abstract, I get it -- we want a monthly forum to get feedback from the wider community. But on the calls I've been on, not just today's, it seems like the bulk of the conversation is the "regulars" and we get precious little feedback from the community that is not on our usual WG and PMC calls. Curious what the PMC's take is. Is there more we can and should do to promote feedback on the call from the wider community who we only hear from on this call? Are there things we can do to promote attendance? Can we better frame in concrete terms why we've invited the general community to the call and what we'd like to hear from them about there? What can FINOS do better? Everyone is so busy -- it's important that every meeting like this we do be seen as valuable use of each respective attendee's time. If we're just doing this call to do it, without a clear purpose, we should consider scrapping it, or maybe doing it, say, less often (e.g., quarterly). Also, I think we probably need to clarify once and for all of this is the "general meeting" or "technical steering committee" meeting? |
| 10 min | AOB | group |