Git Product home page Git Product logo

Comments (15)

ssube avatar ssube commented on August 19, 2024

The concept: 👍
Being gone for a while shows a lack of interest and can have some impact on your ability to RO (don't know who's trolling this week and what the problems have been).

30 days seems like a good timeout, so nobody gets booted for a vacation. If we have contact info for the RO, I think we should try to get in touch with them after 14 or 21 days, before booting them (maybe just a ping on chat).

If they come back, open an issue and we'll hold no vote/just a "you wanna be around? k, cool" check.

They should be able to note their absence here or in chat, though, if they are going to be traveling for a while. If they warn us, I don't think we need to drop them.

from culture.

rlemon avatar rlemon commented on August 19, 2024

yea, circumstances come up all the time. someone may legit be away without notice for a while. I just don't think we should clutter the list with people who may or may not have abandoned ship. And if they return, no fuss no muss?

from culture.

Trasiva avatar Trasiva commented on August 19, 2024

It certainly is a good way to maintain who's actually active at the time, and allowing them to re-obtain ROship once they begin to be active again if they were in good standing keeps a smooth transition.

from culture.

benjamingr avatar benjamingr commented on August 19, 2024

👍 unless the owner has explicitly communicated why they're MIAing

from culture.

RUJodan avatar RUJodan commented on August 19, 2024

👍

from culture.

Zirak avatar Zirak commented on August 19, 2024

👍 with the clause that @benjamingr added.

from culture.

loktar00 avatar loktar00 commented on August 19, 2024

👍 overall however there are some cases that should be discussed such as, if someone stops by 5 days a month, technically it's enough to stay an active Room Owner.. but by no means enough to know whats going on in the room to effectively moderate. These situations should be handled on a case by case basis.

from culture.

Cerbrus avatar Cerbrus commented on August 19, 2024

👍, keeping @loktar00's comment in mind.

from culture.

benjamingr avatar benjamingr commented on August 19, 2024

but by no means enough to know whats going on in the room to effectively moderate. These situations should be handled on a case by case basis.

+1 You can miss the entire context of a conversation or a user by missing a single day. This is why we opened the moderation repo - so kicks are kept track of and people can effectively moderate without being in the same timezone.

from culture.

Trasiva avatar Trasiva commented on August 19, 2024

After a little more reflection over the weekend, 30 days seems like an awful lot of no-notice missing time. I'd say two weeks is a little more justifiable without a heads up, as two weeks without being in the room puts you significantly behind in terms of room activity.

from culture.

benjamingr avatar benjamingr commented on August 19, 2024

-1 for two weeks. Being RO is about trust in your ability to moderate. Lots of people have personal stuff going on, and I'm sure every one of us had to miss a week or two at a point.

from culture.

Trasiva avatar Trasiva commented on August 19, 2024

@benjamingr I'm saying two weeks without a heads up. I think most of us who are regulars have various means to contact someone to let them know something is up. Popping off a quick text/hangouts message/ping in chat takes all of 15 seconds.

from culture.

benjamingr avatar benjamingr commented on August 19, 2024

Right, and I'm against that, if I have a family emergency and a family member gets hospitalized the last thing I'm going to think about is "better let the JavaScript room know I won't be around for the next week or two!".

from culture.

Trasiva avatar Trasiva commented on August 19, 2024

Well, that's fair. Sometimes I forget I'm more disconnected than most people. 30 is reasonable in that case then.

from culture.

Zirak avatar Zirak commented on August 19, 2024

The consensus seems to be:

  • An owner is considered MIA if they disappear for a month without prior notice.
  • If after a month the owner hasn't responded, de-owner.
    • I'll add my own small clause: Raise a de-owner issue about them.
  • If/when they come back we'll have a regular vote on them.

And in addition:

  • An owner's regular activity should also be considered. If an owner doesn't show up often then they're probably not active enough to know the ebb and flow of the room and can't be as helpful.
  • In those cases, vote for removal per norm.

from culture.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.