diff --git a/i2p2www/meetings/logs/280.log b/i2p2www/meetings/logs/280.log new file mode 100644 index 00000000..bfffcd7d --- /dev/null +++ b/i2p2www/meetings/logs/280.log @@ -0,0 +1,100 @@ +20:00:00 0) Hi +20:00:00 1) 0.9.39 release status (zzz) +20:00:00 2) 0.9.40 dev status (zzz) +20:00:00 3) LS2 status (zzz) +20:00:00 4) Status scrum (zlatinb) +20:00:03 0) Hi +20:00:05 hi +20:00:14 1) 0.9.39 release status (zzz) +20:00:33 39 was released 11 days ago, approaching half of the net has updated +20:01:10 still awaiting mavencentral (str4d), our f-droid (meeh), official f-droid (nextloop) and debian (mhatta) +20:01:12 hi +20:01:26 any of you have ETA on when those items will be completed? +20:02:58 if it's as easy as https://f-droid.org/en/docs/Setup_an_F-Droid_App_Repo/ seem to be,later today. +20:03:31 you've already set it up, we've had it for years. It's just a question of putting the new apk in there, which you've done several times before +20:04:08 please harass str4d for maven central, and figure out how to get him out of the process ASAP. It's been a year we've been fighting to get control of this +20:04:08 no, I've hosted it, never uploaded +20:04:47 if you say so, but I remember you copying the apk over there before +20:05:04 I've written to him at twitter now for maven +20:05:36 lets try to get all this done within a week of release from now on. It's a bad look for us to take several weeks +20:05:47 I don't know what's going on with mhatta +20:06:09 we need to get better at this +20:06:44 the good news is, no real complaints about 39, other than it didn't fix 3rd party android apps... but they didn't work before either +20:07:01 meeh, what's your ETA for releasing a new android bote that works? +20:07:29 if you didn't see - it was discovered that it was just a reinstall which where the issue with shared uid +20:07:53 so, didn't fix => probably fixed +20:08:03 I thought that was only for a dev environment? +20:08:33 no clue as I'm not really familiar with either bote or android - monkey hitting the keyboard hoping for useful results +20:08:47 did you read the link he gave us? +20:09:02 zzz, https://developer.android.com/guide/topics/manifest/manifest-element#uid +20:09:02 >if this attribute is set to the same value for two or more apps, they will all share the same ID — provided that their certificate sets are identical +20:09:25 anyway, too much detail for the meeting, but we still have some research to do +20:09:55 ok, no ETA for bote. Maybe mhatta can help +20:10:06 or somebody +20:10:10 anything else on 1) ? +20:11:19 2) 0.9.40 dev status (zzz) +20:11:29 we're two weeks into a short 7 week cycle +20:11:51 zlatinb propped over a new, sophisticated streaming blocker/throttler today +20:12:00 I've checked in a new susidns import feature +20:12:22 and working hard on support for the new "b33" format that makes testing encrypted ls2 possible +20:12:37 we are using the .39 floodfills to test encrypted ls2 and it's working very well so far +20:13:18 there's a very very long list on the .40 roadmap, it's probably way too ambitious, but hopefully we;ll get to half of it +20:13:37 anybody else want to report on things they're doing for .40? +20:14:00 meta-LS backend, hopefully +20:14:13 but that’s not really tied to a router release so w/e +20:14:26 I have mostly got a working i2ptunnels.config.d folder +20:14:58 oh yeah, we need to talk about that at some point eyedeekay to see how it fits in with my half-done work from a year ago +20:15:12 will catch up with you on it at some point +20:15:25 on schedule with osx stuff, will have native shortcut for sharing file/directory with snark, auto-updater, new swift version, general code cleanup +20:15:35 meeh, eyedeekay, any status on the libsam stuff? +20:16:26 not more than that I need to catch up on the example, haven't had time to work with it lately +20:17:01 ok, anything else on 2) ? +20:17:41 I did put together a swig binding for the C++ library but I've only just learned swig, I'm not even sure it works yet. +20:18:28 3) ls2 status +20:18:37 we've had 34 meetings and still going strong +20:18:46 encrypted ls2 is working well +20:19:00 meta ls we're just starting to talk seriously about the backend +20:19:14 b33 is progressing +20:19:36 I've started working on the ratchet proposal again, starting some coding, but it's going to be a while +20:19:49 the blake proposal is stalled, lower priority for now +20:20:32 hopefully a lot of the pieces are in place and we can start using them for real, or by default +20:20:49 any questions on ls2, or anything else for 3) ? +20:21:29 does encrypted ls2 work with ed25519 -> ed25519 (regardless of hash used)? +20:21:53 or is red25519 required? +20:22:09 red is required +20:22:36 ok, thanks +20:22:47 because you need a defined way to blind +20:23:10 you can blind with ed25519 +20:23:14 in theory you could encrypt from/to anything but it wouldn't necessarily be secure, or defined +20:23:20 libsodium has it as an example in their docs +20:23:34 we support ed->red and red->red, thats it +20:23:58 we can discuss more over in #ls2 if you like after the meeting +20:24:08 anything else on 3) ? +20:24:12 right, didn't mean to distract +20:24:49 no problem, I asked for questions! +20:24:54 ok lets move on +20:25:00 4) status scrum (zlatinb) +20:25:03 go zlatinb +20:25:09 Hi. Quick parallel scrum: 1) what you’ve been doing since the last scrum 2) what do you plan on doing next month 3) any blockers or help needed +20:26:10 me: 1) lots of work with arctic on making the client side work well with his outproxies. New access filter (also requested by arctic) 2) meta-LS backend hopefully 3) no real blockers +20:27:16 me: 1) 39 release, ls2 including proposals 123, 144, 146, 148, 149; lots of bug fixes; susidns import; b33; reviewing other's code; support +20:28:14 2) prep for 40 release; lots of bug fixes; more ls2 work; keep trying to get signed windows installer to work; coding on ratchet proposal 144 and updating the docs +20:28:29 1) the osx launcher updates, started catching up on the #ls2 meetings & the libsam example, 2) android bote, osx launcher, new browser build, catching up on the #ls2 meetings 3) if anyone wants, I'll always welcome android help since I don't know the platform, but no spesific issues right now. +20:28:55 3) blockers: mhatta for various debian/tails things +20:28:56 EOT +20:31:29 anybody else for 4) ? +20:33:29 oh, sorry, EOT :) +20:33:31 EOT +20:33:31 eyedeekay, eche|on ? +20:33:31 sorry, just a second +20:33:31 yes? +20:33:31 it's scrum +20:33:31 nothing special so far +20:33:31 1) Since Sunday I've been working on splitting i2ptunnel configuration across multiple directories. 2) Application stuff including self-installing nginx, sshd/ssh, Webextensions/XUL extensions for Browser 3) The first is required to do the second +20:33:31 done services, no blockers, go on +20:33:31 EOT +20:33:31 ok, that’s everyone I think +20:33:52 ok, anything else for the meeting? +20:34:47 didn't think it was much of a turnout until eche|on and eyedeekay spoke up at the end! +20:35:00 last call before the baffer comes out +20:36:21 * zzz *bafs* the meeting closed diff --git a/i2p2www/meetings/logs/280.rst b/i2p2www/meetings/logs/280.rst new file mode 100644 index 00000000..13250306 --- /dev/null +++ b/i2p2www/meetings/logs/280.rst @@ -0,0 +1,14 @@ +I2P dev meeting, April 2, 2019 @ 20:00 UTC +========================================== + +Quick recap +----------- + +* **Present:** + +chisana, +echelon, +eyedeekay, +meeh, +zlatinb, +zzz