John Plocher <[EMAIL PROTECTED]> wrote:
> Joerg Schilling wrote:
> > I have been told that you cannot introduce new things into OpenSolaris
> > in case that there is an unasked expert inside Sun.
>
> As others have said, this is not what is intended or desired. I would
> rephrase the intent as
>
> "you can't introduce new things into OpenSolaris (or change
> existing ones) without first planning for what you want to
> accomplish, communicating your plan to those who have a stake
> in your efforts, and obtaining stakeholder and community
> approval for what you wish to do."
>
> The intent is to encourage projects that impact others to be reviewed
> (and improved) by those that are impacted by it. As we transition from
Well, this has already been done by the people behind the Trusted extension
change for Sun tar. They did introduce a change that will cause me a big
work load in order to implement an undocumented archive format extension that
is based on outdated archive technology.
These changes do impact my software and I have not been called for a review
of the changes that cause the impact.
> being Sun-only-Solaris to Community-driven-OpenSolaris, there /will/ be
> times where there are Sun-Internal stakeholders that it would be foolish
> to ignore. Hopefully, over time, those people will become active OS.o
> participants, and this concern will fade away. Nevertheless, the intent
> is that the right people be involved, no matter where they come from.
Well, please try to understand what OpenSolaris needs to be:
- OpenSolaris can only be successfull if all people from the community
do have the same rights. This does not really mean "all" people but
all people who have expert knowledge should be in a commonly known
expert pool. If you are unable to ensure this, you will lose the
OpenSolaris community in the long term.
- OpenSolaris can only be successfull if there is collaboration.
Collaboration means talking with each other in the first attempt before
doing something that may impact other peoples work.
> -John
>
> PS: What follows, for those that are still awake, is my understanding
What you did write is nice, I believe it after you did backout the change for
Trusted extension in Sun tar and give the people behind this change the chance
to approve an ARC case for this change in the public. This ARC case should
include a description of what it shout do (note that the current man page is
completely unusable as it does not describe the behavior nor the archive
format used). Alone from the fact that there is no documentation, this change
needs to be backed out...
If you are not sure about how a halfway complete man page should look like,
have a look at:
http://cdrecord.berlios.de/old/private/man/star/star.1.html
and
http://cdrecord.berlios.de/old/private/man/star/star.4.html
Let us discuss in the public how the planned change will affect other software
and let the people behind the change explain why they believe that they used the
best solution.
It cannot be that some people create an impact on my software without even
asking me. Let us conclude that the Trusted extensions change in Sun tar did
not follow the rules and thus need to be backed out and to start again,
following the rules.
Let us start a _really_ open Solaris!
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
