| ... | ... | @@ -26,10 +26,9 @@ Snippets can either be accessed via a link in a comment on an "issue" or they ca |
|
|
|
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.
|
|
|
|
|
|
|
|
# How to participate
|
|
|
|
All the activity on the site can be viewed by anyone who has a link to it.
|
|
|
|
Anybody can send a proposal for an issue or a comment on an issue to STF600@groups.etsi.org
|
|
|
|
Anyone who has an ETSI EOL account can directly create and comment on issues within GitLab.
|
|
|
|
- Anybody can send proposals to our group email (how do we expose it without risking too much spam?)
|
|
|
|
- EOL account holders can write directly on the site.
|
|
|
|
- Brief intro about the procedure for accepting proposals
|
|
|
|
- Where to turn to for more information, or comments |
|
|
|
* All the activity on the site can be viewed by anyone who has a link to it.
|
|
|
|
* Anybody can send a proposal for an issue or a comment on an issue to STF600@groups.etsi.org. Emails received will be checked and then submitted by a member of STF600 as a new issue and assigned an appropriate "Label".
|
|
|
|
* Anyone who has an ETSI EOL account can directly create and comment on issues within GitLab.
|
|
|
|
* Whether directly input or submitted by email, each issue should cover a single simple proposal.
|
|
|
|
* If you wish to submit multiple proposals then please making them separate issues or submit each one as a separate email.
|
|
|
|
* If you want more information, or wish to comment on using the site send an email to |
