3 ms·

Create a Github account Which most people have already and it allows you to contribute to a gazillion of repositories. Run git send-email, Check email for rep

Create a Github account Which most people have already and it allows you to contribute to a gazillion of repositories. Run git send-email, Check email for replies There is one important step missing here: Find out who to send the patch to or subscribe to a mailinglist (and later unsubscribe). In the former case, if a maintainer goes AWOL, the patches that they received are lost. In the latter case, subscribing to a mailinglist, let alone for every project that you want to do a drive-by submission, also involves several steps: - Figure out how to subscribe - Subscribe - Set up filter in your e-mail client to avoid cluttering up your inbox. - Unsubscribe when you are done To reply to emails, you can use any email client or even do that in the browser.* You can also reply to GitHub issue e-mails. (I am not a big fan of GitHub, but I think it is important to understand why a lot of people find GitHub so convenient.)

u801e 8y ago
> Which most people have already and it allows you to contribute to a gazillion of repositories. And pretty much everyone has an email account. In fact, I don't think it's possible to sign up for a Github account without providing an email address. > There is one important step missing here: Find out who to send the patch to Many projects have a README or CONTRIBUTING file that describes the necessary steps. Looking at projects that don't accept Github pull requests (like the Linux kernel or git itself), there are (as of the time I'm writing this post) 225 and 155 open pull requests on each respective project, which indicates that people aren't reading the documentation before trying to make a contribution. > In the former case, if a maintainer goes AWOL, the patches that they received are lost. The same thing can happen in Github if the maintainer never bothers to acknowledge the pull request or just closes it. Finding a particular patch out of the hundreds of open but not acknowedged pull requests in the linux and git repositories isn't going to be easy. >> To reply to emails, you can use any email client or even do that in the browser. > You can also reply to GitHub issue e-mails. I made the statement about using any email client (local or web based) because the post I replied to stated that one needed to use a TUI client like mutt.
- Boulth 8y ago
  > I made the statement about using any email client (local or web based) because the post I replied to stated that one needed to use a TUI client like mutt. Wouldn't using HTML email (default in most modern clients and webmails) be frowned upon by the ML participants? (for the record I liked your comparison)
  - u801e 8y ago
    > Wouldn't using HTML email (default in most modern clients and webmails) be frowned upon by the ML participants? It depends on the mailing list. They may not mind in terms of general correspondence or review of code, but they would definitely have strict requirements for emails that contain patches that a maintainer would have to apply (so that it works with git am).

u801e 8y ago

> Which most people have already and it allows you to contribute to a gazillion of repositories. And pretty much everyone has an email account. In fact, I don't think it's possible to sign up for a Github account without providing an email address. > There is one important step missing here: Find out who to send the patch to Many projects have a README or CONTRIBUTING file that describes the necessary steps. Looking at projects that don't accept Github pull requests (like the Linux kernel or git itself), there are (as of the time I'm writing this post) 225 and 155 open pull requests on each respective project, which indicates that people aren't reading the documentation before trying to make a contribution. > In the former case, if a maintainer goes AWOL, the patches that they received are lost. The same thing can happen in Github if the maintainer never bothers to acknowledge the pull request or just closes it. Finding a particular patch out of the hundreds of open but not acknowedged pull requests in the linux and git repositories isn't going to be easy. >> To reply to emails, you can use any email client or even do that in the browser. > You can also reply to GitHub issue e-mails. I made the statement about using any email client (local or web based) because the post I replied to stated that one needed to use a TUI client like mutt.

Boulth 8y ago
> I made the statement about using any email client (local or web based) because the post I replied to stated that one needed to use a TUI client like mutt. Wouldn't using HTML email (default in most modern clients and webmails) be frowned upon by the ML participants? (for the record I liked your comparison)
- u801e 8y ago
  > Wouldn't using HTML email (default in most modern clients and webmails) be frowned upon by the ML participants? It depends on the mailing list. They may not mind in terms of general correspondence or review of code, but they would definitely have strict requirements for emails that contain patches that a maintainer would have to apply (so that it works with git am).