Thanks, @jthomas, for organizing our first call just now. We made progress but we need more time!
Can you help us set up another call? (It may work to do this on a Wednesday design forum, e.g. next week’s.)
Thanks, @jthomas, for organizing our first call just now. We made progress but we need more time!
Can you help us set up another call? (It may work to do this on a Wednesday design forum, e.g. next week’s.)
@darius so glad to hear this worked out well. Is there a place where outcomes are being kept from these calls?
Next weeks Wednesday design forum is open so we could definitely get this on the schedule. Is there anyone who knows they can not attend @burke, @sunbiz, @pascal, @mseaton, @wyclif , @dkayiwa?
Sorry, I couldnt join. But I hope to join next week. Would be nice to look at some notes from the last call
This is the draft spreadsheet we’re working on: https://docs.google.com/spreadsheets/d/1iX_7eUOqHCq2sRrZIDg3HNao_2N0ZaO9VsIdp6d2Rf0/edit#gid=0
(To the general public…don’t comment on this yet please, it’s draft, incomplete, and doesn’t represent our final thoughts.)
@burke, @sunbiz, @pascal, @mseaton, @wyclif , @dkayiwa
We lost some steam on this, but we’ve done some good work so far! I’d like to get us moving again. I have printed out a copy of the text so far to read on an upcoming flight. Maybe others want to refamiliarize themselves also, and we can make asynchronous edits, and set up a final signoff meeting in a month or so.
I fleshed out some more of the blurbs today.
I added a column “Q3-2016 Status”, and I put “DJ” in that column for the ones I’m proposing as ready-to-go. (We should have a better process than this, but I don’t want to figure that out now.)
Let me call out one bigger change: I switched “KenyaEMR Distribution” to the broader “Country-specific Distributions”, and I expanded the blurb to also mention Mozambique and Uganda. This is more in line with what I think Jan and I would say from the Distro team perpspective. (But if someone thinks we should actually be listing these distros individually, we could take that approach too.)
If you’re considering OpenMRS in Kenya, Mozambique or Uganda, you will want to look into KenyaEMR, eSaude, or Aijar (check name), respectively, and see if those distributions meet your needs, before considering one of the general-purpose OpenMRS distributions.
I’m sad to see that nobody has touched the document since I worked on it a month ago.
I propose that we spend next Wednesday’s design forum (Sept 7) doing a final review of our draft document, and we move to publish our first Tech Radar ASAP.
@burke, @sunbiz, @pascal, @mseaton, @wyclif , @dkayiwa, thoughts?
(@jthomas, can we tentatively schedule this for the Sept 7 design forum?)
Works for me. I might be a couple of minutes late though.
@darius we have another topic scheduled for next Wednesday (Sept 7)…
Wednesday, September 14 is open though.
Okay, let it be Sept 14.
Sorry I haven’t been able to work on this lately. The (incomplete and non-functional) code that I’ve written is here. I’ve attempted to use tabletop to load data directly from the Google spreadsheet, and display it using an old radar rendering implementation forked from someone at Thoughworks.
I’m not sure when next I’ll be able to work on this, so if anyone wants to take a look, they’re welcome to use what I’ve done or start from scratch.
I did some more work on this, and I forked the code to https://github.com/openmrs/openmrs-contrib-radar, and it is being published at https://openmrs.github.io/openmrs-contrib-radar/.
We are almost there! There are only two things left to do, then we are ready to publish:
**bold**
[label](url)
npm install -g http-server
and then http-server
from the root directory of the codeThanks @darius!
If I remember correctly, the bug occurs when placing the Adopt/Trial/etc labels. I believe the code is trying to calculate a y-offset based on the position of the previous label + the number of items below it. If there are no values then there’s some kind of null- or zero-related error. I haven’t looked at the code in a while though, so I could be wrong.
Thanks Pascal, that helped a lot. I have a fix for this and I’ll push it up shortly.
In the meantime, everyon please help with markdown on the blurbs
@burke, @pascal, @mseaton, @wyclif, @dkayiwa
Pascal and I have gotten things cleaned up and working at https://openmrs.github.io/openmrs-contrib-radar/. Please take a final look and review it.
Now we need to decide how/when to release it. Personally I think that after people have had a chance to review over the next 3-4 days we can just post it. (I guess to Talk, with a blog post, a tweet, FB post, etc.)
However, looking earlier in this thread I said:
At this point, we’ve had the draft spreadsheet posted since May, and there has been regular activity on this thread (from the usual suspects) so I’m not really sure why socializing it on a dev call before releasing it is necessary. (@r0bby, you were the one I said it to at the time, do you think it’s helpful at this point?)
Anyone opposed to releasing this mid-next week?
@raff, would you mind specifically reviewing the OWA and HTML+JS+REST blurbs in https://docs.google.com/spreadsheets/d/1iX_7eUOqHCq2sRrZIDg3HNao_2N0ZaO9VsIdp6d2Rf0/edit#gid=0 and see if they’re in line with our latest thinking? And in particular what link should we put to the latest of the Soldevelo work?
I don’t think I ever voiced anything about this…
Looks fine to me, good job guys!
This is great for a start!