On Apr 8, 2019, at 2:54 PM, Zak Burke <zburke@cornell.edu> wrote:Mike,
This sounds good to me. In particular, I think the emphasis on the lack of community-wide development issues in the 'what? no developers?!?' section is good. In fact, it should be comforting as it suggests the foundation is already solidly built and we've already dealt with most of the "How are we going to build...?" questions and now the work is to actually go build it.
This is not to say there are no open questions -- I can think of several related to localization, optimistic locking, data synchronization across micro-services -- but as you said, we need to identify these themes well in advance, plan the dates well in advance and away from quarterly deadlines, and figure out who the key players and decision makers are so we can either (a) get them in a room together to make the plan or (b) having made a plan, have them present it to the rest of the developer community.
Zak
On Fri, Apr 5, 2019 at 5:28 PM Mike Gorrell <mdg@indexdata.com> wrote:
Please provide feedback on this message to the PC:
The Tech Council met and discussed the FOLIO Working Meeting in June. The consensus was that it would not be productive to send developers to this meeting for a few reasons:
• There aren’t enough topics defined that warrant face to face interaction. While face to face meetings are inherently valuable they come with a cost
• In order to justify the expense of bringing developers together it was felt that we need to have an agenda that would contain hours worth of sessions that:
• Present detailed information on new directions/techniques/technologies/patterns that would impact a wide portion of the developer community
• Put forth pros/cons of open issues and allow some level of debate but ending with a decision
• Provide educational content/presentations that are applicable to the FOLIO developer community
• Timing-wise, this might be the worst possible week to have this meeting; our first “Go-live” release will be in its final sprint which will require close attention and quick action on any defects or issues that arise. We can’t jeopardize the July 1 release.
For these reasons we recommend that no developers attend the meeting. If anyone is needed for a particular session we should use Zoom to connect them into the meeting. There may be a few individuals that are important for enough meetings that they might consider attending.
The Tech Council did see value in meeting to review its charter, processes, long term tech roadmap, etc. Our ideas for meetings have been added to the master list.
Note that we discussed how other developer meetings are valuable. We recommend the project consider the follow approach:
1) Set the dates well in advance
2) Schedule mid-quarter (most disruptive at the beginning/end of each quarter). This means February, May, August or November.
3) Establish a theme for each meeting
4) Solicit papers/topics/etc. well in advance
5) Run the meeting much like tech conferences - themes/tracks/etc - focus on learning and presentations
Please let us know if you have questions or comments.
-mdg
To unsubscribe from this list please go to http://archives.simplelists.comTo unsubscribe from this list please go to http://www.simplelists.com/confirm.php?u=SeK0ArgpLZB2ijVHc1q8eivZ4CXy8J2w