Content Infrastructure JTF (CIJTF) #4454
Description
Background
The capacity to store and deliver content to end user in an efficient, secure and scaleable way is important for the Joystream Network. It is also something which occurs as a result of the concerted effort of a broad range of participants, and it is a dynamic problem which keeps changing as both requirements and constraints shift. Strengthening the ability of the network to do this more effectively is the motivation behind the new Content Infrastructure JTF, proposed in the spirit, and by using the original template, of the new JTF proposal.
Proposal
Mission
A new JTF focusing on making the content infrastructure, broadly conceived, better. This for includes, but is not limited to, improving
- reliability of uploads and storage
- content delivery speed, latency and scalability
- quality of service monitoring
- security of node infrastructure
- auditability and incentives of storage and content delivery operators
- resource accounting and data access reporting
Means
- Sharing perspectives and information.
- Accountability for ongoing efforts.
- Building reputation and finding collaboration partners and resources.
Membership
Being a member is not a requirement for full participation, including being part of meetings and related work. The purpose of this status is to distinguish an identifiable group of stakeholders who have a long term interest in driving progress, so that they can easily get in touch with each other, and built credibility and reputation in the ecosystem, and offer a pool of candidates when additional support or knowledge is required. Being a member also means you should get notified when new meetings are scheduled, and sensitivity to your availability should be kept in mind. Do you wish to
- be on this list
- not be on this list
- have your info updated
then contact secretary on Discord
Initial Members
Here is the initial set of members and their roles.
| Member | Role | Background |
|---|---|---|
| @mokhtar | Secretary | co-founder & Jsgenesis cto |
| @zeeshan | Deputy Secretary | Jsgensis Argus maintainer |
| @bedeho | Member | co-founder & Jsgenesis ceo |
| @leszek | Member | Jsgensis runtime engineer & Argus creator |
| @AlexUNet | Member | Founding member and storage lead |
| @yasir | Member | Founding member and storage lead |
| @0x2bc | Member | Founding member and storage lead |
| @l1dev | Member | Founding member and multiple group lead |
Rules (informal)
- Current code of conduct.
- Secretary can update rules.
- Secretary can update membership status.
- Secretary can evict a participant from a meeting, an also ban from future meetings for some time, or permanently.
- See additional rules under Meetings.
Meetings
- Meetings are called by the secretary or deputies based on their judgement.
- A meeting should be called with at least 5 working days notice ideally, and when announced it should still be possible for third parties to suggest agenda items.
- A meeting is called by It should have have a
- a meeting lead
- a note taker & recorder: can be same as lead. Notes should cover
- conclusions that come out of agenda topics
- conclusions from any other major topics
- major TODOs
- attendance
- a meeting link: actuals scheduling is handled by person calling meeting, e.g. using Doodle or some other practical mechanism.
- a date and time
- a rough agenda, where each item has a title, rough time scope and a presenter.
- Meetings are all recorded, e.g. like Ethereum Core Devs for the benefit of those who are not there.
- Meeting lead is responsible for ensuring notes and recording later published.