Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 03:33
    wbaid edited #4879
  • 03:23
    wbaid commented #4879
  • 02:15
    DrGFreeman commented #4561
  • 01:18
    eloquence commented #4879
  • 01:04
    eloquence commented #4879
  • 01:03
    eloquence commented #4879
  • 01:03
    eloquence commented #4879
  • 01:02
    eloquence commented #4879
  • 01:00
    eloquence commented #4879
  • 00:59
    eloquence commented #4879
  • 00:59
    eloquence commented #4879
  • Oct 22 23:59
    eloquence commented #4879
  • Oct 22 21:48
    eloquence commented #4880
  • Oct 22 21:47
    eloquence synchronize #4880
  • Oct 22 21:47

    eloquence on docs-source-guide-cleanup

    Add disclaimer-ish notice and l… (compare)

  • Oct 22 20:46
    emkll edited #4950
  • Oct 22 19:43
    eloquence commented #4893
  • Oct 22 19:32
    eloquence commented #4942
  • Oct 22 19:00
    emkll review_requested #4950
  • Oct 22 19:00
    emkll review_requested #4950
Erik Moeller
@eloquence
@conorsch I'm assuming docs branch and github release object are next on your list?
Conor Schaefer
@conorsch
thank for the reminder, one sec...
Conor Schaefer
@conorsch
@eloquence refresh my memory on the docs branch update step? i believe some action is required in ReadTheDocs—ensuring that release/1.0.0 maps to "stable", yes?
Erik Moeller
@eloquence
yes
"Make sure that the default branch of documentation is being built off the tip of the release branch."
so I think that's what you just said in different words :)
Conor Schaefer
@conorsch
still working on docs branch changes... i don't see the release/1.0.0 in there, so rebuilding from latest ad-hoc in an attempt to trigger a branch refresh
the webhook is still connected, i see successful deliveries from today
Erik Moeller
@eloquence
roger that, holding off on release announcement until then so we don't have to link to latest
Conor Schaefer
@conorsch
@eloquence should be good to go now, please check docs.securedrop.org and confirm you see 1.0.0
rmol
@rmol
Can confirm.
Erik Moeller
@eloquence
lgtm as well
Conor Schaefer
@conorsch
documented the steps here in the maintainer guide, since i couldn't find any pre-existing docs on updating the docs ("Yo, dawg...")
Erik Moeller
@eloquence
nice
posting release notes ...
nb, upgraded my instance via cron-apt and it seems to have worked fine, did have to shift+reload to clear out old stylesheets from cache
@conorsch could you poke at that backport docs PR?
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