-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Conversation
This pull request has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/ecosystem-wide-frame-project-manager/1856/9 |
Happy to see you are willing to help. However add a simple readme file isn't justifiable for tips, which are usually done for existing work. If you do believe your prior contribution is significant enough, you should apply it properly to the Polkadot treasury. If you want upfront payment before you start contribution, you would need to make a proper treasury proposal and convince the community first. (I don't have permission to trigger the tip bot and I am also just an external contributor) |
It should be, given the context.
I think i'd better not apply...
Me already in streamlining-mode. (redundant )Bureaucracy would kill my flow... (All good, ty for the info, will for now just go on with the tiny steps) |
Yeah @xlc is right. We don't use tips for regular payments, they are just tips as the name implies. We also don't pay upfront any tips, because we don't want to attract people that are only making noise and costing time. If you want to have proper payments, it would need to be done through treasury as @xlc said. |
Two things:
Except you think that i "only making noise and costing time". |
Alternatively use this issue #13522 (for a mini tip) |
I don't get why you want to verify the process? Verify for what? The payment will not be instant as the council still needs to accept it and decide on the value. |
I don't get it myself (analysis runs non-consciously) |
bot merge |
Waiting for commit status. |
Streamlining dev processes starts with trivial things - like a readme.
Context
https://forum.polkadot.network/t/ecosystem-wide-frame-project-manager/1856
No need for inaction during the wait.
I would like to do some basic work around FRAME, thus the future project-manager can be more efficient.
My work would involve mostly the technical stuff (repository, issue-trackers, automations etc.). At some point I would "dive deep", e.g. providing abstractions to reduce duplications / dev-effort etc.
But it all starts with the basics - like a tiny subsystem readme.
To speed things up (and avoid "time evaporated" on both sides) I'm asking here for a budget (via bounty/tip) and I would start (or better: continue) right away.
Polkadot address: 13mDFYievQov7ie1257v9bXHDyLvpXWPrgYopnUjYxgD9DnZ