11:07:22 <Guest78835> .merge+ #1159
11:07:22 <xmr-pr> Added
11:07:51 <Guest78835> .merges
11:07:51 -xmr-pr- #1150 #1159 #1166
11:08:06 <Guest78835> .merge+ #1153
11:08:06 <xmr-pr> Added
11:10:01 <Guest78835> .merge+ #1149
11:10:01 <xmr-pr> ...
11:10:26 <Guest78835> .merges
11:10:26 -xmr-pr- #1149 #1150 #1153 #1159 #1166
11:11:37 <Guest78835> luigi1111: IMO 921, 1104 and 1075 can be closed
11:12:06 <Guest78835> i'm also about to PR in the readme that we only accept open source platform in the download page. So we can make that official
11:30:12 -xmr-pr- erciccione opened pull request #1170: readme: officialize listing of only FOSS wallets in 'Downloads' sectio...
11:30:12 -xmr-pr- > https://repo.getmonero.org/monero-project/monero-site/merge_requests/1170
17:24:51 <sgp_> luigi1111w: is there anything I should do with 1167?
17:27:43 <luigi1111w> no I'd just like an approval or two
17:33:52 <luigi1111w> same for #1149 Guest78835
20:25:55 <Guest78835> sgp_ I read the comment, i'm still not sure "announcements" is the right place even just temporarly. I think not prioritary blog posts should go in the "all posts" section, otherwise people will tend to use the "announcements" tag for everything to give visibility to the post (since the other voices in the menu don't clearly fit)
20:26:12 <Guest78835> maybe we could create a section called "posts from the community" or something like that
20:26:46 <sgp_> Guest78835: we have put everything in announcements up until this point, including responses to research articles and marketing posts about upcoming pruning features
20:27:04 <sgp_> it's my personal opinion it should go there until we redefine how to use it
20:28:21 <sgp_> I'd much rather post something now to a weakly-defined category as we have always done than post it without a visible category
20:28:33 <Guest78835> If we did then makes sense to keep it that way for now,
20:28:50 <sgp_> fwiw I totally feel you that there should be a better way to separate
20:28:59 <sgp_> 100% agree
20:29:05 <Guest78835>  but i think it's important to have the announcements section as clean as possible in the future, so that it's clear for people that important stuff and urgent announcements only are posted there
20:29:15 <Guest78835> i'll put it in my todo list
20:29:34 <sgp_> but also note that "releases" are their own category too, so ¯\_(ツ)_/¯
20:33:43 <sgp_> on the top of my head, the tags should be "emergency," "releases," "meeting logs," and "community"
20:38:19 <Guest78835> emergencies sounds terrifying :P. I'm ok with all the other ones, but i would keep "announcements" and use it strictly for important communications
20:40:09 <Guest78835> anyway, i will open an issue about it (probably tomorrow) so we can all decide what to put there
20:43:58 <sgp_> thanks :)
20:44:11 <sgp_> I'm trying to focus more on helping the website
20:44:45 <sarang> How about Alerts instead of Emergencies?
20:45:02 <sarang> Conveys importance and urgency perhaps more clearly
20:46:43 <Guest78835> sgp_: that's appreciated 🙂 i left a comment and my ACK to the post
20:47:05 <Guest78835> sarang: that's better i guess
20:48:06 <Guest78835> luigi1111: are you using the squash and merge option on gitlab? Because if you are i don't bother telling people that they need to squash their commits
20:48:25 <luigi1111w> I do sometimes depending how the commits look
20:48:34 <luigi1111w> I don't think it's a big deal either way
20:49:27 <Guest78835> great, i'm adding sgp's post to the queue then, there are 5 commits, but shouldn't be an issue to do a squash and merge on those
20:50:06 <Guest78835> .merge+ #1167
20:50:06 <xmr-pr> Added
20:52:22 <sgp_> sarang: hmm, I'll definitely keep alerts in mind
20:52:30 <sgp_> thanks for the suggestion
21:09:16 <moneromooo> Maybe DEFCON levels.
21:09:47 <sgp_> lol