Community

We've got issues

or how we learnt to squish our bugs
M.community
Kat Gerasimova
<p>This is the story of how we harnessed the power of the community, automation and good habits to reduce our issue burden and helped users be heard.</p> <p>5 years into its life and with vast number of users users, Element - a Matrix messaging client available on most desktop platforms, Android and iOS - had a growing backlog of bugs and enhancement requests. This is a common challenge faced by projects as they mature. I will share some of our lessons learnt and good practices that we have developed, and how our enthusiastic community is helping catch bugs earlier and process our backlog. While we have made good progress, we recognise that there are still further improvements to be made and will share some of our ideas for the future.</p>

Additional information

Type maintrack

More sessions

2/5/22
Community
Italo Vignoli
M.community
<p>LibreOffice was announced in 2010. After 10 years, it was necessary to review and update the strategy based on the evolution of the office suite market, to improve the sustainability model. Enterprises are not supporting the project as much as individual users. Over time, this can represent a threat for the sustainability of the project. We have changed our strategy to educate enterprises about the right approach to FOSS, by giving back to ensure the long term sustainability of the ...
2/5/22
Community
Caleb Kibet
M.community
<p>As research becomes more globalised and its output grows exponentially, especially in data, the need for open scientific research practices is more evident — the future of modern science. There is now a concerted global interest in open science uptake, but barriers exist. The formal training curriculum in most, if not all, universities in the global South do not equip students with the knowledge and tools to practice open science in their research or develop open-source tools. To work ...
2/5/22
Community
Dan Čermák
M.community
<p>Contributions to Open Source Projects are always encouraged, especially from Newcomers and Non-coders. However, actually contributing as someone not familiar with the project, its workflows and its tools is usually everything but simple and requires a substantial time investment. This is especially the case if you are not a programmer or not as experienced with the technology in use, which can ultimately discourage otherwise potential willing contributors.</p> <p>This talk will illustrate ...
2/5/22
Community
Shivam Singhal
M.community
<p>While the coronavirus pandemic continues to send shockwaves throughout almost all industries, it’s important for developers to nurture their communities in a well-efficient way and prepare them for the future. The overwhelmed communication systems, improving remote culture, and fostering community coordination are the three main areas on which we need to focus on. It is important to recognize that community development is an organic process, the listed steps (not in order) are to be ...
2/5/22
Community
Navendu Pottekkat
M.community
<p>Good questions lead to better answers.</p> <p>Asking good questions is a must have skill for software developers, especially if you are involved in open source projects. The problem with poor questions is clear when the person answering starts explaining what you already know or what you think isn't relevant. Or they might go ahead and assume that you know a lot and you end up being confused.</p> <p>In this talk, Navendu walks through his experience as an open source contributor and a ...
2/6/22
Community
Ruth Cheesley
M.community
<p>While money is helpful in open source projects, hands-on contributions are probably more valuable to the long term health and sustainability of the project.</p> <p>In the Mautic project, we wanted to establish a partners programme which would allow us to highlight to our community the organisations who were both financially supporting the project as a sponsor, and were actively contributing to the project. Here's how we did it.</p>
2/6/22
Community
Ixchel Ruiz
M.community
<p>As an engineer failure is not a matter of if but when. We all know that corrective actions are expensive, that is why we focus on preventive actions. The knowledge gained from understanding and embracing failure is potentially the source of better preventive actions.</p>