15 min | Meeting logistics: - Attendees somehow add their own names
- Create an ongoing agenda to better track topics
- Trial of shorter meetings for September? Start at 9:30 or 10am ET?
| | - PC agrees on shortening the meeting to one hour
- PC agrees to start at 10 am ET
- REducing the meeting frequency would make it easier to prepare topics, but we will start with reducing the meeting time
- Brooks in chat: And we need to get better about having extended conversations on meeting topics asynchronously, to make it easier for folks in inconvenient time zones to participate.
- Meetings are on the Wiki calendar
- Record attendance: Martina Tumulla will note the attendance for PC meetings, so that note talers can concentrate on taking notes
|
45 min | Follow up from WOLFCon PC shoulder meeting "what can we do this year?" discussion https://easyretro.io/publicboard/0ALmBRbRDFgKpGdILQIAZio6Nvq1/50ab1c13-8eb5-417a-abff-5742305828de Forming subgroups: Also under https://folio-org.atlassian.net/wiki/display/PC/Product+Council+Sub+Groups. You'll see all 4 at the end of the 1st table. For the moment, the goals and other information is blank. Once the groups form, someone can fill this information out. | all | - How large should the subgroups be: max. 4 members per subgroup
- PC members should at least join one
- we will be starting with subgroups:
- Question: what is the output supposed to be of the subgroup Re-architecting's impact on PC
- it is to discuss Vince's presentation
- PC wants an input on time period of the presented process
- TC members will provide some non-technical questions that need addressing
- Owen in chat: I’m just really struggling to see how a definition of how we have applications and platforms defined in the future doesn’t impact on the product?
- this was discussed and agreed on in the tri-council meeting also
- rewrite description, not everyone has attended the session, we need to catch up and reach same information level, then re-word the wiki page
- subgroup needs to do some catch up, and then come back to the PC
- task: define role and bring back to PC for approval
- there might be changes for PC's work
|