Add your name/nick using the template below to suggest a topic.
Indicate how much time you’ll need so we can time-box the meeting accordingly.
Please be as thorough as you can with your question/topic.
If you can’t make the meeting please ask and name a substitute.
It is expected that you show up and present your topic, or name a substitute and make sure they attend in your absence. These IRC meetings are for real time participation and live discussions, otherwise you can post the topic on here and get responses that way.
We need you to be present to clarify details in the topic, and to ensure the discussion is leading to the answers you are looking for! If you do not participate or your question/topic isn’t clear enough it will be postponed. Also: always ask for more time than you anticipate your topic needs!
Please have your topics ready at least 3 days before the meeting so we can prepare good answers. Topics announced afterwards will be postponed to the next meeting.
Template for topic proposal: (post your topic proposals as comments to this forum topic).
Name/IRC nick:
Topic:
Some details about the topic:
Approx. time needed:
Substitute (optional):
Open Pull Requests:
If you have, or know of, a pull request that’s been open for at least 3 weeks, but which you think deserves attention, please add a comment using the template below and we’ll consider it during the next meeting.
Name/IRC nick: rainemak Topic: Community communication tools and needs Some details about the topic: Discuss started at FOSDEM BoF about community communication channels and methods. We should try to find ways how could we communicate better with AsteroidOS and other projects near by. We do have our usual fortnight newsletters and IRC meetings. How should we evolve & improve in this front? Approx. time needed: 10mins Substitute (optional):
Will it be encouraged going forwards to instead file bug reports on GitHub as opposed to forum posts, or is it viewed as an alternative rather than a replacement?
Not only that! It requires a certain level of technical understanding, to write a bug report on GitHub, as well as in forums.
Personally, I consider myself to be fairly technically versed, but still have problems writing correct error reports.
One nice thing in Github is that there is a template for a bug report that should ease reporting.
We’ll define “domains” to the issue tracker from where it should be easy to select right “domain”-- let’s say email, camera, browser, and so on. Reporter shall not need to worry about concreate software components / libraries.
Yes, and there is also the Bugger app, which got even better these last days, but I still feel that it is a bit too high a threshold for ordinary users, especially for non-English speakers. But okay, maybe it’s just me being picky.
Maybe someone (with the necessary skills) could develop a script, that runs through GitHub Actions whenever a new issue is opened on GitHub, and it would create a new post in the forum’s Bug Reports -category containing a copy of the original GitHub issue ticket? The post could also include link to the GitHub issue and name of the person who opened the ticket etc.
@rainemak When you pick a new chat provider, please consider how it matches the ethos of Jolla - I’m disappointed that Discord still seems to be among your candidates.
