Hello,
Christian is bringing all to the point.
Admins in Provo have been the problem and not you, Lars.
We can fix a small part with the new hardware, but not all. You'll need them for different issues in the future. And that was the reason, why I said they need new admin policys, too.
You can think about adding that to the blog article or not. Speaking every Monday about issues and only doing that isn't a good workflow for such admins...
I recommend agile System Administration with Daily SCRUM in such a situation. Sysadmins, who don't know what to do, "have to" ask their team for coming to the next task or they blame themselves...
What you need is a Team Member (with Sysadmin knowledge) who wants to play the SCRUM Master every day. :-)
I had a Sysadmin without passion in the last company and at first he didn't do his tasks. I introduced Daily SCRUM and he saw the feature that he "has to" ask questions and all task come to an end.
After 1 week he wanted to have it all the time and all Team Members had fun.
I was in the first Sysadmin Team with SCRUM at 1&1 and all teams in our department copied that...
Last week I read an article aabout that and that Google is using it in their best teams with the name "High Performers".
You can think about that and the situation in Provo. Any time that will fall back again and it is the right time for doing changes...
Best regards,
Sarah
Gesendet: Dienstag, 19. Juli 2016 um 20:50 Uhr
Von: "Christian Boltz"
On Mon, 18 Jul 2016 22:56:36 +0200 Christian Boltz wrote:
In the first paragraph, I'd mention Provo to avoid that the admins in Nürnberg, including you, also get blamed by people who don't read the full article.
I see this a bit different - maybe because I'm working here... From my point, we are *one* team, even if we are distributed across countries and even companies. If one fails, the other ones might at the moment not be able to step in - but who from the outside cares if it's "they" or "we"?
Well, if "they" actively refused to give you access to that machine, it would be unfair to say "we" failed. My opinion would differ if the problem would be "nobody asked for access" or "this thing looks like magic, I don't understand it and therefore can't fix it". Yes, this sounds like inside view again ;-) but I'd also apply it to the outside this way. Also, I'm sure people reading the -project or -wiki mailinglist will know who to blame for the wiki problems in the last months anyway ;-)
Guess someone breaks in to one of my machines. Would it be my fault? Yes. Would the community (and not only the openSUSE community) see it as "my" personal fault - or would they see it as "IT" fault in general?
That might depend - if you did a really silly thing (let's say a passwordless root account with SSH open to the public), it could become a personal blame. But in general, yes, "IT" would be blamed.
I'm fine with blaming inside the team, but to the outside we should become - and react - as one team. Nothing else matters ;-)
I probably had (and still have) too much "fun" with the Provo admins to agree completely ;-) - but you have good arguments, so I'm fine with keeping the blaming anonymous to the outside. [snip] Thanks for updating the news article, and also thanks to Sarah. Adding the latest news is a very good idea and shows that the light at the end of the tunnel really exists ;-)
Can you send me the picture in the original format (I'd guess GIMP xcf)? I can make it scalable (by converting it to SVG) so that we can use it everywhere without loosing quality.
might do - but I guess it's better to use git for this?
If you really want your version in git (instead of a bug-free SVG version), go ahead ;-) - but since I'll probably delete the GIMP xcf file after converting it to SVG, I'd say sending it by mail is enough ;-) But well, you could always refer to my commit message in AppArmor bzr r3022 (just quoting the relevant line): - now that write_net_rules() got fixed, drop it ;-)
Just tell me where we should host that stuff ...
I'd say somewhere[tm] on github. The "somewhere" is the interesting part: - a repo for just one file looks exaggerated, which leads to the question if we'll have more files to store in the future (I'm not talking about Salt-related files etc. , they are a completely different topic.) - maybe we can find a place in the openSUSE artwork repo? - another option could be to upload it to the wiki because we'll probably need it there anyway ;-) and also get a versioned history That said: please don't wait for a decision on this before sending me the logo. Experience shows that such "simple" detail questions can take quite some time ;-) BTW: I just noticed that lists.opensuse.org doesn't have your initial "Welcome!" mail. Is there a chance to get this fixed, or would it be too much effort? Oh, and I wanted to ask about the plans for status.o.o - but then noticed that they are already documented in the HTML sources ;-) (and look good, at least on the first view) Regards, Christian Boltz -- Re: [bulk]: Re: [bulk]: Re: [bulk]: Re: [bulk]: Re: [bulk]: Re: [bulk]:
So ungefähr sieht die Betreff-Leiste Aus, wenn der Re: [bulk]: Re: [bulk]: Blödsinn noch 'ne Weile weitergeführt wird. Die Leute wollten vermutlich nur das ebenso schwachsinnige Subject "AW: AW: AW: AW: AW:" der letzten Tage uebertreffen ;-) [Martin Falley und Thomas Hertweck in suse-linux]
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org