I'm sorry but you can't blame me or Klaus for not following any 'Style Guide' discussion. Nobody invited me (nor Klaus ?) to that discussion. We still have our old YaST (Text) Style Guide in our YaST documentation written by yourself: http://forgeftp.novell.com/yast/doc/SL10.2/styleguide/index.html
Everyone was invited. The project was announced both internally and externally through the appropriate channels. It isn't my fault if you chose to ignore that post.
Moreover, you can expect that developers would check any style guide regularly, they have others task to do. Every important change needs to be announced directly to them.
I have other tasks to do too. I can't run around telling everyone. I tried to post the change to results but the list owner rejected the message and hasn't responded to my follow-up e-mails about it. I keep tabs on this list. This is the first violation I've seen discussed. So I promptly responded and reminded you of it. What more do you expect?
Additionally, in such cases, like unification of "repositories, installation sources, ..." is, you need to assign to that task to follow the discussion and make everybody implement the needed changes.
- Nobody has been assigned to such task so far
- Management doesn't seem to have it decided yet
It is always your job to follow the style guide. Management has supported creation of the project and is aware of the discussion and the decision. I'm following the guidelines for project discussion decided in conjunction with management. I'm doing my job to the best of my ability. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org