|
| 1 | +.. |
| 2 | + # ******************************************************************************* |
| 3 | + # Copyright (c) 2024 Contributors to the Eclipse Foundation |
| 4 | + # |
| 5 | + # See the NOTICE file(s) distributed with this work for additional |
| 6 | + # information regarding copyright ownership. |
| 7 | + # |
| 8 | + # This program and the accompanying materials are made available under the |
| 9 | + # terms of the Apache License Version 2.0 which is available at |
| 10 | + # https://www.apache.org/licenses/LICENSE-2.0 |
| 11 | + # |
| 12 | + # SPDX-License-Identifier: Apache-2.0 |
| 13 | + # ******************************************************************************* |
| 14 | +
|
| 15 | +Naming Conventions |
| 16 | +================== |
| 17 | + |
| 18 | +.. _naming_convention_files: |
| 19 | + |
| 20 | +Naming Conventions of Files |
| 21 | +--------------------------- |
| 22 | + |
| 23 | +The overall naming convention is to use snake case for all files and folders (all files are named lowercase and spaces are replaced by underscores). |
| 24 | + |
| 25 | +.. _naming_convention_needs: |
| 26 | + |
| 27 | +Naming Convention for UIDs |
| 28 | +-------------------------- |
| 29 | + |
| 30 | +The naming convention for the UIDs of **all** elements shall be defined as follows: |
| 31 | + |
| 32 | +* It should not exceed 30 characters |
| 33 | +* It shall show a meaningful name |
| 34 | +* It shall only consist of lowercase, digits and underscores |
| 35 | + |
| 36 | +For the naming of the UIDs also following convention shall be applied: |
| 37 | + |
| 38 | +* It shall consist of 3 parts separated by double underscore |
| 39 | + * | prefix |
| 40 | + | (defined in the Metamodel) |
| 41 | + * | structural element |
| 42 | + | (e.g. abbreviation for the feature / subfeature) |
| 43 | + * | keyword (s) |
| 44 | + | (keyword(s) referring the the description, separated by underscore) |
| 45 | +
|
| 46 | +As examples: |
| 47 | + |
| 48 | +* feat_req__ipc__e2e_protection |
| 49 | +* comp_req__kvs__storage |
| 50 | + |
| 51 | +Only for **process UIDs** the structural element is optional: |
| 52 | + |
| 53 | +* gd_temp__review |
| 54 | +* gd_req__req__structure |
| 55 | + |
| 56 | +.. _branch_naming: |
| 57 | + |
| 58 | +Naming convention for git branches |
| 59 | +---------------------------------- |
| 60 | + |
| 61 | +In order to keep an overview which branch belongs to whom the branch |
| 62 | +name also should be descriptive. The following rules shall apply: |
| 63 | + |
| 64 | +#. The branch name shall start with your github username. This will make |
| 65 | + it easier for everybody to identify the owner of the branch. |
| 66 | +#. Branch names must be lower case. |
| 67 | +#. Concatenation is done by underscores _. |
| 68 | + |
| 69 | +An example could look like this: |
| 70 | + |
| 71 | +Mustermann, GitHub Name: maximuster |
| 72 | + |
| 73 | +.. code:: |
| 74 | +
|
| 75 | + maximuster_my_awesome_branch_name |
0 commit comments