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 Salaries #50

Merged
merged 19 commits into from
Dec 18, 2023
Merged

Fellowship Salaries #50

merged 19 commits into from
Dec 18, 2023

Conversation

joepetrowski
Copy link
Contributor

The Fellowship Manifesto states that members should receive a monthly allowance on par with gross income in OECD countries. This RFC proposes concrete amounts.

Copy link
Contributor

@xlc xlc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

presumably we want to update the amount yearly. should we have a section describe how the amount get updated?

text/0050-fellowship-salaries.md Outdated Show resolved Hide resolved
text/0050-fellowship-salaries.md Show resolved Hide resolved
@sourabhniyogi
Copy link

sourabhniyogi commented Nov 23, 2023

I believe many Polkadot Fellows level 3+ are OGs who hold significant amounts of DOT -- for them, salaries are largely ceremonial, like Musk/Ellison/Jobs/Bezos/... saying "see, I only earn $1 in salary!" and pretty much couldn't care less about the salary because staking rewards + DOT value itself dominates their actual compensation. So the following comments are geared for two purposes:
(a) addressing "living wages" of fellows not in this OG category, attempting to approximate a Silicon Valley HR person
(b) using the Salaries pallet for new collectives on the Collectives chain, and the "Dan 3" value as the "standard"

  1. Polkadot fellows (at least everyone I have seen work at 2 or 3 or higher) are SUPER engineers, far better than the average CS grad from top 10 schools in the US. I think the $80K/yr for Level 3 would be unheard of for super engineers. I doubt anyone is doing great work because they are getting a "living wage", they are doing great work because they love doing great work on Polkadot, but you need to increase your Rank 3 to be like a Stanford Master's degree CS grad, which is in the $160K range. For anyone not in the OG club, this would support getting medical insurance for like a spouse and their family, which is par for the course, I think.

  2. The multiplier mechanism on a Dan 3 baseline is a great idea. We can use this baseline in like dozens (up to 40!) collectives -- and I presume each collective's code could reach into the Fellowship storage and fetch that Dan 3 baseline in USDT and skip each collective having to make independent salary decisions. Instead, when Dan 3 goes up due to inflation (its a thing, in the US), other collectives can rise in direct tandem programmatically. Is this possible?

  3. I doubt there is anything special about there being 9 ranks instead of 90 or 100? If you increase the number of ranks by a factor of 10 or 11, you can promote people 10 ranks instead of 1 ... and not have these unnecessarily massive jumps of $40K/yr in salaries when little increments of 1 in a 90 rank system would be $4K/yr is super fine. This can be especially valuable for the spread between rank 2 and 3.. which is a jump of $60K, which is just... too much of a jump! No HR person would think these jumps as reasonable.

  4. Receiving a % of compensation in DOT instead of 100% in USDT or 100% in DOT should be part of this Salaries pallet, in the same way that receiving a portion of compensation in restricted stock or stock options is common to most tech companies. Defining the Dan 3 baseline in USDT and then getting a "salary" in both USDT and DOT determined by the recipient's chosen percentage would be usable by collectives that have members "Salary" receiving a % of Dan 3 in USDT and DOT. All collectives in the Collectives Chain would then manage the USDT+DOT with the Salary pallet. This is not about Fellowship salaries alone.

  5. Being able to take a few months off for parental leave, sick leave, sabbatical, health reasons, etc. should be a key feature of the Salaries pallet. Do salaries get paid on 28 day eras? Having the era-like resolution to get the "I took a leave for 45 eras" should be possible, and automated payment frequencies approximating months is highly desirable, not just for Fellows in this collective, but for other collectives that also should use the same Salaries pallet. For larger collectives with people entering in permissionlessly, we need this granularity and frequency of payment.

@joepetrowski
Copy link
Contributor Author

  1. It's impossible to make one number that applies to every geopolitical location. A good salary for an engineer out of university in Europe (even in cities like Paris) is 50-60k EUR. I know in the prelude you said you are approximating a Silicon Valley HR person, and in that context, you're right. With this proposal, you'd have to be a very high rank to live in the Valley, or be willing to relocate if "living off the Fellowship salary" is your aim.

  2. That would be possible, yes. Just so people know, there's nothing special about having 10 ranks (0 - 9), it's just what was chosen for the Tech Fellowship. You can make a group with 3 or 9 or 100 ranks.

  3. Yeah exactly what I was writing in (2). Jumps in salary like that are not normal for year-over-year inflation adjustments, but they are normal when getting significantly promoted. Although the manifesto declares minimum years of service for each rank, in reality it probably takes more than one year to advance one rank; a lot of the requirements are quite difficult and would require consistent performance and contributions at a very high level.

  4. Yes I agree about having a percentage in DOT be possible. Right now the Salary pallet makes you specify one asset, but we could change it to accept multiple. Also USDT is not the right asset for every group. For example, with Ambassador Program, DOT makes sense (at least at lower levels) because we want them to have some DOT for demos like "how to {stake, vote}". (Sidenote: Let's save this argument for an Ambassador Program proposal, just an example.) But when it comes to implementing these things, priorities/resources/etc. Should I ask someone to stop working on CCTP compatibility or Coretime to support USDT+DOT salaries (when we can just take salary in a single asset)? IMO, no.

  5. It's all configurable. Collectives should be careful about permissionless entry and salaries though. Collectives are supposed to largely self manage, and if senior members don't pay attention, they will allow abuse. If senior members are paying attention, then dealing with things like a vacation seem very doable.

@xlc
Copy link
Contributor

xlc commented Nov 28, 2023

I don't want to scope creep this RFC so #55 for further discussion after this is accepted.

@xlc
Copy link
Contributor

xlc commented Nov 28, 2023

Another related issue, would there be retrospective salary payment? If there is none, I will simply apply for separate treasury proposal.

@joepetrowski
Copy link
Contributor Author

Another related issue, would there be retrospective salary payment? If there is none, I will simply apply for separate treasury proposal.

No, there is no retrospective payment.

@joepetrowski
Copy link
Contributor Author

/rfc propose

@paritytech-rfc-bot
Copy link
Contributor

Hey @joepetrowski, here is a link you can use to create the referendum aiming to approve this RFC number 0050.

Instructions
  1. Open the link.

  2. Switch to the Submission tab.

  1. Adjust the transaction if needed (for example, the proposal Origin).

  2. Submit the Transaction


It is based on commit hash f4626dc00f4dc054ebf15f7251e7300acd725336.

The proposed remark text is: RFC_APPROVE(0050,c4bc6f6c71fa05036c592c7ed0ba4f6f4044f69b7d4b1873d3cb75202c849c19).

@joepetrowski
Copy link
Contributor Author

/rfc process 0x92681c170876480c8f6e840f7845083fd899cdfedd1f556ffb1aa9ab38891005

@paritytech-rfc-bot paritytech-rfc-bot bot merged commit df69e9c into polkadot-fellows:main Dec 18, 2023
@paritytech-rfc-bot
Copy link
Contributor

The on-chain referendum has approved the RFC.

@joepetrowski joepetrowski deleted the fellowship-salaries branch December 18, 2023 10:00
@gavofyork
Copy link
Contributor

A III Dan is someone whose contributions match the expectations of a full-time individual contributor.

Note that this is false. The manifesto defines the expectations at each grade. Even at I Dan, there is an expectation for full-time contributions.

@shawntabrizi
Copy link
Member

A III Dan is someone whose contributions match the expectations of a full-time individual contributor.

Note that this is false. The manifesto defines the expectations at each grade. Even at I Dan, there is an expectation for full-time contributions.

But clearly a Dan I salary is an insufficient living wage, so the expectations are that fellowship members are allowed to facilitate their salary with treasury proposals or companies within the ecosystem?

@xlc
Copy link
Contributor

xlc commented Jan 6, 2024

I just found this in manifesto today under section 8 Allowances

These are a monthly affordance, paid in DOT. There are two levels: standard and passive. Standard should be between the 80th-90th percentile of gross income in the OECD group of countries. Passive is no greater than 50% of standard. The total amount given as passive allowance should be no greater than 10% of the total amount given as standard allowance.

So I guess that means Dan III should be 80% percentile and Dan VI should be 90%?

@gavofyork
Copy link
Contributor

Yes, or the old fashioned way of blood, sweat and tears 😇

@gavofyork
Copy link
Contributor

I just found this in manifesto today under section 8 Allowances

These are a monthly affordance, paid in DOT. There are two levels: standard and passive. Standard should be between the 80th-90th percentile of gross income in the OECD group of countries. Passive is no greater than 50% of standard. The total amount given as passive allowance should be no greater than 10% of the total amount given as standard allowance.

So I guess that means Dan III should be 80% percentile and Dan VI should be 90%?

Broadly speaking, yes. However, it turns out those numbers are rather difficult to find so the actual numbers are something of an estimate. Furthermore, unless there is outside funding, the Fellowship is limited to whatever is acceptable to the Treasury.

bkchr added a commit to polkadot-fellows/runtimes that referenced this pull request Jan 8, 2024
Fellowship Salary Budget & Period

In alignment with the Fellowship Salary
[RFC](polkadot-fellows/RFCs#50), the projected
total monthly budget stands at 240,833 USDt.

With this PR, I invite the Fellowship members to refine the following
constant parameters:
- RegistrationPeriod - # of blocks within a cycle which accounts have to
register their intent to claim.
- PayoutPeriod - # of blocks within a cycle which accounts have to claim
the payout.
- Budget - the total budget per cycle.

Please be aware that the pallet does not have a visibility into the
actual balance of the account holding the salary budget. If this account
lacks sufficient assets, subsequent salary claims will encounter
failures.

---------

Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Oliver Tale-Yazdi <[email protected]>
@anaelleltd anaelleltd added the Implemented Is merged or live as a feature/service. label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Implemented Is merged or live as a feature/service.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants