Hello, if OS persons are peoples making projects, why not simply restrict #assets to OS-Developers group only to post?
Beyond my control, you’d have to ask @Crcoli737
Good Recommendation, I’ll look into it.
If it was restricted to only OS-Devs, then how would we get OS devs? The Whole reason I suggested the OS-Devs group was so that people who made a post in #assets could join it and get special permissions.
os devs are peoples who make projects, but are still normal members, its a request to join group, only os devs could post, u could still read and comment the post (also like it)
Good point… Not sure how we could fix that.
at this point os devs could lock bad assets, but only lock?
for me that a special perk
Locking posts and closing topics are two different things.
what do closing do? delete the page? that mods jobs, os devs could pin, unpin, lock, unlock assets
Close prevents new replies, locking prevents editing.
lemme list all the os perks in the asset category:
- delete messages
kinda a category mod
Only flag things that are breaking the rules. Otherwise just dm me.
And you can’t give those permissions to a group. The only to moderation groups are admins and moderators.
uk what, i just wanna see what do the close post ui looks like, may u can send a screenshot?
I know, but how would we determine if someone was a OS-Dev if they can’t post in #assets? Currently a TL2 lock is perfect for it, as that way we can find out if the user makes open source things.