Closed amsiotdeveloper closed 4 months ago
Ready for initial review
@greenbreakfast this ticket is ready for your review/approval. Both Tomas and I feel there is room for improvement on this article, so please refer to comments in slack.
@remingtontr added a suggestion and comment in the intro to give an overview of what this article is about in plain terms
Looking good, ready for a PR @remingtontr
NOTE: This Subtask is linked to a larger Task List ticket #78
Task Owner:
Who owns this task and will approve the final deliverables? Lazar
Objectives & Goals:
1. How does this task relate to the value track(s)?
2. Create a short statement explaining the objectives and goals for this ticket.
The objectives of this article is to provide the reader with an understanding of best practices and how to avoid IP collisions.
Description of the Scope:
For the draft scope outline please refer to:
[https://docs.google.com/document/d/1w67dYSW5Kp9E4u7liLximAxnMgJMtOyQrj-JYH162yc/edit]
Anything in italics is an instruction to the writer. The rest is content
Reference Material:
1. Provide hyperlinks for helpful and related information.
See this article from old documentation: https://docs.onion.io/omega2-docs/fix-ip-addr-collisions.html
Deliverables or Desired Outcome:
1. What are the task owners expectations?
create an article consistent with the style guide
2. What does the task owner require for a successful completion of the ticket?
i.e. sample code, drawings, documents etc.
working doc in google docs markdown pushed to repo
Date Required By:
1. When is the scope required to be completed?
no specified date
2. Is this a hard date? Specify if the task is a dependency of another task or if it will impact a customer requirement.
no dependencies