diff --git a/design/bg-sidebar.svg b/design/bg-sidebar.svg
new file mode 100644
index 00000000..58783e0e
--- /dev/null
+++ b/design/bg-sidebar.svg
@@ -0,0 +1,292 @@
+
+
+
+
diff --git a/i2p2www/__init__.py b/i2p2www/__init__.py
index 4a830ce0..af3d9440 100644
--- a/i2p2www/__init__.py
+++ b/i2p2www/__init__.py
@@ -22,7 +22,7 @@ except ImportError:
###########
# Constants
-CURRENT_I2P_VERSION = '0.9.23'
+CURRENT_I2P_VERSION = '0.9.24'
CANONICAL_DOMAIN = 'geti2p.net'
diff --git a/i2p2www/blog/2016/01/23/32C3.rst b/i2p2www/blog/2016/01/23/32C3.rst
new file mode 100644
index 00000000..eca5c13e
--- /dev/null
+++ b/i2p2www/blog/2016/01/23/32C3.rst
@@ -0,0 +1,129 @@
+{% trans -%}
+=========
+CCC Recap
+=========
+{%- endtrans %}
+.. meta::
+ :author: lazygravy
+ :date: 2016-01-23
+ :category: ccc
+ :excerpt: {% trans %}CCC!{% endtrans %}
+
+{% trans -%}
+Attending: Sadie, Colin, lazygravy, zzz, hottuna, kytv, cacapo, and eche|on.
+{%- endtrans %}
+
+{% trans -%}
+Start
+=====
+The project has had another successful year at CCC.
+We would like to thank the volunteers at `32C3`_ for all of their help in organizing this event and for being accommodating hosts for us.
+Many I2P contributors were able to attend this year's Congress due to many of the generous donations from supporters like you to the project.
+If you would like to fund I2P, please see `our donation page`_ for more information.
+{%- endtrans %}
+
+.. _{% trans %}`32C3`{% endtrans %}: https://events.ccc.de/congress/2015/wiki/Static:Main_Page
+.. _{% trans %}`our donation page`{% endtrans %}: {{ site_url() }}get-involved/donate
+
+{% trans -%}
+Just like previous years we were located in Noisy Square, located near the EFF's table.
+This proved to be an ideal spot for us as our table was almost always busy with current and new users who were interested in I2P, many of whom we wouldn't have otherwise had the ability to talk to.
+{%- endtrans %}
+
+{#
+
+{% trans -%}
+The Year of Usability
+=====================
+{%- endtrans %}
+
+{% trans -%}
+A common discussion point at the table was the usability of the router console, and how it can be better improved for all I2P users, with a specific focus on new users.
+Many (both developers and users) have mentioned to us that their best experience with I2P was through `Vuze`_ and the `I2PBote Android app`_.
+Currently there are vague discussions of redoing the current router console since it is difficult for many users to understand.
+{%- endtrans %}
+
+.. _{% trans %}`Vuze`{% endtrans %}: https://wiki.vuze.com/w/I2PHelper_HowTo
+.. _{% trans %}`I2PBote Android app`{% endtrans %}: https://play.google.com/store/apps/details?id=i2p.bote.android
+
+{% trans -%}
+{%- endtrans %}
+
+{% trans -%}
+We need your feedback!
+Even if you don't use I2P often, we want to know what you think.
+Please `get in touch with us`_ and let us know what improvements or ideas you have!
+{%- endtrans %}
+
+.. _{% trans %}`get in touch with us`{% endtrans %}: {{ site_url() }}contact
+
+#}
+
+{% trans -%}
+Reseed Status
+=============
+{%- endtrans %}
+
+{% trans -%}
+Let's get more reseeds!
+{%- endtrans %}
+
+{% trans -%}
+If you don't know what a reseed server is, it is first the connection new routers use to find peers.
+There was a lot of discussion around the current status of the reseed network right now.
+As always, more reseed operators are needed!
+If you would like to strengthen the reseed infrastructure, (or if you're talented with Go) email `backup -at- i2pmail.org`_.
+{%- endtrans %}
+
+.. _{% trans %}`backup -at- i2pmail.org`{% endtrans %}: mailto:backup -at- i2pmail.org?subject=How%20Do%20I%20Run%20a%20Reseed%20Node?
+
+{% trans -%}
+Sybil Detection (beta)
+======================
+{%- endtrans %}
+
+{% trans -%}
+Due to the decentralized nature of I2P detecting Sybil attacks is not as straight forward as on other networks (i.e. Tor).
+To mitigate this zzz has been working on a new router-based Sybil detection tool.
+To be brief, the tool runs in the router, and collects information on floodfills your router is currently aware of.
+Currently the tool is mainly collecting a baseline and does not act on any of the information it is collecting.
+Expect to see a writeup on this more as 0.9.25 or 0.9.26 approaches, as it is still in active development
+{%- endtrans %}
+
+{% trans -%}
+Development Meeting
+===================
+{%- endtrans %}
+
+{% trans -%}
+On the 30th we held an in person `meeting`_ at our table.
+The meeting focused on organizationally preparing for more project management, and public relations (both from Sadie).
+{%- endtrans %}
+
+.. _{% trans %}`meeting`{% endtrans %}: {{ site_url() }}meetings/241
+
+{% trans -%}
+We discussed how much of the work done on I2P is lost in the commits and there is not much to see for our users.
+To remedy this lazygravy plans on preparing a series of posts explaining some technical topics in I2P.
+The initial ideas that we discussed writing posts on are what encrypted lease sets are, why different tunnel types are needed, and some observations seen in `I2Spy`_.
+But these are just the start and we would like to hear feedback on topics we should write about!
+{%- endtrans %}
+
+.. _{% trans %}`i2spy`{% endtrans %}: https://github.com/chris-barry/i2spy
+
+{% trans -%}
+Meeting (Future)
+================
+{%- endtrans %}
+
+{% trans -%}
+There will be a `another meeting`_ on 2 Feburary 2016 to discuss:
+{%- endtrans %}
+
+- {% trans -%}Review of assigned tasks from 30 December meeting{% endtrans %}
+- {% trans -%}Project meeting plan for 2016{% endtrans %}
+- {% trans -%}GMP 6 readiness{% endtrans %}
+- {% trans -%}A proposal for a code of conduct{% endtrans %}
+
+.. _{% trans %}`another meeting`{% endtrans %}: http://{{ i2pconv('zzz.i2p') }}/topics/2014-meeting-tues-feb-2-8-pm-utc
+
diff --git a/i2p2www/blog/2016/01/27/0.9.24-Release.rst b/i2p2www/blog/2016/01/27/0.9.24-Release.rst
new file mode 100644
index 00000000..e12598e4
--- /dev/null
+++ b/i2p2www/blog/2016/01/27/0.9.24-Release.rst
@@ -0,0 +1,113 @@
+{% trans -%}
+==============
+0.9.24 Release
+==============
+{%- endtrans %}
+.. meta::
+ :author: zzz
+ :date: 2016-01-27
+ :category: release
+ :excerpt: {% trans %}0.9.24 contains a variety of bug fixes and performance enhancements{% endtrans %}
+
+{% trans -%}
+Update details
+==============
+{%- endtrans %}
+
+{% trans -%}
+0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
+Note that this release is the first to require Java 7.
+Please update to Java 7 or 8 as soon as possible.
+Your router will not automatically update if you are using Java 6.
+{%- endtrans %}
+
+{% trans -%}
+To prevent the problems caused by the ancient commons-logging library, we have removed it.
+This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
+The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
+For more details, see `this post`_.
+{%- endtrans %}
+
+.. _{% trans %}`this post`{% endtrans %}: http://bote.i2p/news/0.4.3
+
+{% trans -%}
+We had a great `32C3 Congress`_ and are making good progress on our 2016 project plans.
+Echelon gave a talk on I2P's history and current status, and his slides are `available here`_ (pdf).
+Str4d attended `Real World Crypto`_ and gave a talk on our crypto migration, his slides are `here`_ (pdf).
+{%- endtrans %}
+
+.. _{% trans %}`32C3 Congress`{% endtrans %}: {{ site_url() }}blog/post/2016/01/23/32C3
+
+.. _{% trans %}`available here`{% endtrans %}: https://download.i2p2.de/media/ccc/2015/I2P_Still_alive.pdf
+
+.. _{% trans %}`Real World Crypto`{% endtrans %}: http://www.realworldcrypto.com/rwc2016/program
+
+.. _{% trans %}`here`{% endtrans %}: https://download.i2p2.de/media/rwc/2016/rwc2016-str4d-slides.pdf
+
+{% trans -%}
+As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.
+{%- endtrans %}
+
+
+**{% trans %}RELEASE DETAILS{% endtrans %}**
+
+**{% trans %}Changes{% endtrans %}**
+
+- {% trans %}Java 7 now required{% endtrans %}
+- {% trans %}SAM 3.2, with several new advanced features, command parser improvements, and lots of bug fixes{% endtrans %}
+- {% trans %}Router Family{% endtrans %}
+- {% trans %}Commons logging removed{% endtrans %}
+
+
+**{% trans %}Bug Fixes{% endtrans %}**
+
+- {% trans %}Fix HTML escaping in the console plugin table{% endtrans %}
+- {% trans %}Fix rare deadlocks in the router{% endtrans %}
+- {% trans %}Fix the tunnel build Bloom filter{% endtrans %}
+- {% trans %}Don't remove tunnel on next-hop failure indication from transport, it isn't reliable{% endtrans %}
+- {% trans %}Fix formatting in summary bar to prevent overflow{% endtrans %}
+- {% trans %}Fix console links in i2ptunnel error pages when on nonstandard host/port{% endtrans %}
+- {% trans %}Don't query floodfills whose version is too old to support encrypted replies{% endtrans %}
+- {% trans %}Reduce out-of-order delivery in SSU{% endtrans %}
+- {% trans %}Fix a rare NPE in the tunnel build handler{% endtrans %}
+
+
+**{% trans %}Other{% endtrans %}**
+
+- {% trans %}Listen for Windows Service shutdown events to shutdown cleanly{% endtrans %}
+- {% trans %}Fix some IPv6 issues on Windows{% endtrans %}
+- {% trans %}Change Jetty request logging from b64 to b32{% endtrans %}
+- {% trans %}New 'family' indication in netdb, don't use two of the same family in a tunnel{% endtrans %}
+- {% trans %}New overview picture in SusiDNS{% endtrans %}
+- {% trans %}Close connection faster if it's for a rejected tunnel request{% endtrans %}
+- {% trans %}Use SSU extended options field for session request message{% endtrans %}
+- {% trans %}Request introduction in the SSU extended options{% endtrans %}
+- {% trans %}Don't offer to introduce unless requested, to introduce only those that need it{% endtrans %}
+- {% trans %}Experimental Sybil analysis tool, requires routerconsole.advanced=true{% endtrans %}
+- {% trans %}Persist some profile netdb stats that weren't being saved{% endtrans %}
+- {% trans %}Memory reduction and other efficiency improvements throughout{% endtrans %}
+- {% trans %}Increase several limits in i2psnark{% endtrans %}
+- {% trans %}New streaming unit tests{% endtrans %}
+- {% trans %}Fix some SSU stats on /peers to be consistent with NTCP{% endtrans %}
+- {% trans %}Change default sig type for new i2ptunnels to Ed25519{% endtrans %}
+- {% trans %}Increase router rekey probability at startup again{% endtrans %}
+- {% trans %}New Chinese (Taiwan) translation{% endtrans %}
+- {% trans %}Translation updates{% endtrans %}
+- {% trans %}Update GeoIP data (new installs and PPA only){% endtrans %}
+
+
+`Full list of fixed bugs`_
+
+.. _{% trans %}`Full list of fixed bugs`{% endtrans %}: http://trac.i2p2.de/query?resolution=fixed&milestone=0.9.24
+
+
+**{% trans %}SHA256 Checksums:{% endtrans %}**
+
+::
+
+ 40a9d162b218c3280170b5e6e5e0f459a2c5348c9488222955be5312144eade9 i2pinstall_0.9.24_windows.exe
+ f5a06c4ed7e3c22048eef18901b85baa1f9bed3e507c212700723701036e2bb3 i2pinstall_0.9.24.jar
+ 134481ae5ef934a411545330d1b22e768189c424a65db47058db0f7d9cf51e7d i2psource_0.9.24.tar.bz2
+ b8ee5d9c88924f631ae03ffcbed4ac0b06542e51cdd144e20dbaad69a8fdcef4 i2pupdate_0.9.24.zip
+ 6a3ddb8cb8d24a3b69d1138244c817852d0aa69a1603a3ed05f8368f01497394 i2pupdate.su3
diff --git a/i2p2www/formatters.py b/i2p2www/formatters.py
index a5987b68..8cd36825 100644
--- a/i2p2www/formatters.py
+++ b/i2p2www/formatters.py
@@ -668,7 +668,7 @@ class I2PHtmlFormatter(Formatter):
style = '; '.join(style)
yield 0, ('
')
+ + (style and (' style="%s"' % style)) + ' dir=ltr>')
for tup in inner:
yield tup
yield 0, '
\n'
diff --git a/i2p2www/meetings/logs/241.log b/i2p2www/meetings/logs/241.log
new file mode 100644
index 00000000..8110d0f8
--- /dev/null
+++ b/i2p2www/meetings/logs/241.log
@@ -0,0 +1,256 @@
+09:49:14 0) Hi
+09:49:14 1) Meeting structure and goals
+09:49:14 2) PR
+09:49:14 3) Project Management
+09:49:14 0) Hi
+09:49:16 Hi
+09:49:30 1) Meeting structure and goals
+09:49:30 First of all I apologize for the horrendous time for this meeting for our North American folks.
+09:49:30 This will be a little different from our usual meeting structure because it's mostly in-person here at CCC.
+09:49:31 We will attempt to relay the highlights to IRC.
+09:49:33 We will also be taking notes here.
+09:49:35 Now let me give a preamble for this meeting.
+09:49:49 As you all should know, Sadie was a huge part of the organization and success of I2PCon in Toronto.
+09:49:49 We all saw her talent and enthusiasm in Toronto, and obviously she wants to do more for I2P going forward.
+09:49:49 As we got to work with her before and during the Con, we learned that she has extensive Project Management and PR experience,
+09:49:49 both with Tor and out in the real world.
+09:49:49 What I asked her to do after the Con was to get to know our project better, to understand our current structure and processes,
+09:49:52 and to come back with recommendations on what we could do better and how she could help us.
+09:50:04 Since then, she's had several long conference calls with tuna, me, str4d, psi, and others,
+09:50:04 and reviewed our website, trac, and current processes.
+09:50:04 Also, psi has named her Assistant PR Director and she is tweeting on the @GetI2P account and helping to get the word out about I2P.
+09:50:06 She is now ready to give us some recommendations.
+09:50:06 While my original question to her was "how can you help us?", the answer coming back is
+09:50:06 more like "here's the things we need to fix so I can effectively help",
+09:50:08 followed by the actual things she could do for us, or more precisely how we can all work together more effectively.
+09:50:19 What I'd like to do today is to hear her recommendations and discuss them each briefly.
+09:50:19 Many of these topics tend to spark long discussion and I'd like to contain that so we aren't here all day.
+09:50:19 For each recommendation, I'd like to get a commitment from one of you to follow up.
+09:50:19 If the recommendation is uncontroversial and we have consensus, that commitment would be to implement it.
+09:50:20 If it needs further research or we don't agree, that commitment would be to review our options and
+09:50:21 come up with a plan, or a counter proposal, or a list of options to be discussed at a future meeting.
+09:50:23 These commitments and due dates will be noted and tracked.
+09:50:25 I don't want to get bogged down on any one thing so I'll be looking for volunteers to follow up most things.
+09:50:42 I want to emphasize that I asked Sadie to do this and give us her opinion based on her previous experience.
+09:50:42 We may not agree but we should listen and carefully consider her recommendations.
+09:50:42 I2P is its own little snowflake and not everything may be appropriate for us,
+09:50:42 but she's gotten to know us pretty well this year, so let's hear what she's got.
+09:50:43 We will of course be able to take suggestions from others but I have a feeling that Sadie's got a lot of things covered already.
+09:51:24 We're going to first talk about PR and then Project Management.
+09:51:24 Both are very large topics and there will be overlap. But let's try to keep them as separated as we can.
+09:51:54 *** end of paste for topic 1), we will start in with 2) in a few minutes. thanks ***
+09:58:39 str4d: heya we should have a talk about the DH stuff we're using
+09:59:30 hottuna, you referring to the NTCP and SSU handshakes?
+09:59:55 i guess wherever DH is used
+10:00:39 ok. lets talk about it after the meeting
+10:00:47 Sure
+10:00:57 According to http://trac.i2p2.i2p/wiki/Crypto/CurrentSpecs it's just NTCP and SSU
+10:01:21 zzz will be reading the long note above to us now
+10:01:48 (I still need to update that page ahead of my talk)
+10:04:10 i think i'm here
+10:06:33 psi: yes, zzz posted a long message just before you joined. talking IRL right now
+10:07:57 So what we're looking to do is to get commitments from people to fix a bunch of different topics
+10:08:25 Some of the stuff we're going to cover will be controversial and some not
+10:08:47 the non-controversial topics we're hoping to just assign a to a person and have that handled
+10:08:56 Onto Sadie and PR
+10:09:16 gravy and sadie have been writing blogpost
+10:09:29 and are looking for more content
+10:10:21 a lot of content is lost in the commit messages
+10:10:38 where the author of the commit does not really record the importance of the commit
+10:11:24 Rather than scanning commit messages, the best/easiest place to look is history.txt
+10:11:30 ideally we would like to publish a blog post at least every 2 months to keep some sense of momentum is kept
+10:12:08 That still doesn't give an indication of importance, but is contextually easier to handle and sifts out the commit chaff that doesn't make it into history.txt
+10:13:04 str4d: the point is that there is so many cool things happening, and no way to find out without following i2p closely. it should be easier for people to see the cool stuff
+10:13:47 Perhaps what might help (this would be rather radical) could be to restructure history.txt to organize items by importance (major/minor/bugfix), more like a changelog (or have a parallel changelog file)
+10:14:13 since as-is, the history file is really just an easier-to-parse commit log
+10:14:30 That said, it *is* convenient, so maybe parallel info would be better (if harder to maintain)
+10:14:38 * str4d stops getting bogged down in specifics
+10:14:41 :P
+10:14:59 lazygravy could act as an editor and sort of delegate the responsibility of writing content when that is appropriate
+10:15:14 Certainly making it easier to know what is going on is a plus, and I think some of the higher-level organization topics will help this
+10:15:33 (ie. a blog post writer can look there for the high-level overview instead of the commit log)
+10:15:56 sounds rather similar to pair programming
+10:16:10 next topic within PR
+10:16:29 regarding having a reseed campaign and attracting new developers
+10:16:46 (or more like married couple programming, the programmer and the programmer's wife)
+10:17:11 str4d: i.e. WTF encrypted lease sets are, or a cool highlight of kytv's debian repo
+10:17:15 we would like to involve torontocrypto to attract more reseed host s
+10:17:23 s/i.e./e.g./
+10:17:24 lazygravy meant: str4d: e.g. WTF encrypted lease sets are, or a cool highlight of kytv's debian repo
+10:18:25 We would like to generate a content package containing all info you would need to set up a reseed host should be available in one place
+10:19:14 we need to articulate why reseeds are needed and important
+10:19:18 Mmm
+10:19:42 It could even be made as simple as "sudo apt-get i2p-reseed"
+10:20:22 str4d++
+10:20:23 I was thinking of making docker images so it can be completely plug-n-play:ed
+10:20:47 the go reseed was excessively easy to set up and use
+10:20:56 hottuna/I volunteered to write a few paragraphs about why reseeds are needed and what they do
+10:21:07 kytv: that would be amazing
+10:21:23 kytv++
+10:21:35 Drop-and-go is the ideal
+10:22:00 Kinda like what was mentioned in one of the Tor talks yesterday, about how people could in future get a LetsEncrypt cert that comes with a free .onion
+10:22:16 (ie. the letsencrypt script sets up the Tor HS for the user)
+10:22:38 mdrollete's i2p-tools is available as a docker image, so maybe we (=I) could just polish up my I2P docker image (not yet advertised) so one could do it all by copy'n'pasting one command line and reseeding would "just work"
+10:22:41 about developed onboarding, making the source code more accessible
+10:22:42 (that in itself would be super neat for I2P, but slightly different from what we need here)
+10:22:55 kytv: docker for sure
+10:23:01 str4d: could I convince you to add some links to the source code from geti2p.net?
+10:23:04 If reseeds are an appliance, it also makes it much easier to keep honest reseeds in sync
+10:23:17 hottuna, where?
+10:23:18 thought: we should get rid of the note from 0.7.6 on the download page
+10:23:33 (I'm more of an lxc guy but I'm learning docker so whatevs ☺)
+10:23:45 ja
+10:23:50 kytv: docker seems "so hot" right now, so it might be best
+10:23:54 wherever it makes sense
+10:24:08 I believe there is at least one link to kytv's ViewMTN, but that's inside I2P
+10:24:11 but the idea is to make it easier to get a quick look at the soruce code
+10:24:13 Move all docs for ancient stuff to /attic or smth related
+10:24:19 to attract developers
+10:24:33 str4d outside i2p and ideally from geti2p.net is what we would want
+10:24:36 I could add links to the new devs page to the Github page, but they would need to be clearly marked as read-only
+10:24:50 if you really want to attract devs we should make the github alive more
+10:24:52 yeah.
+10:25:57 Is the new dev page where you want the links?
+10:25:57 that sounds like a simple straight forward step to take
+10:25:57 just add a read-only link to github
+10:25:57 hottuna, which? Links, or github alive more?
+10:25:57 would be an improvement
+10:25:57 ahk
+10:26:05 str4d: can I write your name next to that?
+10:26:24 that item that is
+10:26:38 Sure. I assume all of these will get issues created on Trac
+10:26:51 not sure if they will.
+10:26:57 will ask zzz
+10:27:09 Well yeah, probably not worth it for the smaller tasks
+10:27:20 As long as I get the list sometime :P
+10:27:26 ok
+10:27:36 i think zzz will do a zzz.i2p writeup
+10:28:22 it'll almost certainly go to zzz.i2p but perhaps also as tickets on Trac
+10:28:41 k
+10:28:50 * str4d pulls up todo list to start adding items
+10:32:43 we're talking about which usecasdes we should promote i2p for
+10:33:13 and the consesus seems to be that we should promote usecases which we are good at. like bote
+10:33:20 Mmm
+10:33:29 We definitely need to push the peer-to-peer aspect
+10:33:36 like torrents to potintiall
+10:33:38 y
+10:33:57 we would like to highlight these good uses on the main page
+10:34:12 *what we would like to highlight
+10:34:20 That's something I2P should have a fundamental advantage with, due to the packet-switched nature and tunnel-level symmetry
+10:34:33 yes. and there are other things we are good at
+10:34:39 And particularly apps that themselves inherently encourage contribution
+10:34:41 and those things we should promote
+10:35:05 and in the meantime we can keep on working on the things that we are not quite as good at
+10:35:09 (because I2P's need for contribution can then piggyback on the app's)
+10:35:43 lazygravy, str4d, cacapo: could you work through the 3 best usecases for i2p
+10:36:01 so that we then can present them properly on the frontpage
+10:36:18 Sure
+10:37:03 yepp
+10:37:08 when can you guys come back with something (recommendations or webstie changes)?
+10:37:43 is a deadline for end of january ok?
+10:37:55 ok
+10:38:01 realting to PR: i2p.net becomes available soon
+10:38:03 Fine with me
+10:39:04 16.4.2016 it is for i2p,net
+10:39:11 I can say right now that if we are meaning "things that work well right now", you're really looking only at high-latency email (bote) and torrents. Soon we can add distributed datastorage too (once Tahoe gets native I2P client support)
+10:39:24 * str4d is looking forward to i2p.net being recovered
+10:39:33 tahoe will only be useable with parallel up/download
+10:40:08 I think it would be ideal to dovetail it with my proposal for dev services on i2p.i2p, have them parallel available in- and out-of-net
+10:40:12 cacapo mentions i2p does not communicate a narrative about the project very well. or at all.
+10:40:29 str4d: tahoe has it's own UI problems... :/ (tho I adore it)
+10:40:29 unlike to which has a lot of history and contextual history to it
+10:41:03 hottuna, what narrative does he mean?
+10:41:09 relating to jake/snowden&/etc
+10:41:42 ah, narrative relating I2P history to world context?
+10:41:43 comraden1: volunteers to do a writeup of the history of i2p
+10:41:52 (like the Tor HS talk did?)
+10:42:05 history: zzz talk on i2pcon, my talk on 32c3
+10:42:06 (didnt see that)
+10:42:33 also my talk at I2PCon had a bit
+10:42:37 zzz, comraden1, lazygravy volunteered to do the actual writeup
+10:42:41 psi: around?
+10:42:53 yes
+10:42:57 str4d: and so did Lance James' bit
+10:43:34 lazygravy, Tahoe UX should improve greatly once magic folders is released. UI-wise, still has work to do, but not as much as us :P
+10:43:52 str4d, sadie, could the both of you help eachother out to do promo for the RWC talk?
+10:44:03 Öast call for PR related topics
+10:44:06 Lest*
+10:44:08 last*
+10:44:49 alright, i'll take that as silence
+10:44:50 hottuna, yep, I'll keep in touch with Sadie
+10:44:56 * str4d still has to prepare that talk :/
+10:45:04 Onto the next topic. PROJECT MANAGEMENT
+10:45:34 str4d: also "history of how i2p started". I'm thinking of navy researching onion routing -> second generation onion router -> tor
+10:46:40 comraden1, mmm, you'll probably find a lot of that in the early I2P meeting logs on the website
+10:47:15 If you do go rooting around in there, feel free to write quick summaries of the meetings that I can add to them :P
+10:48:11 str4d: zzz mentioned that he has a lot of it in his head and wanted to write a rough draft. I'm going to edit and make sure it is perfect before we release it
+10:48:45 +1
+10:49:19 I remember speaking about it with zzz ages ago; if he has logs of that, it might be helpful
+10:49:22 we're talking about what the actual goals of the project are
+10:49:54 and that they are important to have written down somewhere in order to be able to do meaningful project management
+10:50:29 Would make for a good about page
+10:51:16 I've wanted to merge the various intro pages, but we could actually leverage them separately
+10:51:36 Turn https://geti2p.net/en/about/intro into a brief overview of I2P, both the network and the project
+10:51:38 Title: Intro - I2P (at geti2p.net)
+10:51:59 Then make https://geti2p.net/en/docs/how/intro the *actual* "how does I2P work" page
+10:52:00 Title: A Gentle Introduction to How I2P Works - I2P (at geti2p.net)
+10:52:10 Kinda sorta what they appear to be now, but properly split
+10:53:12 hottuna: Where can I find the blogposts?
+10:53:22 hottuna: I can only see one (http://i2p-projekt.i2p/en/blog/post/2015/11/15/Community-Outreach)
+10:53:25 Title: Community Outreach - Blog - I2P (at i2p-projekt.i2p)
+10:54:38 dg: they don't exist aside from that
+10:54:55 and that was mostly a POC IMO. Next one should be published on 10Jan2016 on CCC
+10:58:32 we're talking about whether we want to be managed
+10:58:46 dg, str4d, psi: do you have any thoughts about having your work managed?
+10:59:11 by who and how much management?
+10:59:17 by sadie
+10:59:26 open to it
+10:59:42 and having it be relaxed as in deadlines. but not enforced deadlines
+10:59:46 things are done when they are done
+11:00:11 but mentally attaching a deadline to them might be a helpful tool
+11:00:11 done when they're done but a bit of pushing/motivation
+11:00:40 no thoughts until i eat breakfast
+11:00:47 or at the very least knowing that someone else knows that a given task is on your pile
+11:01:15 re project management: we'd like to get weekly/bi-weekly meetings up and runnning again
+11:01:25 zzz has the goal of starting them up in february agin
+11:01:27 again*
+11:01:36 and then gradually handing them off to sadie
+11:01:48 for that to happen sadie needs got on irc
+11:01:56 I'm good for it. I do tend to work better when I have someone(s) to bounce ideas off
+11:03:23 zzz just committed to having a single roadmap written up by the end of february
+11:03:23 splendid.
+11:03:23 the consensus seems to be that being managed lightly is probably a good thing.
+11:03:23 but anything heavy-handed would just turn this into work
+11:03:23 Sounds good. We can always adjust the level later once we have some experience with it.
+11:03:23 * dg nods
+11:03:23 *roadmap will be for end of jan, not feb
+11:03:23 str4d: agreed
+11:04:35 FYI zzz, sadie and I will be meeting up at the beginning of March, would be good to keep that in mind re: things we can work on/discuss then.
+11:05:52 re: trac tickets, sadie is volunteering to keep an eye on it and relay tickets to the right individual
+11:06:05 Being able to observe our mechanics like trac/zzz.i2p/irc is important for Sadie to fully understand how we work anyway
+11:06:16 Has she been able to do that w/o IRC access?
+11:07:04 str4d: would you bi willing to help sadie out in that endeavour?
+11:07:40 I've had on my todo list for a while a weekly "look over new tickets" item, that I keep postponing because too much on
+11:08:06 But from next year, I'll endeavour to help sadie with that :)
+11:08:49 You may have noticed there's an "open" status now for tickets. I added that so we can differentiate between new tickets and ones we've seen but haven't had an opinion on necessarily
+11:08:53 Last call for PROJECT MANAGEMENT topics
+11:09:10 hottuna: see above
+11:09:25 My goal would be to have as few "new" tickets as possible, ie. moving them either to a relevant person/status, or "open" to at least acknowledge them as a valid ticket.
+11:09:36 Last call for OTHER topics
+11:09:48 dg: getting sadie on trac is key. and a requirement
+11:10:00 I mean on IRC
+11:10:17 okay
+11:10:23 I've had an IRC bouncer account for her for a while now
+11:10:42 str4d: could we ask you to write up few items about what you learned about vulnerability response the the conf?
+11:10:48 All she needs is help getting her side connected, and she can then keep logs etc. without needing to stay connected all the time
+11:11:40 hottuna, you mean from talking to k8em0 at Kiwicon?
+11:11:47 mhm
+11:11:47 Also help with browser config/privoxy?
+11:12:13 I didn't learn a lot more than I already kinda knew, other than hearing in advance about the bug bounty program that Tor just announced
+11:12:26 we're proposing that we defer the VRP discussion to january
+11:12:36 str4d: would making a tiny writeup make sense?
+11:12:40 k8em0 did say she was very impressed with our VRP ticket
+11:12:45 like a zzz.i2p post?
+11:12:55 or was it all kind of useless?
+11:13:15 Not useless, more confirming that our VRP ticket is on the right track
+11:13:31 * zzz ******BAFFFFS***** the meeting closed, thanks everybody
diff --git a/i2p2www/meetings/logs/241.rst b/i2p2www/meetings/logs/241.rst
new file mode 100644
index 00000000..84f47503
--- /dev/null
+++ b/i2p2www/meetings/logs/241.rst
@@ -0,0 +1,18 @@
+I2P dev meeting, December 30, 2015 @ 10:00 UTC
+==============================================
+
+Quick recap
+-----------
+
+* **Present:**
+
+cacapo,
+comraden1,
+dg,
+eche\|on,
+hottuna,
+kytv,
+lazygravy,
+psi,
+str4d,
+zzz,
diff --git a/i2p2www/meetings/logs/242.log b/i2p2www/meetings/logs/242.log
new file mode 100644
index 00000000..b997466f
--- /dev/null
+++ b/i2p2www/meetings/logs/242.log
@@ -0,0 +1,407 @@
+20:00:00 Agenda http://zzz.i2p/topics/2014
+20:00:00 0) Hi
+20:00:00 1) Review of assigned tasks from Dec. 30 meeting - http://zzz.i2p/topics/2016 (zzz)
+20:00:00 2) Other CCC followup - http://zzz.i2p/topics/2019 (zzz)
+20:00:00 3) Project meeting plan for 2016 (zzz, Sadie)
+20:00:00