Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 00:31
    eloquence commented #4997
  • 00:05
    ninavizz edited #4997
  • 00:04
    ninavizz review_requested #4997
  • 00:04
    ninavizz opened #4997
  • 00:04
    ninavizz review_requested #4997
  • 00:04
    ninavizz review_requested #4997
  • 00:04
    ninavizz review_requested #4997
  • Nov 15 23:51
    eloquence commented #4996
  • Nov 15 22:28
    eloquence commented #4996
  • Nov 15 21:10
    zenmonkeykstop commented #4996
  • Nov 15 21:04
    eloquence labeled #4458
  • Nov 15 20:36
    ninavizz commented #4996
  • Nov 15 20:36
    ninavizz commented #4996
  • Nov 15 20:32
    ninavizz commented #4996
  • Nov 15 20:26
    zenmonkeykstop commented #4996
  • Nov 15 20:24
    zenmonkeykstop commented #4996
  • Nov 15 20:24
    zenmonkeykstop commented #4996
  • Nov 15 19:27
    creviera commented #4993
  • Nov 15 19:27

    rmol on 4993-explain-libvirt-cleanup-procedures

    devops/clean: run molecule dest… (compare)

  • Nov 15 19:03
    ninavizz commented #4996
Conor Schaefer
@conorsch
on it
Erik Moeller
@eloquence
will attempt to switch my longrunning instance over to v3 while bulk announce is running, in case of any issues not caught in QA for which it can serve as a canary
Erik Moeller
@eloquence
graphical updater worked, it did pop up an "updater already running" message briefly
Erik Moeller
@eloquence
getting my old friend "waiting for privilege escalation prompt" on playbook run
one of my personal top candidates for a 1.1.0 priority issue to resolve :)
Kevin O'Gorman
@zenmonkeykstop
was it resolvable by nuking ~/.ansible?
Erik Moeller
@eloquence
yeah, that one went away. had a few more playbook timeouts but ultimately succeeded, now happily running v2 alongside v3 :)
your docs worked perfectly
Erik Moeller
@eloquence
I did get the usual "Are you sure you want to continue connecting" SSH prompt on ssh app and ssh mon after the change to the new v3 address, not sure if that's worth documenting in that part of the docs
Erik Moeller
@eloquence

Hello everyone! Our standup is in 5 minutes at the usual location:

https://meet.google.com/ekb-kkhf-mrk

Anyone is welcome to participate! Notes are taken on an Etherpad and will be moved to the GitHub wiki by the end of the day.

Kevin O'Gorman
@zenmonkeykstop
@conorsch or @eloquence #4836 is ready for another pass
Conor Schaefer
@conorsch
^ have not reviewed yet, will get to it shortly
Kevin O'Gorman
@zenmonkeykstop
thanks for nitmit, have rebased :)
Conor Schaefer
@conorsch
reapproved, ready for merge once ci passes
aaaand ci passes, #4836 is ready for backport
Erik Moeller
@eloquence
@zenmonkeykstop are you backporting? otherwise I can
Conor Schaefer
@conorsch
^ backport done and merged. also, love "nitmit" :smiley:
Kevin O'Gorman
@zenmonkeykstop
I'm planning to make it a thing
Erik Moeller
@eloquence

Hello everyone! We'll be starting sprint planning in 5 minutes. This will include a retrospective on the 1.0.0 release. You can find all the materials for the meeting here:

https://pad.riseup.net/p/SecureDropSprint38

It'll be in the usual place:

https://meet.google.com/ekb-kkhf-mrk

Erik Moeller
@eloquence

FYI, extended our standups Monday-Wednesday officially to 30 minutes each, since we still have a few loose ends from sprint planning we can follow-up on incrementally.

@redshiftzero I've not scheduled a mtg specifically for securedrop-admin. How would you like to plan out that particular change? Do you think it would be useful for one team member to write up a spec and discuss it, as we did for v3, or is that not necessary in this case?

Erik Moeller
@eloquence
[Considering splitting near-term backlog on the board into workstation column + securedrop core column, to make it more manageable. Let me know if you have thoughts either way.]
redshiftzero
@redshiftzero
i think it's worth writing out a spec/proposed migration plan (e.g. to answer questions like what should happen if admin checks out 1.1.0 tag and does not re-run setup, how should the virtualenv be migrated, etc.). making securedrop-admin code python 3 compliant is not going to be the main work, it's mostly the migration
Erik Moeller
@eloquence
roger that. do you want to drive that before your trip to germany, or open for takers? if the latter, will briefly poke tomorrow morning when kushal is back around
redshiftzero
@redshiftzero
i probably wouldn't get to this until tomorrow PM, any interested people pretty familiar with securedrop-admin / python 3 transitions want take a stab at a proposal? @rmol or @kushaldas perhaps? else i can do tomorrow or monday towards EOD
Erik Moeller
@eloquence
Sprint planning/retro notes can now be found on the wiki as well, and planning board / spreadsheet should be in sync.
Still a few more estimates to add, we can do so during Monday/Tuesday standups.
Kushal Das
@kushaldas
@redshiftzero I will write one.
Kevin O'Gorman
@zenmonkeykstop
if anyone was looking at #4852 I've updated the PR with another dirty hack for the dynamic inventory.
Erik Moeller
@eloquence
As a reminder, no GMeet standup on Fridays, but quick updates to https://pad.riseup.net/p/SecureDropDailyStandup are appreciated :)
Erik Moeller
@eloquence

Hello everyone! Our standup is in 5 minutes at the usual location:

https://meet.google.com/ekb-kkhf-mrk

Anyone is welcome to participate! Notes are taken on an Etherpad and will be moved to the GitHub wiki by the end of the day.

Erik Moeller
@eloquence
^ same procedure :)
Kevin O'Gorman
@zenmonkeykstop
the curse of libvirt returns
Erik Moeller
@eloquence

Hello everyone! Our standup is in 3 minutes at the usual location:

https://meet.google.com/ekb-kkhf-mrk

Anyone is welcome to participate! Notes are taken on an Etherpad and will be moved to the GitHub wiki by the end of the day.

Conor Schaefer
@conorsch
:heart:
Erik Moeller
@eloquence
Hi folks -- just a heads up that there will be no UX meeting tomorrow (or next week, due to the FPF all-staff). We'll pick up the regular schedule in a couple of weeks.
Erik Moeller
@eloquence

Hello everyone! Our standup is in 5 minutes at the usual location:

https://meet.google.com/ekb-kkhf-mrk

Anyone is welcome to participate! Notes are taken on an Etherpad and will be moved to the GitHub wiki by the end of the day.

mickael e.
@emkll
bringing down apt-test.freedom.press for a brief moment
Kevin O'Gorman
@zenmonkeykstop
looknig at fixing #4387 - would it make more sense to just not start the GUI updater if the amnesia user doesn't have a password set?
upside is it doesn't present the user with something they can't use, downside is that if they never log in with a password set, they never see the gui updater
Erik Moeller
@eloquence
@zenmonkeykstop if we're able to detect that, I think it'd be best to show an error message after the user clicks on "Update Now", and to not set the flag in that case
Kevin O'Gorman
@zenmonkeykstop
yup that's pretty much what I settled on, writing a test now
Erik Moeller
@eloquence
@rmol @zenmonkeykstop are either of you planning to poke at the securedrop-admin py3 changes today? freedomofpress/securedrop#4867
It's basically the last day we have before QA
Kevin O'Gorman
@zenmonkeykstop
to be precise: updater appears -> user clicks update now -> message dialog shown -> update now button deactivated
rmol
@rmol
@eloquence Am planning on it. Still stuck trying to devise a test for the securedrop-app-code dependencies on fresh install.
Kevin O'Gorman
@zenmonkeykstop
I was not. but I can take a look in a bit if noone else is available
Erik Moeller
@eloquence
@rmol would you like to chat with conor or other team members about the dependency testing problem you're stuck on?
Conor Schaefer
@conorsch
@rmol the app code dependencies are installed via ansible. it'd be a bit cleaner and more predictable if we allowed apt to resolve the package dependencies. I suspect we added the ansible install tasks, that essentially duplicate the app-code dependencies, in order to support the install-from-local-packages logic in staging. if we're using dpkg for the deb install, which does not handle Depends on packages, perhaps we could use aptitude instead
i haven't actually confirmed that aptitude will intelligently handle dependencies, but worth a look. that'll allow us to verify that the deps are what's determining the packages pulled in, not the ansible logic (which is seldom run)
Erik Moeller
@eloquence
@zenmonkeykstop your updater strategy sounds good! if you do reach a good stopping point, would appreciate if you could still get some review on #4867 in. if a merge is at all realistic today it's only going to be if both you and John have a chance to test it. If it looks good, Conor can potentially stamp it later.