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

Fellowship secretary #8

Closed
bkchr opened this issue Mar 19, 2024 · 7 comments
Closed

Fellowship secretary #8

bkchr opened this issue Mar 19, 2024 · 7 comments

Comments

@bkchr
Copy link

bkchr commented Mar 19, 2024

Over the time the fellowship exists now (not that long), I and others have seen that sometimes we would need to have more help in organizing stuff etc. So, the idea arose that it would be good to have some kind of Secretary for the fellowship. Here is a preliminary list of things this person could do:

  • Organization of fellowship meetings
  • Help with RFCs. Get more engagement. Do some cat herding and whatever that can help to improve the process
  • Help documenting processes. Help people with basic stuff.
  • Some project management stuff around releases.
  • Maybe help with the fellowship/opendev call.

If you have more ideas, please comment.

We would also want to pay this person. The current idea is that we probably add some secretary collective as other collectives may at some point have the same need.

@ggwpez
Copy link
Member

ggwpez commented Mar 19, 2024

Yea, will be needed even more once the retetion calls start.
Also checking all the UI from Polkassembly/Subsquare is correct and in sync it with the manifesto.

Could also create blog posts about the fellowship? Or maybe im overstretching this 😅

@olanod
Copy link

olanod commented Mar 20, 2024

Maybe we also need a secretarybot? a lot of tasks could be automated and perhaps we can tip candidaes/members to build tools that make processes easier ;)

@anaelleltd
Copy link

Hello all,

I have put together a Fellowship Ops development plan that I think will help address and resolve most of the issues listed on the help-center page.

Please leave your comments/suggestions directly on the Google doc or here on GitHub.
Thank you!

cc @ggwpez @olanod

@ltfschoen
Copy link

ltfschoen commented Apr 19, 2024

Maybe we also need a secretarybot? a lot of tasks could be automated and perhaps we can tip candidaes/members to build tools that make processes easier ;)

i'd been keen to collaborate with anyone who's interested in setting up a generative AI chatbot that's also as decentralised as possible and adopts best practice project management approaches so that stuff gets automated

@bkchr
Copy link
Author

bkchr commented Apr 22, 2024

Another point to discuss is to give the secretary rights to create proposals on all tracks. They should not be able to vote, but to create these proposals. Currently it always requires someone from the fellowship to do this, but the pure creation of the proposal should be fine to be done by everybody. Not really "everybody", but by someone like the secretary.

@anaelleltd
Copy link

Proposal submitted and executed here: https://collectives.subsquare.io/fellowship/referenda/103

@bkchr
Copy link
Author

bkchr commented May 2, 2024

Yeah welcome @anaelleltd :)

@bkchr bkchr closed this as completed May 2, 2024
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

5 participants