Newsgroup: tilde.gopher

Back to Article List


Warning: Undefined array key 1 in /home/deepend/public_html/netnews/view_article.php on line 26

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

xwindows  writes:


[...]

>Though it's still my stance that a proper long-term solution is
>advising people to get off that code-laundering (dis)service,  refrain
>from participating (sending bug reports/patches) there [3],  and/or
>avoid getting involved with projects which insist on such disservice
>to be a sole public participation channel in the first place.  

This is exactly what I am doing.   I won't submit a "pull request"...   I
only send git patches with git-send-email(1) ;-) .  

>-----
>
>(WARNING: Rants ahead,  and you probably already know most of this; so
>they are intended for as "to other people reading this reply")
>
>[1]
>To other people reading this reply: I will remind you that the
>original and proper way for an *external* developer to contribute a
>change to a public software project managed in Git is the way that is
>currently used in kernel Linux development [2]; i.e.  `git format-patch
>origin/master` and `git send-email` to the maintainer or project
>mailing list.  
>
>(There is a very specific format of email message involved [4] which
>allows the maintainer to commit the change directly from MIME
>file.  Easier alternative for less stringent projects [tilde-related
>projects counts in this category too] is one can simply write email to
>the maintainer to explaining what the fixes do,  and attach the patch
>files produced from the first command)
>
>The "pull request" style of "contribution" (which needs
>infrastructure) is rather invented by GitHub to brainwash people to
>believe that such submission would inherently require on centralized
>service; in order to capitalize on network effect (i.e.  you need
>account on single web service to submit changes).  It is not even a
>natural way to maintain public participation in this SCM.  

[...]

>[3]
>This do not imply that you cannot submit bug report or patches,  if
>they publish contact email,  mail those to them.  [1] If they tried to
>redirect you to the disservice,  you got declined,  or treated with
>silence; simply share them as if you got responded WONTFIX on your
>report: post them the old way on your website,  describe what they do,  
>the copyright license you are publishing them under,  as well as the
>exact HEAD/branch/repo that your patch series is intended to apply;
>optionally with your own reasons why they didn't get submitted on the
>"official channel".  
>
>[4]
>When I submit change to a tilde project (like Tilde.club Wiki),  I
>personally don't use `git send-email`,  but rather craft my own MIME
>file manually from what `git format-patch` gave me,  then `sendmail -t`
>the result (or import to Alpine and send); allowing me to have a
>discussion message in the front (usually me describing what the patch
>is and what it fixes/adds) and the patch content itself following
>right next to it in the message (rather than as an attachment) for a
>quick review,  separated from each other by thin a scissor line "-- >8
>--".  
>
>Apart from maintaining one-mail-per-commit relation,  this also allows
>the maintainer side to select Pipe command inside a TUI mail client to
>run `git am --scissors` and issue a commit right there if he
>approves.  (I usually include an instruction too,  whenever `--scissors`
>is needed)
>
>Different people might prefer different way to do this though: `git
>--format-patch --cover-letter` which produces an email thread is one
>of the other choices.  

:-) .   I have learned so much from xwindows and from tilde.club .  
Thank you!  

=2D-=20
A little Consideration,  a little Thought for Others,  makes
all the difference.  ~ Alan Alexander Milne

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJmBAEBCgBQFiEEOVeKaEm0xBhCsMmYlk/BEMQK1XUFAmqcOLAbFIAAAAAABAAO
bWFudTIsMi41KzEuMTIsMiwyFhxrZXlib2FyZGFuQHRpbGRlLmNsdWIACgkQlk/B
EMQK1XUWoA/9GSRZXxj8yHayeRBn0UaKnxOPQ1mPvfTmDx6l998FPW+E91Tk+doD
MlIoe+8C0cep1U8KoNgTyuOAAkKwg6LVRfYU903wdN4znZ4speIdDo/XJAYqfYxQ
t+sPbi+9Am72vgh7KsjTr7GOtjGuP/m1lpIIZM1oGhoNKXASnAGkRAdLHhavk2dZ
jKK8md/n/1APyFX2BPzKFjPQGC9Rpdag4QGRo2FeQQp50YfXNlJsAPmVhoktAZhT
bO+AYuPnRJaYLYhZGDVgV8jEhKNRhASa7xZ5QB+nDFKY1JfM8b+8hX6X2R1R+CFv
g82fWRqRmGuAMEGR1BRLLroy15HUIVRoeJkw1ZP5G2L3HFBrd17MzhGoECk0k+rt
mfDMBPEaLi7k9/OG76/2wZHNXQxEiriLj8a99h7sWVp59gKPv3tmXmrSkG1xdxiz
fE3jkUQFDToTJKM8yftj9d28XGUeJCC4enW4tt5ldD825Sos0Y7gqu5yn18S3Ani
HUc4FMhxKeGhcDKTJay8rTw8iDZKuHB0C/gKi8s+RrSJ9aihtDYTZJDuNc+Ywte3
Q46IxEAfj+uAfJ9uj3M/QpMYfHCfeprEHgiMrVnTFoBfL/HnQgFucaw9eMsNYo6S
ZG44fBoFCWiUQ+bWIb24sTX0fqwASPm3Xdj10qutx/urPDvNvDDqgjA=
=ZLPW
-----END PGP SIGNATURE-----
--=-=-=--