-
Guest78835
.merge+ #1159
-
xmr-pr
Added
-
Guest78835
.merges
-
xmr-pr
#1150 #1159 #1166
-
Guest78835
.merge+ #1153
-
xmr-pr
Added
-
Guest78835
.merge+ #1149
-
xmr-pr
...
-
Guest78835
.merges
-
xmr-pr
#1149 #1150 #1153 #1159 #1166
-
Guest78835
luigi1111: IMO 921, 1104 and 1075 can be closed
-
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
-
xmr-pr
erciccione opened pull request #1170: readme: officialize listing of only FOSS wallets in 'Downloads' sectio...
-
xmr-pr
-
sgp_
luigi1111w: is there anything I should do with 1167?
-
luigi1111w
no I'd just like an approval or two
-
luigi1111w
same for #1149 Guest78835
-
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)
-
Guest78835
maybe we could create a section called "posts from the community" or something like that
-
sgp_
Guest78835: we have put everything in announcements up until this point, including responses to research articles and marketing posts about upcoming pruning features
-
sgp_
it's my personal opinion it should go there until we redefine how to use it
-
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
-
Guest78835
If we did then makes sense to keep it that way for now,
-
sgp_
fwiw I totally feel you that there should be a better way to separate
-
sgp_
100% agree
-
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
-
Guest78835
i'll put it in my todo list
-
sgp_
but also note that "releases" are their own category too, so ¯\_(ツ)_/¯
-
sgp_
on the top of my head, the tags should be "emergency," "releases," "meeting logs," and "community"
-
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
-
Guest78835
anyway, i will open an issue about it (probably tomorrow) so we can all decide what to put there
-
sgp_
thanks :)
-
sgp_
I'm trying to focus more on helping the website
-
sarang
How about Alerts instead of Emergencies?
-
sarang
Conveys importance and urgency perhaps more clearly
-
Guest78835
sgp_: that's appreciated 🙂 i left a comment and my ACK to the post
-
Guest78835
sarang: that's better i guess
-
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
-
luigi1111w
I do sometimes depending how the commits look
-
luigi1111w
I don't think it's a big deal either way
-
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
-
Guest78835
.merge+ #1167
-
xmr-pr
Added
-
sgp_
sarang: hmm, I'll definitely keep alerts in mind
-
sgp_
thanks for the suggestion
-
moneromooo
Maybe DEFCON levels.
-
sgp_
lol