Skip to content

Latest commit

 

History

History
69 lines (45 loc) · 2.24 KB

checklist.md

File metadata and controls

69 lines (45 loc) · 2.24 KB
Raw

What is the project's vision?

This is typically a single sentence that describes what the project aspires to be. Example: "A JS framework that allows developers to build better apps, faster". If this doesn't exist, write "none".

A guide and application that:

  • Teaches people how to solve common problems with DoneJS
  • Demonstrates that DoneJS elegantly solves common problems.

Produce people who can build a good guide without much oversite.

How will the project measure success?

Example: Increase mobile conversion rates to 0.75-1.0%, currently ~0.3%. If this doesn't exist, write "none".

  • Approximately as many page views as PMO.
  • If a question is directly related to parts of this guide, we should be able to post a link to the relavant section and there are no follow ups except for ones not covered by the guide. Basically, if someone asks, how to deal with cookie based sessions, we should post to this guide's session section.
  • Github Stars?
  • Roomplanner and Jobcostracker are successful without Justin managing them (but he's involved when appropriate).

What is the strategy for accomplishing the project's goals?

What is the strategy for accomplishing the project's goals?

  • Establish clear expectations.

    • Goal oriented
      • Start and end of day status updates.
    • Getting help is the solution to delivery quality wtihout working longer hours.
    • Manage by over-async-communicating tasks until developers can take over.
    • Be proactive if you don't have an issue. Upward manage expectations.

  • Sharing knowledge

    • Daily code reviews of previous day's pull requests or progress.
      • Commit to your branch every night.
    • Pairing?

What is the project's roadmap? What are the goals, plans and release schedule after the current release?

  • - Identify common problems in Bitballs that are not in PMO and DoneJS Chat.

    • Sessions, simple admin rights.
    • Relationships between models + derived values.
    • Node restful services and server-side rendering mixed.
    • Ignore parts of SSR

  • - Outline the guide.

  • - Get DoneJS essential features in place.

  • - Justin write the guide.

  • - Convert to a "good" DoneJS app

    • tests
    • docs
    • demo pages

  • Put it together.