Regular Online PyLabRobot Discussions

[rickwierenga]

@CamilloMoschner

Like with most societies/clubs/projects the actual number of people joining will fluctuate but usually a small core team that contributes consistently emerges. I believe in the powerful incentives of PLR to attract people over time

Agreed. The question is when we should start. I think we should just try it out at least once.

@CamilloMoschner

Yes notes are very important. But recordings are a handicap in my opinion: imagine having to go through 24 recordings of 1.5 hours after just 2 years of doing this… the time to go through these would be too long.
Well written, concise notes should be able to be read in 10-20 min.

Agreed.

@CamilloMoschner

Yes, and no: I have used whisper before to transcribe recordings and it works very well for seminars/lectures (i.e. one speaker). I have not yet tested it for recordings with multiple speakers and therefore don’t know whether it would recognise our voices automatically.
But as long as it records and summarises all the information of the meeting, I can see a fast minute-taking workflow:

• generate voice recording of board meeting
• transcribe with whisper
• summarise with GPT4
• maybe ask attendees to check accuracy and add images they might have shown during a meeting to the summary (where appropriate)
• upload to development meeting minutes page/folder on the forum(?) for everyone to freely access and maintain and open record.

What do you think?

Sounds good! Let’s see if it works.

@CamilloMoschner

Potential topics to discuss in board meetings
What does ‘guide and oversee the development of PLR in a structured manner’ mean?
We could discuss and divide workload amongst volunteers for (i.a.)…

• new implementations (modules, functionalities, entire new robots to add,…) and their priority for the open-source community
• the development of a “PLR Guidebook” (a PDF with a lot more documentation and examples than fits into the docs, and allows people an easy reading option; also less intimidating to newcomers); a .tex document hosted on the GitHub repo would work well I think
• a written-down code styleguide that defines the PLR-best-practices (I was a bit thrown off by the two-space tab indent but am happy to adjust to anything consistent)
• necessary code change to enable upgrade to Python 3.11 (that funky business with asyncio’s coroutine decorator…)
• code reviews
  and so much more.1

Great ideas!

@CamilloMoschner

• a written-down code styleguide that defines the PLR-best-practices (I was a bit thrown off by the two-space tab indent but am happy to adjust to anything consistent)

Most of it is defined by pylabrobot/.pylintrc at main · PyLabRobot/pylabrobot · GitHub
I use a vscode extension to check this inline. (and type hinting)