-
janeted
hey ehazlett - I'm pretty sure dean was wanting you to deploy his
pculture.org changes.
-
sylvainc joined the channel
-
hi sylvain - everything go OK yesterday ??
-
sylvainc has quit
-
sylvainc joined the channel
-
sylvainc
yes, thanks, was a long-awaited day ;-)
-
janeted
good.
-
sylvainc, can I get your opinion on this one?
-
-
sylvainc
sure janeted, let me have a look
-
janeted
it involves changing how the keyboard shortcuts display and adding some help guidelines
-
sylvainc
yes, that looks good, I'm just wondering if we should break it into several tickets... but it is actually not that much coding
-
so it might be ok in one ticket,
-
janeted
however you prefer, I think the style guide doens' t really belong there
-
sylvainc
one thing is that I'm not sure all shrtcuts are workable, in case there is a conflict with the browser's or OS's shortcutrs
-
janeted
right - but we don't need to implement them all right now
-
just getting the display to look good, so the UI is more friendly to the user and we can keep the others as proposed.
-
sylvainc
ok, sounds right,
-
janeted
it may be good to get some community feedback on some of the others from the power users.
-
sylvainc
one thing, should we add a "+" between keys in the help panel?
-
when they need to be pressed at the same time?
-
janeted
you don't think that's obvious?
-
another thing I can't really visualize, is if the buttons should all be the same blue - of if we should use different colors
-
the old editor had different colors and it was very eye-catching.
-
maybe we can experiement with that after
-
sylvainc
sure, I'm not confident with my opinios on appearence ;-)
-
janeted
I'm not either
-
sylvainc
so let's start with the design you put in the ticket
-
janeted
but if we get something started - it'll be easier to tell or ask for a second opinion
-
OK - and actually it was this guy Tom who did the mockup - he's a student volunteering some time
-
so I put the assets in the amara-assets repo
-
we are so close to doing this switchover,
-
sylvainc
i saw that, good, I'll assign this ticket to myself,
-
janeted
great thanks
-
sylvainc
is it in the list in the wiki?
-
janeted
I just added it in the help section
-
sylvainc
ok, great
-
janeted
I'm going to go cross off all the tickets that are ready for merge.
-
There's a few more related to the dialogs that ben should be fixing
-
sylvainc
-
from title it does not seem importsnt, but it includes a fix for mp4 videos on firefox
-
without that one, mp4 videos can't work in editor/embedder on FF
-
janeted
yes - I think we can deploy the changes that are currently merged to staging
-
basically any of the editor fixes.
-
as we go along
-
I think the other security ticket ben did is ready - I just wanted to confirm that
-
sylvainc
ok, good.
-
janeted
I think we can keep updating, and then once we are ready - the last push will have to be 1121 - which switches over all the dialogs.
-
so ideally - we just keep improving as usual and merge / deploy 1121 branch for the switchover
-
sylvainc has quit
-
sylvainc joined the channel
-
sylvainc
right
-
janeted
I think we can add auto-pause to the nice-to-have section
-
it's a great feature - but I have no idea how complicated.
-
And I think we should switch the embedder over separately (afterwards)
-
sylvainc has quit
-
sylvainc joined the channel
-
sylvainc has quit
-
sylvainc joined the channel
-
janeted has quit
-
bendk joined the channel
-
bendk has quit
-
bendk joined the channel
-
bendk
sylvainc: are you on?
-
what do you think about making a new branch for making the new editor the primary one?
-
right now I'm working on gh-1121, but that branch is covering more issues than just 1121
-
sylvainc
yes, i'm here
-
shall that branch include everything that should not go on production before we swiutch over to the new editor?
-
bendk
exactly
-
sylvainc
ok, right, I remember that 1121 branch was "the last one"
-
bendk
yeah, 1121 changes the dialogs and stuff to make the new editor primary, then it contains several more fixes
-
and now I'm going to work on 1255 and 1239
-
I could actually make branches just for those issues and base them from staging
-
but I figure the merging is going to get harder and harder between staging and gh-1121
-
sylvainc
oh, i see,
-
how about regularly merge staging back to gh-1121? do you think it'd be workable?
-
bendk
yeah, that's possible
-
I think it would be a bit harder to merge, but on the other hand we could push the changes incrementally
-
okay, you've convinced me
-
sylvainc
I hope I understood you correctly then ;-)
-
janeted joined the channel
-
michelled joined the channel
-
michelled has quit
-
janeted has quit
-
janeted joined the channel
-
michelled joined the channel
-
janeted has quit
-
bendk has quit
-
janeted joined the channel
-
janeted
hey ehazlett can you take a look at this pull request please.
-
-
ehazlett
janeted: merged
-
janeted
and if it's ok to merge, can you merge it and deploy staging. We have a bunch of stuff on there and before we get any more,
-
I'd like to run through it and maybe do prod tomorrow
-
ehazlett
yeah
-
all: deploying staging
-
janeted
cool thanks
-
sylvainc has left the channel
-
ehazlett
janeted: staging deployed
-
janeted
cool thanks
-
ehazlett
yw
-
michelled has quit
-
janeted has quit
-
nigel_bot has quit
-
nigel_bot joined the channel