Perl 6 - the future is here, just unevenly distributed

IRC log for #webwork, 2013-02-05

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:53 mgage_ joined #webwork
05:03 rbeezer joined #webwork
13:35 goehle joined #webwork
15:06 aubreyja joined #webwork
15:59 JohnTravis joined #webwork
16:24 aubreyja Hi mgage, mgage_: around?
16:29 mgage hi
16:29 mgage aubreyja: hi
16:29 aubreyja Hi - did you say you fixed the GatewayQuiz.pm warning message?
16:29 aubreyja in 2.5.1.3 I thnk
16:30 mgage I didn't push it to the openwebwork github.
16:30 mgage There were two warning messages -- one is a $result[0] not defined message -- I didn't fix that.
16:31 aubreyja also - it looks like webwork2-dev master and devel are the same at this point.
16:32 aubreyja I'm trying to see if there have been any bug fix changes in master that should be ported over to webwork2?
16:32 mgage The other is a reference to a .css file that didn't exist.  That is being created in the gateway.template in each theme folder -- the <link   >  tag at the top of each template needs to be adjusted to reference the mathX.css file in the same theme folder
16:32 aubreyja also - the gateway.css file seems to have disappeared.  I have a copy I can push up.
16:33 mgage ok -- I didn't see links to a specific gaaateway.css file but I wasn't looking closely
16:34 mgage I think that someone (probably me) pushed changes from ww2.5.1.3 to the master branch on webwork2-dev.  I would like to roll that back to ww2.5.1.1 but I haven't had time to get to it.
16:35 aubreyja it handles ids like gw*** in the content module
16:36 mgage kk   If master was the ww2.5.1.1 version then perhaps we would have only master (rock stable),
16:38 mgage ww2.5.1.3 (beta release) and devel as branches in webwork2-dev.  All new features of any consequence would go to devel.  Only bug fixes would go to ww2.5.1.3  (maybe really minor features -- can't tell how far to go with this).  and only really disastrous   bugs would be fixed on ww2.5.1.1
16:39 aubreyja Isn't the idea that the latest numbered version and master get bug fixes, then when a new numbered version is created from the devel branch it is merged into master and then master and that new branch get the bug fixes?
16:39 mgage bug fixes added to ww2.5.1.3 would only make it to devel when ww2.5.1.3 is periodically merged into devel (or alternatively, perhaps better, devel is rebased on top of ww2.5.1.3 periodically)
16:41 mgage yes likewise bug fixes to ww2.5.1.3 would only make it to master when ww2.5.1.3 is merged into it (so that it becomes the new master)
16:41 aubreyja ok, maybe this is more complicated because of having webwork2 and webwork2-dev.  In webwork2 right now we want master and ww2.5.1.1 getting bug fixes.  But in webwork2-dev we want master and ww2.5.1.3 getting them.  Is that right?
16:42 mgage Actually only ww2.5.1.3 getting them unless they are deal stopper bug fixes.
16:43 aubreyja but that's in webwork2-dev - what about a legitimate bug in ww2.5.1.1 in webwork2 - wouldn't we want to fix that since a lot of people will be running it presumably?
16:43 mgage bug fixes to ww2.5.1.3 would be new "features" for the most part since people had been living with the bugs in ww2.5.1.1  -- the idea is to make it relatively rare to update two branches
16:43 mgage that gets confusing
16:45 aubreyja yeah, maybe we do need to tighten this up.  What's the argument against just having one repo, webwork2, again?
16:45 mgage well that starts to violate the plan proposed by Davide   -- only "hot fixes" what I'm referring to as deal-stopper bugs  were fixed in both the master and the upcoming  release branches
16:46 mgage 1. The proximity of development branches next to stable branches makes some people nervous.  2. until we get better at using github this gives us a backstop against mistakes.  (such as accidentally upgrading    webwork2-dev/master  to ww2.5.1.3 when it was supposed to stay at ww2.5.1.1   :-) )
16:48 mgage I view webwork2-dev/master as stable -- webwork2/master will be "battle hardened".  Even arnie would use it. :-)    For those who prefer the bugs they know over new bugs that might come along.
16:48 aubreyja ok, so the idea is that once we crystalize a numbered release it gets ported over to webwork2 (as the new numbered release and as master) and we don't touch it until the next numbered release or a serious bug shows up
16:48 mgage I see moving master from webwork2-dev to webwork2   perhaps once a semester at most.
16:49 aubreyja ok, that seems reasonable
16:50 mgage We could do that -- I just suggested something even more conservative.   And we can try to co-opt those who are anxious for newish features or bug fixes to work from webwork2-dev/master (or even from the beta release that we are readying for prime time)
16:50 aubreyja ok - one last thing - the svn.  We really need to shut it down.
16:51 aubreyja I'm not so worried about the core code, mainly the problem library
16:51 mgage If we are going to keep making progress we have to convince at least a dozen or so people to use the beta release once we think it's kind of stable otherwise it will never become rock solid.  If we have the beta release in webwork2-dev along side master then this wouldn't be too risky since one could quickly back out to master
16:52 aubreyja right - I think we can do that (we can use the code camps to evangelize for volunteers)
16:52 mgage I agree -- I wanted to shut it down completely awhile ago.  I think Paul and John Jones convinced me to keep it open a while longer -- but I think they have switched by now.
16:53 aubreyja Well, bug fixes are still going to the svn problem library.
16:53 mgage Yes -- we need quite a few since for example I'm not always teaching a course that I can use webwork in so I'm not always participating in finding bugs.
16:54 aubreyja I can set up a git server and code browser on webwork.maa.org for webwork2 and pg easily that, say, tracks webwork2/ and pg/...
16:54 mgage Djun said something about making sure these get moved to the github repo -- but I think he may be a bit overloaded at the moment so we should help with shutting down svn.
16:54 aubreyja then disable those svn repos and viewvc for them...
16:54 mgage one of the big needs on that is rewriting the docs on the wiki
16:55 mgage ok -- tracking the github version of webwork2, pg, and library code is something we need.  Are you sure we don't have that already with doxygen?
16:56 aubreyja Yes, I think we finally have a clear enough "plan" to put up reasonable docs.  I'm not sure what's going on with doxygen at the moment - if it's pulling from github or the svn….
16:57 aubreyja I can also set up, say, git.webwork.maa.org where people could pull down the code outside of github, perhaps even allowing svn checkouts.
16:58 aubreyja would that be worthwhile, or just a code browser?
16:58 mgage I think that might get confusing -- better to have everyone pull from github.
16:59 mgage Might want some kind of backup in case github goes away --but there will be enough of us with mirrors of the repository that I'm not too worried.
17:03 mgage the POD docs are being pulled from svn still -- I can't tell for sure whether doxygen is running this or not.   Perhaps djun and someone else can get the code review/browsers working rock solid for the wiki during the Raleigh code camp?
17:04 mgage ok --- I have to run now.  ttyl
18:36 aubreyja omg, I just wrote a ton on Git on the wiki but by the time I saved I wasn't logged in and now all is lost….grrr...
18:44 djun joined #webwork
18:48 JohnTravis joined #webwork
19:44 djun joined #webwork
20:30 ChanServ joined #webwork
20:37 ChanServ joined #webwork
20:39 ChanServ joined #webwork
21:03 aubreyja mgage, mgage_: hi
21:05 djun joined #webwork
21:07 djun_ joined #webwork
21:11 djun joined #webwork
21:13 djun_ joined #webwork
21:16 djun joined #webwork
21:17 djun_ joined #webwork
21:19 djun Hello all
21:36 djun joined #webwork
21:43 JohnTravis mgage:  home?
21:45 JohnTravis I'll leave this here for when you get back...at https://github.com/openwebwork/webwork-open-problem-library/blob/master/INSTALL the instructions refer to global.conf.  Wasn't global.conf broken up into parts?  Does this version still require the single conf file?
21:46 ChanServ joined #webwork
22:01 mgage JohnTravis: the instructions might just be bad -- this is stuff that Jason and Djun set up up so I don't have detail -- but in fact it should be a script that works with the new config files.  You can check to see if it refers to site.conf and defaults.conf in the code
22:02 mgage even if it works the instructions should be changed
22:03 JohnTravis Ok then.  I have decided to finally work on moving the webwork install here at MC to our new server that has not been used...been too busy.
22:04 JohnTravis Probably should remove everything and just start from scratch.
22:04 djun Hi John, Mike
22:05 mgage hi
22:05 djun just looking at the install document now
22:05 JohnTravis Hello Djun.
22:05 mgage I think the instructions are just wrong -- it should say conf/localOverrides.conf
22:05 djun I think that's right, Mike
22:06 JohnTravis I did the github version a while back.  The svn version was working and I changed the symbolic link to the github version and it all died.
22:06 JohnTravis Now I can't get back!  :)   No problem since no one is on this machine.
22:07 mgage does your github software have conf/site.conf   and conf/localOverrides.conf defined?  You might not have set it up yet.
22:08 mgage You also need to make sure library version number is 2.5 and not 2.0
22:08 JohnTravis Yes on site.conf.  Checking the other...
22:08 djun Fixed :)
22:08 mgage ty
22:09 JohnTravis no localOverrides.conf.  Humph.
22:10 mgage copy over from localOverrides.conf.dist and make the needed local changes. (you can look them up in your snv global.conf file if you don't remember them)
22:10 mgage also add $problemLibrary{version}  if it isn't there already
22:11 JohnTravis Ha.  Wondered where that stuff went.
22:30 djun mgage, I'm looking at June dates for a code camp in Vancouver.  Does Thurs Jun 27 - Sun 30 work?
22:30 djun Earlier is awkward for me :(
22:35 mgage djun: I could make that
22:36 djun Great!  Is there a "how to organize a code camp" doc around somewhere? :)
22:36 djun The UBC stats department is on board
22:37 djun We have access to good space
22:38 mgage I think Jason created one for Alina -- send him a quick note.  Also send Arnie a quick note about this and have him double check that there are no issues with NSF because the code camp is in Canada. (I'm pretty sure it's not a problem, but I'd prefer that Arnie double checked it.)
22:42 djun OK, will do. Thanks!

| Channels | #webwork index | Today | | Search | Google Search | Plain-Text | summary