If you were only fixing a typo in a comment, seemed to be changing documentation for no real reason, or arbitrarily rewriting a bit of code without making any particular improvement, that's the sort of thing that could raise eyebrows.īut in your case, your PR seems like it would genuinely improve the software. Hacktoberfest is over, and that specific problem has abated (the amount of spam caused them to change the way the program worked after a few days to make it opt-in for project maintainers), at least until next year, but that incident gives a bit of context into how many maintainers think about pull requests: PRs exist to improve the software, and PRs that seem to exist just for the sake of changing something without a clear purpose or benefit may be frowned upon, especially in bulk. It was particularly noticeable this year, with some projects receiving a dozen of these in the first day of the event, which caused a lot of consternation among project maintainers and blog posts like DigitalOcean's Hacktoberfest is Hurting Open Source. A number of these involved trivial changes or vandalism to README files, some inspired by a demonstration on a YouTube channel.Īt worst, we're talking about things like this "improve docs" PR, which only added unnecessary periods to comments, or this one, which added an odd and unnecessary header to a README. Wonderful as it is to encourage more people to get into open source, offering a reward in return for gameable metrics and packing it all into one month resulted in many projects receiving a flood of low-quality pull requests that were perceived by some maintainers as spam. Being humble and kind always contributes to building on the relationships we rely on to develop our businesses.Some context that may or may not be relevant.Ī cloud hosting provider named DigitalOcean hosts an event every year called Hacktoberfest to encourage people to contribute to open source projects in exchange for a T-shirt. Regardless of which side you may be on, this time, always respond with understanding. Responding Appropriately & Professionally So please don’t lose sight of that when it comes to our email activities. Sorry for the confusion and inconvenience.”īusiness success comes from paying attention to details. Then, send a quick follow-up email noting that you discovered your mistake. Next, check the names you add when sending an email to multiple addresses and make sure those addresses are the ones you want to get your communication. So the obvious first step is to slow down. ![]() I get how you can click on an email address unintentionally, especially with auto-fill and contacts with the same first name in your address book. ![]() That is why I always - always - look at the To:, Cc: fields before clicking send. In this fast-paced crazy world, we all make mistakes. In the case of a possible mistake, only reply to the sender (do not “Reply to All”) so they have the opportunity to clarify your involvement or the fact they made a mistake. How can I help?”Īnother consideration, if you feel you’ve been included in a conversation in error, is to help the sender by not exposing that error to others in the conversation. When Cc:’d, my approach may be more passive. Can you let me know at your convenience?” For example, “Got your email and am wondering what I need to do. ![]() If you are in the To: field, I would be more apt to reply promptly, asking what they would like me to do. To: expects your input, whereas Cc: tends to be an FYI. There are different reply expectations if you are in the To: or Cc: field how you reply can consider this. This will allow them to either clarify or let you know if they emailed you in error. ![]() If you receive an email that doesn’t seem to apply to you, I would reply to the sender and kindly ask what they would wish for you to do based on their email. On the other hand, what if you just discovered you accidentally sent an email to the wrong contacts? How do you acknowledge your “oversight”? Email Received in Error What if you receive an email that you believe was not intended for you? Should you reply asking the sender if they meant to send or Cc: you in the email?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |