Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[gov][pcac]: Correcting the document title #3119

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

CsatariGergely
Copy link
Collaborator

Based on the discussion in #3045

Based on the discussion in anuket-project#3045

Signed-off-by: Gergely Csatari <[email protected]>
doc/gov/README.rst Outdated Show resolved Hide resolved
@pgoyal01 pgoyal01 requested a review from steelescotr August 12, 2022 13:18
@collivier
Copy link
Collaborator

I would rather ask an Anuket clean and basically to remove common and gov.

@CsatariGergely CsatariGergely changed the title [gov]: Correcting the document title [pcac]: Correcting the document title Sep 15, 2022
@CsatariGergely CsatariGergely changed the title [pcac]: Correcting the document title [gov][pcac]: Correcting the document title Sep 15, 2022
Signed-off-by: Gergely Csatari <[email protected]>
@CsatariGergely
Copy link
Collaborator Author

I would rather ask an Anuket clean and basically to remove common and gov.

I agree that on the long run we should consolidate these, but I would not just remove them as there are lots of valuable things there.

Copy link
Collaborator

@steelescotr steelescotr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@CsatariGergely CsatariGergely added the Merge-Ready Author of PR signals ready for merge (by Code Owner) label Oct 26, 2022
doc/common/chapter00.rst Outdated Show resolved Hide resolved
3. **Separation of concerns:** to promote lifecycle independence of
different architectural layers and modules (e.g., disaggregation of
software from hardware).
4. **Automated lifecycle management:** to minimise the
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LCM of what? If workloads, then "target zero downtime" is reasonable but if infrastructure then that is not.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pgoyal01 This is about the RM, therefore about infrastructure. Maybe we should remove the zero downtime requirement?

@CsatariGergely CsatariGergely removed the Merge-Ready Author of PR signals ready for merge (by Code Owner) label Jan 18, 2023
Copy link
Collaborator

@collivier collivier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because of RTD forcing the use of .readthedocs.yaml, we don't have another choice than splitting the git repository per stream. This PR must be applied on next RM's git repository and not here.

Everything is already ready on my own repositories but sadly I don't have the rights needed on anuket-project organization. Please give me them to complete the migration.

Be free to ask for any detail about the migration during a Weekly Technical meeting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants