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

Remove chain-spec-generator #395

Open
3 tasks
bkontur opened this issue Jul 23, 2024 · 4 comments
Open
3 tasks

Remove chain-spec-generator #395

bkontur opened this issue Jul 23, 2024 · 4 comments

Comments

@bkontur
Copy link
Contributor

bkontur commented Jul 23, 2024

Where possible, we should use chain-spec-builder from Substrate, which can be downloaded from the polkadot-sdk release page assets or from crates.io.

Relates to: paritytech/polkadot-sdk#4518
Continuation of: #379 (comment)

TODO

@kianenigma
Copy link
Contributor

Seems like a "clear" task that can be mentored. Should we have a mentor tag here as well?

@bkontur
Copy link
Contributor Author

bkontur commented Sep 9, 2024

Seems like a "clear" task that can be mentored. Should we have a mentor tag here as well?

yes, sure, but I cannot update tags/labels here. Do we even use tags/labels for the fellows repo?

@kianenigma
Copy link
Contributor

@anaelleltd what would you suggest? would be good to give label altering rights to existing fellowship members.

Perhaps you can create github teams from different rank. Based on this, then you can give more proper merge/label and such permissions to members.

@anaelleltd
Copy link
Collaborator

anaelleltd commented Sep 9, 2024

@anaelleltd what would you suggest? would be good to give label altering rights to existing fellowship members.

Yes, Bryan also mentioned something along these lines for the RFCs repo; so as to update the status of each RFC.

Perhaps you can create github teams from different rank. Based on this, then you can give more proper merge/label and such permissions to members.

I only have "Member" status in the Fellowship repo, so I will have to speak to Raul, Bastian, or Rob (the current repo owners) about this new setup. I will also ask them to give me team maintainer right for future admin duties.

From what I read, teams would be useful for ping-ing members of higher ranks to do review, at the very least.
When it comes to giving members triage/write rights on the Fellowship repo, this will probably have to be done on a case-by-case basis. I wouldn't recommend adding all Fellowship members to teams at once.

Would this work from your end or do you have any other requirements in mind?

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

3 participants