summer

Prerequisites

  1. Read Six Lines Of Code. Two MVPs. One Chatbot.
  2. Get started with Wechaty
  3. Join our Gitter Channel
  4. Run Wechaty with Whatsapp
  5. Read Introducing Wechaty Puppet Service (Providers)
  6. Read Gource Visualization for Wechaty

About You

  1. Who are you? What are you studying?
  2. What exactly do you intend to do? What will not be done?
  3. Why are you the right person for this task?
  4. To what extent are you familiar with the software you’re proposing to work with? Have you used it? Have you read the source? Have you modified the source?
  5. How many hours are you going to work on this a week? 10? 20? 30? 40?
  6. Do you have other commitments that we should know about? If so, please suggest a way to compensate if it will take much time away from Summer of Code.

Proposed Schedule

During each phase, please make it clear whether the code will be ready to be submitted for inclusion. Also, ensure that your code will be available for review almost every day. Do not work long periods (more than 2-3 days) without submitting code to the git repository for your project. You should normally commit code to Github every day or almost every day (except weekends).

Write down your plan in detail about what will you do during the following periods?

  1. March (Application Period)
  2. April (Acceptance Waiting Period)
  3. May (Community Bonding Period)
  4. June (Coding period 1)
  5. July (Coding period 2)
  6. Aug (Coding period 3)