Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Info
  • Must Have: 
    • Create the module(s) in Github (*
      Jira Legacy
      AM-1
      AM-1
      serverOpenMRS JIRAAM-1
      )*
    • *Load modules into CI (*
      Jira Legacy
      AM-12
      AM-12
      serverOpenMRS JIRAAM-12
      )
    • Get Yonatan Grinberg and Adam Lauz to the point where they can develop on their own
    • Lay groundwork for future, bigger, sprints
  • Should Have:
    • Jira Legacy
      AM-2
      AM-2
      serverOpenMRS JIRA
    • jira
      Jira Legacy
      AM-2
      3
      AM-3
      serverOpenMRS JIRA
    • Jira Legacy
      AM-35
      Jira Legacy
      AM-5
      serverOpenMRS JIRA
    • Jira Legacy
      AM-56
      Jira Legacy
      AM-6
      serverOpenMRS JIRA
    • jira
      Jira Legacy
      AM-6
      7
      AM-7
      serverOpenMRS JIRA
    • jira
      Jira Legacy
      AM-7
      8
      AM-8
      serverOpenMRS JIRA
    • Jira Legacy
      AM-811
      Jira Legacy
      AM-11
      serverOpenMRS JIRAAM-11
  • Could Have:
    • Jira Legacy
      AM-4
      AM-4
      serverOpenMRS JIRA
    • jira
      Jira Legacy
      AM-4
      11
      AM-11
      serverOpenMRS JIRA
    • jira
      Jira Legacy
      AM-11
      9
      AM-9
      serverOpenMRS JIRA
    • Jira Legacy
      AM-910
      Jira Legacy
      AM-10
      serverOpenMRS JIRAAM-10
  • Won't have:
    • The whole module or queuing completed

*

...

Info

Topic: Visit Scheduling or Queueing

Lead (Product Owner): Tobin

Known Developers Assigned (amount of effort in hrs dedicated to this work if possible): Unlicensed userYonatan GrinbergUnlicensed userAdam LauzUnlicensed userDaniel Kayiwa

Date: Start: November 22nd - December 6

...

  1. New to OpenMRS sprints? Want help getting started? Join ?the IRC channel and say "???": I'd like to participate in the sprint!"
  2. Pick a ticket from the available tickets in the top-left of the sprint dashboard page. (listed below)
    • Make sure it does not depend on a ticket that is incomplete.
  3. If you have any questions about the ticket, ask on the group chat
  4. Do the ticket. See our HOWTO for git. Sprint specific git HOWTO for devs with push rights: whatever works for you :-) If you don't like pull requests, don't send them. Commit and push directly to the main repo. If you do like pull requests, fork the main repo and send pull requests, but merge them right after. My favorite way is to work on the main repo, but create local branches (without pushing them to the main repo). Merge branches locally to the master and push to the main repo.
  5. Join the daily scrum to share your updates

...