Open bkontur opened 2 months ago
Seems like a "clear" task that can be mentored. Should we have a mentor tag here as well?
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?
@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 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?
@kianenigma @bkontur @anaelleltd If no one else is already working on this I would like to pick this up!
Where possible, we should use
chain-spec-builder
from Substrate, which can be downloaded from thepolkadot-sdk
release page assets or from crates.io.Relates to: https://github.com/paritytech/polkadot-sdk/pull/4518 Continuation of: https://github.com/polkadot-fellows/runtimes/pull/379#discussion_r1687170911
TODO