18:00:57 #startmeeting 18:00:57 Meeting started Tue May 5 18:00:57 2015 UTC. The chair is larjona. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:57 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:01:00 She's done all the work so far anyway :þ 18:01:10 #chair Maulkin 18:01:10 Current chairs: Maulkin larjona 18:01:17 (for the case I get a heart attack) 18:01:21 :þ 18:01:30 Hello everybody, welcome! 18:01:40 #topic Round of introductions 18:01:46 Please say hello! 18:01:51 hello o/ 18:01:53 o/ 18:01:56 * Lunar^ lurks 18:02:01 o/ 18:02:01 hello! 18:02:04 o/ 18:02:05 Hello o/ (another lurker :)) 18:02:09 o/ Hai! 18:02:15 Hello. 18:02:16 hello, i am Martin Zobel-Helas, member of listmaster, DSA, website, and i work a bit on publicity too... 18:02:22 SPI board member... 18:02:57 I'm the editor for the Ubuntu Weekly Newsletter, so I try to share Debian stories as I come across them, and try to keep an eye on summaries+reviews when I find the time (not much lately) 18:03:33 idea of that meeting is to coordinate a bit more within the team and to see how takes which duties, as the publicity work is quite wide-spread. 18:03:39 (to help larjona...) 18:03:44 Neil McGovern, press@d.o (though hopefully not for much longer), occasional AM for non-uploaders, DPL 18:04:19 Laura Arjona, Spanish translator, website and publicity teams, trying to help with publicity for debconf... 18:04:20 I am Cédric Boutillier, an editor of the Debian Project News letter, French translator of several announcements (member also of the Ruby teams, and other small things) 18:04:39 Andreas Rönnquist, Swedish translations, mostly for debian-www, plus package, and just began on some AM work. 18:05:19 <- Donald Norwood, member of the publicity team (yay), webteam, and acolyte on the mirrors team. I also run one of the many Debian mirrors. I've applied for DD status. I have no time. 18:05:23 Thomas Vincent, french translator, I help with DPN sometimes. 18:06:01 next agenda item? 18:06:09 well, the proposal is a quick round of every service we manage 18:06:31 if people in charge of that are not present we can go on, or leave for later 18:06:33 opic Status of Announcements: distribution of work, call for help, new ideas 18:06:34 hello 18:06:35 larjona: then tell that to meetbot. 18:06:38 #topic Status of Announcements: distribution of work, call for help, new ideas 18:07:13 I used to be one of the main editors of the DPN, but I have now less and less time for that, I am afraid. I thank cnote very much for helping so much with it 18:07:24 * cnote blushes 18:07:31 I'm not sure if there is somebody who works preferently on writing Announcements or depends on the announcement itself, Maulkin? 18:07:35 I regret that we have difficulties to maintain the frequency of once every 2 weeks 18:07:49 announcements are currently mostly collected and drafted in publicity-svn 18:08:15 then tagged content-frozen and asked for translations. 18:08:21 then sent to the according lists. 18:08:50 who decides if writing an announcement or just mail debian-devel-announce, for example? 18:09:03 * Maulkin nods - that's the way it works for non-embargoed announcements. For embargoed ones I basically have to write it myself 18:09:21 Maulkin: embargoed is what? 18:09:32 secret stuff 18:09:34 zobel: Announcement that isn't public until it's released. 18:09:50 Usually done to coordinate press with other organisations. 18:09:57 Maulkin will you need to pass this task to somebody else during this year? 18:10:18 (maybe this is linked to "press team")? 18:10:27 Maulkin: which kind of text is that? obituary only? 18:10:33 I've needed to pass it on to someone else for the past year or so, but haven't managed to find a vict^Wvolunteer. 18:10:43 what's a sample there? Security relevant things? 18:10:59 zobel: https://www.debian.org/News/2015/20150327 for example 18:11:00 #info it would be nice that somebody volunteers to help with announcements (specially embargoed ones) 18:11:21 Maulkin: i can help with that. 18:11:24 So, -announce/-news/-devel-announce split - want me to talk about that now? :) 18:11:38 yes 18:11:48 #action zobel can help with announcements 18:12:12 Ok, basically it depends on the audience. I've been deciding more or less by myself on that. 18:12:30 #info -announce/-news/-devel-announce split depends on the audience 18:12:45 (feel free to #info yourselves :) 18:12:47 Maulkin: -announce is for (point-)releases? -news for the other public statements of the publicity team, that need broader attention? 18:13:03 (typing :P) 18:13:17 both should also go via bits.debian.org? 18:13:26 If it's something that's aimed at the developers, then d-d-a should be used. If it's aimed as a press release, or for the project itself (rather than a particular dd) to communicate wider, then -news or -announce could be used. 18:13:54 need to change laptops. 18:14:02 I can assist zobel as well if a 3rd person is needed. 18:14:13 I believe -announce ends in https://www.debian.org/News/ but not sure where -news ends in the website 18:14:18 -announce is basically releases, point releases, security support ending etc. 18:14:35 #action cnote can assist zobel as well if a 3rd person is needed 18:14:47 -news is more wide, press releases, etc etc 18:14:47 -news also goes to (or rather from) https://www.debian.org/News/ 18:15:17 #info Workflow is described at https://wiki.debian.org/Teams/Publicity/Announcements 18:15:57 #info both -announce and -news go by mail, by website ( https://www.debian.org/News/ ) and by pump.io (the website RSS is published automatically in debian@identi.ca ) 18:15:58 zobel@bendel:~% wc -l /var/list/debian-announce/dist /var/list/debian-news/dist /var/list/debian-devel-announce/dist 18:16:01 31649 /var/list/debian-announce/dist 18:16:04 22623 /var/list/debian-news/dist 18:16:06 to give some subscriber numbers. 18:16:09 7182 /var/list/debian-devel-announce/dist 18:16:19 Thats pretty cool. 18:16:20 thanks zobel 18:16:25 * Maulkin nods 18:16:27 ok, move on? 18:16:36 Hence the importance of sending things to the right place. 18:17:19 ok let's move 18:17:29 we can go on later or in another meeting 18:17:31 #topic Status of DPN: distribution of work, call for help, new ideas 18:17:54 [20:07] I used to be one of the main editors of the DPN, but I have now less and less time for that, I am afraid. I thank cnote very much for helping so much with it 18:18:32 I was thinking in getting more involved in DPN (and its translation as well) 18:18:59 it turns out that it is very difficult to do the work for the DPN not at the last moment (for some reason). 18:19:00 i need to admit that i participate very few in DPN, but it is source that is quite often cited when other press media picks up news items from us. 18:19:42 When Madamezou and taffit were around, it was very motivating to meet on IRC and finish the last bits together in an IRC party 18:19:54 just before the freeze on Friday's night. 18:20:05 boutil I'm not sure I understood. You mean that most of the work goes in the last weekend? 18:20:08 so i consider DPN as an important media for us. 18:20:16 larjona it seems so. :) 18:20:39 so each other Friday we can set a DPN-IRC party? 18:20:41 if several people volunteer to help with the DPN, we can try to find a time spot to gather if others would find this also motivating 18:20:53 larjona: yes. mostly items are collected during the weeks as action items, and then written-out full text on the last friday. 18:20:54 Most of the writing is done prior...Thursday for example, but the editing and the adding of packages and facts is the real pressing stuff at the end. 18:20:55 I don't underestimate the amount of work that this involves - there's a reason it's no longer debian weekly news. 18:21:01 if Friday is not suitable, we can rethink the schedule 18:21:06 ^^ Maulkin spot on. 18:21:32 The current release schedule does set us up to rush it out at the 'last minute'. 18:21:46 #action larjona will get more involved in DPN 18:21:49 having the week-end during the freeze helps to get some people checking the content 18:21:56 I can't make a lot of time, but DPN is important to me and I could commit to helping out once a month or so, getting together to do it would help me too 18:21:59 But having 2 days for people to look over it is ideal. The problem is that is also the weekend and people aren't in front of their computers. 18:22:22 it is basicly following planet.debian.org and several mailing lists, like -user*, -project, d-d-a, -release and summmarize some of the threads. 18:22:31 if each of us gets to write just one paragraph/short article, we would be more than fine :) 18:22:52 #action pleia2 can help once a month or so 18:23:00 also cool other news items from other distributions or sources we can cite (eg. LiMux, Extremadura Linux, Ubuntu, ....) 18:23:24 pleia2: see some of the info i posted... 18:23:26 zobel: a children of section? 18:23:33 Or distro news? 18:23:36 Something like that? 18:24:07 zobel: yep, I've been following along :) 18:24:28 maybe a summary of "new users/vendors/consultants" too (from the respective audits) 18:24:45 cnote: when other Debian blends do cool stuff, we might want to post that to DPN... 18:24:52 but I suppose there's no lack of topics but lack of time to write them down :) 18:25:07 Madamzou some time ago proposed to maybe list popular questions on ask.debian.org 18:25:23 ok! anything else? Can we move on? 18:25:28 move on 18:25:31 I like that idea because it works well with spreading the word in OSS and...because it can give us some filler on small issues. 18:25:38 Wait! 18:25:43 * larjona waits 18:26:09 So what has changed? 2 extra people: larjona and pleia2 to assist and the addtion of extra news from other distros based on Debian? 18:26:16 shall we try to prepare an issue for next monday? 18:26:23 Are we firm in everyone adding a paragraph? 18:26:38 +1 18:27:09 Maulkin: as DPL you could try to motivate ppl to send more ideas for DPN items to the publicity ML. 18:27:09 If everyone can add 1 paragraph over a 2 week cycle we could conceivably have larger issues, with more content. 18:27:41 And lastly, "weekly". Weekly is hard, sometimes there is not a lot to publish, which is why every new section or new item really counts. 18:27:52 someone suggested about cnote's initiative on contacting lists to contact people individually, to hope a better rate of (positive) answers 18:28:03 even if it is only a few words, we still can then try to make full sentences out of that. 18:28:04 Do we stay at weekly or stay with where we are now which is closer to a bi-weekly push? 18:28:07 cnote: every two weeks sounds reasonable 18:28:31 two weeks is good for me too. We also have the social networking 18:28:45 This works for me. 18:28:47 (but DPN gets translated, so I think it's the most important media) 18:28:54 ok, move on! 18:28:58 #action maulkin to delegate zobel as press@ and encourage submissions for DPN 18:29:03 #topic Status of Press team: distribution of work, call for help, new ideas 18:29:33 Anything else that we didn't talk before in the topic of announcements? 18:29:42 yes 18:30:07 press team is also the point of contact where other media sends mail to for questions. 18:30:14 press@d.o 18:30:18 oh 18:30:27 currently it is read by whom? pabs only? 18:30:36 Maulkin: ^ 18:30:37 and Maulkin too? 18:31:05 Maulkin: is there anything confidential on press@ to not have more persons reading it? 18:31:31 There's quite a few subscribers, but the only people actively doing anythign is me and pabs 18:32:02 #info several people is subscribed to press@debian.org but the active ones are pabs and Maulkin 18:32:32 It's less that there's confidential stuff, more that there's a need to deal with certain journalists who may take an offhand comment and turn it into a story. 18:32:55 Curious, could interacting with the press be a function of the publicity team? (From an outside point of view it seems to make sense.) 18:33:11 That would be ideal. 18:33:37 So, what is needed (by publicity team) to improve status of things in "Press team"? 18:33:46 so we s/press@d.o/debian-publicity@ldo/? 18:33:47 Perhaps whomever is 'leading' the publicity team could be the press officers? 18:34:02 boutil :) 18:34:26 #info we need a press officer (or several press officers) 18:34:34 https://wiki.debian.org/Teams/Press 18:34:45 How much of a workload is Press? 18:34:53 It's basically a delegated position. I've tried to push as much as possible into publicity. 18:35:18 cnote: hhhmm no (at least not now...) 18:35:25 i guess it is mostly to distinguse the 1% real mail from 99% spam mails to that alias? 18:35:34 Yup. 18:35:43 And re-directing users to the right email list 18:35:51 (aka: the pabs-bot) 18:36:14 And then dealing with the occasional press release to go out. 18:36:54 I'd prefer press team and publicity team to basically be merged. 18:37:06 (they sort of are already) 18:37:08 Maulkin: ACKACKACK! 18:37:12 haha 18:37:50 would make sense indeed 18:37:52 How would the email situation work? Adding more individuals to the alias? 18:38:07 Maulkin maybe you can send a mail to -publicity about this topic? Or we keep discussing here? I'm not sure if here is the place for volunteering for that 18:38:36 cnote: yes. 18:38:43 #action Maulkin to mail -publicity about merging the teams 18:38:43 larjona: +1 18:38:55 ok, do we move to the next? 18:38:57 Maulkin: maybe -project too. 18:39:06 Yes next 18:39:16 #topic Status of Social Networking: distribution of work, call for help, new ideas 18:39:49 currently debian is present at pump.io only (officially) 18:40:02 https://wiki.debian.org/Teams/Publicity/Identica 18:40:16 larjona: pump.io is identica? 18:40:34 facebook and twitter are unofficial accounts by indivudual developers. 18:40:40 pump.io is the network, identica is the instance where we have our account 18:40:41 who share access to those accounts. 18:40:59 there is also an unofficial google+ account 18:41:02 we have gnusocial too (quitter.se/debian handled by yours truly) 18:41:09 so, who decides eg. what we retweet on the @debian account? 18:41:22 buxy and madduck I think 18:41:22 boutil: oh, thx, forgot that one. 18:41:43 zobel: no one in particular. madduck has had a few issues with that in the past. 18:41:51 We don't really have a workflow in place for it. 18:41:54 Maulkin: i have access to @debian too. but what will be retweeted? 18:41:58 madduck: ^ 18:42:28 it would be nice if we can get some sort of guidelines for social media set up 18:42:33 So a cool thing I have seen done, largely in activist communities is for things like twitter, is a way for supporters to register their accounts with the cause they are supporting, and for important stuff the parent entity can push out tweets, and they get automatically retweeted. 18:42:41 #info we have a workflow for "posting" but not a policy for answers, and repetitions of other people's messages 18:43:03 no strict policy please, but something that guides us. 18:43:42 Are we more cautious with twitter because of the larger audience? 18:43:53 during the release press marathon i mostly answered to @debian questions via twitter with my personal account because i was unsure if i may answer here with @debian 18:43:54 (Not all posts from the entity get automatically rebroadcast, just the ones that are like "call to arms" posts..) 18:44:05 cnote: yes 18:44:10 #info some RSS feeds (news and bits.debian.org) are automatically posted (in pump.io) via a python program 18:44:17 the take buxy and I took 18:44:29 on @debian retweets so far was that twitter is a chatty medium 18:44:33 I like that unofficial approach of responding from a personal account. 18:44:42 that works too 18:44:53 Which would regulate the main twitter account as an information push instance only. 18:44:58 but I also think anything that's positive/remarkable about debian and not offensive can be retweeted 18:44:59 hi madduck 18:45:10 hi, but I've been here since the start of the meeting! 18:45:12 albeit silent 18:45:15 but if someone says cools things about a debian blend, why not answer or retweet from @debian? 18:45:17 which you might not know of me ;) 18:45:25 zobel: yeah, exactly 18:45:43 that is why i ask for guidelines. 18:45:54 zobel: I think it'd be cool, but what if its something that we don't really want to mistakenly 'endorse'? 18:46:05 those also help newcomers, when we add more persons to @debian 18:46:24 #info the different networks work differently, e.g. "share" is for followers only in pump, retweet is public in twitter. And there are different communities. 18:46:42 zobel: I think it'll be hard to create such guidelines, but I am not opposed 18:46:54 why do we consider twitter as unofficialy? only because it is commercial? 18:47:10 same for fb and g+ 18:47:13 so maybe the people handling an unofficial account could agree on how to deal with it, and describe their ideas to the mailing list? 18:47:14 So, I did want to touch on that too. 18:47:21 #info idea I had: handle the various social networks like gettext translations so that messages are not necessarily posted to e.g. twitter until someone "translates" it 18:47:23 zobel because they are not free-software? 18:47:38 because these platform do not promote free software? 18:47:39 * Maulkin isn't clear why non-free platforms have to be unofficial. 18:48:14 * zobel agrees with Maulkin here. we use HP hardware to host our services, but you don't get them for free 18:48:24 we pay money for them when we buy them. 18:48:25 We have, for example twitter.com/fsf twitter.com/fsfe etc... 18:48:26 Technically our presence in the medium makes it official. 18:48:39 cnote: exactly. 18:49:13 I think we should move on, and maybe set a meeting only for social networking... 18:49:24 larjona: ack 18:49:25 one quick item 18:49:28 I liken these social networks to a new form of media. like television or newspapers before, but somehow even more powerful.. 18:49:59 Though this may be kicked to the second social meeting, but are we sharing the same information on both/all mediums? 18:50:16 cnote not exactly 18:50:29 If something is ACKed as a from a DENT, does that automatically make it ok to tweet/quit? 18:50:34 cnote: we try. 18:50:38 Which is how I look at it. 18:50:39 twitter posts planet RSS for example, pump.io not 18:50:53 well, move on! 9 minutes left! 18:50:58 Ack 18:50:58 #topic Status of Press Coverage : distribution of work, call for help, new ideas 18:51:02 Sorry, I'll table that. 18:51:24 I think this is about maybe mailing or including a line in DPN, so people contribute to the wiki page 18:52:06 it is also to collect NEWS items that were posted by other press media. 18:52:17 larjona: you mean collecting articles about Debian on other media? 18:52:24 i think we had a webpage about that. 18:52:36 I mean: press coverage is a wiki page were we gather debian mentions in other media 18:52:39 Yes we did. Its outdated very much. 18:53:01 larjona: you mean an open area where users can post something they've seen in the wild? 18:53:04 * Maulkin suggests a google news alert. 18:53:15 #info this topic is about keeping https://wiki.debian.org/PressCoverage updated 18:53:57 oohh. I see the value to it, but its a lot of upkeep to it I imagine. 18:54:03 Maulkin the google news alert is already here https://wiki.debian.org/Teams/Publicity/#Tracking_press_coverage 18:54:37 Excellent :þ 18:54:55 I think few people know about the existence of those wiki pages, that's why my proposal is to mention about them in a DPN or mail 18:55:13 i feel like we will meet for 2h, which is quite normal for new established irc meetings... 18:55:20 + 18:55:22 so Publicity workforce is focused in the "big" tasks, and this one, I hope other Debian contributors can handle 18:56:02 larjona: I see no issue with adding it as a blurb or mention in the DPN. 18:56:09 can those persons cry, who can NOT stay here for another hour? 18:56:20 * larjona is not sure 18:56:21 * madduck cries 18:56:37 but i am happy to read backlog and slot in 18:56:46 okay. 18:56:52 same for me, and Maulkin hopefully can go on chairing? 18:57:00 I can't really focus for another hour.. but should be able to be around if I am pinged when my agenda item comes up. 18:57:01 madduck: anything not yet covered you need to talk about now? 18:57:02 * Maulkin nods 18:57:09 #action larjona to send DPN paragraph about press coverage 18:57:10 Though I'd quite like to leave work and go home :) 18:57:26 Separately with all the twitter people here, can we come up with a quick procedure for questions we have? 18:57:29 zobel: I would find it useful if our team took a more proactive stance on covering DebConf in general 18:57:39 After or via email I mean. 18:57:50 i.e. helped establish a sort of timeline when we publish what kind of news about DebConf 18:57:50 madduck: ack. 18:58:15 madduck: i also would like to see debconf linked directly from https://www.debian.org/index.html. 18:58:22 because IME also as DebCOnf press office for 3 years, this is a hard job to just bootstrap in a new team 18:58:31 zobel: re-ack. 18:58:52 I am surprised it is not on the main page! 18:59:06 which brings me to an other item: Debian promotion. 18:59:14 I think that topic deserves a whole meeting... 18:59:20 yeah...www. 18:59:23 (debconf I mean) 18:59:25 See what Tolimar used to do - asking for talks he could prepare a press release out beforehand... 18:59:28 well www too... 18:59:41 I'd like to see it be a bit more dynamic. For debconf/debday/etc... 18:59:48 Just a small corner. 18:59:51 moving on.... 18:59:54 #topic Status of Blog (bits.debian.org): distribution of work, call for help, new ideas 19:00:00 ana is not here I think... 19:00:01 zobel: oh yeah, and preparing for events like the DPL election and releases in advance, like Tolimar used to do 19:00:06 madduck: yup 19:00:16 Can't we just clone Tolimar? :) 19:00:26 he's been busily doing so himself 19:00:31 :) 19:00:34 move on 19:00:35 #topic Possible new services or revival of services: Events, calendar service, promote Debian 19:00:38 i am also missing the "Meet debian at the following booth at CeBIT, ...." 19:00:56 zobel this is on-topic (events!) 19:01:18 Do we have somebody from the events team? (is there an events team?) 19:01:30 I sense a delegation coming 19:01:34 now that events is on the wiki, it has become very hard to follow and add the new ones to the DPN 19:01:45 Maulkin: is it only my feeling or is debian WAY LESS present on events in the past 2-5y? 19:01:52 #info now that events is on the wiki, it has become very hard to follow and add the new ones to the DPN 19:02:21 Thete's many events teams: https://www.debian.org/events/ 19:02:22 Ack. 19:02:51 There's far fewer linux specific events these days. Debian UK used to go to 3+ a year. They basically don't exist 19:03:13 (Essentially, people know what this linux thing is now) 19:03:27 there is CeBIT, LinuxConf, linux.conf.au, apachecon 19:03:32 where we used to be present. 19:03:57 yeah, so there's conferences, which are slightly different from events. 19:04:24 FOSDEM still happens. 19:05:09 What's needed to do? Improve our connections with the other communities? Find people to bring news about what's being done already? 19:05:42 Ask Debianers to be more visible as "Debian" when they go to the conferences? 19:05:53 larjona: follow debian-private for "i am going to conference XXX" and ask for to being visable. 19:06:11 and mail the bigger conferences with own debian booth to DPN 19:06:14 at least. 19:06:18 * Maulkin nods 19:06:27 who volunteers to handle that? 19:06:34 i think a statement such as "Debian will fund travel&accom for X people representing us at Y" will also help a lot 19:06:38 maybe do a "we are present at foo, bar, baz" twice a year, if we know way beforehand. 19:07:14 madduck: yes and no. quite a lot debianers will be there on paid work time. 19:07:17 and in general, we'll need to make sure that everyone knows how to easily let us know about stories, and then be able to track them properly. 19:07:36 zobel: yeah, but they won't feel responsible for the booth and e.g. the press work beforehnad 19:07:54 What kind of events are we looking for info on? (I ask because I organize a lot of FLOSS/Linux event in NYC, and could easily forward info on them to someone if I know what people were interested in.) 19:07:55 depending on the company. 19:08:00 right 19:08:12 #info we need somebody to revitalize the situation for events: assist people going to conferences to make Debian more visible, gather info for the DPN.. 19:08:15 it would be good to have the *one* designated official debian representative in charge though 19:08:28 for each event 19:08:46 i must go now, unfortunately. sorry! :( 19:08:52 I can make a proposal to the mailing list 19:09:09 bgupta: the bigger ones, best where we could also man a booth. 19:09:19 and have a standup and flyers. 19:09:41 we have flyers as PDF, they just need to be printed, best case professinally. 19:09:42 #action larjona will review the website wiki and historic info about events and make a proposal to the list for revitalizing 19:09:53 larjona: ack. 19:10:01 wfm 19:10:05 hopefully to find somebody else to handle that :) 19:10:13 wfm < I didn't understand 19:10:14 this is the time to make madduck responsibe :) 19:10:24 haha 19:10:31 wfm = works for me 19:10:32 #topic Planning coverage of "big events" (releases, elections,...what's next?) 19:10:41 Ok.. then not the ones I organize.. which are largely technical talks. (I say largely because they are sometimes freedom talks too) 19:10:50 zobel: If there's someone who'll take on the job, Debian can pay for things like flyers. 19:11:12 #topic Events 19:11:17 Maulkin: i have like 2k flyers at credativ, paid by FFIS. 19:11:46 zobel: Cool :) 19:11:55 #info it would be nice to handle info/requests about merchandising etc 19:12:03 Maulkin: and we have a good print company two roads from us, that could do a Debian roll-up banner for 60 EUR 19:12:16 ok, move on? 19:12:17 I like the banner idea! 19:12:25 zobel: Approved. Go buy. 19:12:31 Nice. 19:12:34 #topic Planning coverage of "big events" (releases, elections,...what's next?) 19:12:35 Move on. 19:12:36 Maulkin: and send to where? 19:12:49 we need to organize that, somehow... Maulkin, later. 19:12:53 zobel: → later :) 19:13:00 I suppose the next big thing is DebConf isn't it? 19:13:03 at least show it off at DC15 please 19:13:06 I think that the live coverage of the release went quite nicely 19:13:31 thanks to the fact that we were on different timezones 19:13:48 Did it help the previous preparation? 19:13:51 I have mixed feelings on it, overall it went very well for the social media portion and getting tweets/quits/dents out at the same time. We had great coverage. 19:13:52 boutil: yes, but on twitter some persons were a bit annoyed about the huge amount of twitter items from @debian.... 19:14:22 maybe we should have a filler for the whole year? 19:14:24 zobel: but thats only once in a while. this was a big deal. 19:14:39 there will alwayss be somebody annoyed on the internet... 19:15:07 The issues I had were that we still managed to leak ourselves with the bit.d.o going out prior to the social media 'official release'. 19:15:08 #info release coverage went nicely, the filler helped, and the geographical diversity :) 19:15:11 Just on that point, a bit of feedback from a couple of the release team members (paraphrasing): "WTF? Where the hell did all those people come from, and created all that content? Did Debian suddenly manage to get a highly professional marketing team join it or something? I was absolutely blown away, it was amazing." 19:15:25 o/ 19:15:57 Maulkin: cool! 19:16:13 #idea to have a filler with ideas for microblog or even DPN 19:16:27 So my larger issue was that while we were unified on one end, we were not on the other. Second was the constraint on the twitter character limit which we have to consider in the future for rapid information release. 19:16:56 #info we need to prepare the items according to the media constraint (number of chars, titles, tags...) 19:17:06 cnote: ack, i needed to rephrase several texts to meet the twitter 140-character limit. 19:17:08 I think madduck made mention we could link to a larger posting, but I don't know how many people are willing to read a post that tells them to go someplace else. 19:17:19 we could have a bot posting items from the filler for the next release. 19:17:29 cnote I didn't understand "while we were unified on one end, we were not on the other." 19:17:44 So that real people can concentrate on items about the actual release process 19:17:55 larjona: the tweet/dent/quiter were good but the bits.d.o broke the news before those 3 did. 19:18:27 boutil: yes on a bot, as it can do all 3 of those and something else in an automated fashion. 19:18:33 you mean it went published in bits before it should? 19:18:48 (and then, in pump.io too, because of the RSS feed...)? 19:18:48 Yes. Due to the build I believe. 19:18:53 * boutil was sleeping at that time 19:18:54 yes. 19:19:22 ok so how can we do better next time? 19:19:30 Also yes on the bot again, I twitted for 10 hours. Fingers...poor fingers... 19:19:33 it would be helpful if bits.debian.org could work with us, and not against. why did bits.debian.org had a different release text? why could we not have used bits.d.o for coverage that is more than 140c also during the same ammount of time. 19:19:49 but i guess we need to discuss that, when ana is around. 19:20:11 (why is bits.d.o different from publicity team, ooi?) 19:20:12 yes, I think it's better to leave for other meeting 19:20:15 zobel: the reason for it made sense, but it just threw everything else off. 19:20:55