Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Comments on A community-maintained list of abbreviations used in electrical engineering?

Parent

A community-maintained list of abbreviations used in electrical engineering?

+1
−1

At Somewhere Else, we started an initiative to make a community-maintained list of abbreviations used in electrical engineering: What are abbreviations used in electrical engineering?

I think it could be a valuable thing to have, although the mentioned list suffered from Q&A style and too many contributors in relation to proof-reading/moderation.

We could perhaps create a better list here at Codidact, either in the form of a single meta post (question) or as a single post in the papers category.

Please share your thoughts about creating such a list at Codidact.

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+1
−0

I was the one who started that list Elsewhere. I thought the same as you, that a few common abbreviations would be good to have in a single place.

However, it quickly turned into a mess. After only a few days I could see it was a mistake.

People added whatever obscure abbreviations they could think of, seemingly trying to outdo others with how many abbreviations they could post. A few even used it to push their favorite uncommon abbreviation somewhat as a political statement.

Voting on such a list also doesn't make sense. It became more of a popularity contest than a measure of quality. Such a list should be in alphabetical order. Your suggestion of using a Paper for the list does get around the voting and sorting problem, but not the other problems.

Elsewhere has shown that crowd-sourcing reference information just doesn't work. No matter how much you try to explain the single coherent vision for what should be in the reference and how it should be organized, people do what they want to. The result is inevitably a mess.

The only way this might work is if one person wrote the list, but that's not workable. Everyone can edit. What are you going to do when someone adds an abbreviation that is obscure enough to detract from the whole instead of adding to it, even though the definition is well-written and formatted? That will lead to endless whines on meta about "Why did my perfectly correct abbreviation get deleted?".

Without a lot of heavy moderation, this won't work. We're all volunteers here. I don't want to waste my volunteer time on dealing with the inevitable bickering and whining. The upside just isn't big enough.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

How about a list maintained by a few users signed up for it? (2 comments)
How about a list maintained by a few users signed up for it?
Lundin‭ wrote over 1 year ago

Maybe we could do a list which is posted by one user but other trusted users can "sign up" as co-authors and only those approved are allowed to edit it? Then we can protect it from too many exotic additions. With the original author having the final say (and the possibility to carry out edit rollbacks). As for if this is feasible as per Codidact post license policies, I have no idea.

Olin Lathrop‭ wrote over 1 year ago

I suppose that's OK as long as those users do the managing and regular maintenance. If you create that as a paper, I won't get in the way.