We don't need linux support, but we do need someone fairly well aquinted with linux to help guide the porting, that can explain to the others what this & that bit do on linux, and offer help in working arround things not possible in AOS
I'd propose this is the job of the leas programmer. He/She should have some skills in understanding Linux code. I'd expect a person capable of beeing a lead programmer to understand alien code, anyway. A specialized function like a "Linux consultant" would fit here, I think.
Anyway, before we talk about managment (which is a word I do not really like), we should talk about functional entitys, define the responsibilities and try to find people taking over those responsibilities. Afterwards, we make some sort of internal applications for these jobs and pick (vote) for the best candidate.
You just described management ;)
I know :) But I do not consider myself a manager, simply because managers are often far off the details or the basic understanding (which is IMO often the case in SW...sorry to say that...but maybe I am wrong and I meet the wrong people ;) Don't take this too serious, I know it could also be the other way round...
I agree, that's actually what i'm trying to get us to achieve, organisation, your proposition is more then welcome :)
Yes, and I guess you're doing a good job already. I just didn't have time to read the whole bunch of emails since two days...(damn, now I sound like a manager ;)
Sorry, was a bit long, but I hope you might find the one or other thought usefull to set up an effective team. I am pretty sure I missed some things here, so if you have things to add, please go ahead.
Feedback is always good :)
Thanx. I'd like see the current organisation broken into more details. How would you (we ?) do that. I mean, what would be the next step. Are you disccussing these things on IRC ?
BTW: the aw-de devsite. This is completely open, ATM. Wouldn't it make sence to lock it down to members only, with maybe some public forum(s) ? Also, should the main communication be done on this mailing list or more on the web based board (which I would prefer) - simply because as soon as components are defined, it might make sence, people in one group (if we establish something like that) can discuss things locally, instead of filling up this mailing list with details.
E.g. a project (e.g. a component, but also establishing the teams) could be discussed there in detail and it is easier to just select the specific project. For example, for me it's a bit hard to follow, if/how things organised by walking thru all emails and filter just the ones covering organisation. There is a thread on an already with HR. I see organisation as one component already.
cheers Jürgen