-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: Version control request
-
Labels:None
-
Environment:
SARIF TC
Submitted on Wednesday, September 13, 2017 - 22:40
Submitted by user:
Submitted values are:
Your name: David Keaton
TC name: SARIF
TC email address: sarif@lists.oasis-open.org
GitHub name: sarif
Maintainer(s):
Larry Golding, github ID lgolding, e-mail Laurence.Golding@microsoft.com
Michael Fanning, github ID michaelcfanning, e-mail
Michael.Fanning@microsoft.com
Description:
Static Analysis Results Interchange Format
This is the repository for the draft standard. Requests for modification
should
be made via Github Issues.
Purpose statement :
The purpose of the SARIF TC is to define a standard output format for static
analysis tools, which will be called the Static Analysis Results Interchange
Format (SARIF).
A static analysis tool is a program that examines programming artifacts in
order
to detect problems, without executing the program. Software developers use a
variety of static analysis tools to assess the quality of their programs. To
form an overall picture of program quality, developers must often aggregate
the
results produced by all of these tools. This aggregation is more difficult if
each tool produces output in a different format. A standard output format
would
make it feasible for developers and teams to view, understand, interact with,
and manage the results produced by all the tools that they use.
Notes:
Please populate this repository from the existing one found here:
https://github.com/sarif-standard/sarif-spec
The results of this submission may be viewed at:
http://tools.oasis-open.org/issues/browse/TCADMIN
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Chet Ensign [ chet-oasis ] | Robin Cover [ robincover ] |
| Component/s | Version control request [ 11325 ] | |
| Environment | SARIF TC | |
| Reporter | Chet Ensign [ chet.ensign ] | Robin Cover [ robincover ] |
| Summary | Request a TC GitHub version control instance be created | Request a TC GitHub version control instance be created:sarif |
Initial spinup work complete; coord needed w/ principals on a couple details
Chairs and tech leads requested name change "sarif" to "sarif-spec"
Initial use for issues ( https://github.com/oasis-tcs/sarif-spec/issues ) per plan:
SARIF Issue Tracking Process
Michael Fanning, 20-September-2017
https://www.oasis-open.org/committees/download.php/61605/SARIF-Issue-Tracking-Process.pptx
https://www.oasis-open.org/committees/document.php?document_id=61605
https://lists.oasis-open.org/archives/sarif/201709/msg00021.html
A preliminary draft of the SARIF TC issue workflow. This content will be further
refined at https://github.com/oasis-tcs/sarif-spec/issues/2.
-------
- All activity that may impact spec content will be tracked as issues, e.g.,
https://github.com/oasis-tcs/sarif-spec/issues/1
- We encourage discussion on the public issues. Editors will
'curate' by applying specific tags, ensuring content from
other sources (email) is recorded, etc.
- Editors will prepare proposed changes in separate repository
branches. A clean document with revisions tracking enabled
will be used for driving specific textual proposals.
- Any issues that require time-sensitive discussion will be
driven through the mailing list (this should be rate)
- Issues that are ready for final approval or which warrant
discussion on the telecon will be tagged in advance of
each meeting.
- After telecon approval/rejection, PRs will be merged or
closed unmerged as appropriate.
- This process (with additional details) will be driven by
an open issue and documented in a file persisted to the
repository (and will be approved next TC)
Repo was created and put into use.
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Repo was created and put into use.
| Status | Resolved [ 5 ] | Closed [ 6 ] |
ACK receipt of the request...