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

Update Hardware Investment Policy Language #56

Open
Comeani opened this issue Mar 7, 2024 · 2 comments
Open

Update Hardware Investment Policy Language #56

Comeani opened this issue Mar 7, 2024 · 2 comments
Assignees

Comments

@Comeani
Copy link
Collaborator

Comeani commented Mar 7, 2024

We need to update the content of the investment policy page to indicate our community model driven adjustments:

Contributing nodes to the general cluster (receiving theoretical equivalent SU award in return) and Investing into a group owned partition (that also becomes available for the community to use with preemption) are two separate routes investors may take.

Any adjustment to priority weighting due to investor status has been removed.

We should include details about how investment partitions are configured, and how investors can expect to use them.

@Comeani
Copy link
Collaborator Author

Comeani commented Mar 8, 2024

Remove item about 20% contribution being set aside for investment partitions. Under the community model, all invested nodes will be placed in an investment partition.

@burntyellow burntyellow self-assigned this Jul 1, 2024
@Comeani
Copy link
Collaborator Author

Comeani commented Nov 15, 2024

Related action item from CRC team meeting agenda:

Investment policy page should link somewhere safe to convey general costs of investing for different hardware

If/when we put together a document for conveying summary hardware cost information for investments, we should host it somewhere where we can control permissions like a onedrive/sharepoint folder

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

No branches or pull requests

2 participants