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

FAST Project Re-alignment HLD #2476

Merged
merged 18 commits into from
Dec 3, 2024
Merged

FAST Project Re-alignment HLD #2476

merged 18 commits into from
Dec 3, 2024

Conversation

rajsite
Copy link
Member

@rajsite rajsite commented Nov 19, 2024

Pull Request

🤨 Rationale

HLD for how Nimble will address the FAST project re-alignment.

See #2207
See microsoft/fast#6955
AzDo Work Item 2842865

✅ Checklist

  • I have updated the project documentation to reflect my changes or determined no changes are needed.

@rajsite rajsite changed the title Fast foundation deprecation hld FAST Project Re-alignment HLD Nov 19, 2024
@rajsite rajsite marked this pull request as ready for review November 19, 2024 18:42
@rajsite rajsite requested a review from fredvisser November 19, 2024 18:48
Copy link
Contributor

@jattasNI jattasNI left a comment

Choose a reason for hiding this comment

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

High level direction seems great, you have my approval to start implementing if you want to. Gonna take one more look once my comments are addressed so not approving the PR just yet.

specs/fast-project-realignment/README.md Show resolved Hide resolved
specs/fast-project-realignment/README.md Outdated Show resolved Hide resolved
specs/fast-project-realignment/README.md Show resolved Hide resolved
specs/fast-project-realignment/README.md Show resolved Hide resolved
@rajsite
Copy link
Member Author

rajsite commented Dec 3, 2024

@jattasNI PR is ready for another look


## Open issues

- Should we publicize the fork in the FAST community / discord?
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think that answering this needs to block completion of the HLD / feature, we can decide it once the fork is set up and published.

My take right now: I'm not opposed to publicizing it. But the questions I would ask as a potential external consumer are things like "what is your maintenance plan?", "how much new investment will this receive?", and "will you accept my contributions?". While we have hopeful answers to those, we might want to establish some kind of track record (e.g. a couple months of Renovate updates or bug fixes) before we convince anyone to use this.

Copy link
Member Author

@rajsite rajsite Dec 3, 2024

Choose a reason for hiding this comment

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

Agreed, and I think the "Update top-level README / CONTRIBUTING to cover intentions of the repo / fork:" section describes high-level guidelines that should answer those questions and we can get the language precise in PR and decide whether to share in discord after "some time" in production.

@rajsite rajsite merged commit 3af471f into main Dec 3, 2024
14 checks passed
@rajsite rajsite deleted the fast-foundation-deprecation-hld branch December 3, 2024 20:52
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.

4 participants