Community IRC meeting, next steps?

General
#21

When scheduling new meeting, please carry over the topics proposed at TJC as they are now.

In principle, we can have one thread per each meeting. Then questions will go as a comments under the announcement.

5 Likes
#22

Why don’t you open a new thread and sticky the next coming up one? All the questions can be asked in the thread and you don’t have the hodgepodge of the olden times.
Edit: rinigus was faster.

1 Like
#23

And the thread could be used for answers also or follow-up information.

3 Likes
#24

Agreed. Just not having high hopes for it… But let us get ready to be positively surprised!

3 Likes
#25

Having a separate category in the new forum for Community events, including the IRC meetings is definitely a possibility. Under the category we could then have topics for events, with the agenda and questions - and answers. I agree that this sounds like a good proposal.

9 Likes
#26

It may even be possible to have community meetings be their own category and each topic be a separate thread. Each of those threads could then be marked as solved, when it was scheduled and answered and for the next meeting the unanswered topics would get scheduled automatically, if everyone is available. The actual announcements would probably still need to happen in a stickied thread, but that way you could keep old topics and their replies around as a reference. Maybe you meant that, but I think it sounds good in theory.

1 Like
#27

@KuroNeko - while it is a great idea, it could be a step too far. We tend to get replies like ‘we cannot comment on this yet’ rather regularly. So, it is not clear whether such questions as a question regarding qt update should be marked as resolved or repeated for few years on every meeting. :slight_smile:

@maajussi - any specific date for the next meeting? do you plan to copy topics that were requested already into the new agenda?

#28

Yeah, that sounds fair. While you could probably work around that by doing some kind of exponential backoff on questions, it would lead to a lot of open topics. On the other hand, obviously Jolla just needs a perfect reply for every topic immediately and this will not be an issue! (beware, I’m joking)

1 Like
#29

@maajussi how about a public bug tracker, for issues to work on for community?

1 Like
#30

Even “we cannot comment” is a reply that should be stickied to specific topic. Agendas refer some specific topic from TJC or forum and should be kept up to date. Even when asked again. “No update on the matter” is also a valid answer and communicates that topic has been looked into and it’s not forgotten.

2 Likes
#31

No meetings, no information! What kind of management is it?
Wake up, please!

#32

No Meetings;
no mailing list;
no public bug tracker.
The writing is on the wall? Recalls alot the last days of meego.

1 Like
#33
6 Likes
#34

The important thing would be continuous information. I am a really big fan of Sailfish OS, but these days, we had no community meeting since 2020-06-25, the translation round that is long over, but no sign of the SFOS 3.4.0 version. We do not hope so, but such kind of communication gives a bad feeling, as if the company would struggle. So delays would be no problem, but silence gives the impression of a slowly dying company and with it the only alternative mobile OS for the moment. So please just give us some life signs :slight_smile:

2 Likes
#35

Honestly, this is an improvement.
It is a generational thing, mailing lists are really inaccessible by today’s standards.
The forum is a nice improvement over askbot/TJC, and spreading information in two places serves nobody.

1 Like
#36

Let’s hope then that the “effort” saved by managing the mailing list translates in more information shared in a better way here on this forum :slight_smile:

3 Likes