Team management, communincations etc.
@ktsaou @alonbl @gnowxilef and I are currently the registered members of the firehol organisation.
@ktsaou and I are owners which allows us to do anything within github. The others are currently in teams which define their access.
How we manage membership and rights is a question that has not been posed so far. The explosion in interest of netdata means we may need to do so soon. Does anyone have any thoughts / links to well regarded (but not too complex!) systems for managing this?
As a starting point if you think a new team should be added / permissions changed / whatever please file a bug in this repo and unless there is disagreement I will see to it. If you want to recommend a new member it might be more polite to mail @ktsaou and I privately. Likewise if your own existing permissions should be increased to let you achieve some goal, please let us know one way or the other.
As a wider question - are we happy with the current comms infrastructure? I am not a big fan using an issue tracker for general discussion but we don't have anything else at the moment other than for the firehol package itself.
I could add more mailing lists if that would be useful? I am aware that many people avoid them these days but personally I prefer them to a forum. I think the new release of mailman is supposed to have more forum-like capabilities which might give the best of both worlds but I don't know how quickly I could make the upgrade.
Nice! Thanks Phil for raising this up. Of course we need to scale. We need help (I need help, given that I can only work on our projects after-hours and weekends).
My concerns are:
- Somehow, we need to communicate with all these folks that use our S/W. I don't only focus on support (personally, I prefer github issues over mailman for support requests and discussion of new features). I am talking about letting them know our news, releases, progress, our presence in the media, collecting opinions, ideas, etc. Github stars provides a list of those interested in general. I don't know though how to use this as a communication channel (or if such actions, using github stars as the source, would be expected from them). Probably social media presence is needed for such tasks now-days.
- I believe we need to give a few roles to other folks too. For example, I need someone to be "the Docker expert", "the LXC expert", "the Debian expert", etc. I don't know what to answer or do in several aspects and I would really need to discuss all these with people we trust.
Well, netdata made something the last few days. It took a lot of attention and many people, of variable expertise, found value to it. I like this and it gives me input, directions and motivation to work further.