We have delivered 2 milestones for the [subsquare collectives](https://collectives.subsquare.io/) development, [M1](https://polkadot.subsquare.io/referenda/631) and [M2](https://polkadot.subsquare.io/referenda/1001). Basic UI components and simple business workflows are implemented, including membership management, salary, referenda, treasury, statistics, etc. Subsquare is now the most used platform by fellowship after the 2 milestones development. According to fellowship members' feedback, we are proposing to develop some new features. Most of our work can be tracked [here](https://github.com/opensquare-network/subsquare/issues/5215).

![Qmek2ndLJPGe1BB48QBP3m69CoUtANhnYhLx7vyjac2wMj.png](https://subsquare.infura-ipfs.io/ipfs/Qmek2ndLJPGe1BB48QBP3m69CoUtANhnYhLx7vyjac2wMj)

## A clear task list

- Member/candidate promotion wish tasks. We show member promotion wishes that need to be handled and provide interfaces for members to cast their votes.
- Member retention wish tasks. Same with promotion wishes, members can see these wishes and cast their votes.
- Fellowship member salaries are paid by cycles including registration and payout periods. We developed a task list to remind members to register and claim their salary. It simplifies the process for members to claim their salaries.
- Wish evidence submission task. This helps members to submit their evidence in time for rank retention and promotion.
- Wish evidence review task. Higher rank members need to review other members' evidence and handle them. They may create a referendum for members to vote.
- Member demotion and candidate off board task. It list all members whose demotion periods are reached and provide an easy way to demote part or all of them.

## Member pages new design and unification

- Redesign fellowship members page and merge the old fellowship core page into it. 
    - The new members page provide 2 views, a list view and a card view.
    - More improved filters to get members/candidates with wishes.
    - Add utility buttons to help quick view and vote wish evidence.
- More member info on profile page fellowship tab
    - Show member's evidence and members with enough ranks can vote on the evidence.
    - Anyone can see this member's vote records, membership and salary activity records. We developed a heatmap for a member's referenda votes and we can use a slider component to see the participation rate of a referenda scope.
    - Check whether to show the profile page fellowship tab on the server side and show it if an address is a history fellowship member.
    - Refactor the salary and status panel to show more info including joined salary cycles, improve the salary component and refactor the rank change statistics component.

## Referendum enhancement

- Improve votes info. Now we can see all members who are eligible to vote.
- On the detail page of a referendum to promote or retain a member, we show the target member's demotion and promotion status.
- We improve vote eligibility checks, so members with different ranks can know whether they can vote a referendum and know the reasons.
- Support anyone to cleanup poll and help release space from storage.
- Members can see whether they have voted on some referenda on the list page.

## Evidence content indexing and discussions

Members need to submit evidence for their rank retention or promotion. Currently, members submit their evidences first on github as a pull request. We develop pages to enable members to review all history evidence list by member and have discussions. Work includes:
1. Fetch evidence content from IPFS when indexing.
2. Update evidence state so members can know whether an evidence is active on chain.
3. Extract evidence title by parsing evidence markdown content.
4. Enable SSR for related evidence on the referendum detail page.
5. An evidence detail page where anyone can discuss it, see its basic info, related referenda and members can vote on it.
6. An evidence list page where we can see all members' active evidence and history submissions.

## New member application

Any one can create a member application by filling its address and application content. Members with enough ranks can review applications and induct applicants to the fellowship.

## A consolidated feeds

We've released activity feeds for [membership](https://collectives.subsquare.io/fellowship/members/feeds) and [salary](https://collectives.subsquare.io/fellowship/salary/feeds), but they are on different sections. According to Gav's [guidelines](https://hackmd.io/@polkadot/fellowshipux), we will implement a consolidated feed stream including proposal, membership and salary activities.
- Latest activities will be shown on the overview page.
- There will be a dedicated page for all activities and we can filter out target ones by type, events and related


## Other enhancements

- Fellowship wish evidence template support.
- A new panel on the overview page to show treasury and salary pool balance.
- Menu simplification:
    - Not show all tracks on the fellowship menu to make the menu simple. Users can still select a track on the referenda list page.
    - Remove the treasury menu and leave only spends menu for fellowship.
- Disable the corresponding approve/promote button where there are already referenda for members.
- Not add track name to referenda title when title is customized.
- Add options on referenda template to enable members placing decision deposit and vote at the same time besides referendum creation.
- Enable users to select target members on member promotion/retention referendum creation template. 
- Add the missed info for tracks to fast promote members.
- Show salary and rank info on salary claim popup.
- Extract treasury spend info from referenda and show it on the referendum detail page.
- Show fiat value for an active fellowship referenda which request DOT.

## Budget

|  Work   | Estimated hours  | memo |
|  ----  | ----  |  ----  |
| Todo list | 800  | 4 FTE * 25 days |
| Member pages new design and unification  | 600 | 3 FTE * 25 days |
| Evidence content indexing and discussions  | 160 | 2 FTE * 10 days |
| New member application  | 160 | 2 FTE * 10 days |
| A consolidated feeds  | 160 | 2 FTE * 10 days |
| Other enhancements  | 800 | 4 FTE * 25 days |
| Total  | 2680 |  |


Hour rate $90, total request is $241,200. We got some feedbacks from fellowship members that the request is high considering it's milestone 3 and we have already developed some basic features. Though we think the work for this milestone is more challenging and cost more of our time, we decide to lower the request and reduce our hour rate from $90 to $60, and the adjusted request is $160,800 which we hope this looks not pricy to the community.


## Q&A

### 1. Why not fellowship treasury?
We did and [here](https://collectives.subsquare.io/posts/22) is the previous proposal. We shared this in the fellowship element open channel and got feedbacks:
- The budget is high considering there are already 2 milestones.
- Fellowship treasury usually approve request under $70K.

Fellowship referenda can only be submitted by members with rank >= 3 and OpenGov is our only option. Though milestone 3 cost more of our time than the 2 privious milestones, it's fine for us to reduce the budget to avoid conflict of expectations.

### 2. Why subsquare and how to prove your work?

[Subsquare collectives](https://collectives.subsquare.io/) is the most used UI by fellowship in several candidates, and we believe our work to support fellowship has the highest ROI. Our work for milestone 3 starts from 2024.Q4, and most work can be tracked in [subsquare issue #5215](https://github.com/opensquare-network/subsquare/issues/5215).

### 3. Will there be milestone 4?

Currently no, but honestly we are not sure in the future. We think we've completed most basic features about related pallets including `ranked-collective`, `core-fellowship` and `salary`, but it depends on members finally. There maybe some necessary work to support customized workflow, fix bugs, UX improvements, etc.

### 4. Any feedbacks from members about subsquare UI for fellowship?

We think in general feedbacks are positive. Some members left issues on github and in most cases we can fix them in time. I'd say it's hard to develop a 100% perfect UI to satisfy everyone and our work is still not perfect, but we are working hard to improve it and always happy to get feedbacks.

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

#1722 Subsquare fellowship support milestone 3

No Active Proposals