5 ms·

That's... something. But it still feels very passive. What do you think about the ideas I listed in the post above? I assume you know who are the people on bot

by akavel 7y ago

That's... something. But it still feels very passive. What do you think about the ideas I listed in the post above? I assume you know who are the people on both sides, and that you have their emails, so I'd guess you're in a good position to actively facilitate communication, no? Is there a way how I could actively reach out to a person that's listed as a maintainer on my project? Why not add a form that would let me do that? even without necessarily revealing their email, if they don't want to? though to tell the truth, why wouldn't they want to, if they claim to want to contribute? Similarly, how about a notification, so that I learn that someone joined my project, with their email so that I can reach out with a welcome? why passive encouragement to a chat server instead of an active facilitation of first contact over email?

StavrosK 7y ago
Oh, I definitely agree with you that communication should be more active, it's just that right now this is more left to the new maintainer to do. On Github, everyone's email is public anyway, so the new maintainer could message the old one. I don't think Github/Gitlab provide any automated way to send people messages (short of creating a new issue and mentioning people). Actually, creating an issue on a maintainer joining might be a good idea, I will look into it. Other than that, we have to take many scenarios into account (many people don't want to talk to the new maintainer, for example, because the project is completely abandoned). We should definitely add something, though. I'll see if we can automatically add issues that will be something like "Introduce yourself" with a body of "Hello @maintainer1, @maintainer2! @newmaintainer just joined, please say hi". I have opened an issue if you want to contribute: https://gitlab.com/codeshelter/codeshelter-web/issues/34 https://gitlab.com/codeshelter/codeshelter-web/issues/34
- akavel 7y ago
  Thanks! I'd say "you're welcome to say hi" sounds softer than "please say hi", but other than that, sounds good to me!
  - StavrosK 7y ago
    Oh, yes, the copy was just illustrative.
  - StavrosK 7y ago
    I've implemented your suggestion, thanks! Here's a sample issue that is automatically created: https://github.com/sirodoht/atom-pastery/issues/3 https://github.com/sirodoht/atom-pastery/issues/3

by akavel 7y ago

StavrosK 7y ago

Oh, I definitely agree with you that communication should be more active, it's just that right now this is more left to the new maintainer to do. On Github, everyone's email is public anyway, so the new maintainer could message the old one. I don't think Github/Gitlab provide any automated way to send people messages (short of creating a new issue and mentioning people). Actually, creating an issue on a maintainer joining might be a good idea, I will look into it. Other than that, we have to take many scenarios into account (many people don't want to talk to the new maintainer, for example, because the project is completely abandoned). We should definitely add something, though. I'll see if we can automatically add issues that will be something like "Introduce yourself" with a body of "Hello @maintainer1, @maintainer2! @newmaintainer just joined, please say hi". I have opened an issue if you want to contribute: https://gitlab.com/codeshelter/codeshelter-web/issues/34 https://gitlab.com/codeshelter/codeshelter-web/issues/34

akavel 7y ago
Thanks! I'd say "you're welcome to say hi" sounds softer than "please say hi", but other than that, sounds good to me!
- StavrosK 7y ago
  Oh, yes, the copy was just illustrative.
- StavrosK 7y ago
  I've implemented your suggestion, thanks! Here's a sample issue that is automatically created: https://github.com/sirodoht/atom-pastery/issues/3 https://github.com/sirodoht/atom-pastery/issues/3