=== maclin1 is now known as maclin === maclin1 is now known as maclin === maxb is now known as Guest16693 [16:00] o/ [16:01] o/ [16:01] o/ [16:01] o/ [16:01] o/ [16:02] \o [16:02] o/ (sorry) [16:02] who chairs? [16:03] heh, I will [16:03] #startmeeting Weekly Ubuntu Foundations team [16:03] Meeting started Thu Dec 7 16:03:15 2017 UTC. The chair is cyphermox. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:03] Available commands: action commands idea info link nick === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Weekly Ubuntu Foundations team Meeting | Current topic: [16:03] #topic Lightning rounds === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Weekly Ubuntu Foundations team Meeting | Current topic: Lightning rounds [16:03] echo $(shuf -e slangasek bdmurray xnox tdaitx doko sil2100 rbalint infinity cyphermox mwhudson rcj philroche Odd_Bloke tribaal fginther) [16:03] tdaitx fginther xnox tribaal philroche mwhudson rcj bdmurray Odd_Bloke infinity rbalint cyphermox doko slangasek sil2100 [16:03] Phew, win [16:04] is tdaitx around at all? [16:05] heh [16:05] fginther: [16:05] (we'll come back if he shows) [16:05] * Fixing an issue causing duplicate image lists in the cloud images header [16:05] * Updated our manual publication documentation for a partner cloud [16:05] * Updated the naming pattern for the minimal images in our CI pipeline [16:05] * Fixed a path issue related to resolv.conf in a partner image [16:05] * Fixed a clock drift issue that was breaking publication to a partner cloud [16:05] * Reviewed Secure Boot on UEFI document [16:05] * Poked around on AWS's updated Cloud9 service [16:05] (done) [16:05] Tribaal, you're up [16:05] xnox is on vacation [16:06] * Partner work, in particular GKE stuff. [16:06] * Prepared an SRU for the vagrant user changes into Xenial (LP:1569237) [16:06] * Some UEFI work and tests for partners [16:06] (done) [16:06] * AWS re:Invent last week [16:06] o/ [16:06] * Work on partner cloud image changes [16:06] (done) [16:06] rcj: [16:06] * cloud-image build system care and feeding [16:06] * cloud-image partner meetings [16:06] * Added NVMe io_timeout tuning to AWS EC2 cloud images (16.04 and later) per http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html#timeout-nvme-ebs-volumes [16:06] (done) [16:06] * Finished work on boot speed metric gathering [16:07] * Adding a metric to allow us to track Docker Hub image age [16:07] * A variety of partner work [16:07] (done) [16:07] rbalint: [16:07] (No infinity in the channel.) [16:07] yup [16:07] infinity is away too afaik [16:07] (short week) [16:07] * gce-compute-image-packages updates [16:07] * livecd-rootfs fixes [16:07] * internal testbed setup [16:07] (done) [16:08] cyphermox: [16:08] - netplan SRU validation [16:08] - investigate d-i crashes reported by powers.j (LP: #1736770) [16:08] - document UEFI SB design in wiki (wiki.ubuntu.com/UEFI/SecureBoot) [16:08] - shim review / harass Peter to approve our shim [16:08] Launchpad bug 1736770 in linux (Ubuntu) "debian-installer/main-menu changes priority" [Undecided,Incomplete] https://launchpad.net/bugs/1736770 [16:08] - quick review of NM DNS/search patch [16:08] - grub TSC bugfix for some new Intel systems (LP: #1734278) [16:08] - preparing SRU for TSC bugfix [16:08] - investigating grub/shim/maas bug in chainloading from MAAS. [16:08] HIGHLIGHT: our shim is reviewed. [16:08] Launchpad bug 1734278 in grub2 (Ubuntu Xenial) "Grub2 cannot boot up when 8254 time function disable" [Critical,Triaged] https://launchpad.net/bugs/1734278 [16:08] LOWLIGHT: we don't have the email to track that yet. [16:08] (done) [16:08] doko? [16:09] - analyzed Python2 demotion from main, excluding OpenStack [16:09] - filed ~50 bug reports, 35 still open [16:09] - fixed the easy ones, worked on the seeds, pinged other teams [16:09] - https://bugs.launchpad.net/ubuntu/+bugs?field.tag=py2-demotion [16:09] - python 3.6.4rc1 release candidate, 3.7.0 alpha [16:09] - gcc-7 update [16:09] - archive maintenance, finished some open transitions [16:09] - packaged icedtea 2.6.12 (OpenJDK 7) [16:09] (done) [16:09] no slangasek [16:09] sil2100: [16:09] uh oh [16:10] - Regular SRU work [16:10] - New kernel SRU cycle (CVE respin) [16:10] - ubuntu-image: [16:10] * Pushing u-i 1.3 to devel and stable series [16:10] * Investigating absurd armhf ADT failure - it's magic [16:10] * Fighting with trying to run the bionic armhf envionment - nothing working, wasted time [16:10] - Ripping out the deprecated Bileto -gles support [16:10] - Looking into how Bileto handles britney [16:10] - Preparing some test-image stuff for T-Systems [16:10] - Updated uvp-monitor to 2.2.0.316, SRUed it to xenial and trusty [16:10] (done) [16:10] * HIGHLIGHT: Added NVMe io_timeout tuning to AWS EC2 cloud images (16.04 and later) per http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html#timeout-nvme-ebs-volumes [16:10] (bad day today) [16:10] ^ forgot to mark it before [16:11] rcj: thanks! [16:11] ok, next up [16:11] #topic http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-aa-incoming-bug-tasks.html === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Weekly Ubuntu Foundations team Meeting | Current topic: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-aa-incoming-bug-tasks.html [16:11] woops [16:11] tdaitx: your lightning round? [16:13] alright, no tdaitx after all [16:13] Bug review? [16:13] are we quorate to do this? [16:15] nothing new / changed in the Criticals/Highs [16:16] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721839 [16:16] Launchpad bug 1721839 in systemd (Ubuntu) "Services asked for by UDEV do not get triggered" [High,Confirmed] [16:16] what about this one? [16:16] nobody is chiming up, let's punt to next week [16:17] #topic AOB === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Weekly Ubuntu Foundations team Meeting | Current topic: AOB [16:17] any other business? [16:18] (HIGHLIGHT)i was working on Hibernation of spot agent in EC2 but i could not talk about it :-) [16:18] rbalint: thanks! [16:18] .. of spot instances .. [16:19] that's it then [16:19] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [16:19] Meeting ended Thu Dec 7 16:19:21 2017 UTC. [16:19] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-12-07-16.03.moin.txt [16:19] thanks everyone! [16:19] o/ [16:19] o/ [16:21] o/ [16:53] flexiondotorg, elopio, ahoneybun, jose, marcoceppi, wxl: are you going to join the meeting? It's in 10 minutes. [16:53] I am. [16:54] * Kilos lurks [16:55] I'm around [16:55] just need a link to it [16:55] hello Kilos, feel free to participate too. [16:56] ahoneybun: https://community.ubuntu.com/t/call-for-topics-community-council-meeting-20171207/2571 [16:56] i have been quiet for many months elopio so ill try catch up [16:57] thanks so -meetings [16:59] So, we start in 2min [17:01] #startmeeting Community Council meeting: 20171207 [17:01] Meeting started Thu Dec 7 17:01:17 2017 UTC. The chair is elacheche. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [17:01] Available commands: action commands idea info link nick === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council meeting: 20171207 | Current topic: [17:01] Hello everybody to the CC meeting.. Present CC members, please raise hands.. In meanwhile I'll share some links [17:02] Today's agenda → https://community.ubuntu.com/t/call-for-topics-community-council-meeting-20171207/2571 [17:02] Last meeting summary → https://community.ubuntu.com/t/community-council-meeting-20171116/1349 [17:02] hello, thanks elacheche for leading this one. [17:04] With pleasure [17:05] ahoneybun: are you going to participate? [17:05] everyone around, please review the 2 links, then we will proceed with reviewing progress from last meeting [17:05] it doesn't seem that we have quorum, but we can at least get the conversations started, and the rest can comment on the hub afterwards. [17:06] elopio: afaik, the quorum is just for votes, we will not vote, we will discuss things, then move them to somewhere else for detailled discussion then vote later on hub or here in an other meeting [17:06] ok [17:07] Both of us already read the links, let's wait an other 4min, before starting the discussion, maybe someone else is reviewing them :) [17:11] #topic Update of the action items from the previous meeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council meeting: 20171207 | Current topic: Update of the action items from the previous meeting [17:11] So, let's talk about actions from last meeting [17:12] #subtopic @popey and @elacheche to start a discussion about the wiki [17:13] Sorry, it's on my to-do but is a big topic so not had time to get to it. [17:13] Big as in, will need some research and thought before I post. [17:13] * jose waves [17:13] So, I didn't talk to popey about that.. But, I was talking to some floks from my LoCo that are interested to join the talk, people like nzoueidi, nizarus, pavlushka, I think that Kilos will be interested to join the discussion as well [17:13] Maybe it's worth me starting the discussion and point at an etherpad doc or something so we can work on it together [17:14] Sure, I imagine quite a few people want to join in :) [17:14] o/ [17:14] popey: That's what I was about to suggest, just start the discussion somewhere (HUB or public ML), then we can invit people to join the brainstorming [17:15] ok [17:15] I think we shouldn't hurry, because if we start with the wrong foot the discussion could be not productive at all. So, I'd say you two should take as long as needed, or wait until you have less tasks. [17:15] hello pavlushka [17:15] Hello elopio :) [17:15] jose: are you going to participate in this meeting? [17:15] * pavlushka waves to popey [17:15] heyo folks [17:16] yep going up the stairs to a chair and wifi [17:16] welcome pavlushka ahoneybun jose :) [17:16] hey ahoneybun :) [17:17] I agree with elopio.. popey can we discuss this in PM during the next 2 weeks, so we can come back with an action roadmap for the next Dec meeting? [17:17] ty elacheche [17:17] Sure [17:17] heyo pavlushka and elacheche [17:18] Great.. So our next task is to create an action roadmap then share it during the next meeting. [17:18] thanks popey and elacheche [17:18] Any other thoughts, ideas about this topic, or we can check the next one? [17:19] yay here [17:20] jose: any comments? :) [17:20] nope. not atm. I'll forward them once I catch up. let's move on :) [17:21] OK, let's move on.. [17:21] #subtopic UCADay [17:21] don't wanna stall you for being late [17:22] The next action from last meeting was the UCADay.. and I think thatI t was a success [17:22] You can check https://twitter.com/hashtag/ucaday?f=tweets&vertical=default&src=hash [17:23] I agree, lots of people making the work of each other visible. [17:23] I don't know if someone partitipated in other social networks or not, I'm not a heavy user of anything other than twitter & diaspora.. elopio do ou have more details about this? [17:23] I saw G+ as well [17:23] the Ubuntu accounts in every social network were full of likes [17:23] Great! [17:24] what's great of this is that the work we do starts attracting more people, and then our calls for action get more hands. [17:24] Should we do a follow up action.. Like an early reminder for next year ucaday or something else? [17:24] I think we should try to get a very noisy event once a month. Last month ucaday, this month google code-in, we need to think of something for january. [17:25] to keep the gears moving, that's a good one [17:25] +1 [17:25] I think we could do a community member day in each month or couple months [17:25] I think we should check the calendar of yearly events [17:25] as well [17:26] get in touch with the LC to figure out days for the global jam and such, and get a 'featured global event' each month [17:26] and since we're about to start next year, we can set probably 'featured global events' for Q1 [17:26] and work on them each Q [17:26] * elacheche is wondering why jose is in his head x) [17:27] lol [17:27] lol [17:27] great minds think alike [17:27] I tottally agree with that [17:27] Global Jam is in Feb right? [17:27] we should list global events [17:27] lets open a topic on the hub to receive proposals for the calendar next year, trying to spread the events to have at least once a month. [17:28] Global Jam is up to the LC I believe, not sure [17:28] as far as I remember when I was in the LC we set the dates [17:28] jose: The Global Jam is when the Beta1 is released [17:29] got it [17:29] So the next gloabl jam should be in "March 8th" [17:29] that could be our March 'ftg' [17:29] 'fge' sorry, didn't sleep yesterday [17:30] The LC just add that event to the LoCo dir, so LoCos can add it as localevent and we can have insight about who's running it [17:30] yep, and we can have a blog post on the planet each month to announce the event [17:30] the planet has huge reach outside the community as well, good place to get contributors from [17:30] On the fridge, will be better I guess :D [17:31] yep. fridge can go to planet [17:31] yep [17:31] Any other thoughts about ucaday and global events? [17:32] I'm set for now [17:33] nothing else here. [17:33] So, UCADay was a success, and we should plan a monthly global event to communicate about it.. So the next action is to plan and list global events for the 2018 Q1.. I am right or I forget about something? [17:34] I think that's it [17:34] * elacheche will see if meetingology still have the action command, so we can have a more visible log later [17:34] it should [17:34] I haven't touched it [17:34] #action Plan and list global events for the 2018 Q1.. [17:34] ACTION: Plan and list global events for the 2018 Q1.. [17:35] Next subtopic [17:35] #subtopic @wxl to announce the new loco council and help with the transition. [17:35] It's well done.. Thanks wxl :) [17:36] Any comments about that? [17:36] oo, about that [17:36] I'd say we should check in with the LC after they've held their first meeting to see how they're doing [17:36] Maybe if wxl is around he can share news about the transition [17:36] and if we can give a hand or they have questions [17:36] I agree with that [17:37] yes, let's make an action topic to tell wxl to send an update on the transition to the hub. [17:37] The next public meeting will be Dev 11, 2017.. (I know because my LoCo re-verification is that day) x) :D [17:37] I can bother him until he makes the post :) [17:37] :D [17:38] elacheche: good luck with that [17:39] #action Contact LC after theire 1st meeting and ask if we can help on something, ask wxl to send an update on the transition to the hub. [17:39] ACTION: Contact LC after theire 1st meeting and ask if we can help on something, ask wxl to send an update on the transition to the hub. [17:39] other thougths? [17:40] that's it from me [17:40] no comment on the monthly community member ? [17:41] monthly community member sounds good to me. [17:41] do you want to take lead that ahoneybun ? [17:41] highlights a member's work [17:41] ahoneybun: That will be with the planning for 2018 Q1 global event I guess :) [17:41] I can make a draft [17:41] Great ahoneybun [17:42] #action Plan and list global events for the 2018 Q1, ahoneybun will make a draft about a "monthly community member" event [17:42] ACTION: Plan and list global events for the 2018 Q1, ahoneybun will make a draft about a "monthly community member" event [17:43] anyr comments about LC ? [17:43] s/anyr/any [17:43] nop. [17:44] We move on then [17:44] #subtopic @Wimpress (aka flexiondotorg ) to investigate about publishing the community council RSS from the hub to the planet. [17:45] I don't think he's around. Let's ask him to update in the hub topic too. [17:45] I don't know if anyone else have updates about this.. flexiondotorg can't be with us today.. [17:46] Last time we talked about this, we find that the HUB have a RSS feed for each category, but we were not sure what the planet will sync if we add that RSS to it [17:47] So, I guess the only way to figure that out, is to host a private planet and test it, or just add the RSS feed to the live planet and see what will be synched or not.. I'm not sure if we remove the feed after that the content will be removed from the planet or not [17:47] too early for me :( [17:48] No problm wxl you can check logs later, and you can discuss with us the current subtopic :) [17:50] trying to find it XD [17:51] seems we don't post the usual format of meeting logs so i'll just go off of the summary [17:51] i.e. https://community.ubuntu.com/t/community-council-meeting-20171116/1349 [17:51] so: [17:51] #action flexiondotorg will share updates about "publishing the community council RSS from the hub to the planet." in a HUB topic [17:51] ACTION: flexiondotorg will share updates about "publishing the community council RSS from the hub to the planet." in a HUB topic [17:52] * still haven't seen a thread about wiki migration, unless i'm blind [17:52] * need to hear back from flexiondotorg on the marketing guerilla campaign, i think [17:53] wxl: the bot posts the meeting logs when the meeting is over. [17:54] next up? [17:54] I'm sorry, but it's almost an hour here. Can we go a little faster please? [17:55] this meeting's supposed to be 2h long though [17:55] elopio: The fridge calaneder say that we can have 2 hours :D [17:55] but yep, what's next on the list? [17:56] #subtopic @elopio to make a proposal for multilanguage in the hub. [17:56] * elopio makes a note to propose to change the meetings to 1h. [17:56] elopio: but that's not in the link to the full conversation [17:56] the link comes after #endmeeting and it appears that's where the logs end [17:56] it's supposed to be 2h first meeting of the month, 1h second meeting of the month [17:57] but if we vote and agree on moving all to 1h, I can change it on the fridge right now [17:57] I have access [17:57] wxl: take a look at the topics on the hub for the meetings, the full conversation is posted there. Not sure what you mean. [17:57] I think we better plan that for an other meeting :) :D [17:57] ok, I made the multilanguages proposals in the hub. One is for posts in a language that's not english. The other is for posts that are translated to multiple languages. [17:58] Or we should discuss it in hub or ml and ask all CC to vote [17:58] Any follow up actions elopio ? [17:58] we have been experimenting with this, and it works reasonably well. But there's a huge problem with languages that are right-to-left. [17:58] ok, I'll take an action item to send an email to discuss changing meetings from 2h to 1h [17:59] elacheche: just, keep insisting on people to post in their languages when it's relevant, to invite more people into the community. We will keep experimenting and adjusting. [17:59] OK elopio :) [17:59] +1 jose [18:00] More comments about this subtopic or we move to the next topic? [18:00] move on [18:00] So, we're good with updates about actions from last meeting, we go back to todays agenda [18:01] #topic Google Code-in updates === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council meeting: 20171207 | Current topic: Google Code-in updates [18:01] elopio: I think you have updates about that? [18:01] This has been amazing. Already 170 tasks completed, more in progress [18:02] we have seen code contributions, translations, tutorials, and I guess many more things because I'm only looking at the 20 snapcraft tasks [18:02] if you haven't mentored anybody yet, I recommend you to do it. It's very nice to see these young people enjoying ubuntu and the work we are doing. [18:03] is there a way to look at the tasks done and to be done? [18:03] we still have one month to go, so new tasks can be added. And please, promote the event so more students can join. [18:03] it's all on google code-in, ahoneybun [18:03] tried looking myself a min ago [18:03] codein.withgoogle.com [18:04] It's good to hear that elopio [18:04] elopio: Can you write a blog/fridge post about that? We can use the post to promote the event.. [18:04] also, I'm having problems to find mentors in other languages. I'm trying to build a list of trusted translators that will help us review the multilanguage projects [18:05] if you know somebody who speaks romanian, please let me know. [18:05] *sighs* language barriers :/ [18:05] elopio: I do know someone [18:05] say hi to him from me ;) [18:05] elacheche: I'm too busy with work and mentoring these days, so no, no post yet. I have to write a summary about the snapcraft experience when we finish. [18:06] OK, no problem.. [18:06] #action Promote the google code-in event [18:06] ACTION: Promote the google code-in event [18:06] introduce me please ahoneybun [18:06] fwiw kubutu just had a meeting about onboarding more packagers and creating some tutorials, etc. and i mentioned google code-in as a potential resource to use with that [18:06] elopio: he hangs around in #kubuntu-devel [18:07] also lubuntu has been kind of busy, but we have it on our task list to add some events [18:07] meanwhile i've been hanging out in #ubuntu-google a bit here and there [18:09] cool.. any actions to add about gci? [18:10] just the recommendation to join as a mentors [18:11] #action Promote the google code-in event to the public, and recommend community memebrs to join as mentors [18:11] ACTION: Promote the google code-in event to the public, and recommend community memebrs to join as mentors [18:11] Next topic [18:11] #topic Deal with the CC ML spams === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council meeting: 20171207 | Current topic: Deal with the CC ML spams [18:12] right now, afaik, the list is unmoderated [18:12] uh, not much we could do there because of that [18:12] canonical spam filter is already getting a bunch of it [18:12] ^^ [18:12] For this, we should talk to marcoceppi_ to have the ML get emails only from members [18:12] and he will need to check every other email and allow it or not to go to the ml [18:12] uh [18:13] i would happily deal with that [18:13] I think that'd be a challenge+problem [18:13] every other council does that [18:13] I believe the reason why it is unmoderated is because we wanted to be easily reachable [18:13] and people were discouraged from emailing us due to getting that 'in moderation' email [18:13] but if inboxes are filled with spam, how easily reachable are we? [18:13] when? [18:13] again, the loco council and the membership board both operate this way [18:13] In my LoCo ML we accept emails only from memebrs, everything else is in hold until the ml admin approve or remove it [18:13] previous CC iirc. I can ask around why they opened it up [18:14] because it was moderated before, but they changed it [18:14] there *has* to be a reason why [18:14] we should be able to change the moderation message template [18:14] wxl: marcoceppi_ is able to do that as he's the ml admin [18:14] OR we could do what flexiondotorg suggested and move it to the hub [18:15] I'd suggest holding it off until we find out why they opened it up. I can take it as an action item [18:15] but that's just my opinion [18:15] #action jose will investigate why old CC opened the ML for everyone [18:15] ACTION: jose will investigate why old CC opened the ML for everyone [18:16] * elacheche statts to lose caffeine in his blood stream, and start to miss read/write things x( [18:17] meanwhile i SEEM to remember that flexiondotorg was giong to investigate how the hub might work so we should check in with him on that [18:17] OK.. I guess until jose investigates that we can't do big thing, if we will vote later on turn on moderation we can ping marcoceppi_ to do that.. [18:17] up to you guys [18:17] we can close it off if you'd like while I investigate [18:17] was just my point of view [18:17] wxl: yep, that should be the next topic [18:18] jose: we better investigate then vote about what to do :) [18:18] elacheche: i meant specifically as it relates to this current topic [18:18] flexiondotorg: can't be with us today.. So we need to ask him later I guess :/ [18:19] make an action item for him? [18:20] OK, the next topic is all about that wxl :D can we move on to the next topic? Or there is other coments about this one? [18:20] carry on [18:20] #topic Create a private HUB category for CC to use instead of ML === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council meeting: 20171207 | Current topic: Create a private HUB category for CC to use instead of ML [18:21] so NOW make the action item. :) [18:21] i don't think any of us have investigated this [18:21] i'll also say that we should investigate this only if two other conditions are true: [18:22] I don't remember that flexiondotorg said that he will investigate this :D But it's his task until he mention that he do'nt want to do it :D [18:22] well, one condition [18:22] that for some reason or another we cannot "resolve" the mailing list issue as previously discussed [18:22] #action flexiondotorg will investigate how the hub might work so we should check in with him on that [18:22] ACTION: flexiondotorg will investigate how the hub might work so we should check in with him on that [18:23] that may be because we believe we should not moderate the list or that in some way we cannot provide a solution that would work for the community [18:23] that said, we need to wait for jose before even doing that action [18:23] To be honest, I'm not a fun of the HUB, and I like the ML and the wiki more than the HUB.. [18:24] jose elopio comments on this topic? [18:24] the hub is a great tool, and a lot of people are using it, but we don't NEED to use it foreverything [18:24] i mean unless you can play doom on it.. [18:24] +42 wxl [18:25] OK, we move on to the last topic, unless someone disagree [18:25] #topic Create a list of CC ressources and make clear the usage of each. === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Community Council meeting: 20171207 | Current topic: Create a list of CC ressources and make clear the usage of each. [18:25] I'd say +1 wxl [18:25] I will only keep insisting that we should have only public discussions every time somebody starts a private one. That's my comment :) [18:26] ^ big -1 on that one [18:26] i believe that there is a time and a place for a private discussion, but not the vast majority of things [18:26] I have to drop now, but I'll check + comment once we're done. sorry guys [18:26] o/ [18:26] feel free to ping me if you need me [18:27] also there's some things that don't have enough bearing on people that decision making needs to be done by everyone [18:27] This one is my idea, I think that we need to list ALL CC ressources in one place, by ressources I mean things like ML, IRC, HUB, Trello, etc.. And come up with a clear description that tells why we need each of them and when we need to use any of them [18:27] do it :) [18:28] OK then [18:28] elacheche: like, [18:28] #action elacheche will investigate CC ressources (ML,IRC, HUB, Trello, Wiki, etc) and list them all in one place (HUB or/and wiki page) [18:28] ACTION: elacheche will investigate CC ressources (ML,IRC, HUB, Trello, Wiki, etc) and list them all in one place (HUB or/and wiki page) [18:29] updating and completing this text? https://community.ubuntu.com/t/what-is-the-ubuntu-community-council/706 [18:29] yes [18:30]