Preparing for next peer review

[jurra]

This 1st peer review had little to none peer reviewing. It was more a pitch with interesting exchange, questions, insights.

If we want to make it a peer review we can:

• Add breakout rooms and let them exchange
• Ask them to comment on issues/documents, perhaps the valuepropostion could be in an issue. Ideally the feedback should be visible to everyone.
• Assign upfront projects to other project leaders. .... any other ideas?

[vektorious]

I agree. Especially with giving them tasks/review jobs before the call. I'd say they can review the general accessibility of the project? Thinks they liked or didn't like?

[amchagas]

For peer review I also agree with tasks before the call. Adding to what Alex mentioned above and considering the next one is closer to the end of the project, we could ask reviewers to see how far they would get in if they were to repdroduce the hardware they are reviewing:

• Bill of materials - are all components sourceable?
• building instruction - step by step provided?
• etc.

On terms of the project and how open it is to others: are communication channels clearly stated, are there first issues, how often main developers responded to questions/suggestions on issues, etc..

[jurra]

@amchagas this questions are assesing documentation which is a subject that I believe we will cover after week 8 Documentation is planned in for week 10: https://openhardware4.me/open-hardware-leaders.github.io/Program/17_Week10.html

These are the things that we have covered and can be peer reviewed:

• Contributing guidelines
• Readme
• Boards with issues including test cards to communicate with potential contributors Agree with @amchagas on this one: On terms of the project and how open it is to others: are communication channels clearly stated, are there first issues, how often main developers responded to questions/suggestions on issues, etc..

We can also provide as a complement document the checklist for open source hardware. But again this one will come for sure in week 10.

[jurra]

Call and peer review what can we do?

Ideas:

• The call is happening
• Why you make some suggestions in the comments

  Email

  Open call break out rooms, with some assignments short in the moment:

Assignments to setup the peer review and call

5 minutes to read the Readme and contrib and give feedback on the following points:

Readme

• Is it clear what the hardware does?
• Is it clear the Intended use of the artifact? Are there any references?

Contribute

• How to contribute? Are there clear channels? clear steps to take forward to contact the core team?