OpenSolaris Code of Conduct

Have you ever read the OpenSolaris Code of Conduct? It's pretty good. Nice and short and all focused around one very basic concept: respect. If you are involved in OpenSolaris, I encourage you to give our little code a quick read. Communities can be rather messy and loud places to hang around in with so many languages and cultures and strong personalities mixing it up around the world. But if you are actually contributing to the community, your voice will be heard and your work will be honored. And if you treat others with respect, you will be respected in return. 

Code of Conduct

Please respect the rules for community interactions and collaboration as follows.
Be Inclusive
Welcome new people to the project. Give them the time you were given when you first joined the community. And if you weren't given enough time please set a new example for others to live by. Be open and transparent so others can participate on an equal footing and contribute to the project in their own way. Everyone has something to contribute.

Be Respectful and Honest
All OpenSolaris participants have the right to be treated with respect at all times in all venues. While we may not always agree with each other, there is no excuse for poor behavior or personal attacks. We expect community members to be honest and ethical, and if a genuine miscommunication occurs we ask that people take a break before responding. If things can't be worked out, we ask that the OGB mediate a common understanding. A community where some members feel uncomfortable is not a productive one.

Be Considerate of Diversity
Any decisions you make will affect other users and community members, and we expect you to take those consequences into account when making decisions. So be considerate of community members coming from different backgrounds. They may not have access to resources you have, and they may not speak your language. So, be patient with people. And be careful that you don't misinterpret someone's tone or content during conversations. We encourage constructive criticism so we can learn and maintain quality, but it's just as important to be considerate so we don't misunderstand each other.

I'm always looking for models to follow. I figure, if someone else did it (whatever it is) I can do it, too, by modeling their behavior. I may not get there entirely, but at least I'll be moving in the right direction. So, on this issue, over the last few years I have noticed a simple pattern of community behavior that repeats itself consistently and is worth following. Here it is:

The most respected people in the community never criticize others, and they focus their conversations like a laser on the work they do for their project.

Have you noticed this too?

This is good,
It is never a shame to have a problem, simply reinstalling and not investigating is an error.

some tasks and administrative tricks are still to me easier on BSD or Linux,
But I get good feedback from some mailing lists.
I have massive dbus problems, certain gnu projects woun't compile, the printing stuff is malfunctioning. I'm reading the 350 pages of the print API and have joined the printing group on then I run this command

netstat -anv | grep dbus

look up the system logs, inspect dmesg , and I feel sxde is missing,
opensolaris is different. I feel more safe in traditional solaris then the latest opensolaris.

So I go this way inspect and observe what is this dbus on debian, and on BSD,

how do they solve it ? I have inserted some additional hardware, which enforces irq sharing ?

And attaching a network print server and a scanner is not easy.

All this is never an issue on commodity hardware, with mac or Windows.

On solaris it is different. the host based printers scanners USB and firewire devices
makes it an easy guess to install virtualbox and simply do the easy things on windows,

But solaris is not a toy operating system, this must be investigated and i need to file a bug report, on solaris 9 I know I did it, and it worked. but not on sxde.

also updates may have caused a software conflict.

I have in bruessels seen a very interesting demonstration of portage,
which on the fly compiles directly to the target.

much better than makefiles or package source collection.

DTrace is also still greek to me, but it may help to troubleshoot and find bottlenecks.

soleris express developer edition, SXDE
opensolaris and the classic solaris is different.

I prefer to rely on classic solaris and do experimental stuff on opensolaris.

It is open source and runs on Dell, IBM, HP and Sparc and intel + AMD + PPC.

can't ask for more than that. maybe it will be available on playstation3 ? Porting it is important for getting it popular.

Posted by Morten Gulbrandsen on March 21, 2009 at 01:19 AM JST #

Diversity - I wish IPS was designed with diversity in mind. Thousands of us worlwide are bandwidth starved. 100 Mbps lines are not a reality even in most corporates - 2 Mbps is a realistic expectation. Home users typically have 256 kbps lines.

Posted by Sriram Narayanan on March 21, 2009 at 02:07 PM JST #

Post a Comment:
Comments are closed for this entry.


« July 2016

No bookmarks in folder