TSC config modifications

[derberg]

We have not these 2 files that come from community repo:

• https://github.com/asyncapi/website/blob/master/config/AMBASSADORS_MEMBERS.json
• https://github.com/asyncapi/website/blob/master/config/MAINTAINERS.json

Until yesterday isTscMember flag was available only in MAINTAINERS.json and from now on it will also be visible in AMBASSADORS_MEMBERS.json.

Current TSC page consumes only MAINTAINERS.json

I guess the best would be to have some script, no logic in TSC component, that will run whenever one of the above files changes. The script will create a new JSON file, only with people that have the following flags provided:

• isTscMember: true
• isBoardMember: true
• isBoardChair: true

Such a file can then be used as a new source for TSC page and the new upcoming Board page as specified in asyncapi/website#4095

[aminoxix]

would like to contribute to this issue by:

steps will be followed:

1. write TS script, let's say tsc-board-members.ts within scripts root directory with loggers & test cases
2. automate the workflow via GitHub Action, by creating .github/workflows/board-governance.yml file

correct me, if i pursued the wrong direction.

[aminoxix]

update:

• created script to read, check duplicates & merge the members to form /config/TSC_BOARD_MEMBERS.ts , also added it to package.json named, generate:board
• added test case corresponds to the aforementioned point (coverage 100%)
• the last part, not very good at it, still somehow managed to developed yaml file .github/workflows/board-governance.yml to automate , should the new generated file be intends to create pull request before merge or?

[derberg]

wow, great lesson why it is important to write what you want to implement before actually implementing it.

now when you write down all of this, I don't think it is needed to implement the script in website, since we anyway generate a new file, better do it from community repo really - lemme transfer the issue

[derberg]

@aminoxix you will need to create automation like https://github.com/asyncapi/community/blob/master/.github/workflows/update-website-ambassador.yml and https://github.com/asyncapi/community/blob/master/.github/workflows/update-website-tsc.yml

the difference is that your automation will have to generate board file, it will never be human edited. It other workflows in this repo you have examples how things can be generated in the workflow and then pushed to this repo as a file update

[derberg]

btw, in your case you need to follow new setup from #1837 PR that introduced testing. So your scripts should not be inlinded inside workflow file

[aminoxix]

btw, in your case you need to follow new setup from #1837 PR that introduced testing. So your scripts should not be inlinded inside workflow file

so, that's reliable on isVotingWithinLastThreeMonths, but in our case, the difference - voting based on "call by board member ONLY" (from ref. #1893)?

now only board members will be able to call a vote -> @asyncapi/governance-board team. Update https://github.com/asyncapi/community/blob/master/.github/workflows/vote-verifcation.yml

---

noted: voting will persist for 7 days

---

another quick question,

additional 2 board members elections need to be organized

what do you mean by ^?:

1. a single election will elect 2 board members (the highest & second highest)
2. 2 elections respective to 2 board members to be elected

[derberg]

isVotingWithinLastThreeMonths

no no, don't worry about this voting code. I just wanted to point out that the scope for you is to provide tests and and put them where isVotingWithinLastThreeMonths is tested

additional 2 board members elections need to be organized

now only board members will be able to call a vote -> @asyncapi/governance-board team. Update https://github.com/asyncapi/community/blob/master/.github/workflows/vote-verifcation.yml

now sure where you're getting these quotes from. This is not related to this issue. This issue scope is to combine 2 json files (one yaml parsed to json) into one with only tsc and board members