【翻译|公告】WPS申请WPF的发展资金

eoshenzhen (44)in #eos • 6 years ago

以下内容来自微信公共帐号“EOS技术爱好者”，搜索“EOSTechLover”即可订阅，翻译Lochaiching。转载必须保留以上声明。仅授权原文转载。

本文原文链接为https://drive.google.com/file/d/1pQRNf69WLA36NMVAFq8MS0AO4q5F0-AE/view

"EOS技术爱好者"全程由EOShenzhen运营，喜欢我们请为我们投票（EOShenzhen的投票账号：eoshenzhenio）！

WPS Development Request for Worker Proposal Funding

WPS申请WPF的发展资金

Date: 2018-08-31

Project Lead: Jae Chung

Building the platform to fund innovation on EOS

在EOS上建立创新资金平台

Proposal Summary

● This proposal includes the following scope of work:

○ Smart contracts for registration, submission, proposal review, and voting.

○ Web platform for registration, submission, forum and voting.

○ Software that incorporates the needs of new categories as they come online.

○ Secure infrastructure to deploy the platform.

The funding asked for 6 months is $378,421

提案摘要

●该提案包括以下阐述的工作范围:

○智能合约注册、提交、审查提案和投票

○网页平台的注册、提交、论坛和投票。

○软件，包含新类别功能上线时的需要。

○平台部署安全基础设施

○这次申请资金共计是378421美元（6个月）

Introduction

Our mission is to support the growth of EOS Ecosystem by developing the WPS software, a platform for the community to review, discuss, select, fund, and hold accountable projects proposed by community members to benefit EOS.

The EOS WPS is a process which allows the community members to fund projects proposed by other community members for the good of the ecosystem. It is a critical piece of software which directly contributes to the success of the system and manages funding. However, it is quite complicated to design and implement a decentralized yet governable system that supports those who are willing to innovate for the community, while managing to prevent non-legitimate projects and frauds from stealing from the network.

The problems the community faces in deploying the WPS system:

● How can EOS Community members share their ideas and request funding?

● Once requested, how can the community intelligently discuss those proposals?

● Once discussed, how will will they select which ones to fund?

● Once funded, how will they track the projects to completion?

● Once completed, how can the community evaluate it?

● How do we make the WPS work?

How do we continuously implement new features based on community feedback?

介绍

我们的任务是通过开发WPS软件来完善EOS生态系统的发展。WPS软件是一个让社区成员为了让EOS社区变得更好而提出可以审查、讨论、选择、资助项目的平台。

EOS WPS是一个为某些社区成员能为社区提出有利于生态系统的项目而申请相关资金的存在。它是一个举足轻重的软件，对整个系统的成功和资金的管理有直接作用。然而，设计和实现一个去中心化但可治理的系统是相当复杂的，它支持那些愿意为社区创新的人，同时想办法防止不合法的项目和欺诈从网络窃取到不法财富。

社区在推行WPS系统时所面对的问题:

如何让EOS社区成员更好地分享他们的想法和资金申请?
一旦申请，社区如何明智地讨论这些提案?
一旦讨论，他们会选择哪些资金申请?
一旦资助，他们将如何跟踪项目保证项目完成?
一旦完成，如何评价它对社区的价值?
如何使WPS正常运转?
如何基于社区的反馈不断迭代功能?

The Solution: The EOS WPS Software and Platform

A native EOS dapp created for the EOS community, allowing the token holders to:

● Propose projects to benefit the ecosystem

● Review and discuss the proposals

● Vote on proposals to be funded

● Oversee funded projects status

● Review the results later to understand the impact

Track all actions real-time on chain

解决方案：EOS WPS软件和平台

为EOS社区创建的本地EOS dapp，允许token持有者:

●提出对生态系统受益的项目

●评审和讨论提案

●投票表达对提案的资助与否

●监督受资助项目的运作状态

●评审项目成果的影响

●在链上实时跟踪所有action

Proposal Details

Phased Approach

Phase 0: Technology Foundation

Phase 1: WPS Bootstrap System (Emergency Phase)

Phase 2: WPS beta

Phase 3: WPS v1.0

Phase 4: Ongoing maintenance

提案的细节

分阶段实现

第0阶段：技术基础

第1阶段：WPS引导系统(紧急阶段)

第2阶段：WPS beta版本

第3阶段：WPS 1.0版本

第4阶段：持续维护

Phase 0: Technology Foundation

Timeline: Aug / Sept

Deliverables: Initial Codebase for community peer review

*Time volunteered by active community members ahead of funding to get the project moving

第0阶段：技术基础

时间轴：8月/ 9月

交付：社区同行评审的初始基础代码

*具体时间由活跃的社区成员在资助项目之前自愿提供的时间段，再进行商议

Phase 1: WPS Bootstrap System (Emergency Phase)

Timeline: October / November

Deliverables: A working, functional WPS platform, with limited functionality. Includes: Create Proposals, List Proposals, Review Proposals, Vote on Proposals, Fund Proposals

Cost: Budget breakdown in appendix

第一阶段：WPS引导系统(紧急阶段)

时间轴：10月/ 11月

交付：一个工作的、功能性的WPS平台（功能有限）

包括：创建提案、列出提案、审查提案、投票表决提案、资金提案

成本：附录在预算细目中

Phase 2: WPS beta functionality

Timeline: December / January

Deliverables: Completed beta functionality, full infrastructure deployed.

Includes: Expanded review tools and on chain evaluation of proposals, expanded review on chain tracking of project progress, completed project metrics

Cost: Budget breakdown in appendix

第2阶段：WPS beta功能

时间轴：12月/ 1月

交付：已完成的beta功能，完整的基础设施部署。

包括：扩展的评审工具和链上评估提案，项目进度链上跟踪的扩展评审，已完成的项目指标

成本：附录在预算细目中

Phase 3: WPS v1.0

Timeline: March / April

Deliverables: Polished UX and Security Audits

Includes: Following projects, discussion threads, navigation bar, project history, following friends, donations, separate categories, and features suggested by the community on forum discussions.

Cost: Budget breakdown in appendix

第3阶段：WPS 1.0 版本

时间轴：3月/ 4月

交付：优化的UX和安全审计

包括：接下来的项目、讨论线程、导航栏、项目历史、关注者、捐赠事项、单独的类别，以及社区在论坛讨论上建议的功能。

成本：附录在预算细目中

Phase 4: Ongoing Maintenance

Timeline: April+

Deliverables: Fix outstanding bugs, update code to match EOS.IO code updates, maintain servers, continue adding features based on community feedback.

Cost: Smaller ongoing costs, to be voted in separately by a worker proposal once the WPS has launched

第4阶段：持续维护

时间轴：四月或四月后

交付：修复明显的bug、更新代码以匹配EOS.IO代码更新\维护服务器，基于社区反馈继续迭代

成本：较小的持续成本，一旦WPS启动，将由WP单独表决

Our Team

Development:

Sungjae Chung (HKEOS) - https://www.linkedin.com/in/sungjaechung/

Syed Jafri (EOS Cafe Calgary) - https://www.linkedin.com/in/sjsyedjafri/

Hugo Campanella (HKEOS) - https://www.linkedin.com/in/hugocampanella/

Adrian Hunter (Saltblock) - https://www.linkedin.com/in/adrian-michael-hunter/

Boram Kim (EOSeoul) - https://www.linkedin.com/in/boram-k-b2530669/

Thomas Do (EOSeoul) - https://www.linkedin.com/in/thomas-do-01911516a

Alfred Cheuk (HKEOS) - https://www.linkedin.com/in/alfredcheuk/

Sheldon Huang (EOShenzhen) - https://github.com/sheldonhh

Abbas Ali (Blockmatrix) - https://github.com/abbasali

Kedar Iyer (Libertyblock) - https://www.linkedin.com/in/kedar-iyer-47552649/

Harry Kim (EOSYS) - https://www.linkedin.com/in/jungyoon-kim-3658a2135/

Sungmin Ma (EOSeoul) - https://www.linkedin.com/in/sungmin-ma-1a3a9b160/

Advisors:
Michael Yeates (EOSDAC, advisor)

Eric Björk (EOS sw/eden, advisor)

John Milburn (advisor)

我们的团队

开发者：

Sungjae Chung (HKEOS)、Syed Jafri (EOS Cafe Calgary)、Hugo Campanella (HKEOS)、Adrian Hunter (Saltblock)、Boram Kim (EOSeoul)、Thomas Do (EOSeoul)、Alfred Cheuk (HKEOS)、Sheldon Huang (EOShenzhen)、Abbas Ali (Blockmatrix)、Kedar Iyer (Libertyblock)、Harry Kim (EOSYS)、Sungmin Ma (EOSeoul)

顾问：

Michael Yeates (EOSDAC, 顾问)

Eric Björk (EOS sw/eden, 顾问)

John Milburn (顾问)

Why Trust Us?

● We are committed to the EOS Ecosystem, affiliated with 7 different standby block producers.*

● We are familiar with EOS software, infrastructure, and deeply involved in the network technology. We have even submitted patches to the EOS.IO code itself, and some of our developers our responsible for managing the EOS-Mainnet repository.

● We have a combined 50+ years of technology development experience.

● We volunteered our time for the past 90 days to put together an initial foundation for the project which is available now for community code review.

● Members of our team have created well-known community tools and projects, including:

○ Bloks.io (block explorer)

○ EOS Test Cave

○ Eosnova.io (Wallet)

为什么应该信任我们?

●我们致力于EOS的生态系统，来自于7个不同的备用BP。*

●我们熟悉EOS软件、基础设施、并深入参与网络技术。我们也向EOS.IO代码提交g补过丁。我们的一些开发人员负责管理EOS-Mainnet的存储库。

●我们综合起来有超过50 年以上的技术开发经验。

●我们作为志愿者在过去90天一起检查最初的基础项目的代码（即现在社区可用的代码）。

●我们的团队成员开发过社区皆知的工具和项目，包括:

○ Bloks.io (区块搜索器)

○ EOS Test Cave

○Eosnova.io(钱包)

原型预览

Our Development Process

● We develop using Agile software methodologies so that we can adapt to changing requirements as we learn about WPS needs.

Our development process will be broken down in bi-weekly development sprints during which we will continuously loop through the following phases; discover, design, code and test. This approach will allow us to quickly learn from previous sprints and iterate the platform regularly.

● We commit to transparency to the EOS Community with bi-weekly updates, a public code repository, a public development backlog (Trello Board) and of course open sourcing the code itself.

我们的开发过程

我们使用 Agile软件开发方法，这样我们可以适应不断变化的WPS的需求。
我们的开发过程将在两周一次的开发冲刺中被分配完成，在此期间我们将一直循环执行以下阶段：发现、设计、写代码和测试。这种方法将允许我们快速回顾学习前面各个短期目标并定期迭代平台。
我们承诺的透明度将会随着EOS社区的双周刊更新，并且会有公共代码库,一个公开开发的待办事项列表(Trello Board)，最后当然会开源代码。