Fedora is one of my favourite systems, because provides to me the best tools ever, that nowhere else I can get. With Fedora rings concept we have received 3 definitive product that gives a baseline, a series that not only makes possible to create new content, and spins, remixes, else a new infrastructure that targets collaboration in a big scale.
If you think that maybe we have made a mistake, think through again. Sooner or later, every app and systems are gonna focus on teams, and sharing what is our cornerstone in the community – and our base products gonna be the key. Even Libreoffice is planned in the next year to come out with cloud and collaboration support. Why? Because we had since years single apps, and single computers, only tied with networking – what is not effective in bigger scaled projects and targets. Checking, maintaining, fixing, updating regularly is technically slow solution with standalone networked systems – even in face to face cooperating teams, because of at the end if the members are constantly growing – and you get huge 20-30+ member in team – that the infrastructure cannot follow flexibly. Therefore makes it harder and harder to maintain, follow code, communicate, and this gonna lead to few issues – such as:
- Lack of direct communication
- Hindered data and information accessibility
- Poor visibility into colleagues’ / members actions
Despite the obvious perks, like saving time on daily commute and being able to work from any chosen place and time, remote collaboration also brings up several organizational issues like how to stay in control and sync with your team – and most of the communities – as a Linux community – working mostly remotely, with constantly changing amount of contributors. Because of this, the result is what we have now: scattered wiki pages, lot of old outdated contents, other series of things that can be value for the teams as resource – but right now it’s hard to find, and use not only by old-time contributors, else new members either. Therefore leaders always get repeating questions about rules, usages, accessibility, and contacts, right?
Earlier we had a problem that how can we bring closer more of the applications to our users, allow them to use it and we created Copr. Copr makes it easy to you to grab apps that you want to build and test, and maybe launch into a container with docker (yes, thats gonna be later Dopr). This was also an great example between users and applications. But now, this is whole new level that we facing of – how can we connect users with apps, contribution and development altogether?
The first answer what we will have, is so called Hubs witch is in my opinion just the first step into a right direction – what is gonna provide input/output points to the virtual teams, and information organising. The next level I think should be something that connects the different leaderships into one team, and parallel we should require a reform inside the teams too. For example within ambassador team we have/had “campus ambassadors”, “regular” ambassadors, and mentors that all tries to do the same: involve and keep together the teams, and community altogether. Instead of the current situation, I think we need to form a something that provides an correct path kinda career ladder – like ambassador juniors, ambassadors and mentors. With that we can cover most contributors IMHO.