NIP-8_NULS Community Product Requirements and Task Release Process

  NIP: 8
  Title: NULS Community Product Demand and Task Release Process
  Author: Reaper Ran <reaper@nuls.io> 
  Discussions-To: https://nuls.community/d/462
  Status: Last call
  Type: Process
  Created: 2019-3-21

Preface

NULS is an open source community project. And innovation is the driving force behind the development of open source community projects. The community is both a carrier for the NULS project and a user of the NULS project. Then the product demand must come from the market and users, so I hope to write a process for community product demand collection.

Abstract

The NULS Community Product Demand and Task Release process demonstrates how a community member can initiate a demand, as well as a process from reporting and evaluating the demand to technology development.

Motivation

In order to give full play to the initiative of the community, and stimulate the participation of community members to provide the products that are creative for NULS development and have great significance for the value enhancement and ecological development of NULS. The product manager then evaluates the demands of the community and then add them to the community development.

Specification

I.The product demand proposal

  1. Initiate a product demand proposal on the community website nuls.community;

  2. The proposal needs to describe the demand in details as much as possible;

  3. The proposor organize the community to participate in open discussions, collect suggestions, and improve the proposal;

  4. Post the demand to the Issues section of the NULS Github related section.

II.Collecting and reviewing demand

  1. Product manager conduct research and analysis on product demand proposals;

  2. The NULS core team and the NULS councils review whether it enter the development.

III. The allocation of technology development

1.Assigned to NULS CCC members

  • Sort out product demands and assign product demands to NULS CCC members for development;

  • Product manager follow up acceptance and release of product.

2.Assigned to non-CCC members— Task release reward

  • Product manager evaluate product demands and determine a task reward standard;
  • The product manager forwards the proposal to the council member to initiate the fund proposal in accordance with the original product proposal;
  • The Product manager publish the product task on the reward task page;
  • The developer applies for the task, and the product manager updates the task status to be in progress;
  • The developer completes and submits;
  • After the Product manager finish product acceptance, the task status is updated to completion;
  • The members of the council submit the fee payment application to the foundation mailbox.
 NIP: 8
 标题: NULS社区产品需求和任务发布流程
 作者: Reaper Ran <reaper@nuls.io>
 讨论渠道: https://nuls.community/d/463-nuls
 状态: 公示
 类型: 流程
 创建日期: 2019/03/21

前言

NULS作为一个开源社区项目,创新是开源社区项目发展的动力。社区既是NULS项目的载体,也是NULS项目的用户。那么产品需求一定是来自于市场和需求的,所以希望制定一个社区产品需求搜集的流程。

摘要

NULS社区产品需求和任务发布流程展示了作为一名普通社区成员如何发起一个需求,以及这个需求的提报和评测再到技术开发的一个流程。

动机

为了充分发挥社区的能动性,激发社区成员参与,为NULS发展提出创意的、对NULS的价值提升和生态发展有重大意义的产品。然后产品管理人员对社区提出的需求进行评估后加入到社区开发中。

规范

一、产品提案

1、在社区网站nuls.community发起产品需求提案;

2、提案中需要尽量详细的描述需求和尽可能多的产品细节;

3、提案成员组织社区参与公开讨论,搜集建议,完善提案;

4、发布需求到Github相关分支的Issues中。

二、收集和评审需求

1、产品管理人员对产品需求提案进行调研和分析;

2、NULS核心团队以及理事会进行评审是否进入开发。

三、分配技术开发

(一)分配给NULS CCC成员

1、将产品需求进行梳理,并且将产品需求分配给NULS CCC成员进行开发;

2、产品管理人员跟进产品验收和发布。

(二)奖励任务发布

1、产品管理人员将产品需求进行评估,确定一个任务奖励标准;

2、产品管理人员将提案转交给理事会成员按照原来的产品提案发起基金提案;

3、产品管理人员将产品任务发布在奖励任务页面上;

4、开发者申请领取任务,产品管理人员更新任务状态为进行中;

5、开发者完成并提交;

6、产品管理人员验收产品后将任务状态更新为完成;

7、理事会成员提交费用支付申请到基金会邮箱。