-
Notifications
You must be signed in to change notification settings - Fork 2
/
nuts-and-bolts-agenda.txt
1593 lines (1286 loc) · 62.3 KB
/
nuts-and-bolts-agenda.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Agenda and minutes of Governance meetings
URL TBD via IRC
Nearly Every Tuesday
Next meeting: Tuesday, November 23 19:00 UTC +1/CET
AGENDA
_______________________________________________________________________
UPDATES
Contractors
Audit
GitLab Migration
Website
Test Grid
Documentation
Summit/Events
Community, Mailing List, Discourse etc.
GOVERNANCE
TBD/suggestions welcome
CTAs
DISCUSSION/INSPO
______________________________________________________________________
Minutes of Past Meetings
NOVEMBER
Tuesday, November 16
_____________________________________________________________________
UPDATES
Contractors
Anxhelo's (Web Dev) contract with BASICS had completed; we did the
closing report together and gathered learnings from the experience
General discussion of how the organization could support contributors
Audit
Remediation has stalled over the last week as we were down one reviewer
Discussion of merging strategy to avoid conflicts as branches grow/age
Discussion of Cure53's verification of fixes and the possible timeline
Insights on upcoming fixes from meejah (core dev)
GitLab Migration
Website
Supposed to be pushed soon; m-L (Community Manager) will follow up
Test Grid
Grid is full
The NixOS config for Tahoe does not support GC - Jean-Paul (core dev)
Lease configuration and lease design
ZKAP faucet to manage access
Cronjob that deletes everything every week
PS would benefit from lease duration being a client setable constraint
Documentation
Summit/Events
Community, Mailing List, Discourse etc.
GOVERNANCE
Tahoe needs more technical and resource availabilty
It's probably going to be 30 hours/wk for each core member, easily
With all of the work that can be done on Tahoe, the processes would direct
themselves, thereby needing nominal process or organizational resources
We need to work on our onboarding, management and retention
**NO MEETING TUESDAY NOVEMBER 9**
Tuesday, November 2
_____________________________________________________________________
UPDATES
Contractors
Encourage contractors to file tickets that describe a desired
outcome and submit small PRs that resolve them
Fenn - continuing to take steps to automate the release process
Audit
Money situation
GitLab Migration
Update needed (development started)
Website
Update needed
Test Grid
Documentation
Summit/Events
Community, Mailing List, Discourse etc.
GOVERNANCE
Project security fix timeline/milestones
*Closed discussion*
OCTOBER
Tuesday, October 26
_____________________________________________________________________
UPDATES
Contractors
Encourage contractors to file tickets that describe a desired
outcome and submit small PRs that resolve them
Fenn - continuing to take steps to automate the release process
Audit
Money situation
GitLab Migration
Update needed (development started)
Website
Update needed
Test Grid
Documentation
Summit/Events
Community, Mailing List, Discourse etc.
GOVERNANCE
Project security fix timeline/milestones
*Closed discussion*
CTAs
Tuesday, October 19
_____________________________________________________________________
Present: May-Lee, Jean-Paul, Sajith
UPDATES
Contractors
Fenn (testing and release manager)
More thoughts on documentation
Getting rid of some documents
Opening PRs/tickets to deal with specific actions relating to
documentation
Suggestions about moving up the PR ladder in terms of asking for and
giving reviews
Yash (documentation) - Met with Fenn to share knowledge from meejah (core
dev) and Jean-Paul (core dev)
Possible three groups of users to design documentation around:
People who are new to Tahoe and trying to use the software
Other group is the builders interested in the building of the project
Third group is a mix of first group; users who want to know the nitty gritty
Audit
We are focusing on fixing issues until they are done
GitLab Migration
Update needed (development started)
Website
Update needed
Test Grid
Documentation
Sajith (core dev) will merge the PR that has the ToC so Yash can build
off of it.
Summit/Events
Community, Mailing List, Discourse etc.
GOVERNANCE
All meeting times will be pegged to Tuesdays at 19:00 in Berlin, because
that is where May-Lee (Community Manager) is located
CCX will be joining the remediation team according to a vote
He is interested in reliability and working on mutables
We discussed and voted to share the audit report only with 1) Community
members (according to a vote by the core devs) and 2) also they will be
joining or are interested in joining the remediation team.
After the fixes are pushed, we will share the report publicly
We edited typos in the audit report together
CTAs
DISCUSSION/INSPO
Tuesday, October 12
_____________________________________________________________________
Present: May-Lee, Jean-Paul, meejah
UPDATES
Contractors
Fenn (testing and release manager)
Updates on the week's work and his goals for the year:
Learning about set-up tools and production vs. development
Wants to do 4 Hacktober PRs
Releases
We don't do reproducible builds, but we needed to reproduce one to
track down a size discrepancy between 1.16.0 rc1 and rc2 (meejah, core dev)
Audit
GitLab Migration
New conversion tool started by Jean-Paul (core dev)
Website
Test Grid (Jean-Paul)
Deployed and is working
All Nix, no Terraform
It now has its own codebase, so anyone who wants to do Nix can do Nix
PRs: https://github.com/tahoe-lafs/infrastructure
Documentation
Summit/Events
Community, Mailing List, Discourse etc.
GOVERNANCE
We talked about documentation and how it is the first point of contact
for contributors entering the project.
Agreed: we need to write down rules for documentation so that documentation
is cohesive and united in purpose.
We also don't want to keep changing our direction on documentation.
Other considerations:
Documentation is an important part of the on-boarding process
We have these potential groups interacting with the project: Developers,
endusers, cryptographers
Setting a goal for the README: to tell different types of audiences where to
find what they are looking for
How deep should we do linking?
We should also do general documentation PRs
CTAs
DISCUSSION/INSPO
***NO MEETING TUESDAY, OCTOBER 5***
SEPTEMBER
***NO MEETING TUESDAY, SEPTEMBER 28***
Tuesday, September 21
_____________________________________________________________________
Present: May-Lee, Fenn, Jean-Paul
UPDATES
Contractors
Fenn (Internews/BASICS) did release for 1.16.0; tracked documentation
issues
Audit
Closed discussion about strategy for audit fixes
(summarized and sent via email)
GitLab Migration
Website
Test Grid
Documentation
Summit/Events
GOVERNANCE
How will we address the audit fixes?
CTAs
DISCUSSION/INSPO
Tuesday, September 14
_____________________________________________________________________
Present: May-Lee, meejah, Jean-Paul
UPDATES
Contractors
BASICS/Internews: Anxhelo (web) on vacation, Yash (documentation) is working through
documentation goals (consuming/providing storage) and Style Guide
Audit
Contentful discussions happening
Start a private area to work on any critical issues
GitLab Migration
We would like another dev for this, still
Website
Test Grid
Possibly ask hacklschorsch (contributor)
Documentation
See above
Summit/Events
None
GOVERNANCE
PR bottleneck
Balance of work has shifted from long-time Tahoe contributors to new
Tahoe contributors
Itamar (core dev) is very productive (working on 4 PRs), he could also be
requested to more review to smooth out our coordination
Jean-Paul and meejah (core devs) review and renew ping strategy.
Meeting schedule
One standing meeting per week (Tuesday's Nuts and Bolts at UTC +1/+2)
Meetings with outside organizations should also try to be scheduled during
this time
If a meeting for a specific purpose needs to happen outside of this time,
then it will be the ONLY meeting that week, and the Tuesday meeting gets
cancelled
ACTIONS
meejah and Fenn (Testing and Release) to put out the Release
***NO MEETING TUESDAY, SEPTEMBER 7***
Tuesday, August 31
_____________________________________________________________________
Present: Fenn, May-Lee, meejah, Jean-Paul, Sajith
UPDATES
BIG UPDATE: RC 1.16.0 - Thanks meejah (core dev) and Fenn (Testing and Release)
https://tahoe-lafs.discourse.group/t/1-16-0-release-candidate-a-message-from-meejah/34/2
Contractors
Fenn (Testing and Release Manager) did an RC w/meejah
Also tried to land a branch with Black but there were tons of merge
conflicts; still in process
Talked about time-outs in the testing suite
Yash (documentation): mapped out the three major articles of the documentation
Yash and Fenn will update the release documentation together
Mailing list is back: https://lists.tahoe-lafs.org/mailman/listinfo
Need admin gpg keys
Thanks Sajith (core dev)!
Discourse via Github to avoid forcing people to open new accounts
Discourse and all Tahoe-LAFS Discourse admins will have access to the GitHub Oauth secret;
this is non-optimal but we might still be okay with it
We discussed the actual consequences of this situation
Audit
Have the commit we want audited by September 6th
Can keep developing; avoid major architectural overhauls
Lots of tickets that Jean-Paul (core dev) has to turn in; will help with the audit and make the audit more useful
Yash could help by answering documentation questions
Itamar has been looking at new interfaces that will help the GBS integration
Have one in place that would do still have Foolscap and also GBS;
Foolscap would work the same way and be behind a slightly different API
Monthly report will be late
GOVERNANCE
Have a list that gets cut and pasted from one meeting to the next so we
know what we're focused on - Jean-Paul
Tuesday, August 24
_____________________________________________________________________
Present: Fenn, May-Lee, Meejah
UPDATES
Contractors
try to max out Anxhelo's (Web dev) BASICS contract before requesting Tahoe
Fenn (testing and release) 2 PRs; need another merged
Website (Anxhelo) - focus is on accessiblity; using dark theme; created blog page
GOVERNANCE
RC for Python 2 + 3
Only Warner (core) and meejah (core dev) have the Tahoe signing key
Jean-Paul (core dev) also can sign via Warner/meejah
We have enough documentation for a release although needs to be revamped
meejah and Fenn will go through it together
Fenn will take notes to help update the documentation
The Python 3 port was intended to have a Python 2 + 3 release
Reformatting codebase with Black/YAPF
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3775#ticket
Fenn will choose Black over YAPF and try to land the following branch:
https://github.com/meejah/tahoe-lafs/tree/2916.grid-manager-proposal.5
could be lots of conflicts/other effects
DISCUSSION/INSPO
https://en.wikipedia.org/wiki/IP_over_Avian_Carriers and other RFCs
The IETF has an impending one that will result to a move to end-to-end
encrypted protocol
Monthly report call for items
Tuesday, August 17
_____________________________________________________________________
Present: Jean-Paul, Fenn, May-Lee, meejah, Anxhelo
UPDATES
Tahoe-LAFS PR bot has returned :)
Cure53 chosen to do audit
GOVERNANCE
Presenting landing pages - Anxhelo (Web Developer)
Suggesting a static site generator
Anxhelo will choose tooling and begin creating the website
Preparing for our security audit
https://leastauthority.com/blog/audit-preparation-checklist-5-important-steps-to-prepare-for-a-security-audit/
What's the experience of being audited going to be like?
A bunch of people ask questions about your codebase in the IRC for three weeks, so have answers
New development over the next 2-3 weeks should keep in mind the auditing process
Organize project/get to know project
Look at unknown lines of code - 40k off in some dusty corner
Reformatting of code using Black by Fenn (Testing and Release Manager) - more research needed
Recommended: a python2+3 release before we refactor/start GBS stuff
Freeze codebase Sept 6
Tuesday, August 10
_____________________________________________________________________
Present: Jean-Paul, Fenn, May-Lee
UPDATES
Contractors
GOVERNANCE
No force pushing, except when working alone, and never when reworking PRs
Confidential internal discussion: Evaluating SOWs, by vendor (meejah gave input via email)
Sent questions to Radically Open Security and Cure53
Updated all core Tahoe members with discussion notes and voting process
DISCUSSION/INSPO
What to do with unmerged PRs?
Tuesday, August 3
______________________________________________________________________
Present: Jean-Paul, meejah, Sajith, Fenn, May-Lee
GOVERNANCE
Setting a monthly IRL meet-up
Will be in Berlin and probably an "Open Source" theme vs. strictly
Tahoe
Standing meeting for "onboarding" new contributors.
Thursday evenings in the EU
Summit planning: Agenda needed to clarify project
https://github.com/tahoe-lafs/community/issues/12
UPDATES
Contractors
Fenn (Testing and Release Manager) introduction and assignments
Monthly Report
https://github.com/tahoe-lafs/community/blob/main/Monthly%20Reports/july-2021.md
DISCUSSION/INSPO
Getting multiple servers for our test grid/pub grid
Sajith (core dev)/May-Lee (community manager) working on it
GitLab migration - Jean-Paul (core dev) might take it on
JULY
Tuesday, July 27
______________________________________________________________________
Present: Jean-Paul, meejah, May-Lee
GOVERNANCE
Clean Insights - do we think Tahoe could use this?
Tahoe should not do analytics of any kind to its users
Admin permissions for servers given to all core
Core will make sure to take no action, so that no extra work will be
created
Security Audit
Try to get proposals but then YOLO
Worst case scenario we have an audit done!
Continuing contractor contracts and don't contractors have the right to choose
with whom they will contract?
UPDATES
New Gentoo overlay - thanks jpds! (contributor)
https://github.com/jpds/tahoe-lafs-overlay
Contractor updates
New Testing and Release Manager Fenn will be introduced next week
Technical Assessment published
https://github.com/tahoe-lafs/community/issues/9#issuecomment-886648737
DISCUSSION/INSPO
CTA: Survey for branding and mockups published by Anxhelo (Web Dev)
It is anonymous and takes 15 - 20 minutes
https://cloud.ura.design/apps/forms/Qet3iaZKmrcCLSdY
The regal look of graying hair and our impending collective mortality
Is it okay to use the term "douche chills"?
Tuesday, July 20
______________________________________________________________________
PRESENT: meejah, Sajith, May-Lee
GOVERNANCE
Private meeting with core team and security auditing firm
Now we wait for a SOW
Public community meetings resume next week
UPDATES
Documentation merged; thanks all for PR review!
Congrats to Yash (documentation) for getting into the codebase!
New Nix packages courtesy of Aaron Janse (volunteer contributor)
Thanks Aaron!
Tuesday, July 13
______________________________________________________________________
PRESENT: meejah, Sajith, May-Lee
UPDATES
Documentation getting updated - Thanks Yash!
Mailing list progress - Thanks Sajith (core dev)!
Only mailing list we're keeping alive is Tahoe-Devs
All core team are now admins
Tarballs have been sent; contain passwords (admin passwords are encrpyted;
subs' are not)
New Testing and Release Manager (Fon) from BASICS interviewed
GOVERNANCE
When people approach us with interesting use cases, or projects they want to
build, how can we handle that?
Try to break it into pieces as feature requests, bug reports or asking on the IRC
We don't offer consulting as part of our sustainability model at this time.
Tuesday, July 6
_______________________________________________________________________
PRESENT: meejah, Sajith, Jean-Paul, May-Lee
UPDATES
Security Audit progress - we will prefer a vendor that has given us a
concrete timeline
Development:
Loose ends being tied up, and also I2P integration testing being added,
as well as a release of foolscap
CI being kept running, including `tox` configuration clean up and
fixing of integration tests for macOS and py27
GOVERNANCE
We need to choose our next Testing and Release Manager
The Technical Assessment was the minimum of what we should expect
Because only one person was able to complete all tasks, they will be
the one invited back
DISCUSSION/FUN
Software:
We should have both CPython and PyPy3 (most of the people using are server operators)
we should have a Linux unit test and integration test CI job and not worry about
other stuff unless someone wants to show up and do it (do don't worry about MacOS or Windows)
DNS management discussed; no next steps yet
JUNE
Tuesday, June 29
______________________________________________________________________
Present: May-Lee, Jean-Paul, Sajith
UPDATES
RfP Progressing; more vendors need to be contacted
We have a candidate to work on the NixOS test grid
Contractors weekly meeting
New thing for contractors to touch base regularly
Pursuing a trademark on the Tahoe logo needs to be governance issue
Sajith's (core dev) AMAZING I2P presentation
He put a lot of work into that and I appreciate it
GOVERNANCE
We decided to use
https://engineering.memrise.com/memrises-engineering-growth-framework-f3ba767dde1c
to provide inspiration as we advance contributors through the organization
"good enough guideline" for now
"FUN"
No fun today, only sadness.
j/k love ya'll :)
Tuesday, June 22
_______________________________________________________________________
Present: Jean-Paul, meejah, Sajith, May-Lee
DISCUSSION
Jean-Paul's (core dev) NixOS system configuration for his laptop controlling
bluetooth and audio
https://gist.github.com/exarkun/c78a8b912aa7ef8fae3cfe89e6e59c72
DECISIONS
Cure53 and NCCGroup contacted; need more vendors and a public RfP
Scopes: GBS, codebase, crypto
Outreach:
Sajith (core dev) suggests: https://www.metzdowd.com/mailman/listinfo/cryptography
meejah (core dev) suggesets: Erights IRC channel
BASICS technical assessments scheduled
GOVERNANCE
Python 3 porting sync:
Itamar going to do some more testing/then possibly GBS implementation in
August; also I2P stuff
We won't change the versioning
meejah is the best candidate for a release candidate
One day, we WILL have a build automation person
Test grid talk - next step is finding someone who doesn't use: Puppet/Chef,
Docker Compose, Fabric or Kubernetes.
Prefer: NixOS + Terraform, Saltstack and maybe maybe if they're really nice,
Ansible
Also not meant to overlap with the GitLab situation
New summer (till end September) meeting schedule:
No Friday meetings, only Tuesdays. 20 minutes of Governance, then "fun stuff"
Friday, June 18
_______________________________________________________________________
PRESENT: Sajith, May-Lee, Jean-Paul
UPDATES
GBS strategy: approach multiple vendors and ask for proposals/determine market
Ask for help with scoping
Jean-Paul (core dev) has post on Discourse
Discussion on our relationship with Aspiration
Mailing list action items:
Sajith volunteers to look at mailman stuff before it gets handed to OSU OSL
JP will MWH a tarball of a mailman directory to Sajith
We need to keep URLs stable, so will have to have two different archives
Tuesday, June 15
_______________________________________________________________________
PRESENT: meejah, Sajith, may-Lee, Jean-Paul
UPDATES
Brian Warner has handed over mailing list/DN to Sajith and meejah
Thanks to Sajith's persistence
Sajith and Jean-Paul will work on it
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3742#ticket
GOVERNANCE
https://github.com/tahoe-lafs/community/issues/6
Now has some TODOs
GitHub Issues will be for governance; Trac tickets for code/work units
CTAs
Everyone make one post to the Discourse either during this meeting or shortly after
Friday, June 11
_______________________________________________________________________
PRESENT: Anxhelo, Jean-Paul, Sajith, May-Lee, Chris
PRESENTATION OF NEW LOGO COLORS AND ASSET GUIDELINE:
Anxhelo's redesign of the logo, including change in color scheme - yay!
Including guidelines for how we use assets
https://www.figma.com/file/DXsZlDGduNp1m0b8iqDEoc/Tahoe-LAFS?node-id=0%3A1
Next step will be a survey to help understand how we want to lay out the webpage information
MISSION STATEMENT:
We worked on this a bit
Tuesday, June 8
_______________________________________________________________________
PRESENT: meejah, Yash, teratorn, May-Lee, Jean-Paul
GOVERNANCE
Presentation of Assets Guideline Draft by Anxhelo (Web Dev) rescheduled
https://github.com/tahoe-lafs/community/issues/4
RESOLVED: Create Technical Assessment for BASICS Testing and Release Manager
https://github.com/tahoe-lafs/community/issues/9
Assessment sent to BASICS; will be secret until after candidate is chosen
UPDATES
Yash has joined our documentation team!
teratorn will write proposals or open PRs against codebase to begin contributing
Sajith (core dev) bought tahoe-lafs.net. Need to figure out devops.
"Create a repo" - Jean-Paul (core dev)
TICKETS
Last week's tickets:
* #3727: Add Fosshost link to README (fixed)
* #3716, #3718, #3728, #3729: Port allmydata.scripts to Python 3 (fixed)
* #3730: Update towncrier (fixed)
* #3731, #3732: Tox tinkering (open)
Old timey ticket:
* #1353: make the FUSE interface be a supported, first-class feature
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1353
(We did not get to talk about this last week.)
Friday, June 4
_______________________________________________________________________
Present: Jean-Paul, May-Lee, Sajith
INCOMPLETE MINUTES - DRAFT
ANTI-ANTI-PATTERNING
Jean-Paul (core dev) - "Let's bottom out on items at meetings until they are
actually done"
All governance items are now Issues on the Community
JP will look at ReadtheDocs webhook situation
Sajith (core dev)
UPDATES/FOLLOW-UP
Anxhelo (web dev) will present asset management guideline on Tuesday for feedback
Will begin working on wireframes for new website
Tuesday, June 1
_______________________________________________________________________
Present: May-Lee, meejah, Sajith, teratorn, Anxhelo
INCOMPLETE MINUTES - DRAFT
Deferred items:
Libera.Chat IRC cloaks
- Should we adopt IRC cloaks?
- We could adopt cloaks like "tahoe-lafs/team/<nick>" and
"tahoe-lafs/bot/<nick>" that show project affilation.
- exarkun, maylee, meejah, or sajith should be able to ask for
cloaks in #libera-communities.
Mailing list status
Still waiting on Warner. What do we do next?
TICKETS
Last week's tickets:
* #3727: Add Fosshost link to README (open)
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3727
* #3725: Brand trademarking for Tahoe-LAFS (open)
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3725
(Relevant: https://www.uspto.gov/trademarks)
* #3624: Tahoe-LAFS logo and branding assets (open)
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3724
* #3721: Move official IRC presence to libera (closed)
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3721
* #3677: Tahoe logo looks bad on dark background (closed)
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3677
https://github.com/tahoe-lafs/tahoe-lafs/pull/1070
Python 3 porting tickets:
* #3722: Enable integration tests for Python 3 on Windows (open)
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3722
* #3723: pefile should work correctly on Python 2 and 3 now (open)
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3723
* #3700: On Windows, some tests are still failing on Python 3 (closed)
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3700
#3701: Enable Python 3 Windows test runners (closed)
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3701
Both closed in https://github.com/tahoe-lafs/tahoe-lafs/pull/1067
Ticket of historical interest:
* #1353: make the FUSE interface be a supported, first-class feature
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1353
MAY
Friday, May 28
_______________________________________________________________________
PRESENT: Jean-Paul, Sajith, May-Lee
NON-GOVERNANCE
Web Dev update:
Onboarding doc seems relatively comprehensive
https://cryptpad.fr/pad/#/3/pad/edit/f130ce6cd2dee0a329f847f5982e8951/
A checklist is good a the beginning, but we need to communicate the broader
vision of Tahoe (perhaps this will come out of the Summit)
Anxhelo (web dev) is making tickets, doing PRs, recreating assets
We might want to keep the Tahoe logo, but want it updated
Agree that we like it
Jean-Paul (core dev) wonders what the symbology/story of it is
May-Lee (community manager) wants it to be "more metal"
Waiting on Radicle VCS to speak at a Lightning Talk:
https://radicle.xyz/
FOSS P2P code collaboration built with Git and decentralized with opt-in
Ethereum
Other non-governance topics?
May-Lee (community manager) recommends 2.5 hr podcast on Moon Math:
https://www.youtube.com/watch?v=ycK3AUTdl1w
SWAG - part of contributor/fan pipeline
Sajith (core dev) shares cautionary tale of `curl` sticker swag:
https://daniel.haxx.se/blog/2021/05/28/giving-away-an-insane-amount-of-curl-stickers/
Jean-Paul (core dev) "all swag is useless" (stickers, mugs)
brief tour of JP's useless sticker collection
suggestions for branded security hardware:
Yubi keys
pre-loaded flash drives that are a self-contained Tahoe instance
plug in, have a Tahoe node, works on all major platforms
GOVERNANCE
Items decided for Tuesday's meeting
All items should be framed in the form of: what is the outcome we want?
TBD but must be scheduled at GOVERNANCE eventually:
FOSdem meetings should be scheduled
Getting a new domain/getting rights to our current domain
Domain not urgent until needed for infra
But yea, mailing list
Worst case scenario, we get YET ANOTHER domain ahead of getting permissions
We currently have three domain names pointing towards us
Pro-tip: once your organization gets a domain name that is visited by your
users, you MUST NEVER LET IT FALL INTO ENEMY HANDS or they will defile it mightily
Tuesday, May 25
_______________________________________________________________________
PRESENT: May-Lee, Sajith, meejah, Jean-Paul, teratorn, Anxhelo
Today we all got to meet Anxhelo (new Web Dev from BASICS)
*New Contributor* teratorn from the IRC also joined
GOVERNANCE
Community channel - ideas and when to vote?
meejah (core dev) made a ticket: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3721
We have moved off freenode.net and onto Libera.chat
The Slack bridge is broken and may never come back
GBS RfP https://cryptpad.fr/pad/#/3/pad/edit/39b52aeb24c546044f22c6e111252220/
Everyone has been asked to look at the scope and try group items in a
manner that would be digestible for a security firm
OTHER DOCS TO REVIEW (no urgency):
Web Dev Onboarding doc was commented on and put into use on Wednesday, May 26
Web Dev Onboarding process
https://cryptpad.fr/pad/#/3/pad/edit/441aaca21dad3f0a75cf6ef0b482af6f/
Testing and Release Manager retrospective - still being processed
https://cryptpad.fr/pad/#/3/pad/edit/e4ba29febafd61c15f1e1de9d461a258/
Friday, May 21
_______________________________________________________________________
PRESENT: Sajith, May-Lee
LIGHTNING TALK w/ Jason Snell rescheduled; possible collaboration with Michelle
Ledddon and Julia-Scott Stevenson
INSPO/Revolution vibes:
Freenode kerfuffle? Actions taken:
- #tahoe-lafs on Libera.chat
- need to do a little governance on this one, likely Tuesday
- There's also https://tahoe-lafs.zulipchat.com, if not as an IRC
alternative, as a Slack alternative.
- OFTC might be a good choice, but I2P has control of #tahoe-lafs
Tuesday, May 18
_______________________________________________________________________
Jean-Paul and Sajith attended and discussed the below items:
ROADMAP
We need to discuss and document the roadmap somewhere. Trac is not
the preferred place to hash out the roadmap. Perhaps we could use
the community repository for this.
Some wishes for the future (other than shipping Python 3 port):
1. Shipping Grid Manager
2. Non-foolscap storage servers and introducer
3. Re-engineering the API
4. The WUI should be separated from Tahoe-LAFS proper
5. Improving responsiveness
We could aim for 1 and 2 in 2020. We need to discuss 3 and 4.
Regarding responsiveness: tahoe-lafs "feels" slow from a user
perspective. As in, `tahoe --help` takes a little bit of time just to
print the help message.
Regarding ZKAP, Chrome extension, other integrations, etc: at the
moment, we do not have enough information in order to discuss them.
Regarding netifaces: maintenance might be taken up by a team within
Red Hat. That is good news.
Did not discuss onboarding doc or retrospective doc, since they
require May-Lee's presence.
Regarding tickets: we looked at the tickets from the past week.
- Python 3 porting: 6 new tickets, 4 closed (itamarst)
- Others:
- #3710: "tahoe get" emits HTML for dircaps (meejah)
- #3711: release checklist update (meejah)
- #3713: README update (exarkun)
- #3712: Nix packaging update (exarkun)
Not sure if #3710 ("tahoe get <dircap>" emits HTML), not sure if that
behavior is a regression or not. #3711, #3712, and #3713 are closed,
with corresponding pull requests.
Old timey ticket: We looked at #1942 ("Replace google chart in wui
with d3.js: it leaks information")
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1942
This was interesting because there ever was a chart in the web UI was
news to me. Ticket #1942 was closed today, with the resolution that
we will not fix it. Google Chart API usage has been long removed, the
wui has not produced any charts in a long time, and the WUI should be
a separate project anyway.
Friday, May 14
_______________________________________________________________________
SHOUT OUT TO ITAMAR (AGAIN):
all integration tests now pass on python 3 too
(at this point you should just assume all code has to be python 3 compatible)
Sajith (core dev) has volunteered to run the meeting Tuesday
Testing and Release Manager contract ended by BASICS/Internews
INSPO AND ANTI-ANTI-PATTERNING
NICE. A lot of good work got done this week, healthy PRs and good channel
convos :)
LoneTech is a new contributor!
Rants and discussions:
Current newfangled fad of meddling kids trying to get Typing into Python
All of our complex testing needs (Windows, user testing, coverage complete?)
Implementing a Tahoe-LAFS browser extension and what that would entail
Conferences:
May-Lee (community manager) wants to start sending our folks to Conferences
M-L suggested Sajith represent us/present at FOSSdem 2022,
suggested Jean-Paul (core dev) represent us/present at Haskell Love 2021
Also believes we should find someone(s) for EuroPython/PyConDE 2021
Tahoe-LAFS Summit 2021:
Suggested to add a day or so on either end of the LA Summit in Berlin
Would be an efficient use of resources for Core Team
Would not replace a larger, more general Summit, either online or IRL
Discussion: gather.town, theonline.town as virtual summit tools
Professional development:
May-Lee wants to know if people want PD/what would they want?
No promises, but can present the idea to the Board
Tuesday, May 11
_______________________________________________________________________
GOVERNANCE
* SHOUT OUT TO ITAMAR
Python 3 porting milestone: ALL UNIT TESTS PASS ON PYTHON 3
(don't get too excited; we're still porting ;)
* Release 1.15.1 completed internally; brought up to date
* Next Lightning Talk May 21: Jason Snell/EEG Music demo/Talk: privacy and security issues
of brain interface devices (collaborated with Michelle Leddon, Julia Scott-Stevenson as
part of the Assembly of Privacy Doxographers and Liz/Least Authority)
https://leastauthority.com/blog/privy-to-will-be-featured-at-copenhagen-international-documentary-film-festival/
* UPDATES:
Liz (Board) receptive to podcast idea
May-Lee (community manager) working on Discourse/OAuth with Sajith (core dev)
Jitsi issue being worked on
* DISCUSSION: Testing and Release Manager's performance since daily stand-ups started
Friday, May 7
_______________________________________________________________________
PRESENTATION
* Pantherscore.com w/Hernán Romero (currently Product Manager at Yoti)
Project now in Beta; started in October 2020
Uses NLP to weight specific privacy policy clauses and assigns and generates a score
Other strategies: examines SDKs, past breaches, Firefox's TL;DR
Goal: show the worst offenders, promote good products (Jitsi, Signal), make
security accessible, vs. technical, dry or "scary"; "making privacy convenient"
Other key takeaways:
80% of consumers worried about security; 20% take minimum action
Still a lot of discrepancies between policies and intentions/practices
Communities can fill in the gaps by providing conversation around issues
GDPR and issues of portability/deletion should be considered bare minimum
DISCUSSION - stale PRs up for review
* (thank you to meejah (core dev) and Jean-Paul (core dev) for engaging on this)
Make PRs smaller, easier to review, easier to move on from
Smaller could mean thinking about how the feature could be split up into
smaller branches of minimally executable implementations
Scheduling - things get lost in the cracks; so circling back for sync appts
General organizational issue with dispersed attention/unclear priorities
Tuesday, May 4
_______________________________________________________________________
GOVERNANCE
* New Web Dev chosen for the next three months via the Internews/BASICS program
* Python 3 porting discussion
Ajibola (testing and release manager) to create Release Automation Plan
"Kitchen sink"-style Security Audit RfP to go out ASAP (to prevent blocking
implementation)
Create a list of distros and get into them
Decide if we want to drop any platforms
https://app.circleci.com/pipelines/github/tahoe-lafs/tahoe-lafs/2376/workflows/a3f39a12-ae32-4e85-8695-b9264340628b
Discussion: How do we express errors more productively?
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3695
* Reorganizing Trac Roadmap
https://tahoe-lafs.org/trac/tahoe-lafs/roadmap
For the time being, avoid due dates on milestones unless foreseeably clear
Lowercase anything "undecided" (list is sorted with ASCII)
For the future: Which items should take priority?
* Gitlab migration
Sajith (core dev) ready to hand over findings and next steps
* Update: mailing list: waiting on Brian Warner
APRIL
Friday, April 30
_______________________________________________________________________
BIKESHED
* SnakeDev meeting
Liz (Board), May-Lee (community manager), Jean-Paul (core dev) and Itamar
(contributor) met with Pete Fein from SnakeDevs to chat about Python 3 porting
progress and next steps.
* Documentation
There's no right way to do it
BUT we need a shared vision that is written down somewhere and will act as a
metric of progress
Tuesday, April 27
_______________________________________________________________________
GOVERNANCE
* Discussion on reaching consensus within the project
Decided against quorum right now because there are only 3 - 4 people to check in on
Small community allows for quicker moves
Rough consensus is basically working so we just need to keep improving
documentation and directing attention
Project Leader Role could help with consensus
Have some formalized agreements for more contentious areas
* Side discussion:
How do contributors enter and advance in the project?