To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=48031
User jj changed the following:
What |Old value |New value
================================================================================
Assigned to|mh |pjanik
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Wed Jan 4 07:29:14 -0800
2006 -------
joergwartenberg, pjanik:
Automatically marking all Sun-internal CWSs as public which contain at least one
OOo module would quickly lead to a bunch of Sun-internal CWSs being visible on
OOo with all their information, as even Sun developers do make mistakes ;-) and
might e.g. erroneously have overlooked that they modified a file inside the OOo
modules they added. But suddenly having CWSs appear unwanted on OOo with all
their data, e.g. a description which tells what is being done on the CWS, is not
something which, at least to me, seems acceptable for Sun. I hope you agree that
- just as the license does allow this to others - Sun should be allowed to do
development of additional components privately, without telling the world what
we are working on.
Therefore this very drastic solution of making a CWS fully visible once it
contains at least one OOo module or task does not seem to be an acceptable
solution. To me the question is which information is really needed to help you
in a situation when another CWS breaks the build i.e. what is the information
you would be looking for in the OOo-EIS in such a situation? It is probably
easier to "sell" the idea internally to make a _subset_ of the EIS information
of an internal CWS visible in such cases than to make _everything_ visible.
E.g. a very simple step I could imagine would be to have the CWS name appear in
the announcement mails of a milestone, where the CWSs are currently not listed.
Would this help? If not, what else would be needed? Something like this would be
a small change, easy to implement and it would not reveal any unwanted data that
other cannot already gather elsewhere. OTOH it might help you (and others) as
the data is quickly at hand. I guess this idea does not go far enough for you,
so perhaps you have a better idea for a compromise.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
