16:31:23 #startmeeting fedora_coreos_meeting 16:31:23 Meeting started Wed Dec 9 16:31:23 2020 UTC. 16:31:23 This meeting is logged and archived in a public location. 16:31:23 The chair is dustymabe. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:31:23 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:31:23 The meeting name has been set to 'fedora_coreos_meeting' 16:31:32 #topic roll call 16:31:36 .hello2 16:31:37 dustymabe: dustymabe 'Dusty Mabe' 16:31:40 .hello2 16:31:41 bgilbert: bgilbert 'Benjamin Gilbert' 16:31:52 .hello2 16:31:53 cyberpear: cyberpear 'James Cassell' 16:31:57 .hello2 siosm 16:31:58 travier: Sorry, but you don't exist 16:31:59 .hello sohank2602 16:32:00 skunkerk: sohank2602 'Sohan Kunkerkar' 16:32:02 .hello siosm 16:32:04 travier: siosm 'Timothée Ravier' 16:32:20 .hello2 16:32:21 jlebon: jlebon 'None' 16:32:48 red_beard: around today? 16:33:01 .hello redbeard 16:33:02 red_beard: redbeard 'Brian 'redbeard' Harrington' 16:33:09 yup. am today 16:33:12 .hello2 16:33:13 davdunc: davdunc 'David Duncan' 16:33:17 .hello2 16:33:19 jdoss: jdoss 'Joe Doss' 16:33:24 .hello2 16:33:25 lorbus: lorbus 'Christian Glombek' 16:34:08 #chair bgilbert cyberpear travier skunkerk red_beard davdunc jdoss lorbus 16:34:08 Current chairs: bgilbert cyberpear davdunc dustymabe jdoss lorbus red_beard skunkerk travier 16:34:53 #topic Action items from last meeting 16:35:06 * red_beard to investigate forklifting FCOS artifacts into OVH to see if 16:35:08 they work 16:35:10 * red_beard to open a ticket to strategize on FCOS RH summit presence 16:35:13 * jlebon to talk with King_InuYasha to see if they can be co-captains 16:35:14 for the proposed change to move the rpmdb path (#639) 16:35:17 * dustymabe and jlebon to talk to the systemd team to see if we can come 16:35:19 to agreement on a path forward for the fallback hostname behavior 16:35:21 introduced in systemd in fedora 33 16:35:57 #info jlebon and dustymabe have been working with the systemd team on the hostname issue. Unfortunately the simple revert didn't completely solve the problem. Will discuss more in dedicated meeting topic. 16:37:33 welp, half of those are me..... 16:37:56 so, if someone can bring the zodbot magic 16:37:57 .hello2 16:37:58 lucab: lucab 'Luca Bruno' 16:38:05 #chair lucab 16:38:05 Current chairs: bgilbert cyberpear davdunc dustymabe jdoss lorbus lucab red_beard skunkerk travier 16:38:12 red_beard: want me to re-action? 16:38:30 #info jlebon started conversation about rpmdb path move -- we're waiting for feedback from the rpm team 16:39:03 .hello jasonbrooks 16:39:04 jbrooks: jasonbrooks 'Jason Brooks' 16:39:14 #info forgot to open the ticket with regards to RH Summit (fortunately we've still got quite a few months) 16:39:30 #chair jbrooks 16:39:30 Current chairs: bgilbert cyberpear davdunc dustymabe jbrooks jdoss lorbus lucab red_beard skunkerk travier 16:41:16 #action red_beard to investigate forklifting FCOS artifacts into OVH to see if they work 16:41:19 #action red_beard to open a ticket to strategize on FCOS RH summit presence 16:41:23 i'll just re-action them for now 16:41:39 #topic delayed stable release / pending F33 migration 16:42:09 as mentioned in the action item #info above, we're working hard with the systemd and NetworkManager teams to unwind the mess around hostname handling in Fedora 33. We're trying to make sure that we know as much information as possible so we don't break people's existing setups. 16:43:07 We worked with the systemd team last week and agreed on a simple fix to revert the change in systemd. Unfortunately the simple fix that we thought would solve every problem had a weird twist. All of this is covered in detail in https://github.com/coreos/fedora-coreos-tracker/issues/649#issuecomment-741555046 16:43:36 TL;DR - we're still working through our options with the systemd team and sorry for the delay 16:44:00 thanks for keeping at it, Dusty! 16:44:30 if we want to discuss any details here I'm up for that, otherwise we can just keep it to the ticket 16:44:47 dustymabe: if we go down that road, we might take up the whole meeting :) 16:45:24 #info Unfortunately the simple fix that we thought would solve every problem had a weird twist and we're working through the options with the systemd team still. All of this is covered in detail in https://github.com/coreos/fedora-coreos-tracker/issues/649#issuecomment-741555046 16:45:31 :) 16:45:33 you need at least like 64G of brain RAM to load in all the information 16:45:40 ok I'll move on to the next topic 16:46:13 #topic Mount /boot as RO by default 16:46:22 #link https://github.com/coreos/fedora-coreos-tracker/issues/652 16:46:24 this one is for travier 16:46:35 TL,DR: Mount /boot as RO by default 16:46:45 We will be mounting /boot RO by default. bootupd and fwupd have been updated to handle this case. 16:46:54 Users should change kernel arguments and boot order via rpm-ostree only and should not edit files in /boot directly. 16:47:30 +1 16:47:37 It is still possible to remount RW but this is discouraged 16:48:27 This is preparatory work for not mounting /boot/efi by default 16:48:34 travier: the main benefit being: "The main thing we're accomplishing here is making the system more resilient against accidental damage from a sysadmin root shell as well as configuration management tools like Puppet/Ansible. None of those should be directly manipulating files on these partitions, they should go through the API of one of our projects (e.g. rpm-ostree kargs, bootupctl) 16:48:36 etc." 16:48:39 https://github.com/coreos/fedora-coreos-tracker/issues/694 16:49:00 my only concern would be that fwupd and bootupd have a way to detect if it's been mounted RO for some other reason, such as drive corruption 16:49:04 dustymabe: Thanks 👍 16:49:23 cyberpear: good point 16:50:04 I guess the operation would just fail? 16:50:10 cyberpear: I think private RW remount will fail for rpm-ostree and that should be reported in the logs 16:50:34 sounds reasonable if it works that way 16:51:04 travier: when is this work scheduled to land? 16:51:36 As dustymabe said, this is not a hard RO mount and rpm-ostree and fwupd are remounting RW in a private namespace to operate on /boot 16:52:06 we are currently waiting for a bootupd release with the remount code and then it should be ready to land 16:52:38 I know at some point we were thinking about using grubenv vars for some of our greenboot fallback stuff 16:52:55 i guess this might hinder that some? or we could just mount private RW if we ever got to that point 16:53:12 cc lorbus 16:54:49 oh well, seems like we'll cross that bridge when we get there 16:54:53 as part of the RAID work we've basically ruled out using grubenv 16:55:15 hm yeah good question. greenboot calls out to /usr/bin/grub2-editenv to manipulate the grub env 16:55:42 but OTOH greenboot isn't used in FCOS atm 16:55:47 #topic open floor 16:55:57 a whole lot of time for open floor today 16:56:00 The FCOS hands-on lab has been accepted for DevConf.CZ 2021! 16:56:06 travier: woot woot 16:56:21 i guess we do have jbrooks and red_beard here today, we could revisit the twitter @coreos handle discussion 16:56:49 nice submission travier on the hands-on lab. 16:56:50 lorbus: if needed, we will be able to teach greenboot to remount RW in a private namespace 16:57:29 davdunc: I think it was nasirhm as I didn't do the submission :) 16:57:44 travier: +1 16:57:55 red_beard, Do you want to weigh in on the twitter discussion? 16:58:01 dustymabe: can we topic it? 16:58:13 #topic twitter @coreos handle 16:58:28 done 16:59:13 I have some thoughts but want to wait for red_beard 16:59:58 i'm around 16:59:59 plays jeopardy music 17:00:15 sorry, so to be quite frank 17:00:37 based on the suggestions from before, it seems like this is the blind leading the blind 17:00:54 with little understanding of the ramifications of changing twitter handles, etc 17:01:13 and my stance is, if you don't understand it: don't touch it 17:01:23 What don't we understand? 17:01:41 * red_beard sighs 17:01:47 ^^ - I have some opinions on what that means, but would be nice to state it so we are on the same page 17:01:54 what were the 2/3/4 proposals again? 17:02:08 one sec 17:02:30 That handle is retired now. It's being used for nothing. We can use it for this project. We change the display name to Fedora CoreOS and start tweeting from there. 17:02:33 just finished a video call which required about 75% of my attention (my apologies) 17:02:52 fwiw, the status quo is not an option. either we do something with @coreos or it gets deleted. 17:03:11 so, along those lines: if a name is deleted, another user can sigh up to use it 17:03:18 If we are concerned that the info won't be useful to the current followers, we can poll them. My view is that we should just make the switch. 17:03:19 thus, spoofing coreos. next proposal 17:03:42 1. take twitter account keep name/followers. Stop using the @fedoraCoreOS account 17:03:44 red_beard: I understand. but those are the alternatives we've been given. 17:03:49 2. if possible: take twitter account renamve to @FedoraCoreOS (our existing name), keep followers 17:03:55 3. don't take @coreos account, just keep using our existing @FedoraCoreOS with current followers (building them up from scratch) 17:04:01 4. Delete @coreos account, rename @fedoraCoreOS to @coreos (building followers from scratch) 17:04:07 5. put a Twitter poll on the @CoreOS account 17:04:20 so, #2 is the same. if you rename it, it can be claimed. 17:04:43 I don't think it has to be deleted, it can just be dead 17:04:48 ^^ 17:04:52 #2 and #4 are (more or less the same) 17:04:58 Not that I think that's a good idea 17:05:06 jbrooks: I may have misunderstood. but @coreossecurity was outright deleted. 17:05:13 jbrooks: if you open a ticket and have the juice, yes, but it's hard 17:05:31 otherwise we wouldn't have paid a guy in Greece to get it 17:05:34 #2 and #4 differ in how many followers we retain 17:06:00 and also what handle gets used 17:06:07 red_beard, Open a ticket with who? There are tons of accts with no recent tweets, right? I guess we'd have to log in periodically to keep it status quo 17:06:17 Random Question from the Peanut Gallery: Have you looked at the followers to see how many are legit, active, etc.? 17:06:25 great question 17:06:39 * PanGoat <- Jaime Magiera 17:07:19 jbrooks: account purging is _relatively_ new and not automated 17:08:30 maybe adopt @coreos handle for FCOS marketing things/feature announcements, and keep @FedoraCoreOS for updates/security announcements? (If you're worried about spamming the @coreos followers too much) -- My preference would be to adopt the @coreos handle as-is and change only the display name 17:09:15 So, we want attn for Fedora CoreOS. To the extent that the OS, CoreOS, lives on as an open source project, it lives on through Fedora CoreOS. Why not use this twitter handle? 17:09:27 damnit.... i've been sending messages to lucab 17:09:30 cyberpear: so you vote for 1. 17:09:38 * bgilbert waves at lucab 17:09:46 dustymabe: yes, I vote for 1 17:09:49 https://help.twitter.com/en/rules-and-policies/inactive-twitter-accounts 17:09:49 :) 17:09:53 that's the actual policy 17:10:10 we "encourage" folks to log in....accounts "may" be deleted... 17:10:51 the @fedoracoreos account got mysteriously suspended earlier this year for no reason (i suspect it was inactivity) 17:11:02 that may be a precursor to getting deleted 17:11:38 dustymabe: to be clear, looks like it's back now? 17:11:51 oh yeah, jdoss helped us find a contact at twitter that got us squared away 17:12:06 this was before we started using it at all, originally we were just squatting on the name 17:12:12 so I see a couple independent things here: the name of our account, and whether we keep the existing followers. 17:12:21 bgilbert: right 17:12:43 re 1, we're talking about using the account for Fedora CoreOS things, so @fedoracoreos seems like a more accurate name. 17:13:12 "CoreOS" is pretty ill-defined. with Container Linux and CoreOS Inc. both gone, it's sort of synonymous with "OSes built by coreos-assembler" but that may change 17:13:22 and anyway we don't plan to speak for RHCOS on this account. 17:13:38 my personal feel is that @fedoracoreos is the more appropriate name 17:13:47 (I don't have inside info on "that may change", it's just an observation about the stability of such things) 17:14:19 but there are strong opinions that feel like using @coreos would be better 17:14:27 and re 2, it feels really sketchy to repurpose an account with a lot of followers that joined for some other purpose, and redirect their attention to something semi-unrelated. 17:14:44 I think we should have confidence that we can earn followers on our own merits if we work at it :-) 17:14:48 Eh, that's twitter. They can unfollow if they want. 17:14:59 jdoss: that's true but not the point 17:15:04 for that 'repurposing', i'm less concerned. especially if the account is effectively dead 17:15:32 dustymabe: that's... backwards? they're still following because the account is effectively dead, so nothing irrelevant is showing up in their timelines 17:15:40 From a marketing standpoint we should want the awesome work happening in Fedora CoreOS to be in front as many eyes as possible. 17:15:49 if we took over the account and started advertising motorhomes, people would be annoyed, right? 17:15:56 and yes, they'd unfollow 17:15:59 But this is nothing like that 17:16:01 but it'd be an abuse of their trust 17:16:02 i'd rather make a clear statement this account was going bye bye, so we repurposed it for this, if you don't subscribe to that idea then please unfollow 17:16:03 at all 17:16:08 jbrooks: it's like that, just less extreme 17:16:12 not at all 17:16:18 they were interested in k8s and Tectonic and Container Linux 17:16:41 The Container Linux name changed happened only a year before the acquisition 17:16:53 i think we'd still be tweeting about Fedora CoreOS, OKD, Typhoon, K8s, etc.. 17:17:04 jbrooks: ...they weren't following it because the name was CoreOS, they were following it because they were interested in CL (or etcd or whatever) 17:17:06 I bet that CoreOS means the OS, CoreOS to the vast majority 17:17:08 (which to bgilbert's point is why i still get tripped up calling it "container linux" 17:17:09 all relevant and in the same ballpark 17:17:20 years of muscle memory 17:18:19 This project has worked hard to carry on the things that CoreOS was about 17:18:41 We'd be tweeting in good faith 17:19:05 jbrooks: to be clear, I think that argument has _some_ merit. but the motivations I'm hearing are concerning. 17:19:09 "we can't lose the followers!" why not? 17:19:18 they're not ours to lose. 17:19:31 Red Hat is giving them to us 17:19:39 they're not Red Hat's to lose. 17:19:47 Red Hat bought them 17:19:54 you can always tweet "Hey, we're moving over here because..." and leave it to users to follow 17:19:55 Agree with jbrooks, and dustymabe: we should keep it and tweet about upstream Fedora CoreOS, OKD, Typhoon, K8s, etc work 17:19:56 they are human beings, who are there for their own reasons. 17:20:15 or maybe retweet only 17:20:32 And they can leave if they want to, but if they stay, they'll hear about the same sort of stuff they came for, coming from a lot of the same people 17:20:55 We should use the @coreos account to get more eyes on the project. It's a good name. If people don't want to see that on their feed, losing followers shouldn't be concerning. The project already lost users to Flatcar because of more important technical reasons. 17:21:09 i think if this was a "pay $100 per year" subscription it would be different. It's really not hard to unfollow if this isn't their interest any longer. 17:21:23 can we do something like: clearly declare that the account will be "reset" and why, then do an atomic rename of FedoraCoreOS to coreos? 17:21:42 jlebon: something like is what I was suggesting 17:21:57 dustymabe: then +1 to that :) 17:21:59 I'm talking about the principle, not the mechanism. yes, of course they can unfollow. but I'd rather we do what we can do show respect to the community. 17:22:08 I think a rename is more sneaky than keeping it as it and tweeting about upstream projects 17:22:33 i.e. still use the way nicer handle, but accept to lose the followers and gain them back on merit 17:22:34 so yes, at an absolute minimum we should be very clear about announcing what we're doing. 17:22:43 I've made my point and will stop :-) 17:22:43 bgilbert: all agreed on that point 17:22:46 I really don't think it's disrespectful. If this *were* an RV company, I'd agree with you 17:22:54 jbrooks: :) 17:23:02 wait, we're not building RVs here? 17:23:14 jlebon: I'm confused about that myself often 17:23:21 jlebon, you can suggest that in open floor 17:23:21 RVOS 17:23:25 lol 17:23:27 (I lean a bit towards a middle ground: just using it very occasionally, like at most once a month and see what happens) 17:23:40 I like travier's idea, but it's pretty much a full-time marketing job no? 17:23:41 I still think putting a poll on the existing @coreos account is a good idea, to see what active followers would like to see from the account, if anything. 17:24:05 wouldn't hurt to ask people. THe ones who respond will likely be the ones who care. 17:24:26 most folks won't take a poll if they don't have an interest, right? 17:24:30 lucab, my colleague in ospo can help schedule posts 17:24:31 I would suggest we do only simple retweets of FCOS announcements and some kubernetes or typhoon ones, which should be light load 17:24:47 travier: i agree with you overall.... i just feel realistically nobody is going to tweet about Typhoon or Flatcar 17:24:54 Ehhh I think we are overthinking this a bit. We as a project should want more people to use FCOS. Using @coreos can help with that. 17:25:22 "nobody is going to tweet about Typhoon or Flatcar" ?? 17:25:27 jdoss: i'd disagree about the over thinking 17:25:27 doesn't typhoon work w/ fcos? 17:25:29 walters: Does the FCOS group have a monthly announcement/update via email or any other platform? 17:25:34 that'd be worth boosting 17:25:40 PanGoat: intentionally no 17:25:55 we can also decide that we only retweet some accounts, no custom tweets 17:25:56 PanGoat: the idea is that FCOS should "just work" 17:25:59 bgilbert: our council reports are kind of like that 17:26:04 dustymabe: okay, fair 17:26:07 I send them to the devel@ lists 17:26:08 jdoss: we keep tweeting from @fedoracoreos, and @coreos retweets that as well as other related stuff 17:26:15 dustymabe: ah, I didn't know that 17:26:20 jbrooks: Dalton definitely has a penchant for Fedora so i'd _assume_ Typhoon has been tracking FCOS 17:26:35 red_beard, I just checked, it does 17:27:00 i like lucab's suggestion 17:27:06 lucab: +1 17:27:10 lucab: +1 17:27:19 so keep @coreos and make it just retweet @fedoracoreos' tweets? 17:27:22 So, we don't use @coreos for Fedora CoreOS? 17:27:23 it's actually travier's suggestion 17:27:35 dustymabe: as well as retweets of other things in the CoreOS ecosystem 17:27:36 And why not? 17:27:39 what would the "other related stuff" be? 17:27:45 sorry.... too much scrollback 17:27:57 And what is the CoreOS ecosystem? 17:28:15 jbrooks: let me know if you figure that out :-( 17:28:27 red_beard: seems like a good idea, though I was thinking @fedoracoreos would retweet other things in the CoreOS ecosystem :) 17:28:28 I am still with jbrooks on this. I followed @coreos for when CL was called CoreOS. That is all I cared about back then and now I care about FCOS and it makes sense for @coreos to be talking about FCOS things. 17:28:29 PanGoat, jbrooks : etcd, prometheus, k8s, typhoon, ostree, okd, ... 17:28:33 at a minimum accepting re-tweets from Typhoon, FlatCarLinux, etc 17:29:16 So promoting all that stuff is now a goal of this project? 17:29:18 FCOS and Flatcar tweets from the same account would be... confusing 17:29:27 agree ^^ 17:29:58 agree too unfortunately 17:30:06 Let's keep this focused on Fedora CoreOS -- where those other topics touch fcos, tweets make sense 17:30:07 well, to be fair, Flatcar still bears more resemblance to CoreOS/Container Linux 17:30:34 so basically the new proposal is: 17:30:38 toolbox works in that one (unless we fixed it recently) 17:30:39 red_beard: right and they didn't buy CoreOS and the brand. 17:30:59 wait... so this is just now about what was "bought" and not the community of users? 17:31:04 6. keep @coreos, retweet @fedoracoreos stuff (and other related stuff that touches on fedora coreos) 17:31:07 that's some BS 17:31:15 Its reality 17:31:27 It's about both of those things 17:31:41 jdoss: it's not. again, we don't own the users. they come of their own volition, they leave of their own volition. 17:31:47 we serve them, not the other way around, and I hope we keep that in mind. 17:31:49 bgilbert: +1 17:31:56 there's a trademark, the thing in the market under that name is the project we're all working on here 17:32:20 dustymabe: this new 6 was pretty much the status quo, until we have been told RH wanted to give back the account to us 17:32:44 dustymabe: I personally liked the way it was going 17:32:44 and along those lines 17:32:46 I still vote 1 17:32:47 lucab: except we don't have access to it and no retweeting was going on 17:33:07 I guess the difference is that we will not be retweeting product announcements but upstream announcements 17:33:09 lucab, There have been only 3 tweets this year 17:33:15 i find it ironic that when Red Hat gives the asset back to the community project, the folks on the community project become "yes men" to Red Hat 17:33:18 dustymabe: exact, there was some RH marketing person doing it 17:33:28 ? 17:33:32 the exact PR Red Hat is (generally) trying to avoid 17:33:33 red_beard, what do you mean? 17:33:44 red_beard: *eye roll* 17:33:55 jdoss' standpoint 17:33:55 I want what's good for this project 17:34:17 And I want to do right by the users 17:34:25 I'm a bit lost in the conversation, but just to be clear, jdoss doesn't work for Red Hat 17:34:36 Yea I don't work for Red Hat at all. 17:35:00 jbrooks: this year was pretty rough on many sides, I was thinking of 2019 mostly 17:35:05 and I can see that using @coreos to get more eyes on FCOS is good for the project and the current users of FCOS. 17:35:14 lucab, it's retired, that's the status quo 17:35:22 fair enough, i stand corrected. 17:35:35 * jbrooks does work for Red Hat :) 17:35:45 The old CoreOS is dead. That company is dead. CoreOS, the brand, lives on in Fedora CoreOS. 17:35:59 +1 17:36:09 bottom line 17:36:12 Users that don't want that followed @flatcar to have the old CoreOS. 17:36:15 * dustymabe just realized he brought up a naming discussion.. in 2020 of all years 17:36:35 FWIW we've worked pretty hard in the official messaging to make it clear that things are slightly more complicated 17:36:49 see the various FCOS release announcements and the CL EOL announcement 17:37:18 I think it's important to stay specific to the FCOS that is associated. It has a strong association . I agree it is important to celebrate achievements in Flatcar, but from a more personal account. 17:37:40 so.. without more information I don't think we're going to make a lot of progress today. 17:37:55 I think option 6 is a good "almost status quo" option 17:37:56 What information? 17:38:06 we do need to have some path forward 17:38:09 It's all opinion, I'd say, feeling 17:38:11 a twitter poll might give us more information 17:38:29 but we haven't agreed to do that yet 17:38:42 I think short of a poll we're not going to move past our current differences 17:38:55 If that's what's holding us back, ok, but I don't think that's what's holding us back 17:39:00 so we'd need to probably put a stick in the ground and just choose one 17:39:07 just a straw idea 17:39:15 +1 dustymabe 17:39:19 ask the users 17:39:20 https://en.wikipedia.org/wiki/Curators_of_Sweden on top of 6 17:39:38 dustymabe: I don't especially like the poll but I agree that we're not coming to a consensus 17:39:50 The poll idea isn't going to get us any useful info. 17:39:51 you may get lots of responses or zero responses (which may say something in itself) 17:40:06 jdoss: what it would give us is a temperature check from the existing followers 17:40:11 a poll isn't going to get us closer to consensus either 17:40:25 which would address the question of how unhappy we'll make them :-/ 17:40:29 whoever volunteers to, rotate weekly(?) on @coreos, retweeting things that seems relevant to "coreos" 17:40:30 davdunc: at least it would give us some data 17:40:37 which means FCOS and more 17:40:45 The poll tells you what the followers would think about the options. 17:40:49 bgilbert: they can unfollow. FCOS is the reality of the CoreOS brand. 17:40:49 dustymabe: good point. 17:41:20 dustymabe, I guess, for the people who are against using the handle, would a poll change their minds? 17:41:32 If not, the data is useless 17:41:34 jdoss: I'm just going to reiterate that IMO "they can ask us to stop" is not ever a good justification for being obnoxious 17:42:04 I sort of take issue with the idea that this is obnoxious 17:42:27 yea same. 17:42:30 jbrooks: I don't think we're going to change peoples minds too much, but if there are clear conclusions from the data, the outcome can be easier to accept for those that believe whatever the decision is is the wrong way to go 17:42:38 IMO the poll isn't about changing anyone's minds, it's about seeing whether anyone cares. if no one cares, great. if people are in favor, great. 17:43:20 If you go a different route than the adamant poll responders (or even just users), respond "we factored in a variety of concerns" 17:43:35 You can at least say you cared enough to ask 17:43:42 so laying it all out. If we had to decide today and I had to make the decision I would try to do what is least offensive to everyone here 17:43:46 which is option 6 17:44:02 to be clear that isn't my personal opinion of what I would have chosen 17:44:08 that is me reading the room 17:44:28 so there you have it, do you want option 6 or do you want more data (twitter poll)? 17:44:30 I don't think 6 makes sense 17:44:51 jbrooks: why? 17:45:01 Because it conjures up a new community 17:45:08 I want to drive more users to FCOS and from a marketing standpoint using @coreos can help do that. 17:45:10 The CoreOS ecosystem community 17:45:31 We need more focus on this project, we don't need to be looking at ways to diffuse our efforts 17:45:34 I agree with jbrooks on 6 17:45:36 effectively option 6 would be a retween bot of @fedoracoreos (let's face it no one is staffing this thing to do some more legit curation) 17:45:45 retweet* 17:46:02 I'm not going to block any option. I've raised my concerns, and if they're unconvincing, do what you think is right. 17:46:52 ditto what bgilbert said 17:47:06 anybody else want to way in on "option 6 vs twitter poll" ? 17:47:21 twitter poll kicks the can til we get more data 17:47:21 Look at it from this angle CoreOS the brand was bought by Red Hat and they are using it for Red Hat CoreOS and we are using it for Fedora CoreOS. FCOS is the base for RHCOS. They are giving us the root brand account @coreos and we should use that to drive more eyes this awesome work. 17:47:32 which means more help! 17:47:35 but that community exists, it covers modern OSes, safe language, metrics/observation, distributed systems, immutable infra, etc 17:47:39 +1 for 6. No need for polls for me 17:48:23 lucab, where does that community meet? 17:48:26 (where's the list of options again?) 17:48:29 vote time: please put "6" or "poll" in the chat :) 17:48:36 We can go ask them if they want to take over the acct :) 17:48:41 reducing it to "a fairly new emerging flavor of Fedora" misses the whole reason why we do FCOS 17:48:42 I am of the same opinion around the branding. 17:48:44 6 17:48:50 dustymabe, We're down to just 6 or poll? 17:48:52 * PanGoat is happy to contribute towards promotion, including social media (once you make a decision) 17:48:55 I'm still on 1 17:49:02 jbrooks: I'm trying to find *some* way forward 17:49:02 I vote 1 17:49:14 this is literally impossible 17:49:19 jbrooks: it's me, you, the people I ping when I have doubts, OCI committee, etc 17:49:24 and we can't keep having this same conversation every month 17:49:37 (not sure if it's on the list but there's also the idea that we could try to let flatcar have things there too but...) 17:49:47 walters: read scrollback 17:50:12 poll 17:50:31 between 6 or poll, poll 17:50:32 lucab, Best to let those projects tweet for themselves, and @coreos could retweet when that work touches fedora coreos 17:50:49 Yes, if those are our only choices, poll 17:50:51