publishing biweekly status reports

[ChristianKuehnel]

converting the discussion on the mailing list into an issue:

I would like to propose that we start publishing biweekly status reports for the community on all the outstanding infrastructure projects that are going on.

The way I envision this working is that during the Tuesday meeting we would ask for a volunteer to do the status report (due the following Tuesday). That volunteer would contact each project owner and ask for current status and then produce a report that we commit to the llvm-iwg repo and email the mailing lists.

What do you think about this?

I think the current projects / owners we have outstanding are:

Discourse / Tanya Lattner Bugzilla / Anton Korobeynikov Code Review / Tom Stellard

[lazyparser]

I'd like to collect data and write the biweekly. I have two questions:

• what questions should be included in the mails that the owners received?
• There is several holidays ahead, the response from community members or owners may postponed. Do we want to wait until we get enough feedback, or should I publish the biweekly on a fixed date since next week?

[tstellar]

@lazyparser Are you interested in doing status reports for this week?

[lazyparser]

@lazyparser Are you interested in doing status reports for this week?

no problem. will do.

[ChristianKuehnel]

thx, let us know if we can help with that in any way

[lazyparser]

Update:

In the past two weeks I did not collect enough feedback from project owners. I think we may have to postpone the report in two weeks, and wait for more feedback.

[ChristianKuehnel]

update from meeting on 2022-05-10:

• no major ongoing efforts, no need for communication right now
• @ChristianKuehnel to check the status/announcements around a Pull Request decision