Page Comparison

Technical Council Sub Groups Updates

Your FOLIO related work will be coordinated by the chairs of the three councils (Community, Product and Technical) with special assistance from the Tech Council. You will retain your current organizational manager for all personnel-related matters.

What is the nature of the TC's role in assisting in the coordination of the Developer Advocate's FOLIO-related work?

The council members discuss the logistics of the position, including how to coordinate with the developer advocate, manage documentation updates, and provide support. There is debate over whether the developer advocate should report directly to the technical council or to the council chairs. Members express concerns about the clarity of the role and the support provided to the advocate, highlighting the need for further discussion and clarification.

1. Clarify Reporting Structure: Determine whether Patrick will report directly to the Technical Council or to the Council chairs. Assign responsibility for managing Patrick's day-to-day activities and ensuring alignment with Folio's objectives.

2. Define Role Expectations: Clearly outline Patrick's responsibilities and role within the Folio community, specifying how he will contribute to the Technical Council's initiatives and objectives.

3. Onboarding Plan: Develop an onboarding plan for Patrick to familiarize him with Folio's projects, technology stack, and community dynamics. Assign mentors or buddies who can provide guidance and support during his initial period.

4. Integration Strategy: Decide on an integration strategy for Patrick within the Technical Council's activities. Determine whether he should actively participate in TC meetings from the beginning or gradually ease into his role.

5. Support Mechanisms: Establish support mechanisms within the Technical Council to assist Patrick in overcoming any challenges he may encounter. Encourage open communication and collaboration among TC members to facilitate Patrick's integration and success.

6. Regular Check-ins: Schedule regular check-in meetings between Patrick and his direct supervisor or mentor to evaluate his progress, address any issues or concerns, and provide feedback and guidance as needed.

7. Documentation: Document Patrick's role, responsibilities, and onboarding process to ensure transparency and consistency. Create resources and guides that can help him navigate Folio's projects, community guidelines, and best practices.

8. Feedback Mechanism: Implement a feedback mechanism to gather input from both Patrick and TC members regarding his integration progress, areas of improvement, and any adjustments needed to optimize his performance and contribution to the community.

Proposal: 

The Technical Council discusses a proposal for a presentation at Wolff Con. The presentation aims to highlight the top three technical topics for community discussion. The proposal serves as a placeholder, subject to refinement closer to the event. The Council agrees that the proposal can be submitted as is, with the option to update it later. There is consensus that the proposal effectively communicates the intended purpose of the presentation. With no objections raised, the proposal will be submitted for consideration.

Officially Supported Technologies (OST)

Topic Backlog Grooming

00:07:54	Marc Johnson:	What happens if the MOU is not renewed?
00:08:31	Maccabee Levine:	Replying to "What happens if the ..."

FOLIO explodes.  No, the point is just to generate discussion about whether that functionality is still needed/desired, and if so who might take it on.
00:08:44	Maccabee Levine:	MOU: https://docs.google.com/document/d/183G5ZhxZS3hfqbjWu3FAukQGSdh9_jBl/edit
00:10:08	Jakub Skoczen:	Guys, is anyone handling scribe duties?
00:10:24	Huff, Jeremy T:	Replying to "Guys, is anyone hand..."

Taras has it
00:11:43	Jakub Skoczen:	Replying to "Guys, is anyone hand..."

K, thanks and sorry for being late
00:13:19	Marc Johnson:	Reacted to "FOLIO explodes.  No,…" with 👌
00:20:55	Maccabee Levine:	Job description: https://docs.google.com/document/d/1esuP2nNke051LJ9PcmfiuG8z-E4ZlJyxMsNGtJQU-jk/edit
00:22:27	Maccabee Levine:	Lead the management and updating of developer documentation, with a focus on gaps identified by new developer questions.
00:36:23	Ingolf Kuss:	We should give that person room to participate and ask questions.
00:37:10	Owen Stephens:	We don’t need to know what they will be doing to ask them what help they need, and advising whether the TC can help with those things
00:39:04	Maccabee Levine:	Reacted to "We don’t need to kno..." with 👍🏻
00:39:28	Maccabee Levine:	Reacted to "We should give that ..." with 👍🏻
00:39:51	Marc Johnson:	Replying to "We don’t need to kno…"
I don’t think I follow. How can they know what help to ask for if they don’t know what they are doing?
00:40:23	Marc Johnson:	Let them drive what?
00:40:52	Marc Johnson:	Who decides what they do?
00:40:58	Owen Stephens:	Replying to "We don’t need to kno..."

I don’t expect them to know on day 1, but the position scope seems reasonably clear to me, and they have direction from the council chairs
00:41:05	Marc Johnson:	Are they meant to be self directing?
00:43:21	Marc Johnson:	My main point was that we make sure it’s well understood who they talk to for direction 

I’m not especially fussed that it’s a group (as long as the group knows what they want)
00:46:52	Owen Stephens:	It is not their job to establish best practices, but to encourage & reinforce already established best practices
00:47:02	Owen Stephens:	That’s where I think the TC has a stake tbh
00:47:30	Ingolf Kuss:	Reacted to "That’s where I think..." with 👍
00:47:44	Ingolf Kuss:	Reacted to "It is not their job ..." with 👍
00:48:39	Marc Johnson:	Replying to "It is not their job …"
I think that is where I don’t understand the role properly 

FOLIO has very little established practice in many areas, if they aren’t going to define that then I’m not sure how they can encourage it
00:51:28	Owen Stephens:	Replying to "It is not their job ..."

Not sure I completely agree - my impression (and I may well be wrong) is there is a whole load of established practice that is not well enough documented OR it isn’t easy to find what it is for developers coming to the project for the first time
00:51:41	Ingolf Kuss:	Reacted to "What topics of signi..." with 👍
00:55:03	Marc Johnson:	Replying to "It is not their job …"
It’s probably a combination of my poor understanding and a different understanding of practices that means I don’t have as much confidence in that