Giter Site home page Giter Site logo

Comments (4)

makyen avatar makyen commented on August 11, 2024

Using prescribed close reasons was discussed at the January 2017 room meeting, as an offshoot to the topic "Do we need to watch our tone more?". The summary of the discussion was:

Stick to the prescribed CV reasons when making requests, and always use constructive language when describing a question. We already require members to act professionally and with a high standard.

from room-meeting-topics.

Tyler-H avatar Tyler-H commented on August 11, 2024

@makyen In that case, I would like to adjust the question to:

Can we please discuss enforcement of prescribed close reasons?

Currently we see lots of close reasons that use unnecessarily unfriendly language or terms in the close reasons by many users, several of which regularly use these inappropriate close reasons.

However, I can count on one hand or less the number of times such a cv-pls request has been binned due to inappropriate close reasons or a failure to change it after prompting.

from room-meeting-topics.

makyen avatar makyen commented on August 11, 2024

Given that we forgot to add it to the FAQ, it's a good idea to do so.

I agree that it should be enforced. My main concern is that I don't want to restrict it to only actual close reasons. I'd like to permit there to be additional factual information intended to help other users save time in evaluating the post. For example: "Typo: see 5th line of 2nd code block foo should be bar. Confirmed by OP in comments."

I definitely agree that derogatory language should not be used. If you see cases where such requests are not dealt with by an RO, please point them out, as we don't read every single thing, at least not immediately (varies based on how active each of us is in the room at that particular time).

It's also possible that we've let things slide from time-to-time. Feel free to bring such to our attention.

from room-meeting-topics.

Tyler-H avatar Tyler-H commented on August 11, 2024

Certainly, custom close reasons should definitely remain available, but reasons like "zero value" "crap question" "no effort" etc. should not be permitted IMO. I see these used on an almost daily basis.

from room-meeting-topics.

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.