Sync 2.0 Project daily stand-ups

Software Add-on Modules
,
1

Hi Everyone,

in this thread, each of developers will share own work day. Each post should have 3 sections. Daily stand-up pattern

Blocked?

  • no

What I’ve done

  • Fixed SYNCT-001: short description of ticket
  • Worked on SYNCT-002: short description of ticket

What’s next

  • Start work on SYNCT-010: short description of ticket
  • Continue work on SYNCT-002: short description of ticket
3 Likes
2

Is this because the time for our daily stand ups is not convenient for your team? https://wiki.openmrs.org/display/RES/Daily+Scrum+Meeting

3

No, the daily stand-ups time is convenient for us. However, we will use both threads. This one and IRC channel.

4

Blocked?

  • no

What I’ve done

  • Worked on SYNC-342: Sync 2.0 Kickoff, familiarizing with the project and documentation, create first tickets

What’s next

  • Continue work on SYNC-342: Sync 2.0 Kickoff, familiarizing with the project and documentation, create first tickets.
  • Start work on first tasks.
5

Blocked?

  • no

What I’ve done

  • Worked on SYNC-342: Sync 2.0 Kickoff, familiarizing with the project and documentation

What’s next

  • Continue work on SYNC-342: Sync 2.0 Kickoff, familiarizing with the project and documentation
6

Blocked?

  • no

What I’ve done

  • Worked on SYNC-342: Sync 2.0 Kickoff, familiarizing with the project and documentation

What’s next

  • Continue work on SYNC-342: Sync 2.0 Kickoff, familiarizing with the project and documentation,
  • Sync 2.0 sprint planning
7

Blocked?

  • no

What I’ve done

  • Worked on SYNC-342: Sync 2.0 Kickoff, familiarizing with the project and documentation

What’s next

  • Start work on SYNCT-1: Create the Sync2 module from template
8

Blocked?

  • no

What I’ve done

  • Worked on SYNC-342: Sync 2.0 Kickoff, familiarizing with the project and documentation, create first tickets
  • Worked on SYNC-6: Sync 2.0 Sprint Planning

What’s next

  • Start work on FM-203: Add code quality tools to the FHIR module
9

Blocked? * no

What I’ve done * Worked on SYNC-342: Sync 2.0 Kickoff, familiarizing with the project and documentation * SYNCT-6: Sync 2.0 sprint planning

What’s next * ATF-1 Create the Atom Feed module from template

10

Blocked?

  • no

What I’ve done

  • Worked on FM-203: Add code quality tools to the FHIR module

What’s next

  • Start work on FM-204: Cleanup FHIR strategy code.
11

Blocked?

  • no

What I’ve done

  • Worked on FM-202: Cleanup FHIR strategy code. Remove unused strategy.

What’s next

  • Start work on ATF-5: Create default config file.
12

Blocked?

  • no

What I’ve done

  • Worked on SYNCT-1: Create the Sync2 module from template
  • Worked on SYNCT-2: Add to Sync 2.0 code quality tools

What’s next

  • Start work on ATF-6: Create config parser and manager
13

Blocked?

  • no

What I’ve done

  • Start work on ATF-6: Create config parser and manager

What’s next

  • Continue work on ATF-6: Create config parser and manager
14

Blocked? no

What I’ve done Worked on ATF-5: Create default Feed config Worked on ATF-7: Create Feed config upload UI

What’s next Continue work on ATF-7: Create Feed config upload UI

15

Blocked?

  • no

What I’ve done:

  • ATF-1: Create the Atom Feed module from template
  • ATF-4: Create the feed config class

What’s next:

  • ATF-2: Switch the advice based feed propagation to event based
16

Blocked?

  • no

What I’ve done

  • ATF-5: Create default config file.
  • ATF-7: Add Feed Config UI.
  • ATF-11: Add Travis CI to the AtomFeed module.
  • SYNCT-7: Add Travis CI to the Sync 2.0 module.

What’s next

  • ATF-7: Add Feed Config UI.
17

Blocked?

  • no

What I’ve done

  • ATF-6: Create config parser and manager

What’s next

  • ATF-6: Create config parser and manager
18

Blocked?

  • no

What I’ve done:

  • ATF-2: Switch the advice based feed propagation to event based

What’s next:

  • ATF-2: Continue work on switching the advice based feed propagation to event based
19

Blocked?

  • no

What I’ve done

  • ATF-7: Add Feed Config UI.

What’s next

  • ATF-7: Add Feed Config UI.
20

Blocked?

  • no

What I’ve done:

  • ATF-2: Switch the advice based feed propagation to event based

What’s next:

  • ATF-2: Continue work on switching the advice based feed propagation to event based