Strengthening Communication in our Community
Dec27

Strengthening Communication in our Community

One of the core tenets of Omni has been transparency: transparency in decisions, transparency in actions, and transparency in communication (to name a few). As we mentioned in our last update, we’ve been going through many changes over the past year and one of those has been in how we communicate internally and externally. In the past we have used IRC where we had our internal team channel and a few public channels for discussion and development. This worked well for a time, but as our team encountered real-life challenges became a bit of a challenge to remain connected – so, as many development teams do, we added Slack thinking it would solve things. It did – to some extent – but it also presented us with the challenge that we have a commitment to Open Source and using a closed-source, hosted solution like Slack didn’t fit that commitment. So, we pivoted and moved to Mattermost, an open-source, self-hosted alternative to Slack. Over the last month we have been using it, and it definitely has improved our workflow and increased our productivity as a team. The move to Mattermost was solidified for us due to the convenience of communication between maintainers and our core team was much better than on IRC for the following reasons (YMMV): constant IRC presence requires a bouncer or quassel, which generally cost money and/or are not available to all. many important topics of discussion quickly became buried in IRC between part/join messages and other irrelevant chatter. a private mattermost implementation allows us to maintain better communication over IRC as well as host the server on our own, making us completely self-sufficient That of course brought about the next level of questions, which was “what about our transparency to the community?” To address this, and to make sure that we continue to be connected to the community as we work to improve and grow OmniROM, we have created a bridge between our #omni channel on IRC and Mattermost. Over the coming weeks and months we aim to grow our communication with the community, and this seemingly small step is a great step in that direction.  ...

Read More
Gerrit Getting You Down?
Nov04

Gerrit Getting You Down?

Gerrit getting you down? Don’t worry, we know it can be a bit annoying to get Gerrit working properly to make contributions, but we’ve made a list of the top 5 reasons for Gerrit giving you problems when submitting changes. You should check these in order from 1 to 5, and you’ll be contributing in no time! 1) Have you set a username within Gerrit? Log into the Gerrit interface, and select your name at the top right. Click Settings, and ensure a username is set correctly there. 2) Have you configured your local repo client to use the correct Gerrit username? Our wiki has instructions on how to do this. 3) Are you contributing from a secured business connection? Some businesses employ SSL sniffing, and will block connections to unknown HTTPS websites, for information security purposes. This mainly affects military and defense company networks. We are looking into possible solutions such as permitting HTTP access for such users (without SSL), but for now it is not possible to upload contributions without SSL access. This is for your own security. 4) Have you accepted the CLA? In the recent downtime, we enabled the Omni CLA. There’s more information about this agreement available yet again on the wiki. In order to accept the CLA, you should log into the web interface of Gerrit, select your name at the top right, select Settings, and then choose Agreements. You can also access it directly by browsing to the submission page. 5) If you are receiving errors about Change IDs, you should ensure that the Change ID line is the last line of the git commit that does not begin with a comment symbol (#). To make this process easier, you can also install the git hook, which will automatically add a commit ID onto each commit. The instructions for this are given during the error message when the commit fails for this reason. If you are still having issues after following the above, maybe now is a good time to drop into our IRC...

Read More