InKCre / .github

document of InKCreThing
Creative Commons Attribution Share Alike 4.0 International
0 stars 0 forks source link

Organization initial tactic/roadmap #2

Closed xiaoland closed 9 months ago

xiaoland commented 9 months ago

This tactic serves for our organization's launch stage. First, we need to define the launch stage. Then, we discuss topics from InKCre/.github#3, and set OKRs for each. Finally, we make plans for every OKR.

What aspects/topics

  1. Product(core product)
  2. Development
  3. Management
  4. Operation
  5. Ecosystem

What's next

The tactic will be implemented through aspect plans stored in our knowledge base. Aspect plans will be then implemented through GitHub Projects.

Considering read

https://zhuanlan.zhihu.com/p/343046046 https://www.perdoo.com/okr-guide/#how-to-write-okrs https://asana.com/resources/okr-meaning

xiaoland commented 9 months ago

Let's define the launch stage first. We will establish the fundament for future development, management, operation ... etc. Also, the core product's first release implemented the basic features.

Time Range: from 2024-2-14 to 2024-5-1

Here are the stage-level OKRs:

  1. build the core product into basically usable
    • this part will be discussed in InKCre/InKCre#3
  2. build the development's code of conduct
  3. build the organization's management mechanism
  4. build the operation's mechanism
  5. build the operation following the core product's first release

As you can see, Key Results aren't listed yet. This part will be discussed in each topic.

xiaoland commented 9 months ago

Development

OKR from stage-level

Build the development's code of conduct

  1. document supporting code contribution
  2. fundament for coding
  3. how to react to code-related issues

Aspect-level Objective

Build the fundament for coding

  1. coding standard
  2. coding workflow
  3. automated coding workflow

Write documents supporting code contribution

  1. how to give a pull request
  2. how to develop on your env

Considering read

https://opensource.guide/code-of-conduct/ https://www.browserstack.com/guide/coding-standards-best-practices

xiaoland commented 9 months ago

Management

OKR from stage-level

Build the organization's management mechanism

  1. static organizing
  2. dynamic organizing
  3. SOP for decision-making
  4. SOP for planning

Aspect-level OKRs

Build static organizing

  1. organization roles, duties and permissions
  2. organizational governance structure

Build dynamic organizing

  1. project management
  2. knowledge management
  3. communication

Condering read

https://opensource.guide/leadership-and-governance/#what-are-examples-of-formal-roles-used-in-open-source-projects

xiaoland commented 9 months ago

Operation

OKRs from stage-level

Build the operation's mechanism

  1. encourage contribution
  2. document everything
  3. make people feel welcome
  4. make users keep in touch with us

Make the operation keep up with the core product's development

  1. license for core product
  2. issue's code of conduct
  3. get the core product out to users

Aspect-level OKRs

Make people feel welcome

  1. thank them for landing
  2. make it easy to use our product
  3. be responsive
  4. give a place for users to gather

Encourage contribution

  1. what can be contributed
  2. how to give a contribution
  3. what can be attained through contributions

Document everything

  1. knowledge management
  2. an easy-accessed document

Make users keep in touch with us

  1. contact
  2. subscribe to our channels
  3. blog

Get the core product out to users

  1. publish videos to the video hub
  2. post on social media
  3. post to newsletter
  4. post to AlternativeTo
  5. post to Reddit

Considering read

https://opensource.guide/building-community/#setting-your-project-up-for-success

xiaoland commented 9 months ago

Ecosystem

Not yet ready, maybe in next stage Currently, Operation will take over its responsibilities.