IOG Funded Cohort Communication Issues

[stephen-rowan]

IOG Funded Cohort Communication Issues

The Fund 5 Project "Quality Assurance DAO" is tasked with the documentation/tracking of :

• The pathway of a funded cohort and • An assessment of funded cohort reporting requirements.

The pitfalls of synchronous communication on Telegram

• [x] A major issue with the use of Telegram for inquiries is that its synchronous nature leads to rapid loss of information and an incessant repetition of questions.

  I agree. I suggest to keep track of pinned messages for now in this telegram chat or via announcement channel that only has important updates listed there as of recent. In general there are two key things for coordinator members to keep track of - bi weekly reports and coordinator meetings. Both of which are static scheduled events. Zoom event can be added onto calendar as recurring event. Reporting form can be, perhaps, bookmarked - as well as the public document showing completed reports. However, please chat with Roberta to see what else can be done in this regard and find out where we can support each other. Let's knock this out of the park together. <3

Lack of a website for a Funded Cohort FAQ

• [x] Who are the IOG Team who support the Funded Cohort ?

  Listed during onboarding call, included in the slide deck which was there on the first day and circulated to all members. Purpl1, Marklar_IO,and myself originally. Now, we are onboarding new team members, Khalid and Roberta to help with Coordinator specifically and something I am very excited about personally. One of the first tasks that we've been working on is new reporting mechanism and improved communication cadence including repo of information available.

• [x] What are their roles and responsibilities ?

  Generally listed on the onboarding call and slide deck. For any inquiries myself primarily and Marek for everything related with release of funds. With introduction of new team members to look after Coordinator specifically - some of these responsibilities will shift somewhat towards these new team members to allow for greater bandwidth.

• [x] How do I contact them ?

  All e-mails listed on the onboarding slide deck and are all part of this coordinator chat. I trust you know where to find me by now as I have been circulating quite a few e-mails over the period of past months. Marek's email also must be very well documented because he has been coordinating proof of life and dispersion of funds. This coordinator chat was also set up primarily to ensure that whenever you have questions - we or fellow members can swiftly assist you. We are also considering a dedicated e-mail address for all things Coordinator.

• [x] What is the timetable of cohort reporting ?

  Bi-weekly aka every two weeks. All listed for each individual Fund under own respective tab as presented during one of the Coordinator meetings in the past and during one of the recent town halls: 👉 Public Reports: https://bit.ly/3DcyVBo

• [x] Where and when are cohort meeting recordings uploaded ?

  Generally Zoom cloud/occassionally gDrive and shared into coordinator chat once available. Last meeting pending as this week is mad with Summit and all. Generally shared as soon as possible after meeting is done, but at least in the same week that coordinator meeting takes place. Needless to say, email round ups will be sent to all particpans as well solid reminders to submit reporting forms. New help on the team is primed for this.

Issue management

• [ ] Does the IOG Team who support the Funded Cohort maintain an issue log ?

[kiriakos]

Interestingly, just having a github repo for reporting and ops might be easier :thinking: We are seeing github usage for non code intents all around the Cardano Community, stuff like essential-cardano, CMDP Donations and even this repo!

[stephen-rowan]

Interestingly, just having a github repo for reporting and ops might be easier 🤔 We are seeing github usage for non code intents all around the Cardano Community, stuff like essential-cardano, CMDP Donations and even this repo!

A GitHub repo might be a solution to issue management for funded cohort. Although for some this may present accessibility issues (these could be overcome with integration with Telegram or Discord). Unfortunately this repo is quite narrowly scoped and under funded (as per my F5 proposal) - so is likely to raise more questions regarding QA of funded cohort than answer them in its lifetime. The best solution to an Funded Cohort Issue Management repo would a collaborative project.

I do hope to provide some resourced answers in my Fund 6 Proposals, particularly Distributed Auditability (https://cardano.ideascale.com/a/dtd/Distributed-Auditability/366707-48088) and Open Source Training (https://cardano.ideascale.com/a/dtd/Open-Source-Training/368678-48088).

[stephen-rowan]

Added responses in main body of issue from Daniel Ribar posted on Telegram (https://t.me/c/1556514618/695)

Just a note: we have static FAQ page planned to introduce and will help with many Coordinator/Funded projects inquries but also for those who are aspiring to start funding process and wish to see more visibility into the future. Which also has been not as good as we'd like it to be. We are working on making it better.

Appreciate you, swhitenstall. And I hear you loud and clear.

[stephen-rowan]

My response for reference - https://t.me/c/1556514618/696

Thanks Daniel, much appreciated. I will transfer you answers to the GitHub issue and update my own F5 QA-DAO proposal Gitbook. You refer to the onboarding call and its associated slide deck - where can I find a recording of that and where is a static location for the onboarding slides? The onboarding email (August 17th 2021) only lists links to the Telegram Announcements and Chat. If a cohort missed the synchronous information, they would be led to ask these questions again. I know I can contact you or Marek etc. - but for what issues (again roles and responsibilities), in public or private, and on what platform (e.g., my email remains answered)? Again, an asynchronous option would relieve the burden of FAQ inquiries. I will contact Roberta as you suggested to work together on resolving these issues. I hope the IOG team understands that it is the brief of my F5 project to ask these questions and document the cohort process as I find it – these are my deliverables. All the best. S

• [ ] - Where can I find a recording of that and where is a static location for the onboarding slides?
• [ ] - For what issues can IOG members be contacted (again roles and responsibilities), in public or private, and on what platform

[stephen-rowan]

Hi Roberta, Daniel suggested I contact you in respect of issues I was raising in respect of the "pitfalls of synchronous communication on Telegram" which I have documented in this GitHub issue ( https://github.com/Quality-Assurance-DAO/F5-Developer-ecosystem-Proposal/issues/141) as part of my F5 Quality Assurance proposal. Daniel answered a lot of my questions - but left the major issue of having a static, asynchronous source of information for funded cohort unanswered. A single place where a cohort FAQ, report timetables, cohort meeting recordings etc can be referenced. I would like to work with IOG and funded cohort to address these issues and would be very interested in your perspective. All the best. S (QA-DAO)