Re: [Debconf-team] Swag, extension cords, and Open weekend PC's
On 30/06/16 06:09 PM, Bernelle Verster wrote: > * Swag for bags (that I know of): > Ubuntu (pens and stickers) the bag taht xnox gave us also contained ubuntu buttons too. normally they should be in the orga room. if they are not I can bug others from my flight to find them signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] DC16 feedback summary
thanks for the summary, this helps to get a better picture of feedback. On 28/07/16 05:24 PM, martin f krafft wrote: > - the talk details template should include room and time > information. Attendee said: "I collected some links of talks > I want to attend before debconf. When I opened the links again, > I did not had the time and room information on theses links." [1p] on this front, I did submit a patch to upstream Wafer exactly for fixing this, but new code was not pushed to production during the conf I believe for lack of availability and also to avoid risking to break the conf web site during the event. so next year's web site should have the info :) signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] dc17 haz no website, let's fix it!
Tiago Bortoletto Vaz: > I propose a hacking/bier/sprint/whatever dedicated to it. I'm out of > town from Dec25, but any datetime before that works for me. Can be > anywhere in Montreal. If you like to be in the woods we can make it at > my place (Baie-D'Urfé). Otherwise we can meet more downtown-ish. > Please confirm you like the idea and you'd be available for that, then I > come back with a more concrete plan. I'm up for a sprint! any time before 23rd except on the 18th. for the sprint, the best thing would be to try and have some VMs+wafer. I can try and have a jessie with this installed in my vagrant setup. I invite others who can also have such a setup to prepare it before the sprint. this way we'll be able to test different changes. signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] dc17 haz no website, let's fix it!
Philip Hands: > However, I note that it shows me nothing in some browsers (e.g. midori > and qutebrowser). By nothing, I mean that the area where the animation > should be remains blank -- the rest of the page is as it should be. > > I'm afraid I have no idea why. Just thought I'd mention it in case > there's some way of providing a fall-back image, or some such. this is not informed.. but a quick guess would be a lack of support for SVG (maybe combined with animation) in those browsers. signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Debconf Accomodation 13 - 16
shirish शिरीष: > The only thing is I dunno (for debconf i.e.) if college would be > session or not then and would there be any noise level issues. Have > put it in house rules as couple of question marks During DC17 the college will almost be only used by DebConf. There is going to be some activity, mostly for preparing the next semester but there will be no courses with students. signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
[Debconf-team] Reminder: Meeting on monday 20th at 15:30 UTC
Hello all, This is a reminder about tomorrow's (february 20th) meeting that will happen at 15:30 UTC on the #debconf-team channel on the OFTC irc network. You can find the proposed agenda at http://deb.li/il9wc See you on then! signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
[Debconf-team] Next meeting IRL
Hello, It's now time to plan for the next IRL meeting for debconf 17. I'll be hosting the next meeting so some warnings might be in order: * I have a cat, so it might be annoying to ppl that are allergic * Partners and children are definitely welcome, but the place is not child proof (merely cat proof which is generally less safe). If you want to bring kids, I can make some changes if you send me some suggestions :) Please fill in the poll at: https://framadate.org/BphQ9pwQoh1AU6Rr The date will be decided upon on monday 27th during the debconf meeting. signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Request for our dear Wafer overlords (so we can better do Content Team work)
Gunnar Wolf: > It is time for me to start pestering the Content team (and I'm hereby > doing so!) so we can start rating and classifying talks; after all, we > have a deadline during April for announcing the first set of approved > talks. > > So... We could really really use pull request #348 to do our filtering > and discussing: > > https://github.com/CTPUG/wafer/pull/348 from that pull request, I can see that it's been merged upstream already. so what's needed is to pull from upstream. signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Next meeting IRL
Hi, Gabriel Filion: > I'll be hosting the next meeting so some warnings might be in order: > > * I have a cat, so it might be annoying to ppl that are allergic > * Partners and children are definitely welcome, but the place is not > child proof (merely cat proof which is generally less safe). If you want > to bring kids, I can make some changes if you send me some suggestions :) > The date will be decided upon on monday 27th during the debconf meeting. The date was chosen for the next in-person meeting according to ppl's availability who confirmed on the poll. We'll meet on april 9th at my place right after lunch, so aroun 13:00 EDT. I will send the address to ppl who put their names on the poll. see you soon! signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Looking to help out
Hi there Molly and znot...@hailmail.net, Molly de Blanc: > I've lent hands for the past couple of years around diversity > scholarships and a few other things here and there. Who (and what) needs > some extra hands and eyes right now? znot...@hailmail.net: > I live in Montreal. I've been using Debian since either Hamm or Bo. > I'm not a developer, just a humble user, but I love Debian. I'd like > to help with DebConf in Montreal this summer. Thanks for offering your help, it's most welcome :) We mostly use either this mailing list or the IRC channel[0] to organise. [0]: #debconf-team on the OFTC network. IRC is really the best way to poke ppl and to exchange ideas/details quikly with others. it's also there that we have regular meetings: currently we have meetings each monday at 10:00 EDT (so 14:00 UTC). Those meetings are mostly for status report and coordination but sometimes some actions come up and you can suggest your name to do them :) if you're uncomfortable with IRC, no biggie: you can suggest to take on a task by email too. we usually send meeting summaries to this list so you can see what's happening and what might need some attention. right now we're trying to: * finish what's needed to open up registration. this means some last changes are needed in the django website using wafer. * get some artwork done for banners * continue pushing to get more sponsors * review talk submissions, encourage ppl to send more of them, and eventually prepare a schedule * come up with a plan for day trip with different options that ppl can then choose during the conference * once registration is open, we'll have to bootstrap the bursaries program, reviewing requests for them etc. signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] DC17 budget approval request
Paulo Henrique de Lima Santana: > - Mensagem original - >> De: "Louis-Philippe Véronneau" >> >> Even considering these expenses, we will still have some money left >> budgeted in this account. If someone has ideas on neat things we could >> do, don't hesitate to reach out to us. > > Maybe hire a photographer to register all activities? > I'm not sure if it's common to have volunteers to do this during all days. last year, Valessio made a cool video with photos he took during the event. the video was shown during the closing ceremony. > With photos, we can post on social networks making a "live coverage". Some ppl might not want pictures of them taken, let alone posted on social media. It might be arranged though, it there is some way for attendees to communicate with the person taking pictures/videos. signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] debconf code of conduct and public sitemap
Hi there Shirish, shirish शिरीष: > There should be a link to the debconf code of conduct as a visible > link on the landing page, it is not there. > https://debconf17.debconf.org/ Yes we definitely do want to make the code of conduct super visible. The current state of affairs though is that there have been some revisions to this code of conduct and the revised version is still unapproved. As soon as we can get the new version approved, we'll make it visible on the site. signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
[Debconf-team] Revision of DebConf CoC
Hello, [cc'ed to antiharassment@d.o to get their opinion as well since they most likely will be the ppl who will need to enforce this code during the future DebConfs] During DebConf16 some ppl put some effort to rephrase parts of the code of conduct. We'd like to gather opinions on this rephrasing in the hope to get the new version, or an amended version, adopted. The old code of conduct is: https://debconf.org/codeofconduct.shtml The new code of conduct can be found here: https://titanpad.com/9l9d5GEMzA For convenience in reviewing this new text in an email conversation, I'm also including the text of the new version below so that ppl can comment it inline: --8<--- What is this? It's mostly a clarification of the existing CoC, which stems out of a lunch discussion between Bernelle, Marga, Michael, Valerie, Karen, Neil and Martin. Martin then worked on this on the flight back from Capetown and got Donna Benjamin involved, who works on the CoC and related steps of inclusion and incidence response for LCA. The draft has been unchanged since late September or so. DebConf Code of Conduct In a nutshell * We fully stand behind the [Debian Diversity Statement](https://www.debian.org/intro/diversity). * The rules defined in the [Debian Code of Conduct](https://www.debian.org/code_of_conduct), as well as the rules put forth by this DebConf Code of Conduct apply to every attendee of DebConf and throughout the entire time of the conference, at the venue, and off-site. * The dedicated [Debian anti-harrassment team](https://wiki.debian.org/AntiHarassment), as well as the organisers are available around the clock in case you need help. We promise to treat every incident discretely, confidentially, and without delay. * Be respectful, considerate, inclusive, and aware. * Speak up if you notice offensive behaviour, or inform the organisers. * Our attendees come from very different social and cultural backgrounds. Help each other find a common ground where everyone feels comfortable. Always assume the best intentions in other people, but never let that be an excuse. * Consequences for offenses range from warnings to being banned from the conference and the Debian Project. Our priority is to restore safety and comfort for everyone at the conference as quickly as possible. Our goal As organisers of DebConf, we strive to ensure that every participant can feel comfortable and make productive and enjoyable use of their time at our conference. We embrace diversity and value that our conference thrives upon the different backgrounds, personalities, traits, and preferences of our attendees. We fully stand behind the [Debian Diversity Statement](https://www.debian.org/intro/diversity). Our conference is an official Debian community event: The [Debian Code of Conduct](https://www.debian.org/code_of_conduct) applies in full. We acknowledge, however, that these rules are not enough in the context of a convention of hundreds of people from diverse backgrounds, sharing physical space for several days in an intense working and socialising environment. The purpose of this DebConf Code of Conduct is to set forth additional rules and procedures to maintain your safety and comfort. These rules apply to DebConf, as well as all related events, including those organised inofficially, such as excursions, evenings at the pub, sports, and other events. We require every attendee to abide by and uphold these rules. There are no exceptions, not for speakers, not for guests, and not for organisers. If your space, dignity, or freedom has been violated, every member of the organisation team is available to help. We have a dedicated [Debian anti-harrassment team](https://wiki.debian.org/AntiHarassment), and clearly defined processes enabling timely action to restore your safety and that of others. We promise to handle every incident with due diligence and full respect for your privacy and confidentiality. Do your part We are a diverse community. Sometimes this means we need to work harder to ensure we're creating an environment of trust and respect where all who come to participate feel comfortable and included. In addition to abiding by these rules, you can help us maintain a safe space for everyone. If you witness behaviour that is disrespectful or in violation of any of our rules, and you are comfortable to do so, please speak up and point out that the behaviour in question could make other people uncomfortable. Instead of confronting someone in a group (which could make them feel cornered), it might be better to take them aside, or ask one of their peers to carry on the message. Conversely, if you are told that your behaviour may have been inappropriate, don't take it as an attack on yourself, nor should you feel compelled to defend yourself. The best course of action is to apologise, try to understand what happened, and to avoid doing it again. People come from different bac
Re: [Debconf-team] Revision of DebConf CoC
Gabriel Filion: > During DebConf16 some ppl put some effort to rephrase parts of the code > of conduct. We'd like to gather opinions on this rephrasing in the hope > to get the new version, or an amended version, adopted. I forgot to mention: during the last meeting, we decided on a date before which we need to come to an agreement on this document: may 15th signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] Revision of DebConf CoC
shirish शिरीष: > The draft is somewhat long, could it be shortened otherwise people > will sign it just as they sign any terms of service (i.e. blindly) . I must concur that the code of conduct is too long and has many repetitions in it. .. we could base our efforts on work done by other folks that did a great job. and then maybe reintegrate some elements that were added to the DebConf CoC remash. One example is the Tails CoC. It's based on the Django CoC https://tails.boum.org/contribute/working_together/code_of_conduct/ This lists a bunch of CoCs and their differences. It could be a good tool to fetch elements we want from others: http://geekfeminism.wikia.com/wiki/Code_of_conduct Also a resource for this : https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/ signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] [rt.debian.org #6836] Migrating DebConf's KanBoard instance to DSA machines
Hey there pollo, (replying only on dc-team list since I'm not bringing anything new to DSA) Louis-Philippe Véronneau: >> 3) what's the expected SLA (roughly)? should/can the service be > redundant? > > I have no idea what a SLA is :( SLA is "Service Level Agreement". I guess normally it mostly means how much uptime is expexted (in terms of number of 9's -- or in reverse how much downtime is acceptable, which you address a little bit further down), but also defining who's responsible for what. More details in: https://en.wikipedia.org/wiki/Service-level_agreement > I don't think this needs to be redundant at all, as KB is not a critical > system and if it dies, people can wait a few hours until I fix it. > > I don't think this should be a "public" Debian service for now. I'm open > to making it "public" in the future, but my main concern at the moment > is migrating it off a personal machine so DebConf18 folks can keep using it. signature.asc Description: OpenPGP digital signature ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
