{% extends "_layout.html" %} {% block title %}I2P Development Meeting 210{% endblock %} {% block content %}

I2P dev meeting, November 27, 2012

Quick recap

Full IRC Log

{% filter escape %}
19:33:46   Alrighty.
19:33:49   So, today's agenda is:
19:33:52   0) Hi
19:33:55   1) IRL events
19:33:55   2) Websiet
19:33:58   (2a) redux
19:34:01   (2b) SSL
19:34:08   3) that space where you can pitch anything else
19:34:39  *** KillYourTV sets mode: +l 65
19:34:45   psi, Meeh, and ech (among others) are those who are attending IRL stuff or are able to/willing
19:34:51  * dg pokes
19:35:02   0) Hi
19:35:02   Hi!
19:35:18  *** KillYourTV sets mode: +lf 60 [10j#R10,20m#m5,3n#N15]:15
19:35:28    oh.. it's meeting time..
19:35:29  *** KillYourTV sets mode: +l 65
19:35:32   Hey
19:35:32   sorry
19:35:35   hi
19:35:38   no problem welt, hi!
19:35:49   'lo
19:35:57   1) IRL events then
19:36:24   We kind of touched on this last time--, I'm wondering if we can utilize the tickets (and men) we have at CCC to get i2p out there somehow
19:36:39   http://zzz.i2p/topics/1273 is relevant
19:36:56    I'll be @ 29c3
19:36:59   I've got stickers and am going to 29c3
19:37:01    (and bring stickers)
19:37:18   What would be nice is a talk or a workshop
19:37:41   Exactly my thoughts. Stickers are cool and all but they only vaguely provoke interest.
19:37:55    (hmm.. maybe I should bring a big "LANG=en" along this time :P)
19:37:55   A workshop/talk would be far better
19:38:04    +sign
19:38:12   (A talk would have lasting effects)
19:38:37   * weltende@freenode is an terrible speaker.. *waves vaguely at other people*
19:38:52   What would be the talking points of a talk?
19:38:55   a general into talk probably wouldnt be very interesting to many people
19:39:39   It's not really *our* place to perform a talk on the French researcher's points
19:39:41    we could do an getting started with i2p workshop or so?
19:39:49   General intro would need some sort of point also
19:39:51   Yeah
19:40:01   intro*
19:40:01   (due to the technical nature of the event)
19:40:16   Maybe a comparison to other solutions like tor?
19:40:31   s/solutions/options/
19:40:34   LaughingBuddha meant: Maybe a comparison to other options like tor?
19:41:22   What does make I2P an attractive option?
19:41:22   LaughingBuddha: maybe I didn't see your suggestion in context, but I don't think we should compare software made for different purposes.
19:41:34   Tor's .onion then, heh.
19:41:45   That may or may not interest the CCC folk
19:42:00   It'd still be somewhat generic *as a talk*
19:42:06   A workshop however would be perfectly apt
19:43:34   i don't think differences to tor are a good topic. they are rather subtle from a listener's POV and you would have to go into too much detail.
19:43:49   workshops are good if you can get a knowledgable volunteer to run it
19:44:00   i vaguely remember an i2p workshop in the past that didn't go so well. i might be making that up though.
19:44:11   What would we be trying to convey to the listeners? Are we assuming no knowledge of I2P? Passing knowledge?
19:44:15   any hint as to why?
19:44:26   There was a tor/i2p workshop last ccc, but it was cancelled by its creator (gamambel). About 10 ppl were there before realizing it was cancelled.
19:45:04    ah.. I remember
19:45:04   str4d: I'd assume a brief kind of acknowledgement and "hey, I've heard of that. maybe." but nothing more(?)
19:45:18   hottuna_: is 10 good or bad for CCC? I've really no idea about it :(
19:45:18   Schnaubelt: I am aware of that. But i2p and tor often get used in the same sentence.
19:47:44   I dont know, not terrible at the very least?
19:47:47   What does a workshop usually entail?
19:47:47   Im not sure, that was the only one I've ever been to.
19:47:47   welt please pm me on ein after meeting... have a couple questions
19:47:50   i think a lightning talk would be pretty good. a diverse selection of people watch them for one. and even if they wonder about the apparent lack of differences to tor, it's still a win if that gets them to look into it more.
19:47:50   But probably some setting up and demo:ing
19:47:50   yeah, a lightning talk would be appropriate
19:48:13   do we have anything new and/or interesting to present?
19:48:19  *** Farside  has left #i2p-dev (leaving)
19:48:22   maybe something that tor does not offer?
19:48:28    RN: k
19:48:32   Well, torrents..
19:48:36   That's not new but.
19:48:42   Big.
19:49:28   the torrent bridging idea/infrastructure is interesting
19:49:39   but not very complete/deployed
19:50:41   Yeah, that needs work.
19:51:00    having a lightning talk is something the ccc visitors can discuss later on
19:51:00   hottuna_: that would deserve an extra lightning talk. i'd worry that mentioning it briefly with i2p would only create the old "is everyone an exit node?" kind of confusion.
19:51:11   it doesnt have to be planned extensively
19:51:14   What would our desired result be? What sort of people would/should this attract? New general users? New high-profile routers? New technical users? New researchers?
19:52:23   technical users and researchers?
19:52:46   darrob, true. We do need to be consistent with terminology in that respect I think - outproxies are a service run by volunteers, just like IRC servers, eepsites and repository hosts. They are not something hard-baked into the router like Tor.
19:55:44   In that case, posing some open research questions near the end of the talk would be useful, to show that there is room for novel research (always a drawcard for academics ^_^)
19:56:19   str4d: sounds good.
19:56:19   yes squashing the misconception that I2P is meant to hide your login on facebook should be a big bullet point in any such talk/demo imho
19:59:09   "I2P is not a ${DEITY}damn proxy!"
19:59:34   Hm, ok
19:59:55   proxy is a really tricky term in I2P context
20:00:24   Yep. That's why I changed the default text for the IRC tunnel.
20:00:46   (It said "IRC proxy" which is *technically* true but not in the way users think it)
20:00:53   I think those of us visiting CCC could *really* do a workshop this year, and possibly a lightning talk (although that'd most likely be regarding torrents)
20:01:05   Time to move on to website
20:01:05   ?
20:06:52   did you skip updated info on mergability?
20:08:14  * dg missed messages
20:09:02   str4d: that's a good idea
20:09:05   also:
20:09:12   <+dg> I think those of us visiting CCC could *really* do a workshop this year, and possibly a lightning talk (although that'd most likely be regarding torrents)
20:09:12   <+dg> Time to move on to website
20:09:12   <+dg> ?
20:10:19   Messages keep getting dropped. gah.
20:10:19   oops sorry I was late
20:10:26   no problem
20:10:26  * topiltzin catching up with backlog
20:10:49  *** w8rabbit_ is now known as w8rabbit
20:11:11    dg, I was asking if you were skipping over mergability of fux update to website, (but my connection is tripping)
20:11:39   Mine is too.
20:12:08   * ReturningNovice_@kytv flips some switches and adjusts some knobs
20:12:14   fux hasn't changed in the last week, so no need to cover it at present.
20:12:25   I am. The outcome last time wasn't good and the fux folk have expressed that any merging is not desirable (at least right now). It may be possible for us to grab some features in future but I guess there's more important things right now?
20:12:28   Perhaps I'm wrong.
20:12:28   Yeah.
20:13:43   (I'm working on feeds for 0.9.5 so that's my priority)
20:13:54   Oh, right.
20:14:20   I setup #i2p-www (just reg'd it), and the idea was that me among others could participate in a "book sprint" almost to get the pages done
20:14:28   I wasn't sure which pages *actually* needed work, though
20:14:57   The idea is that #i2p-www could be used as a sort of web committee to get revamp up to scratch and report back to -dev (in meetings I assume) when there's updates
20:15:28   We're updating docs or are we revamping the site?
20:15:37   Revamping the site
20:15:51   <@dg> http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/site/
20:15:51   <@dg> i2p.www.revamp is the mtn
20:15:57   dg, I'd recommend that text revamp be done know
20:16:00   argh
20:16:03   We determined that the current design isn't friendly enough etc.
20:16:20   in I2p.www
20:16:48   ok caught up with backlog
20:16:59   and design/structure of the new site in I2p.www.revamp
20:16:59   we on website now?
20:17:07   yup
20:17:22   alright! duck's design. Very nice.
20:17:34   str4d: If that's easier for you, sure.
20:17:57   do we have a eepsite with that design?
20:18:04   does it require javascript for anything?
20:18:11   huch can you reaach the eepsite
20:18:11   ?
20:18:20   &cs http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/site/
20:18:20   Trying to check status of "http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/site/" for dg. Please wait...
20:18:26   http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/site/ responded with status 200 within 5 seconds.
20:19:09   and "Ur mom" is still there. :-/
20:19:12   What work needs to be done before it's a viable alternative?
20:20:04  * dg is wondering this
20:20:47   topiltzin, I apologize for not removing that yet -_-
20:20:58   design needs work/overhaul
20:21:45   yeah, I remember seing a preview of that... it was a nice profesional look...
20:21:45   (and vekw35...i2p's bandwidth gets slashdotted lol)
20:21:48   but that can be worked on later, with multiple proposals if necessary
20:21:55   looks alright to me.  Is all the content - mtn howto, developer keys, that stuff there?
20:22:22   first priority IMHO is getting backend finished.
20:22:41   topiltzin, I've migrated most of it.
20:22:44  *** sayliwo_ is now known as sayliwo
20:23:03   does the revamp use the regular trac tickets?
20:23:41   I'm still not happy with the page / navigation layout though..
20:23:48   a ticket for "remove "ur mom" " would serve as a reminder to whom it gets assigned to...
20:24:07   I don't know if "Supported Software" is the best name for the middle column because it's really listing actions, not actual software
20:24:30   RN, the frontpage needs a rethink.
20:25:09   duck's layout copied the Tor site, and it would be good to make it more unique.
20:25:20   Could we get a list of things that need doing so someone could perhaps tackle it/at least we have a clear, concise list?
20:25:39   I agree dg
20:25:54   how drastic of a rethink do you have in mind, str4d ?
20:25:57   I can outline later what I know needs doing.
20:26:19   Thanks!
20:26:22   I guess we're done with that
20:26:36   weltende: you here?
20:26:46    yup
20:26:59   topiltzin, I like the general layout, but the three columns content needs rethinking.
20:28:17   Agreed.  I'm available to discuss whenever you think it's best
20:29:45   and the footer is almost unnecessary
20:29:48   fwiw the news column on the right is dynamic
20:29:48   (i.e add a new article to backed and the list is updated)
20:29:48   That's another thing-  caching needs thought
20:29:48   
20:30:36   dg: we can dig in deeper on the website or keep going - your call
20:34:32   <+topiltzin> dg: we can dig in deeper on the website or keep going - your call
20:34:35   <+dg> I'm fine with digging deeper, I just don't want this to drag on too long and have some people leave, but the remaining topic is pretty small and mainly just between me and welt
20:35:11   ok
20:36:00   I would change the name of the middle column "Supported Software" -> "What can I2P do"
20:36:11   and since we already have a similar question in the title above, I would consider changing that
20:36:34   maybe "What does I2P do for you" -> "What is I2P"
20:37:28   RN: Do we actually have a trac category for this?
20:37:35   no passive tense on the front page == good
20:37:38   I'd suggest changing "can be conducted anonymously on I2P." to "can be conducted anonymously inside I2P."
20:37:50   Ooh.
20:37:57   inside does sound far better, actually.
20:38:08   A lot of people do not seem to understand that i2p is a space.
20:38:19   We don't want too much text on front page, but given the improved navigation, how much redundant linking is needed?
20:38:37   dg, if we don't one could probably be created...
20:38:59   And could some of it be replaced with other feeds/intro text/something?
20:39:14   dg, www
20:39:21   of course, I'll go create a ticket for "your mom".
20:39:28   What about simplifying that sentence a bit? "Many things would risk your privacy on the public Internet but you can do them anonymously inside I2P"
20:39:46  * topiltzin was hoping we were mature enough to not need ticket for "ur mom" but we do, so be it
20:40:48   Should I spare us the embarrassment or do we actually need to make a ticket?
20:40:51   I'm trying to come up with the most condensed and accessible description possible for the front page
20:41:25  * RN giggles at " of course, I'll go create a ticket for "your mom"."
20:41:44   I think str4d won't forget about it so it's probably not needed.
20:41:59   (nor anyone else that does anything on it)
20:42:02   toss a coin.  whatever it takes to get it done :-/
20:42:05   we don't need a ticket for it
20:42:24   didn't mean to start such an uproar
20:42:27   It'd be nice to have some things officially noted, although uh.. not the "your mom"..
20:42:30   as I said, I think that entire column needs replacing with something else.
20:42:38  * dg sweeps "your mom"-gate under the rug.
20:42:45   but at least we know there's definately an apropos place for such
20:43:00   dg, then a ticket for "replace left column content with something else"
20:43:51   ok
20:44:22   left column could even go away entirely imo
20:44:49   gives us more room to expand on the functionality more
20:45:16   as
20:45:16   Argh, ignore that- _-
20:45:49   Trac keywords are delimited by "," right?
20:46:12   afaik, yes
20:47:11   we could even remove the heading "Supported Software" and just use that space to list the different things I2P can do
20:47:26   http://trac.i2p2.i2p/ticket/792
20:47:29   better than list - give a small blurb on each if appropriate or include an icon
20:47:39   topiltzin: That'd be sweet, actually.
20:48:00   remember that the navigation, columns and footer are just lists, so the left column could be altered/removed with a different theme as well.
20:48:03   "Supported Software" isn't user friendly anyway
20:49:06   hmm.... icons... that could get stylisticly opinionated quickly
20:50:34   icons etc should be left to theming. maybe we should think about the content we want on the front page for now, and not necessarily how it will be arranged?
20:50:45   if we can't agree on what icons we think look good we don't have to have any
20:51:49   you mean beyond removing the left column str4d ?
20:52:35   yeah, I agree with str4d I think content first, form second, icons as eyecandy in theemes or later
20:52:50   the most important two questions someone will likely have when they come to the site, are either, why do I need this? and I've got it, so what now?
20:53:16   Well, does it need removal? Would a brief intro with a "read more" link be useful? Would a small infographic be helpful?
20:53:35   Things like that - content.
20:53:38   I like infographics in Pretty Colors (TM)
20:54:30   and as RN asked - what do we answer when the first-time visitor asks "why do I need this?"
20:54:33   yeah topiltzin, but you use paint
20:54:40   ;)
20:54:51   it wouldn't be me alright, zero visual skill here :-P
20:55:43   breif with a "read more" is a good idea imho
20:55:57   <+dg> I'd rather not fill up trac with loads of unnecessary tickets but at the same time, it helps to keep a handle on what needs to be done.
20:56:00   <+dg> Oh, and http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/site/volunteer/bounties - Bounties links are broken.
20:56:00   <+dg> I think I'm going to go ahead and make tickets for these.
20:56:11   Title: Bounties - I2P (at vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p)
20:56:40   dg, are they? Must have missed a link migration...
20:57:11   I tried a few links at random and they loaded for me
20:57:18   what would you say in such brief RN ?
20:57:45   GCJ, for example. "http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/Makefile.gcj"
20:57:52   A duck.i2p one too.
20:58:07   I'll trac these too.
20:59:10   Oh, that is text- related dg
20:59:17   well, I'd say something like, the internet is watching you...
20:59:17   lol
20:59:24  * dg notes
20:59:24   they will fail on current website as well.
20:59:39   I'd need a little time to think up something more serious
20:59:47   str4d: Thanks :)
21:00:13   I'm not opposed to having something not-so-serious but not all the way to "ur mom"
21:01:25   ideally something inviting.. not too formal
21:01:36   definitely worth brainstorming
21:06:05   i2p.trac: #795: Bounties being broken http://trac.i2p2.i2p/ticket/795
21:06:08   i2p.trac: #793: Mirror links http://trac.i2p2.i2p/ticket/793
21:06:08   i2p.trac: #792: Replace left column content http://trac.i2p2.i2p/ticket/792
21:06:43   <+dg> Tickets #793 - #795 I have created so far.
21:06:43   <+topiltzin> ideally something inviting.. not too formal
21:06:43   <+topiltzin> definitely worth brainstorming
21:06:43   <+dg> btw I'm in no rush to close this up unless you guys are ready
21:07:41   I guess it comes down to why do we want more people to use i2p and what do we tell them so that they start using it
21:08:00   mirroring and ssl are the only remaining items, aside from brainstorming about the content?
21:08:19   SSL is between me and welt mainly, and I made a ticket for it
21:08:19   wanna take care of those two and come back to content at the end?
21:08:34   Mirroring was touched on last week.. I think we still may need welt for that.
21:08:34   Oh.
21:08:42   I'd like to bring up something, actually
21:08:56    I am here..
21:09:00   Do you guys think that a mailing list returning for dev discussion etc would be useful or not?
21:09:10   +1 yes please
21:09:17   weltende: See ticket #794
21:09:29   imo we closed the discussion wrt SSL last week
21:09:40   a mailing list yes, would be good to start one up again imhho
21:09:43   Im not so sure about a mailinglist. zzz.i2p seems to fill that void very well.
21:10:02   http://trac.i2p2.i2p/ticket/794 - (assigned defect) - SSL
21:10:03   though, the warm fish has a good point
21:10:39    hottuna: the old ML attracted outsiders though..
21:10:59   zzz.i2p is also already established and working quite well
21:11:23    hottuna: not as much as the ML used to be
21:11:35   welt: yeah, that is true. but it has to be useful and not just bloat for the sake having more stuff
21:11:56   both work although mailing lists in general are very common in open-source projects
21:11:56   it's a long-standing tradition in a way.  I can live with zzz.i2p but I'd feel right at home with a developer mailing list
21:12:17   mailing list could be handy (I'd considered setting a mailing list site up, but wasn't sure how to handle emails without creating one email per list on postman)
21:12:23  *** blitzkrieg_ is now known as blitzkrieg
21:12:38   is attracting outsiders a bad thing? ;-)
21:12:46   maybe build it and they will come? if no-one cares it will die soon enough
21:13:00    topiltzin: I meant it as a pro-argument for an ML
21:13:12   oh ok
21:13:32   alternatively ask zzz for an externalized versions / linkto zzz.i2p.to / linkto zzz.i2p.in
21:13:39    yeah.. will set one up once I have time
21:14:43   I generally don't feel comfortable typing in my password when using those in/out proxies but others may not mind
21:15:56   yeah, an inproxy is probably not optimal
21:16:26   <+dg> This exists, by the way. It's dead though.
21:16:29   what's the last thing you got dg?
21:16:29   <+dg> http://lists.welterde.de/mailman/listinfo/i2p-general
21:16:29   <+dg> Also, might wanna turn directory listing off on *.welterde.de.
21:16:32   <+dg> http://lists.welterde.de/mailman/
21:16:32   <+dg> Anyway, ok
21:16:32   <+topiltzin> I generally don't feel comfortable typing in my password when using those in/out proxies but others may not mind
21:16:35   Title: I2p-general Info Page (at lists.welterde.de)
21:16:35   <+dg> I don't either.
21:16:38   Title: Index of /mailman/ (at lists.welterde.de)
21:17:14    dg: ah.. I forgot about that.. just never made it onto the website I guess..
21:17:25    (would rather make it lists.i2p2.de or so though)
21:17:33   I would too :-)
21:20:27   topiltzin, personally - I'd like a mailing list but for me, at least it'd be more about the professionalism of it et all, rather than any benefit I can describe to you and preach
21:20:42   but I suppose the rest of you feel that it'd be beneficial, so that's good
21:20:45   dg: return true;
21:20:45   having mailing list archives is very useful; makes the project more like other open-source projects if nothing else
21:21:49   how is that different from zzz.i2p + inproxy access : not much different other than the random new developer would have less of a learning curve to deal with
21:22:30   also allowing search engines to index the mailing list archives contributes to the global knowledge base so that's good
21:22:40   or someone curious about I2P could read some discussion and perhaps decide to install it and try it out
21:22:55   very often I'm searching for something and I find the answer in the mailing archive of some open-source project
21:23:18   RN: that is possible, I prefer to keep all possible venues open.
21:23:28    topiltzin: the ML is not about new developers.. or people that are involved in i2p at all.. but rather people outside of the project, that critique the protocol, implementation, etc.
21:23:40   and then let the users / developers / market decide which place is the best
21:23:47    which has very much died down since the crash
21:24:14   I don't see why it can't be for both, weltende
21:24:44    topiltzin: sure.. but imho my aspect is the more important aspect ;-)
21:25:04   :-P
21:25:14   <+topiltzin> I don't see why it can't be for both, weltende
21:25:14   <+dg> Also, going to throw an idea out here: geti2p.net as a default domain from some $period onwards
21:25:14   <+dg> (maybe when we launch the new design)
21:25:34   <+dg> <+dg> I was thinking that, actually
21:25:34   <+dg> <+dg> It paints a better picture
21:25:34   <+dg> <+topiltzin> I don't see why it can't be for both, weltende
21:25:34   <+dg> <+dg> Also, going to throw an idea out here: geti2p.net as a default domain from some $period onwards
21:25:37   <+dg> <+dg> (maybe when we launch the new design)
21:25:44   I like geti2p.net
21:25:55   iRelay>  topiltzin: sure.. but imho my aspect is the more important aspect ;-)
21:25:55    :-P
21:26:06   So do I, not perfect (i2p.net would be better, obviously) but better than the current IMO.
21:26:17   ticket #795 is now fixed for the live site.
21:26:20   also, sorry for my flaky connection.
21:26:26    the stickers already say geti2p.net iirc ;)
21:26:34   http://trac.i2p2.i2p/ticket/795 - (new defect) - Bounties being broken
21:26:38   Is I2p.net still registered to jrandom?
21:26:48   it was paid for many years
21:26:51   so yes
21:26:58   unless jrandom returns, we're kind of screwed.
21:27:02   There's no promise we'll get i2p.net once it expires, either.
21:27:08   (unless we go to ICANN?)
21:27:10    yeah... until 2016
21:27:18   And I agree with your idea dg
21:27:29    dg: verizone actually
21:27:42   yeah, new design + new domain name = freshness
21:27:51    err.. verisign
21:27:57   I thought you'd go to ICANN for getting a domain back if someone else steals it afterwards, say it is your "brand".
21:28:04   I already plan to have the site dynamically change URLs for sites it knows are available inside and outside I2p
21:28:15   sadly, I doubt we can go to ICANN/etc now and say "hey, can we have it now please? We don't want to wait until 2016!"
21:28:35   (unless we have some good friends)
21:28:41    dg: no.. ICANN only deals with TLD's.. you have to go to the TLD
21:28:49   So e.g. forum.I2p <-> forum.i2p2.de
21:28:52   ah, rite
21:29:07   Is it possible to get in contact with $hostOfForum?
21:29:11   We could get *.i2p? :D
21:29:22   forum.i2p is/was popular and the stability would help..
21:29:51   (It doesn't help that an officially linked forum is down a lot of the time and we have.. no forum for users). It worked good for a while.
21:30:08   str4d: also, yes. the "(in i2p)" and conflicting linking styles on pages is strange and obscure.
21:30:15   I'd rather what you suggested. :-)
21:31:10   btw - "2007-09-28 - Syndie 1.101a" is kind of lame to have on the site..
21:35:18   syndie actually is something I think we should keep
21:35:25   it needs a dev to show it some love, but it works and is quite usefull once you get used to it
21:35:25   heck, putting this meeting log in syndie would be a cool idea imho
21:35:32   Keep but find someone to work on.
21:35:35   Yeah.
21:36:14   So we have domain name, mailing list, content brainstorm.  Any specific one we want to or need to focus on further?
21:36:56   I don't think so, but maybe someone disagrees heh.
21:38:53   what do you mean by "should keep" RN?
21:39:05   <+dg> btw - "2007-09-28 - Syndie 1.101a" is kind of lame to have on the site..
21:40:30    I think syndie has huge potential
21:41:02    it seemed dg was suggesting removing it from the software list or something
21:41:18   We need to have updated tarballs/installers linked. Perhaps we should also have syndie.i2p2.de managed by mtn as well.
21:41:40   Kind of. I was proposing that we perhaps hide the date or change the design to have it standing out less, it looks bad IMHO to have such stale software on the page
21:41:47   It hurts first impressions of Syndie and i2p
21:42:01   KillYourTV: Yeah. Just having those tarballs/etc up would help..
21:42:04   Maybe we can keep it but remove the date?  I think the lameness stems from the 2007 token
21:42:15   (and the broken installer..)
21:42:19   s/installer/packaging
21:42:29    ah, just changing the link text to "Syndie"
21:42:29   that is until active development picks up again (re: removing the date)
21:42:32    I agree
21:43:28    yeah, I'm with that
21:43:44   :)
21:43:55   dg, revamp doesn't have it there.
21:43:55   That box on current site is meant to be the equivalent of the "news"
21:43:55   Having a Syndie link would be good, but more as e.g. part of middle column.
21:44:05   I think we're mostly done
21:44:16   Although netsplit
21:44:23   (So the 2007 syndie page is still there, but accessible through the blog)
21:44:26   pfft, I don't think we're missing anyone who was involved
21:44:33   Good meeting, guys.
21:44:40   How about 8:00PM next time?
21:44:43    dg: next meeting could with a bit more structure ;-)
21:45:14   weltende: heh, sorry. We had a lot to talk about and I didn't anticipate it'd go like this, I figured it'd be short. I'll include that in my planning next time. :-)
21:45:14   oh well
21:45:17   still, good outcome.
21:45:24   RN: since you brought the focus on content I'm looking forward to hearing your suggestions :)
21:45:31   Mmm. Maybe structure the shorter topics first, and the more discussion-y ones later.
21:45:31   whenever they're available
21:45:42   +1 str4d
21:45:53   the more open-ended ones at the end makes sense
21:45:56   str4d: Yeah, might be a good idea. I hope I'm doing okay though, heh.
21:45:59   I think I have.
21:46:14   It's better than no meeting at all =)
21:46:28   topiltzin> RN: since you brought the focus on content I'm looking forward to hearing your suggestions :)
21:46:31    whenever they're available
21:46:31  * dg smiles
21:46:42   return true; // ;-)
21:46:44    you are getting a good start dg...
21:46:44   topiltzin: nah, RN got it from kytv
21:47:10    yeah yeah  topz
21:47:13    ;)
21:47:23    so did you bang the mallot... ?
21:47:27   I'm glad, I feel as if we've done something good today (and last week)
21:47:27  * dg uh.. bamfs the meeting closed.
21:47:38   Meeting will be 8:00PM next time, same day.
21:47:47    YAY! officialness
21:47:47   RN: bam
21:48:05    :)
21:48:06  * dg highfives RN
21:48:20  *** KillYourTV changes topic to "Latest dev build: 0.9.3-11 | Dev mtg here 8:00 PM (20:00) UTC Tues. Dec. 4 | Report bugs at http://trac.i2p2.i2p / http://trac.i2p2.de"
21:48:28   * RN@kytv gives dg a beer
21:48:31   **smooth**
21:48:38    dg: actually it used to be *baf*s I think :P
21:48:50   drat
21:48:53  * dg notes
21:49:00   Yep. So not finished yet =P
21:49:30   *baf*s
{% endfilter %}
{# TODO: pygments #}
{% endblock %}