Community breakout session A community riot 1 / 17 Goals Review - - PowerPoint PPT Presentation

▶
community breakout session
SMART_READER_LITE
LIVE PREVIEW

Community breakout session A community riot 1 / 17 Goals Review - - PowerPoint PPT Presentation

Feb 26, 2023 383 likes •562 views

Community breakout session A community riot 1 / 17 Goals Review the current community channels Identify issues with our community interaction 2 / 17 Overview Categories of channels. Which communications channels do we have?

slide-1
SLIDE 1

1 / 17

Community breakout session

A community riot

slide-2
SLIDE 2

2 / 17

Goals

  • Review the current community channels
  • Identify issues with our community interaction
slide-3
SLIDE 3

3 / 17

Overview

  • Categories of channels.
  • Which communications channels do we have?
  • Review of the communication channels.
  • Discussion!
slide-4
SLIDE 4

5 / 17

Communication types

Sync Async News F2F

slide-5
SLIDE 5

6 / 17

Communication channels

slide-6
SLIDE 6

7 / 17

Communication types

slide-7
SLIDE 7

8 / 17

Having that said

  • The channels we have should be as easy as possible to use
  • Any threshold in the participation process can hamper the new user.
slide-8
SLIDE 8

9 / 17

Having that said

  • How should an IoT enthousiast join and participate in the RIOT

community?

  • Does he join the mailing list?
  • Scroll through the open issues on github?
  • Where to show us the awesome project using RIOT?
  • Where to ask if RIOT doesn’t compile?
slide-9
SLIDE 9

10 / 17

Github

  • Proven for code enhancements and issues
  • Not suitable for questions

– Closed vs resolved

slide-10
SLIDE 10

11 / 17

Matrix (Chat)

  • Quick response to questions
  • Depends on maintainer activity
  • No records
  • Time zone issues with America / Asia
slide-11
SLIDE 11

12 / 17

Mailing lists

slide-12
SLIDE 12

13 / 17

Mailing lists are hard for users

For a new participant, there are multiple issues with the mailing lists

  • No searchable archive. How to know if a question was already

answered before subscribing?

  • No way to pin important topics
  • Where should the question be submitted to? Devel or User?
  • 2.8K email vs 106K github notifications over 4 years
slide-13
SLIDE 13

14 / 17

But maintainers like them right?

Nope:

  • What is the best protocol for Real-Time Communication1
  • Using IEEE802.15.4 on RIOT-OS native2
  • Multi-Agents and Riot3
  • TCP send recv on ESP324

1: https://lists.riot-os.org/pipermail/users/2020-August/001595.html 2: https://lists.riot-os.org/pipermail/users/2020-July/001573.html 3: https://lists.riot-os.org/pipermail/users/2020-June/001558.html 4: https://lists.riot-os.org/pipermail/users/2020-May/001549.html

Works fine for release announcements

slide-14
SLIDE 14

15 / 17

What are we missing out on?

User stories:

  • Appreciated features
  • Lack of features
  • Usage problems
  • Show & Tell
slide-15
SLIDE 15

16 / 17

What are we missing out on?

How do we (maintainers) know what to prioritize?

  • IPv4?
  • Link layer security?
  • Power saving?
  • USB firmware upgrades?
  • GPIO extenders
  • AODVv2?
  • Userspace threads
  • SCHC
slide-16
SLIDE 16

17 / 17

What we need

  • A show & tell
  • A venue to ask usage questions
  • Discussion between users and maintainers
  • With an easy to use interface
  • Because the mailing lists do not provide this
slide-17
SLIDE 17

18 / 17

Discussion

  • Does the RIOT community have a good grasp what the user base

needs?

  • Do we want to replace the mailing list?
  • How do we want to use Stack Overflow?