input-output-hk · aleeusgr · Jun 1, 2023 · Jun 1, 2023 · Sep 13, 2023 · Sep 13, 2023
diff --git a/CHARTER.md b/CHARTER.md
@@ -44,7 +44,7 @@ Positions and names to be agreed and confirmed in the coming sessions as the gro
 
 Chairpersons:  
 * Ben Hart
-* Alex TODO
+* Alex Seregin
 * Phillip DiSarro
 
 4.3 Chair Selection
@@ -61,7 +61,6 @@ Chairpersons:
 
 4.5 New members 
 
-
 This is a community-led initiative so we encourage members of the Cardano community who want to improve the overall developer experience across the cardano ecosystem to join the Developer Experience Working Group start by joining the Discord Channel 
 
 
@@ -75,7 +74,9 @@ Members of the Developer Experience Working Group are committed to a high standa
 Consensus/Voting/Approval. Each Working Group will endeavor to make all decisions by consensus. Where the Working Group cannot reach consensus with respect to a particular decision, the Developer Experience Working Group will make that decision by a supermajority vote of the Working Group Participants, as applicable.
 
 7. Process 
-The repository is designed to simplify and consolidate GitHub status tracking of work items managed by the Developer Experience Working Group. 
+
+7.1 The repository 
+The is designed to simplify and consolidate GitHub status tracking of work items managed by the Developer Experience Working Group. 
 
 The working group uses the GitHub workflow as it's primary mechanism for discussion and for decision making
 
@@ -85,6 +86,12 @@ Issues/Proposals can have the following statuses
 - Accepted - the proposal describes a sound solution to a statistically significant problem. A proposal is deemed Accepted when the working group agrees to merge a proposal into the main branch of the repository.
 - Seeking Sponsorship/Action - The working group is actively soliciting sponsors or other actors to provide the solution described. Accepted proposals will either be accepted with an active sponsor, or the group will actively seek sponsorship for unsponsored, accepted proposals. A sponsor may include a large actor in the ecosystem or a small individual developer.
 
+7.1 Scribe
+A scribe is role is to be described;
+A scribe for a meeting is assigned in the end of the previous meeting. The primary source for scribes is the chairs, if unavaliable a member of the group is selected by volunteering.
+The scribe can not be the same person in two successive meetings.
+If there is only one WG member in the meeting and there is noone to assign as a scribe for the next meeting, a question of relevance and impact is raised.
+
 8. Success Criteria
 
 * Identified issues result in change

diff --git a/README.md b/README.md
@@ -6,7 +6,8 @@ Welcome to the Cardano Developer Experience Working Group.
 
 We're a community-driven group dedicated to identifying and presenting potential solutions to developer experience problems that span the Cardano ecosystem. Once a potential solution is identified, we work with actors in the ecosystem to find sponsorship to implement a solution.
 
-We meet every Tuesday at 3:30PM/15h30m UTC.
+We meet biweekly at 15-00 UTC every even-numbered week. 
+The meetings take place in Intersect Discord.
 
 We also use Github for discussions and the IOHK Developer Discord.
 
@@ -21,11 +22,9 @@ We also use Github for discussions and the IOHK Developer Discord.
 
 Do you have a concern relating to developer experience working on Cardano? Check our [issues](https://github.com/input-output-hk/Developer-Experience-working-group/issues) page and contribute to a discussion, or file a new issue.
 
-To join the [Developer Working group Discord Channel](https://discord.gg/9zPhXfdF9A)
-
 ## How do we use this github repository?
 
-This repository houses the [Charter](CHARTER.md), which defines how the group operates and makes decisions. We also have the [minutes](minutes) folder which houses text records of each Tuesday meeting, arranged by date.
+This repository houses the [Charter](CHARTER.md), which defines how the group operates and makes decisions. We also have the [minutes](https://docs.google.com/document/d/196b_9yoaF-J7rRC4_5tg4UFXyh3vnH6L_pm2tmMOh1E/edit?usp=sharing) folder which houses text records of each Tuesday meeting, arranged by date.
 
 Most discussion topics will take the form of Github issues and pull requests.
 Issues describe a given problem facing the Cardano developer ecosystem, or a desired change to how the group is run.

diff --git a/minutes/2023-09-12.md b/minutes/2023-09-12.md
@@ -0,0 +1,20 @@
+Attendance: Alex, Waalge, Marshall, Ignacio
+
+1. Marshall: IOG teams are interested in transparency and user feedback to the tooling they create.
+The engagement in the Working Groups discord server is disappointingly low so far.
+
+Waalge, Ignacio: planning joint calls with the dev teams may boost developer engagement.
+
+Toolchain maintainers and TxPipe are the first priority to coordinate with.
+
+Twitter, Catalyst Townhall and Intersect Townhall are the suggested public channels.
+
+2. The expreince of being a developer in Cardano seems to be connected to a certain sense of crisis of identity.
+Catch-22 plagues decision making and scarcity mentality may set in near future.
+
+3. Marconi vs Kupo: two indexers.
+
+Action items:
+Alex is the chair for this meeting.
+
+
diff --git a/minutes/2023-09-19.md b/minutes/2023-09-19.md
@@ -0,0 +1,11 @@
+## Stellar, Helios, Developer Experience
+initiator: Randall Harmon
+
+## DevX vision, values, community, goals and timelines
+init: Demi EMURGO
+
+## Intersect + DevX
+init: George Flerovsky Mlabs
+
+## Aiken vs Plutus standoff in IOG Tech Discord
+init: Waalge and Ignacio IOG