20:08:14 so hi all 20:08:33 we didn't really talk much about the agenda but we have some big stuff to discuss anyhow so no big deal 20:08:55 first topic is the new website design and the blockers for getting it live 20:08:58 so i'll hand over to str4d 20:09:09 * dg passes metaphorical spotlight to str4d 20:09:20 Hi! 20:09:27 20:10:07 Right, well I haven't had as much time over the last week to work on it, but the site *can* go live if desired. 20:10:26 The blockers (that I see) are tagging the documentation for translations. 20:10:37 Oh, and fixing URLs - that actually is a blocker. 20:10:48 (I've been doing them at the same time). 20:11:45 I've done the rest of the site - we just need to go through every page of the documentation and repeat what I've been doing: add translation tags to each paragraph/heading/list item/whatever, and check/correct the site-internal URLs. 20:12:29 The other bit that I consider a blocker is getting the old translations migrated to the new format, i.e. going through the old faq_lang.html etc. pages and copying their text into the .po files as appropriate. 20:12:55 Translation tagging IMHO isn't a true blocker but something we need to finish soon, I don't know how you guys feel about going live without translations fully done 20:13:14 (I've done 1.2 pages for de and 1 page for es as an example, but it really needs to be someone who understands the language, so that the copy-paste can be verified) 20:14:00 (since there is no guarantee that the two individual pages have the same content) 20:15:52 Design-wise, I'm starting to be more inclined to just leave the modified duck's theme there; it's had praise from quite a few people, including a designer. I'm personally still not happy with it (e.g. I find it a bit hard to read the long text passages in the documentation), but I wouldn't call it a blocker. 20:16:09 I like it more or less 20:16:40 Oh - one bad thing currently is that the mobile CSS I added seems to not work on mobiles *derp* 20:16:52 (Though it works quite nicely on a narrowed desktop browser) 20:19:26 That's really about it for the site, as far as I can think of - it's functioning nicely, and most of the groundwork is in place. 20:19:41 I'll go check out for any broken links later 20:19:52 I found some previously 20:20:17 dg: my test site is running the latest version, so you can check there. 20:20:32 The only broken links should be in /lang/doc/* 20:20:35 let me dig up the ticket 20:20:38 Every other page should be fine. 20:20:45 It's ticket #807 20:20:52 saved me some time :) 20:20:59 http://trac.i2p2.i2p/ticket/807 - (accepted enhancement) - Revamp of website 20:20:59 want to revisit this next week then? 20:23:38 Found one. 20:23:46 http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/docs/how/networkcomparisons from http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/docs/how/garlic-routing 20:23:49 Oh, and /lang/misc/* hasn't been looked at either. 20:23:56 Title: Garlic Routing - I2P (at vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p) 20:24:06 Should be /en/comparison 20:24:12 sorry for pasting whole thing, won't do it again 20:24:15 eyerape 20:24:22 dg: yep, that is a side-effect of my hypenating all the double-worded pages. 20:24:30 Oh, that too. 20:25:09 /en/docs/how/garlic-routing has /en/docs/how/elgamalaes, should be /en/docs/how/elgamal-aes 20:25:16 i'll put them all into the ticket later 20:25:23 <+dg> want to revisit this next week then? 20:26:01 I'm happy to. Anyone else want to comment? ^_^ 20:27:18 http://meeh.i2p/viewmtn/viewmtn.py/ 20:27:49 internal server error on http://meeh.i2p/viewmtn/viewmtn.py/branch/changes/i2p.i2p 20:28:45 yepp 20:28:48 working on it 20:28:55 I'll take it as a no, anyway 20:28:58 so onto .. crypto? 20:29:18 One last question then: given the apparent level of apathy from people in here regarding copying over the old translations, would it be a better idea to just abandon them and upload the blank .po to Transifex? 20:29:44 Isn't Transifex reasonably active? 20:29:51 The .po file will end up on Transifex anyway; I had just planned on it containing the old translations as a bit of a head start. 20:30:05 I'd say yes 20:30:48 Any other votes? 20:32:38 If we go with that, then I'll try and tag as many more pages as I have time for, and then I'll create .po files for the current website languages. Then someone with Transifex access can create an i2p.www subprojcet and upload them (KillYourTV?) 20:32:50 * psi reads scrollback 20:33:34 votes on a hackfest? 20:35:05 * psi reads more scrollback 20:39:01 ... 20:39:04 * str4d doesn't like assuming, but assumes that no one has objections to that line of action. 20:39:04 too quiet >.> 20:39:04 In that case, the old translations will be discarded from i2p.www.revamp (or maybe just left in the branch for now - if a translator really wants to they can find them for reference). 20:39:04 no formed opinion 20:39:14 hi, i heard k0e touches himself whilst watching granny pr0n 20:39:21 uh? 20:39:32 >.> #i2p-chat 20:40:45 Right, that's it from me on the website. 20:49:59 well.. 20:50:11 IDK if wait(str4d) 20:51:33 AFK, back soon 21:03:55 zzz, did you see the update of http://trac.i2p2.de/wiki/Crypto/CurrentSpecs ? 21:03:58 Title: Crypto/CurrentSpecs – I2P (at trac.i2p2.de) 21:07:36 yeah you guys are doing a great job 21:08:13 do you think we are using asymmetric ciphers where they aren't needed? 21:08:23 and could be replaced by symmetric alternatives? 21:08:38 I doubt we're using anything where it isn't needed 21:09:04 good 21:09:15 the web page crypto section needs the symm/asymm crypto added ofc, right now it's only sigs 21:09:46 yeah. But one issue at a time 21:09:53 I think the signs are the most vulnerable anyway 21:10:07 right. just as a one-liner placeholder is all I meant 21:20:19 zzz, sud signing should be fairly do-able as far as implementation and not having a flag day goes? 21:20:41 do-able as in possibly to change cipher for. 21:23:58 back 21:26:53 i guess. we did su2 w/o incident, so why not su3, su4, ... 21:28:38 but before we should decide what cipher is the most viable 21:36:25 okay 21:36:33 since str4d_afk is gone.. uh 21:36:51 zzz, hottuna, do you want to discuss anything further or should we close the meeting? It seems like nobody else is around 21:40:29 a'ight 21:40:35 * dg bafs the meeting closed 21:41:11 thanks dg :) 21:41:55 str4d went MIA 21:45:03 anyway, np 23:00:32 Sorry, connection went down and then I was AFK