... | ... | @@ -9,6 +9,22 @@ This site has been created to help to enhance and broaden participation in decid |
|
|
At present a two-person team [STF600](https://portal.etsi.org/STF/STFs/STF-HomePages/STF600 "STF600") has been responsible for putting this site together and managing the process of looking at potential changes prior to the creation of a larger team to manage changes that are part of a specific new publication plan.
|
|
|
|
|
|
# How the site is organised
|
|
|
## Issues
|
|
|
Each proposal for a potential change or addition to EN 301 549 starts off as an "Issue". Issues can be accessed by selecting "Issues" in the main (side) menu. Each issue will have one or more "labels" assigned to it to show the context of the suggested change and to assist in filtering changes to only view a subset.
|
|
|
|
|
|
A threaded discussion can take place for each issue. Issues can contain links to other resources including "Snippets".
|
|
|
|
|
|
## Snippets
|
|
|
Rather than trying to follow the evolution of proposed resolutions to the issues across multiple comments in the discussion thread, a "Snippet" is associated with each thread that proposes new or changed content for EN 301 549. The snippet will show what the revised parts of EN 301 549 should look like, within the constraints of the Markdown or html formatting that they support.
|
|
|
|
|
|
A link to the relevant snippet is usually contained in the initial definition of an issue.
|
|
|
|
|
|
Snippets can either be accessed via a link in a comment on an "issue" or they can all be viewed under the "Snippets" heading in the main (side) menu. Snippets should normally contain a link back to Issue with which it is associated.
|
|
|
|
|
|
## Word documents
|
|
|
|
|
|
A snippet will allow a very realistic looking facsimile of how the proposed revised text will look when formatted according to the ETSI Word templates. However, to ensure that everyone is clear on the exact appearance of a proposed revision/addition, a correctly ETSI formatted Word document will also be created before any final decisions are made. This will also be linked to the relevant issue during the final stages of agreeing the changes.
|
|
|
|
|
|
Brief intro about the structure (Issues, Snippets)
|
|
|
- Information about permissions:
|
|
|
- Read access for all
|
... | ... | |