Skip to content

Instantly share code, notes, and snippets.

@skopp
Created September 1, 2012 00:04
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save skopp/3561488 to your computer and use it in GitHub Desktop.
Save skopp/3561488 to your computer and use it in GitHub Desktop.
the github social coding paradox
/**
* the github social coding paradox
*/
background-width:960px;
background-color: #fff;
background: linear-gradient(-30deg, #fff, lightgray, #fff);
max-height: 100%;
font-family: helvetica;
font-style: sans-serif;
font-shadow: #fff;
offset-y: -200px;
-webkit-background-clip: padding-box;
-moz-background-clip: padding;
-ms-background-clip: padding-box;
-o-background-clip: padding-box;
background-clip: padding-box;
article, aside, dialog, figure, footer, header, hgroup, nav, section, p
display:block; padding-left: 20px ; offset-horizontal: -200px; width: auto; height:auto;
<!-- content to be placed inside <body>…</body> -->
<ul><ul><ul><ul>|| GIST_____#________| 356 0 714 ||
<h1>The GitHub Paradox</h1>by <a href="http://github.com/skopp">skopp</a> <---- </ul>
<br />
<p>Github is supposed to be about <strong><q>social coding</q></strong> and this aspect must be rather high on their priorities list &mdash;<ul>I mean, it's <em><strong>on the official Github logo</strong></em>.
</p>There is currently (1 September 2012, at time of writing) a sort of paradox in this regard. <br />
<br />
I think I'll illustrate by means of copy/pasted text from actual comment 'threads' of arbitrary issue-tickets of arbitrary repos.</ul><br />
<ul><code><q><strong>With...</strong><br />[continues to describe issue status]... <br />... <strong>is an addition to issue #111</q></strong>
<br /></code><br />
&mdash; now this is where it gets interesting, because he/she goes on to identify (unwittingly) - echoing my own suspicions at the same time - the <em>gist</em> of the problem:</p></li>
<br /><code>
<h1><q>P.S.: Is there a way to discuss things without spamming new issues or thread-nap others?</q></h1>
</code><p><em>&mdash; ["github-user"]</em></p>
<br />
</ul><p>Currently, there are two (as far as I know/as far as I care to know) ways of communicating with devs working on a repo or fork/issue:
<li>Commenting on the issue page itself, or much quicker/simpler and more convenient,
<li>Responding directly via email to a "watched" project.
<li>There is no means of discussing methods, issues, family problems, i.e. no Private Messaging facility on Github itself without "hijacking" an issue's thread
<li>To extend this a bit - there is a gap between noobs and aces. Neither can ask questions/discuss (yes, there are things like email - and many devs don't provide their addresses, yours truly included, twatter, flamebook, IRC, MMORPGs but
why no linked "discuss/ask away" thread linked to issues/repos just as the aforementioned threads are?
<li>note: by "noob" I'm referring to technically-apt newbies, people who understand the concepts, the uses, but maybe just need help with syntax. Or need someone to say: "you muppet, you are supposed to use a ; there instead of a :"
, not the passersby who ask: "duhhh.... wut is guthub lol." <--- if you find these, unleash the wrath of Mammon upon them."
<br />
<ul><br />
&mdash;<a href="http://github.com/skopp">skopp.
{"view":"split","fontsize":"100","seethrough":"","prefixfree":"1","page":"result"}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment