docs(governance): reflect the real status of the procedure and roles (#287)

Remove the Chair role.

Author: bfabio

governance/charter.md

@@ -30,14 +30,6 @@ level.
 
 # Roles and duties
 
-### Chair ([@ruphy](https://github.com/ruphy))
-
-* Plans, organizes agenda and moderates meetings
-* Prepares and shares milestones and deadlines
-* Oversees the voting procedure
-* Is the ultimate responsible for the development of the project
-* Has administrative access on GitHub and other platforms
-
 ### Maintainer ([@bfabio](https://github.com/bfabio), [@sebbalex](https://github.com/sebbalex))
 
 * Maintains the non-Standard side of repositories

governance/procedure-proposing-changes-and-voting.md

@@ -34,8 +34,8 @@ participation from everyone but restrict the voting to public servants, for this
 only open to members of the [Steering Committee](charter.md#steering-commitee-publiccodeymlsteering-committee),
 typically one per country.
 
-[The Chair](charter.md#roles-and-duties)  of the Steering committee is responsible for holding a
-regular vote, which happens as deemed necessary. Once the voting starts, it stays open for a week.
+Votes are held following an [experimental cadence defined here](https://github.com/publiccodeyml/publiccode.yml/discussions/228#discussioncomment-14314999).
+Once a vote opens, it remains open for two weeks.
 
 Voting happens on formal proposals opened as Pull Requests through expressing a clear intention to
 *approve*, *reject*, or *abstain*.  This can be done by either using GitHub's code review feature,
@@ -65,7 +65,7 @@ so.
 
 ### Results of the vote and implementation of the changes
 
-After a week from the vote has passed, the Chair formally announces the results.
+After the voting session ends, the results are announced.
 
 The Maintainers act accordingly to reflect the changes on GitHub and proceed to queue the changes in
 the next release cycle.