Notification: Monthly RIOT developer meeting @ Mon Jan 29, 2018 5pm - 6pm (CET) (RIOT Events)

Development archive
1

more details »

Monthly RIOT developer meeting

When Mon Jan 29, 2018 5pm – 6pm Berlin

Where Online (map)

Calendar RIOT Events

Who

•

Martine Lenders - creator

Invitation from Google Calendar

You are receiving this email at the account peterschmerzl@gmail.com because you are subscribed for notifications on calendar RIOT Events.

To stop receiving these emails, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar.

Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More.

2

Hi RIOTers!

Our first monthly meeting of the year will take place this afternoon at 17:00 CET. In the last meeting, Martine suggested to start at 16:00 CET IIRC, so if no one is against this change, we can start the next meeting at that time.

The draft agenda I have is:

1. Release bugs (see https://github.com/RIOT-OS/RIOT/projects/16) 2. Coding review guidelines (see PR #7087)

At the beginning of the meeting we can add items to the agenda.

As usual, some notes will be written on the fly at http://piratepad.net/dev-meeting-29012018

See you there!

Paco.

3

Oh! I almost forget, this is the link for the meeting: https://zoom.us/j/235153205

Cheers,

Paco.

4

Hi!

Below you’ll find the minute of 29 January 2018. It is also already on the wiki.

Thanks to the attendants!

Agenda

1. Release bugs (see https://github.com/RIOT-OS/RIOT/projects/16) 2. Coding review guidelines (see PR #7087) 3. Documentation efforts (see https://github.com/RIOT-OS/RIOT/projects/17 ))

Attendants - Francisco Acosta - Jose Alamos - Koen Zandberg - Sebastian Meiling - Bas Stottelaar - Emmanuel Baccelli

1. Release bugs: - Put in the project only major issues, handle better the labels - Better clasification of the bugs, add more columns

2. Coding review guidelines - Add checkboxes for maintainers, so far: * Documentation * Architectural coherence * Functional tests * Code style - It may need several ACKs if only one maintainer can't check all the boxes

3. Documentation - Propose to move documentation for boards (support, configuration pin, etc) to doxygen. If agreed: * Propose a place where to put the resources (mostly images of the board, etc) * Take care of copyrights * Links to the images or actual images in the repo? - Look at openthread.io * Jose will check which kind of tools they use to generate their webpage with documentation (likely oxygen).

Feel free to comment about the discussion!

Cheers,

Paco.