docs: Runtime Defined Entity Behaviors Part 1

[kirilkadoncheva]

This commit contains Behaviors general concepts, invocation, RDE hooks documentation.

Signed-off-by: Kirilka Doncheva [email protected]

[iiliev2]

Overall the last section with the hooks is rather unclear for me. The information should be regrouped. Always think from the point of view of a third party who do not know any of this:

• is the necessary context explained prior to any given new statement
• there should be no duplicated information(also because when there are slight differences between the two versions it becomes even more confusing as to which one is the correct one)

If there will be so many documents for the RDEs we should put them in a sub folder.

[kirilkadoncheva]

Overall the last section with the hooks is rather unclear for me. The information should be regrouped. Always think from the point of view of a third party who do not know any of this:

• is the necessary context explained prior to any given new statement
• there should be no duplicated information(also because when there are slight differences between the two versions it becomes even more confusing as to which one is the correct one)

If there will be so many documents for the RDEs we should put them in a sub folder.

I have added the RDE related documentation in a subfolder. Also reorganized the hooks section of the document.

[vmwclabot]

@kirilkadoncheva, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit e8fb9be must be signed by [email protected]

[vmwclabot]

@kirilkadoncheva, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit e8fb9be must be signed by [email protected]
• Commit b7cba9a must be signed by [email protected]

[vmwclabot]

@kirilkadoncheva, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit e8fb9be must be signed by [email protected]
• Commit ac3a107 must be signed by [email protected]

[vmwclabot]

@kirilkadoncheva, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit e8fb9be must be signed by [email protected]
• Commit db006f0 must be signed by [email protected]

[vmwclabot]

@kirilkadoncheva, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit d7b708d must be signed by [email protected]
• Commit 6cb7a53 must be signed by [email protected]
• Commit d42c5f4 must be signed by [email protected]

[vmwclabot]

@kirilkadoncheva, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 0def957 must be signed by [email protected]
• Commit 1b70ae2 must be signed by [email protected]
• Commit f9eebc5 must be signed by [email protected]

[vmwclabot]

@kirilkadoncheva, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit d3fb062 must be signed by [email protected]