IPFS: OPEN ROADMAP TO SUCCESS
My notes for everything IPFS-related. Feel free to collaborate, and let's discuss and plan the future of IPFS and the Web together!
Note: These are notes and drafts. They're not reviewed nor polished before publishing.
Outline
- Overview
- Objective
- Technologies
- Architecture
- Projects
- Merge & Unify
- Documentation
- Brand Identity
- Style Guides
- Guidelines
- Marketing
- Social Media
- YouTube Channels & Videos
- Community
- Recruitment
- UX Research
- UX Design
- DX Research
- DX Design
- eBook
Outline #2
- Standardize
- Consistency
- Guidelines
- Style Guides
- Minimize
- Review (e.g., what's old)
- Modularize
- Unite / Relocate
- Merge & Unify
- Centralize
Topics
- Directing efforts
- user onboarding
- streamlining technical processes
- process improvement
- decision support
- ecosystem growth
- organization structure / governance
- exploring new monetization strategies
- investment
- feature development
- strategy
- talent attraction
- talent retention
- employer branding programs
- creative recruitment marketing
- detailed internal best practices documents
- best practices documents
- decision making support
- discussion in the form of longer, asynchronous conversations
- make learning and using IPFS fun
- tangible results, tools, and projects.
- target audience
- our advantages and disadvantages
- insights
Ideas
- Partnership with universities, libraries and whatnot, that could help workers find reliable work space, Wi-Fi, and fight loneliness.
- Build useful tools to common problems to showcase the technology.
- Gamify the learning and usage experience
- Write articles, tutorials, and tools that relate to people's interests and day-to-day activities.
Ideas #2
- IPFS Rebranding
- IPFS Landing Page Redesign
- Create icon set
- Create living design system/style guide/branding guidelines
- Podcast
- Institutional videos that employees can show employers to influence adoption
Adoption Paths
- Integrability
- Ease of use (Usability)
- User interface
- Less time to setup and start working
- Documentation
- Extensibility
- Stability
- Compatibility
- Scalability
- Security
- Robustness
- Portability
- Operability
- Management
- Fault tolerance
- Flexibility
- Interoperability
- Emotional factors
- Performance
- Accessibility
- Adaptability
- Auditability
- Availability
- Backup
- Capacity
- Compliance
- Configuration management
- Data integrity
- Data retention
- Dependency on other parties
- Deployment
- Development environment
- Disaster recovery
- Durability
- Efficiency (resource consumption for given load)
- Effectiveness (resulting performance in relation to effort)
- Elasticity
- Platform compatibility
- Privacy (compliance to privacy laws)
- Reusability
- Safety
- Resilience
- Quality
- Certification
- Cost
- Deployment
- Modifiability
- Stability
- Testability
- Supportability
- Transparency
- Complexity
- Comprehensability
- Changeability
- Analyzability
Other
- We need a straight-forward path: Who we want to be adopting our technology first? Who's our main target?
Roadmap #1
- Start with a minimal, bundled tool that installs IPFS with minimal requirements, privacy-focused defaults, with P2P deactivated, and slowly transition into P2P activation while we educate people on how it works, their privacy concerns, and the security of allowing P2P networking.
- Content strategy
- User and market research
- Detection of Misconfiguration Vulnerabilities in Distributed (Web) Environments
References
Drive domain expertise in running open source projects by codifying best practices and creating scalable playbooks. https://jobs.lever.co/protocol/0bee6a4e-21f8-4930-81aa-d89cb305234a
- Describe the current state of the problem. Use quantitative metrics to demonstrate the importance of solving it.
- Discuss the existing research, listing the most relevant related work and key background readings. Be quantitative, and explain why the current or proposed solutions do not adequately address the problem. This is your opportunity to demonstrate your capacity as a researcher in this field.
- Define your approach to addressing or solving the problem: a. Describe the steps you would take to reach a solution. Do not simply describe the end goal. Be technical. b. How would you de-risk this research problem? What is the biggest obstacle to ensuring a successful project? For example, if your solution involves combining two technologies, explain how they would work together and what problems would likely need to be solved. c. In relation to the problem you are describing, what would define a “successful” research project?
- What limits your ability to solve this problem without Protocol Labs? How do you see Protocol Labs supporting you in pursuit of this project? https://jobs.lever.co/protocol/a1954805-fa9e-4ab1-822b-27b0cef6b34a
Get us excited about the work you want to pursue, convince us of its importance, and then convince us that you are the right person for the job. Don’t speak in generalities or broad concepts; be technical, specific, and thorough! Assume we will consult experts in relevant fields to evaluate the novelty and potential risks for your proposal. https://jobs.lever.co/protocol/a1954805-fa9e-4ab1-822b-27b0cef6b34a
Produce concise, story-centered presentations to communicate analytic insights. https://jobs.lever.co/protocol/9965d8d7-1a6c-4b94-8e94-fd83aa822c49
"calm, deliberate and timezone-inclusive conversation and decision-making" https://buffer.com/resources/instead-of-transparent-email/
"Think of your brand identity as your company’s personality. It’s how the world recognizes you and begins to trust you. If you see someone change how they look and act all the time, you won’t feel like you know who they are, and you certainly wouldn’t trust them." https://99designs.com/blog/logo-branding/how-to-create-a-brand-style-guide/
"Inconsistency will confuse and alienate your customers. A style guide is important because it helps your business communicate in a consistent way across all teams and channels." https://99designs.com/blog/logo-branding/how-to-create-a-brand-style-guide/
to Frank Weishaupt, CEO of Owl Labs, the creators of the Meeting Owl, a smart 360° camera, microphone and speaker all-in-one. When it comes to splitting a team between remote and office-based, no matter the ratio, he says that “the challenges remain the same: ineffective communication. As an employer, it’s critical to maintain a community for all workers despite their physical location, and require manager training specific to remote workers as well as provide the latest technological advancements in digital collaboration tools across the organization.” https://lp.buffer.com/state-of-remote-work-2020