IRC Chat : 2011-12-14 - OpenMRS

02:52:16 *** r0bby is now known as robbyoconnor
03:28:55 *** upul` has joined #openmrs
03:28:55 *** ChanServ sets mode: +v upul`
04:05:40 *** surangak has joined #openmrs
04:05:51 <surangak> hi djazayeri
04:06:05 <surangak> djazayeri, regarding ticket 2588.....
04:48:25 <djazayeri> hi surangak
04:48:42 <surangak> howdy djazayeri .. mm.. I just sent you a mail :-)
04:48:52 <djazayeri> I just read it.
04:48:54 <djazayeri> No worries.
04:49:04 <djazayeri> Get your uni work done first.
04:50:20 <surangak> I should be free by the weekend at least.. the embarassing part is I had not followed the mail thread :-)
04:50:49 <djazayeri> surangak: it's okay, there are lots of emails. don't worry, the weekend is fine.
06:04:38 *** rafa has joined #openmrs
06:04:38 *** ChanServ sets mode: +v rafa
06:09:54 *** rafa has quit IRC
07:18:58 *** dkayiwa has joined #openmrs
07:38:51 *** kishoreyekkanti has joined #openmrs
08:00:47 *** kishoreyekkanti has quit IRC
08:31:21 *** djazayeri has quit IRC
08:42:39 *** kishoreyekkanti has joined #openmrs
08:47:07 *** dkayiwa has quit IRC
08:56:48 *** djazayeri has joined #openmrs
08:56:48 *** ChanServ sets mode: +o djazayeri
09:22:38 *** djazayeri has quit IRC
09:23:16 *** dkayiwa has joined #openmrs
09:24:48 *** djazayeri has joined #openmrs
09:24:48 *** ChanServ sets mode: +o djazayeri
09:27:17 *** rafa has joined #openmrs
09:27:17 *** ChanServ sets mode: +v rafa
09:27:29 *** rafa has quit IRC
09:47:06 *** dkayiwa_ has joined #openmrs
09:47:08 *** dkayiwa has quit IRC
09:47:09 *** dkayiwa_ is now known as dkayiwa
10:19:49 *** djazayeri has quit IRC
10:20:05 *** djazayeri has joined #openmrs
10:20:05 *** ChanServ sets mode: +o djazayeri
10:58:38 *** surangak_ has joined #openmrs
10:58:38 *** surangak has quit IRC
10:58:41 *** surangak_ has quit IRC
11:00:11 *** bwolfe has joined #openmrs
11:00:11 *** ChanServ sets mode: +o bwolfe
11:00:11 *** djazayeri1 has joined #openmrs
11:00:47 *** djazayeri has quit IRC
11:06:37 *** rafa has joined #openmrs
11:06:46 *** ChanServ sets mode: +v rafa
11:28:33 *** upul` has quit IRC
11:35:04 *** kishoreyekkanti has quit IRC
11:35:26 *** dkayiwa has quit IRC
12:17:32 *** dkayiwa has joined #openmrs
12:18:08 *** james_regen has joined #openmrs
12:18:08 *** ChanServ sets mode: +v james_regen
12:31:59 <rafa> dkayiwa: bwolfe I can't start trunk
12:32:09 <rafa> I've just updated
12:32:30 <rafa> and it didn't work so I did fresh install
12:32:34 <bwolfe> rafa, whats the error? probably caused by me 10 mins ago
12:32:58 <rafa> http://pastebin.com/wBwHhtAC
12:33:09 <rafa> it's like spring exploded ;)
12:36:44 <dkayiwa> :)
12:38:36 *** kishoreyekkanti has joined #openmrs
12:40:53 <bwolfe> rafa, is that the full log?
12:41:00 <bwolfe> I don't see the real cause there
12:41:23 <bwolfe> (spring likes to hide the real cause amoungst 34234 lines of stacktrace and other "caused by"s)
12:47:46 <rafa> bwolfe: I'm trying to find jetty's logs...
12:48:00 <bwolfe> console
12:48:10 <bwolfe> are you starting in eclipse? open console view
12:48:21 <rafa> yeah, but it cuts the rest
12:49:27 *** wyclif has quit IRC
12:49:40 <bwolfe> hmm, thats unhelpful...
12:50:03 * bwolfe svn updates and tests it out
12:57:34 *** dkayiwa has quit IRC
12:58:01 *** kishoreyekkanti has quit IRC
13:38:39 <rafa> bwolfe: okay I droped the database and it worked
13:38:51 <bwolfe> rafa, PEBKAC?
13:38:57 <bwolfe> or PEBOAD ?
13:39:03 <bwolfe> (openmrs and database)
13:39:22 <rafa> bwolfe: what? :P
13:39:26 <bwolfe> rafa, I just switched over to my openmrs localhost tab. a fresh trunk deployed fine for me
13:39:36 <bwolfe> !google PEBKAC
13:39:36 <OpenMRSBot> bwolfe: http://www.google.com/search?q=PEBKAC
13:39:40 <bwolfe> :-)
13:39:53 <rafa> haha
13:40:20 <rafa> bwolfe: yeah that's probably right :D
13:41:23 <rafa> bwolfe: I have around 10 openmrs databases :D
13:41:36 <rafa> bwolfe: I need to get rid of them
13:42:02 <rafa> I lost control what uses what :D
13:43:35 <bwolfe> rafa, I name all new dbs very accurately
13:43:52 <bwolfe> e.g. "1.8.x-db-test-kanter-huge-concept-dictionary"
13:43:54 <bwolfe> :-)
13:44:08 <bwolfe> that way I know if its a specific version and what I did to make it special
13:45:26 *** wyclif has joined #openmrs
14:00:57 *** wyclif has quit IRC
14:10:59 *** downeym has joined #openmrs
14:10:59 *** ChanServ sets mode: +o downeym
14:10:59 *** OpenMRSBot sets mode: +o downeym
14:13:11 *** wyclif has joined #openmrs
14:23:59 *** r0bby has joined #openmrs
14:23:59 *** ChanServ sets mode: +v r0bby
14:24:08 *** robbyoconnor has quit IRC
14:24:42 *** dkayiwa has joined #openmrs
15:01:28 <downeym> bwolfe: just got word that port 22 outbound is now opened :)
15:11:52 *** ball has joined #openmrs
15:14:10 <bwolfe> downeym, perfect timing!
15:15:29 <downeym> bwolfe: indeed
15:20:11 *** burke has joined #openmrs
15:20:11 *** ChanServ sets mode: +o burke
15:46:14 *** r0bby has quit IRC
16:18:02 *** rafa has quit IRC
16:21:12 *** rafa has joined #openmrs
16:21:12 *** ChanServ sets mode: +v rafa
16:30:42 <wyclif> hi bwolfe
16:39:08 *** deadpool_ has quit IRC
16:46:50 *** dkayiwa_ has joined #openmrs
16:49:00 *** dkayiwa has quit IRC
16:49:01 *** dkayiwa_ is now known as dkayiwa
16:49:42 *** suranga has joined #openmrs
16:53:20 *** cav has joined #openmrs
16:53:34 <downeym> Hi cav and welcome to the #openmrs IRC channel.
16:53:56 <cav> Hi downeym
16:55:49 <cav> I was trying to define a person attribute, but instead of free text i wish it could be a list of previous 'fixed' entered (ie like male, female). is it possible?
17:00:43 <downeym> bwolfe: can the value of a person attribute be a defined Concept?
17:00:57 <downeym> or wyclif :)
17:01:53 <cav> yes. (I took a look at concepts and did not find a way to make one as a list of values)
17:01:55 <dkayiwa> oy YES :)
17:02:13 <downeym> :)
17:17:50 <cav> Anyway of doing it like gender field or a combo?
17:18:30 <dkayiwa> hi bwolfe
17:22:12 *** cav has quit IRC
17:24:50 *** deadpool_ has joined #openmrs
17:25:51 *** djazayeri1 has quit IRC
17:28:08 <bwolfe> hi dkayiwa
17:28:55 *** dkayiwa has quit IRC
17:29:21 <bwolfe> cav, downeym, the CIVIL_STATUS concept is an example of that. if you want the concept answers to be the answers for a person attr you put the concept_id into the foreign_key column (bad name for it, I know)
17:33:05 *** dkayiwa has joined #openmrs
17:41:02 *** dkayiwa has quit IRC
17:43:45 *** dkayiwa has joined #openmrs
17:44:47 <suranga> hi guys, sorry , wont be able to make it to the Documentation call right now... but I'll take over a ticekt or two soon :-(
17:48:06 <bwolfe> suranga, cool :-)
18:01:29 <bwolfe> !scrumon bwolfe
18:01:29 * OpenMRSBot says the DAILY SCRUM MEETING is STARTING. This meeting should not last longer than 15 minutes. Please hold other comments until the end of the meeting, or message someone privately. Thank you! ScrumMaster bwolfe- you may begin when ready.
18:01:44 <ball> I'm in.
18:01:47 <bwolfe> hi rafa, wyclif, dkayiwa, ball, downeym
18:01:57 <dkayiwa> hi bwolfe
18:02:02 <rafa> hi
18:02:07 <bwolfe> lets go in that order. rafa, you ready?
18:02:15 <rafa> yes
18:02:17 <bwolfe> (with me at the end)
18:02:23 <dkayiwa> :)
18:02:38 <rafa> no sorry
18:02:42 <rafa> lost my report :)
18:02:51 <bwolfe> ha
18:02:55 <bwolfe> lost it? dog ate it?
18:03:08 <dkayiwa> :)
18:03:10 <rafa> okay found it :D
18:03:10 <dkayiwa> Tried compiling standalone but put it on hold because of the "standalone-build-support version 0.4" artifact not being in the nexus repo
18:03:11 <dkayiwa> Checked tickets closed after branching 1.9 to ensure they are all back ported.
18:03:11 <dkayiwa> Did back port some of them and commented on others where am not sure
18:03:11 <rafa> Today:
18:03:11 <rafa> * Committed TRUNK-2961: Saving user options for the default super user should not throw error message on second and subsequent times
18:03:11 <rafa> https://tickets.openmrs.org/browse/TRUNK-2961
18:03:11 <rafa> * Committed TRUNK-2913: Simplify display of visit on Visits tab
18:03:11 <rafa> https://tickets.openmrs.org/browse/TRUNK-2913
18:03:11 <dkayiwa> Started some rudimentary testing and created a few tickets
18:03:11 <dkayiwa> Continuing with testing and after which i will create the beta release notes page
18:03:11 <rafa> * Started with https://tickets.openmrs.org/browse/META-161
18:03:11 <rafa> Tomorrow:
18:03:12 <dkayiwa> No Blockers
18:03:12 <rafa> * Finish META-161
18:03:12 <rafa> * Other sprint tickets (Which dashboard are we using right now?)
18:03:13 <rafa> No blockers.
18:03:49 <bwolfe> rafa, you can always look at the sprint schedule page and follow the links
18:03:56 <bwolfe> https://wiki.openmrs.org/display/RES/Sprint+Schedule
18:04:14 <bwolfe> click through to this week, then near the bottom the dashboard(s) are linked to
18:04:33 <bwolfe> rafa, so you did do sprint tickets today?
18:04:44 <rafa> yes, the two
18:05:15 <bwolfe> rafa, if you have time, would like to have another pair of eyes on the things I committed. thats half of the things in the To Be Reviewed column
18:05:30 <bwolfe> (or maybe on the side of whatever else you are working on on the sprint)
18:05:38 <bwolfe> ok, wyclif?
18:05:40 <rafa> sure
18:05:50 <bwolfe> paging wyclif...
18:06:27 <wyclif> yesterday:
18:06:27 <wyclif> -TRUNK-2956 - Row highlight fails on verbose row when home/end/pageup/pagedown keys are used
18:06:27 <wyclif> -FORM-130 & HTML-221 - Need to use the new provider API to get the list of providers
18:06:27 <wyclif> -Wiki documentation for additional attributes added to concept mappings and related GPs
18:06:27 <wyclif> -other sprint tickets
18:06:28 <wyclif> today:
18:06:32 <wyclif> -Complete FORM-130 & HTML-221 - Need to use the new provider API to get the list of providers
18:06:34 <wyclif> -TODO for SMART-22
18:06:36 <wyclif> -TRUNK-2958 - Refresh the authenticated user when edited
18:06:38 <wyclif> -SMART-29 - Smart datatypes should extend an abstract class
18:06:40 <wyclif> No blockers
18:06:53 <bwolfe> ok
18:06:56 <bwolfe> dkayiwa?
18:07:17 <dkayiwa> Tried compiling standalone but put it on hold because of the "standalone-build-support version 0.4" artifact not being in the nexus repo
18:07:17 <dkayiwa> Checked tickets closed after branching 1.9 to ensure they are all back ported.
18:07:17 <dkayiwa> Did back port some of them and commented on others where am not sure
18:07:18 <dkayiwa> Started some rudimentary testing and created a few tickets
18:07:18 <dkayiwa> Continuing with testing and after which i will create the beta release notes page
18:07:19 <dkayiwa> No Blockers
18:07:34 <bwolfe> dkayiwa, oh, sorry, will deploy that post-haste
18:07:44 <dkayiwa> ok
18:08:18 <bwolfe> dkayiwa, there are a number of tickets with your name on them in the In Progress queue
18:08:34 <dkayiwa> bwolfe: for beta2?
18:08:47 <bwolfe> (you might not have gotten emails due to the known bug with jira and state transitions) *cough* downeym *cough*
18:08:59 <downeym> (that should be fixed)
18:09:09 <dkayiwa> bwolfe: are they on the beta2 dashboard?
18:09:15 *** jriley has joined #openmrs
18:09:24 <bwolfe> dkayiwa, oh wait, I'm confused. I forgot wyclif rearranged from the standard layout of the boxes!
18:09:36 <dkayiwa> :)
18:09:59 <bwolfe> oh, nm dkayiwa, continue on
18:10:05 <bwolfe> :-)
18:10:10 <dkayiwa> :)
18:10:21 <bwolfe> who's next...ball! ball you're up. :-D
18:10:35 <ball> (Pressure)
18:10:38 <ball> Yesterday:
18:10:39 <ball> Reviewed the eBook and put review notes on the etherpad. Not sure how to discuss these further or how this process for making changes will work. Pow-wow?
18:10:39 <ball> Today:
18:10:39 <ball> Will work on this ticket:
18:10:39 <ball> https://tickets.openmrs.org/browse/TRUNK-2936
18:10:40 <ball> Adding in 1.9 changes to concept maps
18:10:42 <ball> And others as time allows (this week and next)
18:10:49 *** ChanServ sets mode: +v jriley
18:10:59 *** ChanServ sets mode: +v ball
18:11:15 <bwolfe> ooo, jriley, didn't notice you were here, you can go at the end. :-)
18:11:26 <jriley> Just got here, catching up on IRC log
18:11:31 <bwolfe> ball, any blockers for you? did you see darius' feedback on the notes page for you?
18:11:55 <ball> I saw the notes and made a couple of responses
18:12:17 <bwolfe> ok
18:12:18 <ball> Not sure if I make changes or let others read my important thoughts (see Socretes)
18:12:30 <ball> (joking)
18:12:31 <bwolfe> downeym, are you joining this sprint on the doc side? or am I just mistaken?
18:12:40 <downeym> bwolfe: yes, i am supporting it
18:12:50 <downeym> is it my turn? :)
18:13:00 <ball> i'm done
18:13:04 <bwolfe> ball, go ahead and make them as htey are "approved"...and then cross them out
18:13:08 <bwolfe> hopefully others will follow suit
18:13:12 <bwolfe> downeym, go ahead
18:13:20 <downeym> Yesterday:
18:13:20 <downeym> * Out of the office so wasn't really working.
18:13:20 <downeym> * (Helped to get the 1.8.3 files released/uploaded.)
18:13:21 <downeym> Today:
18:13:21 <downeym> * Got caught up on doc sprint progress from yesterday.
18:13:21 <downeym> * Sent out information about daily scrum meeting to try to help with status communication.
18:13:22 <downeym> * Reviewing doc sprint tickets & dependencies.
18:13:22 <downeym> * Will review book edits so far.
18:13:22 <downeym> Blockers:
18:13:23 <downeym> * None directly for myself, however...
18:13:23 <downeym> * Want to make sure everyone on the doc sprint is clear about the daily scrum meetings.
18:13:23 <downeym> * Not sure the JIRA doc sprint dashboard has the right information to track the tasks people are actually working on.
18:14:05 <bwolfe> ok, lets talk about that afterwards downeym
18:14:15 <downeym> sounds good
18:14:41 <bwolfe> for me today:
18:14:42 <bwolfe> released maintenance branches
18:14:42 <bwolfe> commented on tickets
18:14:42 <bwolfe> applied patch for TRUNK-1637
18:14:42 <bwolfe> created doc sprint ticket
18:14:42 <bwolfe> cleaned/moved/triaged a few tickets
18:14:44 <bwolfe> set up for design call
18:14:46 <bwolfe> doc conf call
18:14:50 <bwolfe> design call
18:14:52 <bwolfe> pm call
18:15:16 <bwolfe> and tomorrow: release sync 1.0, sprint stuffs
18:15:19 <bwolfe> no blockers
18:15:47 <bwolfe> jriley?
18:16:04 <jriley> YESTERDAY/TODAY:
18:16:04 <jriley> * reviewerd notes and gantt
18:16:04 <jriley> TODAY:
18:16:05 <jriley> * updated gantt with links to tickets
18:16:05 <jriley> * want to make a top-level Documentation wiki page called "guides" and move things from the playground to pages there
18:16:05 <jriley> BLOCKERS:
18:16:05 <jriley> still figuring out how to work in
18:16:08 <jriley> sorry bout the bold
18:16:54 <bwolfe> ok. lets talk about moving pages here too.
18:17:12 <jriley> The playground pages aren't editable, so we can't use them as the core
18:17:20 <bwolfe> so 2.5 discussion points.
18:17:32 <bwolfe> right, they're on ppl's "personal" sections
18:17:56 * downeym has a suggestion
18:18:00 <jriley> There's a tension in how the wiki is organized - we can use the parent/child structure, but a page can only have one parent . Some pages are applicable to more than one guide
18:18:09 <bwolfe> ok, do we scrumoff before talking about blockers? I can't remember...
18:18:16 <downeym> bwolfe: yeah :)
18:18:18 <jriley> I'd like to put that on the back burner by making links in the page for the first draft
18:18:20 <bwolfe> ok
18:18:22 <bwolfe> !scrumoff
18:18:22 * OpenMRSBot says the DAILY SCRUM MEETING has ENDED. This channel is now returned to normal hacking operations. Post-scrum meeting follow-up conversations may now begin.
18:18:25 <jriley> and then figure out how to rearrange the furniture when we have a draft
18:18:37 <bwolfe> ah, there we go! the answer is in the scrumoff itself :-)
18:18:46 <downeym> jriley et al: so I'd recommend that we ask jamie to move her pages into somewhere in the doc space (we can rename the "top level" later.
18:19:01 <bwolfe> ok, jriley's point first I suppose
18:19:49 <downeym> jriley: in confluence, we can use the include macro to include content from other pages without needing to rewrite or copy/paste.
18:20:08 <bwolfe> so we'd have two pages with the same content just diff names?
18:20:16 <downeym> bwolfe: it's possible, yes
18:20:37 <downeym> bwolfe: when editing the page, you'd see a reference to the "master" page for the content and realize you need to change it there.
18:20:39 <bwolfe> yes, but is it desirable
18:21:06 <downeym> do we have any examples of what kind of content this might apply to?
18:21:38 <jriley> Troubleshooting pages are suitable for both implementers and users/admins
18:21:46 <jriley> for example
18:22:12 <ball> performance
18:22:26 <downeym> jriley: agreed. right now we have a separate section for troubleshooting. we could either keep it separate (for now) and link to that, or create shell pages to include that content. (for example)
18:22:56 <bwolfe> I'd vote we just link to places. there will always be things that fit into multiple places
18:23:03 <downeym> we could also just copy & paste and maintain two similar-but-unique pages
18:23:12 <jriley> downeym, there's too much of that already
18:23:28 <jriley> I'd vote for fewer pages that are complete, correct, and up to date
18:23:29 <bwolfe> downeym, TODO: write to jamie to move the playground page to the DOC space. you can pick (or she can) where it goes for now and what more official name it gets
18:23:30 <downeym> jriley: yeah i tend to agree :)
18:23:40 <downeym> bwolfe: contacting her now
18:24:04 <ball> totally agree with Janet. Don't duplicate content.
18:24:36 <bwolfe> downeym, your "blocker" questions:
18:24:56 <bwolfe> did you want more contact with folks about the scrum meetings? what was your first point there?
18:25:28 <downeym> bwolfe: just want to confirm/validate we're going to use the daily scrum meetings for the doc sprint, and see whether or not we'd have enough people able to participate in them at their scheduled time.
18:26:04 <downeym> bwolfe: I got a mail from Jan about it
18:26:14 <downeym> bwolfe: looks like she will be able to attend starting tomorrow
18:26:29 <bwolfe> ok
18:27:01 <bwolfe> so we'll continue on as planned as of now...
18:27:10 <downeym> bwolfe: i'd vote for that :)
18:27:16 <bwolfe> doc sprint people are welcome to ask any/all questions anytime as well
18:27:23 <bwolfe> in here, dev list, etc
18:27:44 <bwolfe> the devs know to make time for all doc sprint questions. :-)
18:27:54 <downeym> +1 for avoiding individual (i.e. direct) email conversations vs. IRC or mailing list
18:29:11 <bwolfe> ok, downeym, your other point: how are you proposing the jira dashboard be changed for doc sprint folks?
18:29:50 <downeym> bwolfe: i'm not :) until we get some feedback as to if it's useful for folks in its initial layout. i know it works well for code sprints but want to see how it will work for us, and if there might be other things we can add/change.
18:29:57 <downeym> https://tickets.openmrs.org/secure/Dashboard.jspa?selectPageId=11157
18:30:49 <bwolfe> downeym, ok, well, I made the page and queries, so I think I have to be the one to change them. let me know if you hear any feedback and I can adjust
18:31:44 <downeym> bwolfe: does everyone know to look there for sprint-related tasks? I don't think we had a chance to mention it on Monday really
18:32:04 <bwolfe> downeym, I put it in my latest email to the "doc" team
18:32:10 <downeym> bwolfe: ok cool
18:32:16 <jriley> is it possible to add tags to issues and make them appear in the dashboard? I'd like to sort issues into book tickets and wiki tickets
18:32:19 *** suranga_ has joined #openmrs
18:32:25 <jriley> I didn't see a way to add a tag column in the filter
18:32:43 <downeym> jriley: we could have boxes/lists for each label
18:32:53 <downeym> and maybe color code the boxes
18:32:57 <jriley> The list of available issues does not naturally organize itself into "do this next" when I look at it
18:33:06 <jriley> The gantt chart is a start
18:33:46 <downeym> ball: are you working on TRUNK-2936?
18:33:49 <downeym> !ticket TRUNK-2936
18:33:51 <OpenMRSBot> downeym: [#TRUNK-2936] Add section to implementation book about concept mapping changes - OpenMRS JIRA - https://tickets.openmrs.org/browse/TRUNK-2936
18:35:05 *** suranga has quit IRC
18:35:36 <downeym> jriley: that makes sense. we have priority but it's really more of an overall priority rather than a sequence based on dependencies
18:35:42 <downeym> bwolfe: any ideas on how to represent that?
18:36:57 *** djazayeri has joined #openmrs
18:36:57 *** ChanServ sets mode: +o djazayeri
18:37:18 <downeym> jriley: based on your comments earlier, i think you'd be perfect to pick up TRUNK-2942
18:37:39 <jriley> JIRA has a way to show dependencies, but is there a way for me to sort with them in a list of issues?
18:37:46 <downeym> jriley: not that i'm aware of :(
18:37:57 <jriley> !ticket trunk-2942
18:37:58 <OpenMRSBot> jriley: [#TRUNK-2942] Analyze proposed documentation hierarchy - OpenMRS JIRA - https://tickets.openmrs.org/browse/trunk-2942
18:38:18 <bwolfe> to represent an order? the best way would just be to split the two and then do priority
18:38:24 <jriley> downeym, I can pick up 2942. I'm depending on Jamie moving her pages
18:38:38 <jriley> Shall I make a ticket for that?
18:38:39 <downeym> jriley: i just dropped her an email about it and will run over and check with her after we're done here
18:39:14 <downeym> bwolfe: wasn't sure if there was anything hidden in greenhopper that could visualize the linked issues
18:39:18 <jriley> Ah! How old fashioned! Ok
18:39:36 <jriley> I can also reorder rows on the gantt chart
18:40:19 <bwolfe> downeym, not that I've seen
18:40:22 <jriley> I have workarounds to the dashboard. If there were a way to do it in the sprint dashboard, my feedback would be to request that. But if not, I can organize myself
18:40:37 <downeym> jriley: we'll do some research to see what can be done.
18:40:43 <bwolfe> jriley, if you label each of the tickets I'll try to get them split up on the dashboard later
18:40:45 <downeym> s/we/I/
18:42:14 <downeym> jriley: something like https://plugins.atlassian.com/plugin/details/5003?versionId=27067 ?
18:42:21 <OpenMRSBot> <http://ln-s.net/9Rph> (at plugins.atlassian.com)
18:44:04 <jriley> That looks cool. It would be easy to see when a dependent issue is waiting on a preceeding issue
18:44:30 <jriley> downeym , does that have value for everyone else too?
18:44:47 <downeym> bwolfe: would that be useful for code sprints?
18:45:07 <jriley> Atlassian plugins can be a bear to make work , is there an ROI for the rest of th world?
18:46:05 *** bwolfe has quit IRC
18:49:33 *** r0bby has joined #openmrs
18:49:33 *** ChanServ sets mode: +v r0bby
18:50:49 *** bwolfe has joined #openmrs
18:50:49 *** ChanServ sets mode: +o bwolfe
18:51:41 <downeym> bwolfe: would that be useful for code sprints?
18:54:39 <downeym> jriley: i've got it installed, still need to figure out how to use it. we can take it off if it's not very useful.
18:54:49 <jriley> ok
18:56:29 <downeym> jriley: https://wiki.openmrs.org/display/docs/Documentation+Playground
18:56:47 <jriley> awesome, thanks
19:01:50 <bwolfe> downeym, looks like that is a greenhopper report? probably less useful
19:02:17 <downeym> bwolfe: i think so, although still digging through docs to see how to actually use it :)
19:04:45 <jriley> downeym, is there a shortcut link for the book? go.openmrs.org/ ... ?
19:05:59 <downeym> jriley: try http://go.openmrs.org/guide
19:06:18 <jriley> Are we going to keep old versions available, e.g. Getting Started with OpenMRS 1.8 ?
19:06:44 *** jthomas_ has joined #openmrs
19:07:05 <bwolfe> hmm, good point
19:07:11 <bwolfe> is that possible with the wiki though?
19:07:17 <downeym> bwolfe djazayeri any thoughts? i assume if we bundle the PDF in the download then we should :)
19:07:45 <downeym> the book itself can't really be branched per se, although it could be copied (just never re-merged)
19:07:58 <jriley> I mean the Flossmanual, not wiki guides
19:08:20 <jriley> I'm asking because the playground suggested a link to version 1.8 , 1.9
19:08:47 <jriley> My vote is the current version only - if you're getting started, you're most likely starting with the current release
19:08:50 <djazayeri> downeym: I thought your idea (and I liked this a lot) was that we'd export the 1.8.x, 1.9.x, etc version of the book with each release, put those on a read-only wiki page that's commentable
19:08:55 <downeym> jriley: what we'd talked about when writing the book was to publish a PDF for each release and link to it on our main download page
19:09:12 <downeym> or what djazayeri said :)
19:09:25 <djazayeri> we'd bundle just a vetted PDF version of the current version of the book with all 1.9.x releases
19:09:52 <djazayeri> it'd be similar to code, I assume (but not much "backporting" would happen)
19:10:33 <bwolfe> sorry, I meant the flossmanual too. not sure why "wiki" came out
19:10:34 *** suranga__ has joined #openmrs
19:11:24 <downeym> i wouldn't worry about the book versioning yet until we get this review process complete (i.e. let's begin that process, if so, with 1.9)
19:11:31 <downeym> </opinion>
19:11:47 <bwolfe> fine by me to start this with 1.9
19:11:55 <bwolfe> although...
19:12:13 <bwolfe> could we just export the book as it is now (before this weeks edits) and call it the 1.8 reference?
19:12:35 <downeym> sure
19:12:49 <downeym> http://en.flossmanuals.net/_booki/openmrs-guide/openmrs-guide.pdf
19:12:53 <OpenMRSBot> <http://ln-s.net/9RqI> (at en.flossmanuals.net)
19:15:19 *** suranga_ has quit IRC
19:29:24 *** jthomas_ has quit IRC
19:33:18 <wyclif> bwolfe, we lost you on the call
19:33:33 <bwolfe> yes I know :-p
19:43:20 *** jriley has quit IRC
19:53:17 *** suranga__ has quit IRC
19:53:18 *** Echidna has quit IRC
19:57:39 *** Echidna has joined #openmrs
19:57:39 *** ChanServ sets mode: +v Echidna
20:06:18 <downeym> bwolfe: ping
20:06:36 <bwolfe> pong
20:06:51 <downeym> bwolfe: meeting starts now
20:07:07 <downeym> !pmon
20:07:08 <OpenMRSBot> downeym: Error: "pmon" is not a valid command.
20:09:35 <bwolfe> ha
20:09:40 *** djazayeri has quit IRC
20:12:29 <burke> bwolfe: yo! are you still alive?
20:12:40 <bwolfe> burke, no
20:12:58 <bwolfe> I see no one on skype
20:13:04 <bwolfe> (including freeconferencing)
20:18:08 *** r0bby has quit IRC
20:18:34 *** r0bby has joined #openmrs
20:18:34 *** ChanServ sets mode: +v r0bby
20:57:21 *** rafa has quit IRC
20:59:01 *** r0bby has quit IRC
21:00:05 *** dkayiwa has quit IRC
21:00:21 *** james_regen has quit IRC
21:10:10 *** dkayiwa has joined #openmrs
21:28:02 *** dkayiwa has quit IRC
21:51:44 *** djazayeri has joined #openmrs
21:51:47 *** ChanServ sets mode: +o djazayeri
22:13:56 *** deadpool_ has quit IRC
22:18:55 *** wyclif has quit IRC
22:20:40 *** burke_ has joined #openmrs
22:24:30 *** burke has quit IRC
22:56:39 *** r0bby has joined #openmrs
22:56:46 *** ChanServ sets mode: +v r0bby
22:56:52 *** downeym has quit IRC
23:13:12 *** wyclif has joined #openmrs
23:13:32 *** r0bby has quit IRC
23:20:44 *** bwolfe has quit IRC