The Peptide CommonsEst. May 2024
Independent. We sell nothing and are affiliated with no manufacturer or pharmacy. Every moderation action is logged in public
Meta · Announcements

Guidelines revision: what changed and why

MP
mira.patelTL4 Admin24 Jul 2024#1

Guidelines revision: what changed and why Writing it up because I had to work it out twice and would rather nobody else did.

I was wrong about guidelines revision in a thread last spring and I would like to correct it publicly rather than quietly.

The error was in the units, which changed the conclusion by an order of magnitude. Setting out the corrected version, and the way I now check for that class of mistake.

47 likes 2y
TT
taper_tableTL3Regular24 Jul 2024#2

My experience of guidelines revision contradicts the reply above. I am posting it as a data point rather than as a refutation, because one person's experience is exactly that.

12 likes 2y
AH
a.hartmannTL224 Jul 2024#3

I read the opening post twice before replying, because I had assumed the opposite.

Guidelines revision is well covered in the tag pages, and the older discussions are better than the recent ones because they were argued out properly. Worth twenty minutes before adding to this one.

1 like 2y
EC
excursion_checkTL3Regular24 Jul 2024#4
a.hartmann, post #3: I read the opening post twice before replying, because I had assumed the opposite. Guidelines revision is well covered in the tag pages, and the older discussions are better than the recent ones because they were argued out properly. Worth twenty minutes before adding to this one. Go to post

Worth saying publicly: stepping back cleanly and handing over is a service. Documents with an absent maintainer go wrong quietly, which is the worst way for them to go wrong.

0 likes in reply to #3 2y
KH
k.haddadTL224 Jul 2024#5
taper_table, post #2: My experience of guidelines revision contradicts the reply above. I am posting it as a data point rather than as a refutation, because one person's experience is exactly that. Go to post

The rare case here is the one that costs somebody a week, though, and the common case costs everyone ten seconds. I think the trade is clearly correct.

18 likes in reply to #2 2y
BM
buffer_marginTL3Regular24 Jul 2024#6

This is the sort of exchange that makes the archive worth searching.

7 likes 2y
TA
t.abubakarTL224 Jul 2024#7

Coming back to post #5, because the follow-up matters more than the original answer.

If someone has run guidelines revision properly I would rather read that than my own reconstruction of it. Posting mine only because the thread has gone quiet.

0 likes 2y
P
PSkarbekTL3Regular24 Jul 2024#8
buffer_margin, post #6: This is the sort of exchange that makes the archive worth searching. Go to post

Picking up post #5: that is the part I would want checked first.

Marking my uncertainty on guidelines revision explicitly. I am confident about the direction, much less confident about the size, and not confident at all that it generalises past the case in the first post.

0 likes in reply to #6 2y
CS
c.serranoTL224 Jul 2024#9

Clear enough that I do not think I have a follow-up, which is unusual.

13 likes 2y
TN
t.nardoneTL3Regular24 Jul 2024#10

Post #8 is right about the mechanism and I think understates the practical bit.

Thank you for announcing it in advance rather than after. The number of places that do the reverse is remarkable.

4 likes 2y
AT
a.teixeiraTL224 Jul 2024#11
excursion_check, post #4: Worth saying publicly: stepping back cleanly and handing over is a service. Documents with an absent maintainer go wrong quietly, which is the worst way for them to go wrong. Go to post

Post #10 answers the question as asked. The question underneath it is different.

Guidelines revision: I would want to see the raw numbers rather than the summary before agreeing. Summaries lose exactly the information that would settle this.

11 likes in reply to #4 2y
KB
k.brandl_deTL3Translator · DE25 Jul 2024#12
buffer_margin, post #6: This is the sort of exchange that makes the archive worth searching. Go to post

On post #8 — agreed on the reasoning, with one qualification.

The reason guidelines revision is hard to answer is that the obvious measurement and the relevant quantity are not the same thing, and substituting one for the other is silent.

24 likes in reply to #6 2y
AN
a.nascimentoTL225 Jul 2024#13

Bookmarking this. I will come back when I have something worth adding.

0 likes 2y
DB
d.bramleyTL3Regular25 Jul 2024 · edited#14

Reading the changed pages: the diff is smaller than the announcement implies, which is reassuring rather than disappointing. A large change to a documentation page usually means the previous version was wrong.

I looked this up rather than remembered it, which is the right order.

3 likes 2y
AK
a.krastevTL225 Jul 2024#15

Post #14 is right about the mechanism and I think understates the practical bit.

I would be cautious about generalising from the guidelines revision example above. It is a good example. It is one example.

7 likes 2y
G
GEldridgeTL3Regular25 Jul 2024#16
t.nardone, post #10: Post #8 is right about the mechanism and I think understates the practical bit. Thank you for announcing it in advance rather than after. The number of places that do the reverse is remarkable. Go to post

A definition problem is doing most of the work in this guidelines revision discussion. Once the term is pinned down I suspect the disagreement mostly goes away and what is left is small.

18 likes in reply to #10 2y
AV
a.vestergaardTL225 Jul 2024#17

When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.

The evidence for this is thinner than the way I have phrased it suggests.

0 likes 2y
GD
glossary_deskTL325 Jul 2024#18
RP
r.petrovTL225 Jul 2024#19

Agreed on all of that, and I have nothing to add to it.

4 likes 2y
MP
mira.patelTL4 Admin25 Jul 2024#20
t.abubakar, post #7: Coming back to post #5, because the follow-up matters more than the original answer. If someone has run guidelines revision properly I would rather read that than my own reconstruction of it. Posting mine only because the thread has gone quiet. Go to post
Staff post. Actions described here are recorded in the public moderation log and may be challenged in Meta.

Announcement about the vendor documentation set. Two pages have had their review dates brought forward because the underlying records changed. The pages themselves say what changed and when, as they always have.

That is the version I use. It may not be the version that is correct.

12 likes in reply to #7 2y
L
LJankowiakTL3Regular25 Jul 2024#21
c.serrano, post #9: Clear enough that I do not think I have a follow-up, which is unusual. Go to post

The edit is clearer. For anyone arriving now, read the edited version — the confusion in the replies above is about wording that no longer exists.

27 likes in reply to #9 2y
RN
r.novakTL225 Jul 2024#22
k.haddad, post #5: The rare case here is the one that costs somebody a week, though, and the common case costs everyone ten seconds. I think the trade is clearly correct. Go to post

The bit of guidelines revision that nobody enjoys is that the answer changes depending on what you are trying to decide with it. Say what the decision is and the thread will converge.

13 likes in reply to #5 2y
BR
buffer_reviewTL3Regular25 Jul 2024#23

Reframing guidelines revision slightly, because I think the disagreement is about the question rather than the answer. If the question is "does it happen", yes. If it is "how often", nobody here knows.

4 likes 2y
AC
a.cardosoTL225 Jul 2024#24

Sensible. I would want the same detail before I acted on it either.

0 likes 2y
CD
cannula_driftTL3Regular25 Jul 2024#25
PSkarbek, post #8: Picking up post #5: that is the part I would want checked first. Marking my uncertainty on guidelines revision explicitly. I am confident about the direction, much less confident about the size, and not confident at all that it generalises past the case in the first post. Go to post

On post #21 — agreed on the reasoning, with one qualification.

Archives: older announcements are archived by date. Checking archives is useful if you want to know what changed when.

Take the reasoning and check the arithmetic; I do not always get it right.

20 likes in reply to #8 2y
SV
sa.vogelTL225 Jul 2024 · edited#26

One question about the transition rather than the policy: what happens to topics that are in flight when it takes effect? The announcement is clear about posts and silent about drafts.

9 likes 2y
K
KTurkingtonTL3Regular25 Jul 2024#27

Useful. I have added it to my own notes with the date on it.

2 likes 2y
AM
a.mwangiTL225 Jul 2024#28

Adding what did not work for me on guidelines revision, since the failures never get written up and they are half the useful information.

0 likes 2y
MC
m.coelhoTL225 Jul 2024#29

Good question, well framed, and I would like to see it answered properly.

0 likes 2y
SB
s.bergstromTL225 Jul 2024#30
mira.patel, post #1: Guidelines revision: what changed and why Writing it up because I had to work it out twice and would rather nobody else did. I was wrong about guidelines revision in a thread last spring and I would like to correct it publicly rather than quietly. The error was in the units, which changed the conclusion by an order of magnitude. Setting… Go to post

Post #28 is right about the mechanism and I think understates the practical bit.

My understanding of guidelines revision is a few years old and may have been superseded. If it has been, I would genuinely like to know rather than keep repeating it.

26 likes in reply to #1 2y