The agenda for the coming meeting is given in the topic of the channel.
2016-07-29 21149, 2016
ruaok
I gotta say, git is amazing.
2016-07-29 21103, 2016
QuoraUK
^ this is how I was feeling tuesday :P
2016-07-29 21112, 2016
ruaok
coupled with github, the shit we're doing today was simply not possible a few years ago.
2016-07-29 21141, 2016
ruaok
Gentlecat: have you had a chance to run the vagrant LB stuff yet?
2016-07-29 21149, 2016
QuoraUK
once i figured out rebase I finally got the whole point :P
2016-07-29 21151, 2016
ruaok
not sure why PG is so angry there.
2016-07-29 21159, 2016
ruaok
QuoraUK: yep. :)
2016-07-29 21124, 2016
alastairp
hmm. I was going to bring that up some meeting
2016-07-29 21130, 2016
alastairp
what's our timeline for jira upgrades?
2016-07-29 21145, 2016
ruaok
jira is not going to be touched until we're at newhost.
2016-07-29 21147, 2016
alastairp
honestly, we do so much discussion on github with PRs, having tickets on jira is annoying me
2016-07-29 21124, 2016
ruaok
yeah.
2016-07-29 21127, 2016
alastairp
(e.g., our discussion about playing now timeouts, We decided to add the result of our irc discussion to jira, but you missed it because there was other discussion happening on github(
2016-07-29 21121, 2016
ruaok
canonical problem of too many mediums of discussion.
2016-07-29 21127, 2016
alastairp
yep
2016-07-29 21130, 2016
armalcolite
we can use github issues instead of jira, it would also be easier to refer things and quite handy.
2016-07-29 21149, 2016
alastairp
armalcolite: unfortunately it's not as easy as saying "let's just change"
2016-07-29 21150, 2016
ruaok
armalcolite: not yet. as alastairp suggested, this is something we should discuss as a team.
2016-07-29 21102, 2016
alastairp
but it's definitely an option that we should consider
2016-07-29 21103, 2016
Freso has quit
2016-07-29 21107, 2016
armalcolite
sure.
2016-07-29 21111, 2016
ruaok
and it is a huge amount of work to switch. :(
2016-07-29 21123, 2016
alastairp
ruaok: no it isn;t, just fix all of the open bugs ;)
2016-07-29 21127, 2016
ruaok
another problem is that zas is on holidays and he's become the critical path for docker work.
2016-07-29 21144, 2016
armalcolite
ruaok: does that mean taking all the issues on jira to github?
2016-07-29 21146, 2016
ruaok
and the jira upgrade path is stooopid.
2016-07-29 21100, 2016
alastairp
I actually like related tickets in jira
2016-07-29 21102, 2016
ruaok
armalcolite: it could, but for MB that would be a huge undertaking.
2016-07-29 21104, 2016
Freso joined the channel
2016-07-29 21113, 2016
alastairp
github issues are good for something that has never had issue tracking
2016-07-29 21125, 2016
alastairp
but if you use all the features of a more complex tool, it's laughable
2016-07-29 21152, 2016
ruaok
I suspect that upgrading jira is a better first step. if only is wasn't so much freaking work.
2016-07-29 21115, 2016
ruaok
who was it who wanted to volunteer for that, but we couldn't because of confidentiality?
2016-07-29 21119, 2016
alastairp
yeah, I think a new version will provide better integrations
2016-07-29 21121, 2016
alastairp
not me
2016-07-29 21132, 2016
ruaok
I wanna say it was Leo_Verto.
2016-07-29 21158, 2016
ruaok
christina was so opposed to no value contract that bound the person to confidentiality.
2016-07-29 21108, 2016
alastairp
ah
2016-07-29 21116, 2016
ruaok
that or a no-value contract that handles the confidentiality.
2016-07-29 21123, 2016
ruaok
well, that road-block is removed now.
2016-07-29 21135, 2016
ruaok
Leo_Verto: was that you who was wanting to help?
2016-07-29 21123, 2016
ruaok
if we can find a volunteer, I will work out a contract and setup a google VM to get this done.
2016-07-29 21131, 2016
alastairp
I remember that the problem was that we can't do a direct upgrade? or the hosted jira service was dying on our dump? Do we have an idea of what to do instead? incremental upgrades?
2016-07-29 21145, 2016
ruaok
a few things:
2016-07-29 21146, 2016
alastairp
though was there also the problem that the incremental versions of jira we need aren't available
2016-07-29 21156, 2016
ruaok
1) incremental upgrade was required to self host.
2016-07-29 21101, 2016
colbydray joined the channel
2016-07-29 21103, 2016
ruaok
2) to get SSO we need to self host.
2016-07-29 21116, 2016
alastairp
ah, sso. that was the other thing
2016-07-29 21127, 2016
ruaok
3) if we want no SSO, then we can use the online version which actually worked after some tinkering.
2016-07-29 21153, 2016
ruaok
I think in the end we agreed that self hosted, SSO was the way to go, even though it was a horrible upgrade path.
2016-07-29 21157, 2016
colbydray
just updated my RequestBrainz Page. new feature: FormList and new style
