OpenSolaris

Questions about the information on this page should be sent to arc-discuss@openSolaris.org. (The ARC community leaders monitor the list.)

Requesting a historical ARC case

• Requests to publish an existing, historical ARC case should be screened and the screening should take place - at least in part - on an open forum.  This is to ensure that each request to release a historical ARC case is worth spending cycles on.
• Any OpenSolaris community member can submit a request to have an ARC case processed and released. A justification must accompany the request. Positive comments by other members become part of the request's justification.
• The request should be addressed to the mailing list most relevant to the case. For example a request for a case about a network technology should be posted to networking-discuss@opensolaris.org. In addition, requests should be cross-posted to arc-discuss@opensolaris.org.
• An OpenSolaris ARC leader will enter the request into the status table (usually the same day, but no more than 48 hours after the request) with an initial status of "Received - under review". For the lifetime of the request record, changes to the status or ETA fields will result in a change notification being posted to arc-discuss (manually for now).
• New requests will move from received status to open or deferred in two weeks or less. All open cases will carry an ETA.
• When a case release is completed the case is published on the ARC community site.

Safe harbor section

Answer the following questions:

• Do these documents contain any cryptographic algorithms?

    If yes, delete the algorithm and replace with "[cryptographic algorithm redacted]"

• Are there are discussions about security issues?

    If yes, it is probable that special handling is needed for these materials.

• Do these documents contain any information that Sun doesn't own? Examples: source code covered by a contract with a third party or information covered by a NDA/CDA?

    If yes, the case CAN NOT use //this// process for public release.
    You will, at a minimum, need to get lawyers involved and obtain
    executive approval to publish this material. 

• Is there discussion about existing patents or prior art?

    If yes, a lawyer needs to review and provide further guidance for the section in question.

Checklist for publishing historical ARC case materials

If you are a Sun engineer (especially if you are responding to one of the
above requests), this checklist should help you to understand what is needed
to transform an existing "Sun ARC case" into something that can be published on the OpenSolaris web site.

This self-directed checklist is used to initiate the publishing of ARC case materials, including onepagers, opinions, materials, minutes and mail logs:

• remember to use SCCS to ensure that the orininal versions of any modified files is retained:  sccs create file; sccs edit file; vi file; sccs delget file; rm ,file
• Sun Confidential notices must be removed - in particular, look for them if exposing the onepager, the opinion and/or the mail log.
• Any existing disclaimer text about why the information is Sun Confidential must also be removed (but note that if the information is not Sun's in the first place, you can't use this process to publish it!)
• Check for (and redact) comments that could be considered defamatory/libelous, etc.
• Clean up Trademark usage

Example This project may be  delivered  in a  Minor
 release  of  Solaris.  

 Note that Solaris is a trademark.  Except when talking about the
 trademark itself, trademarks must be used as adjectives rather than as
 nouns.  
 

Should be  This project may be delivered in a Minor release of the ON Consolidation.  
or         This project may be delivered in a Minor release of the Solaris Operating System.

• Prune any competitive analysis or marketing info 
• For cases older than June 2005: Manually search and replace names of former Sun employees with "First L."
• The following will not be published:
•  * sccs created files (,foo s.foo, p.foo)
•  * .mp3 audio files
•  * .gz, .zip, .class and .o files
        Anything in directories named OLD, old, SCCS, sc, uirb, javadoc or closed*

Getting the case published on the OpenSolaris web site

• Any Sun ARC member, intern or licensee can complete the following steps.  See the ARC Leaders Page if you need assistance.  
• Ensure that there is an ASCII/Text version of the opinion:
•  * If the opinion is in NROFF, use nroffit to create opinion.txt
•  * If the opinion is in HTML, generate an ASCII/Text version with "elinks -dump -no-numbering" to remove internal URL references.  Name the file opinion.txt
• If the entire case and all its supporting materials can be published, mark the IAM file with a line that says "Exposure: open", and you are done.
• If only parts of the case can be exposed, mark the IAM file with "Exposure: manual" and create/symlink the following:
•  * Save the cleaned up case materials in the case directory on sac, using one of the following naming styles (html files should contain page fragments, without any <html> and <body> tags):
  • * proposal.opensolaris[.version][.html]
  • * spec.opensolaris[.version][.html]
  • * onepager.opensolaris[.version][.html]
  • * opinion.opensolaris[.DRAFT][.html]
  • * issues.opensolaris
          examples:* spec.initial.opensolaris, spec.final.opensolaris.html