The next meeting is scheduled for Tuesday, January 15 @ 20:00 UTC (8:00PM)
{% filter escape %}
21:02:22 Alright, I'm going to go ahead and start the meeting.
21:02:29 0) Say hi
21:02:29 1) Feeds progress
21:02:29 2) JUnit hackfest summary
21:02:29 3) discussion of Syndie progress and where we are going with that
21:02:29 4) Suggestions for future hackfests
21:02:29 5) PR manager nomination
21:02:32 6) 0.9.4 progress
21:02:35 7) Website revamp
21:02:38 0) Say hi
21:02:38 Hi!
21:03:06 Hi!
21:03:49 hi :)
21:06:50 Anyone else?
21:08:58 The "hi"s have it.
21:09:05 1) Feeds progress
21:09:35 This will be short.
21:10:51 The feeds work is getting close, but I won't have it ready for 0.9.5 unfortunately - too many little things that need tidying up (user notifications etc.) as well as some not-so-little things (re-working the /home design, specifically how categories are presented to the user).
21:11:55 woah
21:11:58 I goth ere in time
21:11:58 And I'd rather push it to the next release than release it in its current state, since I want users to have a good first impression of it =)
21:12:05 I thought I'd missed you guys
21:12:15 dg: we started an hour late, FYI =P
21:12:15 dg: Nope, still here.
21:12:23 \o
21:13:38 So, any feedback, comments and suggestions for the feeds work would be greatly appreciated, but it's not urgently required before the 0.9.5 release.
21:14:37 Anyone have any points to raise on this topic before we move on?
21:14:53 No.
21:15:51 I don't, if zzz is here, he might?
21:17:23 We can come back to this at the end if necessary.
21:17:26 Next:
21:17:26 2) JUnit hackfest summary
21:17:57 Anyone else here who participated? zzz? topiltzin? KillYourTV?
21:18:55 yup, went well, the 4 of us all hacked away, and zab fought to the end until they all passed. First time in years, or maybe ever.
21:19:22 Kudos to zab for that.
21:20:04 And as a result we now have a Jenkins service run by kytv which will hopefully keep us in check ^_^
21:21:47 Next step there is to expand our code coverage (which Jenkins also monitors) with moar tests.
21:22:06 Not much else to say here, so:
21:22:09 kytv: you running sonar as well?
21:22:14 3) discussion of Syndie progress and where we are going with that
21:23:08 zzz and eche|on have started the Syndie hackfest - how bad is it looking? =P
21:23:39 going well, need more people to test, code, or make suggestions, but we have several dozen checkins in the last few days
21:24:01 suggest people try the latest version in mtn, they will find a lot of fixes
21:24:32 * str4d plans to pull the branch in the next day or so and have a look
21:24:32 but the point here is to recruit somebody to work on it steadily. It needs a lot of work
21:25:50 One of the points I recall from the TODO was a big-picture question: where are we heading/do we want to go with Syndie?
21:27:11 As in? Development wise? Popularity wise?
21:27:54 Both probably.
21:28:29 What needs to happen to reach its original goals? What were those goals? Do they still make sense?
21:29:13 This sort of thing would be good to outline on the Syndie bounty.
21:29:23 Popularity wise: get Syndie at least considered alongside "anonymous publishing" tools (I don't know if there even are any apart from Freenet?)
21:29:35 If we get to that point, we're doing well
21:29:49 (Since then people can look at the bounty and actually get a feel for what is required)
21:29:52 The goals are on the site, I believe. At least the use cases which sort of explained..
21:30:19 Useful links for reviewing the original goals:
21:30:22 http://www.i2p2.i2p/status-2006-09-12.html
21:30:22 http://www.i2p2.i2p/status-2006-10-03.html
21:30:29 Title: I2P Status Notes for 2006-09-12 - I2P (at www.i2p2.i2p)
21:30:33 Title: I2P Status Notes for 2006-10-03 - I2P (at www.i2p2.i2p)
21:31:36 dg: then it would be good to review the Syndie site and update it.
21:31:58 in the hackfest we're just fixing obvious problems. But hopefully the fest will attract new users and devs with ideas.
21:33:16 PR will help in that respect (which we will get to shortly).
21:34:21 Would it be a good idea to create a ticket for reviewing the Syndie docs/goals/bounty etc. to ensure they are current?
21:35:07 I'd say so
21:36:37 dg: could you do that? =)
21:37:05 * dg nods
21:37:08 And does anyone have anything else to add to this topic at present?
21:37:11 Thanks
21:39:35 no.
21:41:07 zzz: any other comments before we move on?
21:41:34 Aside from "Get hacking on Syndie NOW!!!!!!!!!!!!" ;P
21:43:41 Oh - why is syndie.i2p not up?
21:43:44 welterde?
21:43:51 (Or whoever runs it)
21:43:57 syndie.i2p2.de is up.
21:44:48 * KillYourTV guesses it was jrandom's.
21:45:31 Mmm, probably. In which case it would be worth setting up syndie.i2p2.i2p
21:45:58 (I recall seeing syndie.i2p in the I2P docs, so that needs changing at some point)
21:46:41 I don't think syndie has an eepsite...(yet)
21:47:16 It has a clearnet site...
21:48:00 hell...the most recently downloads are from 2007, other than my Debian packages or the plugin versions.
21:48:03 I don't think many (other than mosfet, darrob, echelon, and I) have cared about syndie for a long time (which is why there's the hackfest!!!!!!!11111onetyelven)
21:49:54 Okay, meeting will move on for now, we can revisit this if needed.
21:50:05 4) Suggestions for future hackfests
21:51:17 weltende: not familiar with sonar but i'll look into it. maybe I can handle that too...
21:51:32 So, what other hackfest ideas do we have?
21:56:17 me too!
21:56:36 So, what other hackfest ideas do we have?
21:58:32 Things that we have on the boiler at present:
21:58:35 I2P itself
21:58:35 Syndie
21:58:42 Android port
21:58:49 Website
21:59:54 Anything within those that might be deserving of a hackfest?
22:00:05 (Anything I've missed?)
22:01:14 str4d: Is the protocol spec something hackable?
22:07:25 orion: you mean the docs for it?
22:07:48 If the documentation is unclear then that is something worth considering.
22:08:03 Especially as we now have someone trying to use it to replicate a compatible I2P =)
22:08:34 str4d: I meant actually modifying the protocol.
22:08:45 orion: that, not so much.
22:08:53 zzz can elaborate more.
22:09:09 It depends on what protocol you are referring to though.
22:10:00 Upgrading crypto mainly.
22:10:00 Existing protocols (SSU, NTCP, I2CP, I2NP etc.) should ideally be backwards compatible, so a hackfest on them is probably counter-productive as any changes need to be carefully considered.
22:10:35 Ah yes. That is certainly something worth considering, especially before you get too far along with i2pcpp
22:10:54 Again, probably not hackfest-worthy, but it's something that we should probably dedicate some time to.
22:11:05 ok
22:11:23 btw http://trac.i2p2.i2p/ticket/840
22:11:27 Title: #840 (Review Syndie site) – I2P (at trac.i2p2.i2p)
22:11:47 * str4d tables the motion that the next meeting (or maybe the one after) be a crypto review meeting.
22:12:39 I agree
22:12:50 o/
22:13:10 /o
22:13:41 zzz? KillYourTV? welterde?
22:14:29 We'll want it to be a meeting that the people with the most knowledge of I2P's crypto can attend (so definitely zzz and zab)
22:16:32 str4d: ah.. crypto.. I'll be there.. when? *fetches calender*
22:17:02 Next week?
22:17:05 Same time?
22:17:48 welterde, I'm proposing either the next meeting or the one after (so Tues Jan 15 or 22, 20:00 UTC) but if another time suits you/zzz/zab/etc better...
22:22:57 * str4d has just emailed zab to ask about his availability.
22:24:08 s/just emailed zab/is attempting to email zab (and waiting on postman's SMTP to respond >_<)
22:26:17 * str4d waits for welterde to finish checking his calender
22:26:32 str4d: already noted ;)
22:27:04 Okay, so the currently-proposed time is Tues Jan 15, 20:00 UTC.
22:27:23 * str4d will make a zzz.i2p post about it
22:27:26 Next:
22:27:29 5) PR manager nomination
22:27:36 orion: you're up!
22:27:47 (Finally ^_^)
22:29:26 yay
22:32:30 What is the role of the PR manager position?
22:32:33 formally.
22:33:00 "PR manager: press contact, manages public relations and affairs"
22:33:10 (from /team)
22:34:51 So the person who gets I2P known, handles interview/article requests, organizes I2P appearances... that sort of thing, I'd imaging.
22:34:54 I can be a press contact. I like speaking in front of public audiences.
22:34:57 imagine*
22:35:39 It needs to be someone who can IRL.
22:35:50 I can meet press/media IRL.
22:35:53 Also, general i2p public face for things we need would be helpful..
22:35:53 I don't mind that.
22:36:03 (GSoC for one, if Google demand)
22:36:17 dg: good point there.
22:36:48 I know that mentors don't have to be public, but Google does require a single person to be the main point of contact.
22:36:48 Interviews, all that stuff sounds good. The one thing I am not good at though is media stuff (making flyers, etc)
22:37:36 I don't mind being a main point of contact -- organizing I2P appearances I can do, so long as you guys tell me about them. Hell, if they're in the area I can go IRL.
22:37:39 orion: making flyers etc. isn't technically part of the job - it would be to organize flyers etc. getting made (which themselves would be done by a designer)
22:37:58 Ahh
22:38:13 eche already has a competition running to get some leaflets, banners etc. designed.
22:38:20 Ok.
22:38:23 So e.g. the PR manager could promote that competition.
22:38:30 (To get a wider variety of entries)
22:38:55 For me, it's showing people that i2p is more than a few people hiding with no face at all
22:39:01 However you wish to do that
22:39:08 Talks, interviews, whatever, it's all good
22:39:15 Right.
22:39:15 Something I've wondered - what about posting a/the competition on a freelance design website? To get more exposure.
22:40:06 If people reach out to me, I have no problem talking to them.
22:40:52 I can even show up to events if they are in the area.
22:41:03 (New Hampshire)
22:41:06 Mind if I ask the area?
22:41:06 -
22:41:07 haha
22:41:39 There is a train that goes directly to Boston though.
22:42:14 One event that would be good to get people to is http://wiki.openitp.org/events:techno-activism_3rd_mondays
22:42:22 Title: events:techno-activism_3rd_mondays [OpenITP Wiki] (at wiki.openitp.org)
22:44:58 orion: FWIW, as PR manager, the page/subpages on the website (revamp) http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/about/media would basically be under your jurisdiction.
22:45:05 Title: Presentations on I2P - I2P (at vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p)
22:45:22 I will accept the PR role, but I am a poor college kid.
22:45:49 I can't afford to go to too many events.
22:46:16 orion: talk to eche|on - there's always a possibility of funding.
22:46:27 Ok.
22:46:38 And as a PR manager, you may end up drumming up additional funding anyway =D
22:47:13 I accept the position, and I will relinquish the position if I feel I am not up to it.
22:47:41 You can't be expected to detract from your own RL work of course, but we do appreciate your assistance. And you won't be acting alone.
22:48:15 That sounds great. assistance would definitely be appreciated.
22:50:40 * str4d updates the website
22:52:03 And done! Welcome (officially) to the team orion =D
22:52:18 Yay!
22:52:29 (Though if being on the /team page makes it official, then I'm not technically an official team member =P)
22:53:40 Okay, moving on to the last couple of topics:
22:53:43 6) 0.9.4 progress
22:53:43 IRL is evil.
22:53:43 How are we looking at present? We are over the halfway mark for the usual 6-week release period.
22:54:06 s/0.9.4 progress/0.9.5 progress/
22:54:09 str4d meant: 6) 0.9.5 progress
22:55:49 As outlined in topic 1) the feeds work won't be ready for 0.9.5.
22:58:32 I'm not sure if this is an inappropriate time to ask, but is the Android i2p still in development? Or is that not an 'official' thing?
22:59:16 primal: yes it is. zzz has an old stable version (0.9.1) but sponge has been working on the latest stuff.
22:59:23 Current release: 0.9.1-0_b1-API8 http://zzz.i2p/topics/949 | Current dev build: 0.9.3-5_b2-API8 http://sponge.i2p/ (scan/click QR code)
22:59:38 Title: SPONGE (at sponge.i2p)
22:59:58 sponge is also working on getting the normal Oracle JVM working on Android though, so stock I2P could potentially be used.
23:00:27 str4d: hmm, I ought to get ahold of him, I'd be interested in working on this.
23:01:12 primal: talk to sponge, and see #i2p-android-dev
23:01:12 And, yay!
23:02:01 So, no feedback on 0.9.5 progress?
23:04:59 If not, then on to the last defined topic:
23:04:59 7) Website revamp
23:05:03 http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/
23:05:14 Ticket #807 outlines my progress.
23:05:26 http://trac.i2p2.i2p/ticket/807 - (accepted enhancement) - Revamp of website
23:05:30 Just slipping this in, we're doing better thanks to the bug fix in 0.9.4 for network capacity. http://stats.i2p/cgi-bin/avg.cgi?a=tunnel.buildSuccess.60m&s=93&u=q
23:05:38 The estimated router count has gone up which implies better connectivity to zzz's router?
23:06:01 If we look at 6 months though, we're still not doing as good
23:06:12 anyway, sorry to hijack. :p
23:06:19 dg: yes, good that you mentioned that
23:06:26 The new site is far far superior
23:07:21 First point: I have changed the content of the left column (as per ticket #792 ) - thoughts?
23:07:24 http://trac.i2p2.i2p/ticket/792 - (assigned task) - Replace left column content
23:09:00 Second point - at the bottom of #807 I have suggested some URL changes, which I would like feedback on. Another one is /lang/about/media vs /lang/media ?
23:10:39 ugh
23:11:03 str4d: Is http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/ supposed to show the new design?
23:11:10 Title: I2P Anonymous Network (at vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p)
23:11:10 Third point: http://trac.i2p2.i2p/ticket/807#comment:12 lists several content-related issues that need resolving, but I'm not that great at writing content. Assistance here would be greatly appreciated.
23:11:13 errr nvm. Had a complaint about links going to clearnet sites and being unmarked, then I realised this is to be the i2p clearnet homepage :P
23:11:16 Title: #807 (Revamp of website) – I2P (at trac.i2p2.i2p)
23:11:20 orion: it shows one of the new designs.
23:11:43 But the design itself is not finalized yet.
23:11:46 Ahh. How do you alternate between them?
23:12:01 orion: look in the footer
23:12:13 str4d: I can help with writing, it's what I do. What needs fixing?
23:12:20 Firefox doesn't like the footer.
23:12:20 "Duck" is the default, "danimoth" is another proposal I found, the others are from the old site.
23:12:30 primal: see comment 12 as above.
23:12:37 orion: I have no issues with FF17
23:12:40 str4d: indeed, checking now
23:13:11 primal: re: clearnet links, this site will be the I2P-internal site as well.
23:13:23 So your point about marking clearnet links is a good one - examples?
23:13:54 * str4d already has added logic so that I2P-internal sites get rewritten when viewed on the clearnet (to either their clearnet URLs if known, or to an inproxy).
23:14:25 http://i.imgur.com/PwDF8.png
23:14:29 Why is Research under Volunteer instead of About?
23:14:33 It might just require adding a CSS class to any external links so they can be specifically outlined or something.
23:14:52 I went and looked under 'About' first, and would if I was someone wanting to see 'hey, has this been TESTED? Can I trust it?'
23:15:30 primal: because I'm intending that page to be more aimed at researchers wanting to test I2P, but that is a good point.
23:15:37 Ahh okay
23:15:55 Stuff under the "About" menu (to me) is about existing stuff, rather than potential developments.
23:16:06 So maybe the Papers link should be moved back into the about menu.
23:16:37 * str4d already split off the papers page from the presentations, tutoruals etc (which is now the media page)
23:16:52 tutorial
23:16:55 *
23:17:20 orion: oh - that's because the old site doesn't have a footer.
23:17:23 I'd agree. A fellow at my local hackerspace who works on Tor actually asked me for that info once and I didn't know where to point him
23:17:30 having it clearly available would be good
23:18:05 And I'm not a designer, so I haven't been playing with the old CSS much - I just got it mostly-migrated over to show how the new structure and layout fits into the old clothing.
23:18:20 * str4d moves the Papers link now.
23:18:54 str4d (see image)
23:19:56 orion: yes, I looked at it - that's the theme from the current website, and I didn't add footer CSS to it. The two more modern themes (duck's and danimoth's) have footer CSS.
23:21:14 str4d: I would put the academic papers under 'Presentations, Tutorials, and Articles'
23:21:34 primal: under it as in position-wise, or as a sub-menu?
23:21:37 Unless you want to emphasise them highly themselves
23:21:52 * str4d split off Papers from that page, and isn't about to merge them back =P
23:22:15 Hmm...
23:22:26 * str4d put the link under "Comparisons" for now.
23:22:45 above them position wise. 'Academic Papers and Peer Review' perhaps
23:23:59 the content is quite mixed there already
23:24:33 christoph: I'd prefer to amalgamate the content, but str4d said he isn't about to merge stuff ;)
23:25:00 I'm just saying, anyone who is *seriously* looking at I2P for security reasons will want to focus on the academic / peer review.
23:25:11 primal: my point is, it's merged on the current site - I split it off because I felt that academic papers deserved their own page with their own layout.
23:25:21 hm it's actually mostly fine now, /me seems to remember lots of different stuff mixed
23:25:31