meeting 261
This commit is contained in:
92
i2p2www/meetings/logs/261.log
Normal file
92
i2p2www/meetings/logs/261.log
Normal file
@ -0,0 +1,92 @@
|
||||
20:00:00 <zzz> 0) Hi
|
||||
20:00:00 <zzz> 1) 0.9.31/.32 update (zzz)
|
||||
20:00:00 <zzz> 2) 34C3 planning (zzz/echelon)
|
||||
20:00:03 <zzz> 0) Hi
|
||||
20:00:06 <zzz> Hi
|
||||
20:00:27 <backup> Hi zzz
|
||||
20:00:31 <zzz> 1) 0.9.31/.32 update (zzz)
|
||||
20:00:45 <str4d> Hi
|
||||
20:00:49 <zzz> OK, we pushed the release out a week, new checkin deadline this friday
|
||||
20:00:53 <R4SAS> Hi
|
||||
20:00:56 <manas> Hello
|
||||
20:01:18 <zzz> we'll take a couple extra days for review, since it's so big, with a review deadline of next tuesday, and a build late tuesday or early wednesday
|
||||
20:01:47 <zzz> that puts 0.9.32 release in early to mid September, more or less as planned
|
||||
20:02:04 <zzz> everybody please test the latest dev build
|
||||
20:02:11 <zzz> anything else on 1) ?
|
||||
20:02:33 <backup> it is possible that you push the guide on zzz on how to use build dev's
|
||||
20:02:55 <manas> 'ant updater' generates i2pupdate.zip
|
||||
20:02:55 <zzz> there should be instructions on bobthebuilder.i2p maybe?
|
||||
20:03:14 <orignal_> hi
|
||||
20:03:16 <zzz> search around on zzz.i2p for how to subscribe to auto dev build updates
|
||||
20:03:29 <str4d> There's probably already a guide there, but definitely we need to improve visibility of these kinds of things. It's part of my brief for the next phase of the website udpate
|
||||
20:03:38 <zzz> or as manas says, ant updater, copy zip over, restart. done and done.
|
||||
20:03:41 <backup> I mean something ready like KYTV did ?
|
||||
20:03:41 <zzz> anything else on 1) ?
|
||||
20:03:49 <backup> would attract more testers...
|
||||
20:04:06 <str4d> New website frontpage is up
|
||||
20:04:10 <str4d> http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/
|
||||
20:04:23 <zzz> let's stay on topic. anything else on 1) ?
|
||||
20:04:34 <str4d> zzz, I *am* on topix
|
||||
20:04:58 <str4d> I'd like to have this live around release time ideally
|
||||
20:05:15 <str4d> But the blocker is working on the copy (front page text)
|
||||
20:05:18 <manas> Loading
|
||||
20:05:30 <zzz> 2) 34C3 planning (zzz/echelon)
|
||||
20:05:38 <manas> looks nice so far
|
||||
20:05:50 <str4d> Not going to force it though, would prefer it be right than on-time
|
||||
20:05:59 <zzz> ok, I don't want to do much discussion about CCC now, but rather to schedule the budget meeting for either august or september
|
||||
20:06:25 <zzz> is there anybody that needs to know how much the reimbursement will be before buying plane tickets? when are people buying tickets?
|
||||
20:06:27 <str4d> Have ticket sale times been announced yet?
|
||||
20:06:48 <zzz> no, and realistically, you'll have to buy plane tickets months before you know if you have a conference ticket, sadly
|
||||
20:06:57 <manas> I'm tracking a couple of tickets, have not finalized yet
|
||||
20:07:12 <manas> What will the process for ticket procurement be like?
|
||||
20:07:19 <zzz> I'd expect at least as much reimbursement as last year, maybe more, due to BTC
|
||||
20:07:25 <manas> eche|off kindly sent me at ticket last year
|
||||
20:07:30 <manas> *a
|
||||
20:07:34 <zzz> let's not discuss the conference ticket process now. that will be much later.
|
||||
20:07:43 <str4d> I'll be flying from the UK, so will be significantly cheaper for me to reach it
|
||||
20:07:44 <manas> okay :)
|
||||
20:07:48 <zzz> I just want to set a budget meeting. August or September?
|
||||
20:07:59 <manas> str4d: and a much shorter flight :D
|
||||
20:08:09 <manas> When are ticket sales open?
|
||||
20:08:16 <zzz> let's not discuss the conference ticket process now. that will be much later.
|
||||
20:08:33 <str4d> August is probably safer
|
||||
20:08:40 <manas> either month works with me
|
||||
20:08:49 <zzz> most of the sales were in november iirc? you'll want to get plane tix much earlier. LEJ looks harder to get to than MUC
|
||||
20:08:49 <str4d> Perhaps with some overflow built in?
|
||||
20:09:05 <zzz> ok I'll put it on the agenda for next month's meeting
|
||||
20:09:06 <manas> there are a couple of flights from MUC
|
||||
20:09:07 <manas> to LEJ
|
||||
20:09:14 <manas> if someone is flying in to MUC
|
||||
20:09:19 <manas> okay
|
||||
20:09:19 <zzz> anything else on 2) ?
|
||||
20:10:14 <zzz> anything else for today's meeting?
|
||||
20:10:56 <str4d> I've been discussing more performance stuff in #i2p-science with various people
|
||||
20:11:05 <manas> new frontpage loaded, looks really nice str4d
|
||||
20:11:12 <str4d> Make sure to lurk if you are interested and haven't already
|
||||
20:11:22 <manas> I have been testing the UI, it looks good as well
|
||||
20:11:43 <zzz> good stuff
|
||||
20:11:45 <str4d> I've also pushed an update to Prop140 in light of the confusion it caused, starting to clarify that it is about the balancer protocol
|
||||
20:11:58 <str4d> (so basically OnionBalance but compartmentalised)
|
||||
20:12:07 <R4SAS> zzz, q. about bug in jks2pem
|
||||
20:12:29 <zzz> ok, hard to restart that discussion after 6 weeks, but I'll try to get my head back in it
|
||||
20:12:30 <str4d> Not complete, the protocol etc. still needs designing - see my comments on the zzz.i2p thread
|
||||
20:12:35 <zzz> R4SAS, after the meeting please
|
||||
20:12:44 <zzz> anything else for today's meeting?
|
||||
20:12:44 <R4SAS> kk
|
||||
20:12:50 <str4d> I also had a few comments on NTCP 2 from David Fifield, one of the PT people
|
||||
20:13:36 <zzz> any progress on proposals is good, even if it's only every 6 months
|
||||
20:13:44 <str4d> I updated the proposal with them, and will shortly post it for comment to the traffic-obf Google Group (which he said would be interested in this kind of thing)
|
||||
20:13:53 <zzz> anything else for today's meeting? /me grabs the baffer
|
||||
20:14:11 <str4d> One last thing
|
||||
20:14:34 <str4d> F3real has been working away on differential privacy for statistics
|
||||
20:14:49 <str4d> He sent me today his current patch file, which I will look at later this week
|
||||
20:15:14 <str4d> (tl;dr binning and additive noise for stats, to make it safer to publish them without compromising privacy)
|
||||
20:15:42 <zzz> tough topic, lots of room for research and experiments. hopefully lazygravy can get involved
|
||||
20:15:54 <zzz> anything else for today's meeting?
|
||||
20:15:59 <str4d> Early stages, but AFAIK they are our first new contributor coming in via Summer Dev! Woo!
|
||||
20:16:43 <str4d> I did some research a week or two ago around Apache Kafka too, looks like it would be a useful platform for stats collection
|
||||
20:17:06 <str4d> (suggested by lazygravy, seems several people I know through infosec companies use it)
|
||||
20:17:27 <zzz> last call for today's meeting
|
||||
20:17:28 <str4d> Will kick that around at some stage (probably after PETS - I still have to write my talk for that)
|
||||
20:17:40 <str4d> Okay, okay, I'm done :P
|
||||
20:18:29 * zzz **bafs** the meeting closed
|
14
i2p2www/meetings/logs/261.rst
Normal file
14
i2p2www/meetings/logs/261.rst
Normal file
@ -0,0 +1,14 @@
|
||||
I2P dev meeting, July 4, 2017 @ 20:00 UTC
|
||||
=========================================
|
||||
|
||||
Quick recap
|
||||
-----------
|
||||
|
||||
* **Present:**
|
||||
|
||||
backup,
|
||||
manas,
|
||||
orignal,
|
||||
R4SAS,
|
||||
str4d,
|
||||
zzz
|
Reference in New Issue
Block a user