Date: Thu, 3 Apr 2014 20:47:00 -0400
From: Mike Gerwitz <email@example.com>
To: "[Name Removed] (GitHub Staff)" <firstname.lastname@example.org>
Hey [Name Removed]; thank you for your reply.
On Thu, Apr 03, 2014 at 04:45:02PM -0700, [Name Removed] (GitHub Staff) wrote:
> Thanks for getting in touch with us here. Some of our internal projects
> are specific to running GitHub, and as such will probably remain closed.
Unfortunately, the code that I am referring to---the code that is served to
the client---is not internal; it runs on the user's web browser, just as any
other software. By visiting GitHub's website, users' web browsers download
* Updating account/profile data;
* Sending pull requests;
* Forking, staring, and watching repositories;
* Changing repository/organization settings;
- Creating wiki pages;
- The issue tracking system; and more.
I would consider the starred ones above to be the most essential features of
disabled---that users should be permitted to do without being required to
surrender their freedoms, especially on a website that should understand at
a deep level the fundamental need for those freedoms (even if GitHub's
philosophy does not coincide).
So my question is this: would GitHub consider:
those tasks---under a free software license of GitHub's choice?
These features would be a great start.
> We do make an effort to open source projects that we create that we think
And while I and many others do certainly appreciate that---some good free
software projects have come out of GitHub---these are things that are
is no different than using any other proprietary software and is therefore
very difficult for free software users to take full advantage of.
The free software community and myself would appreciate a strong
consideration on this topic.
Free Software Hacker | GNU Maintainer
FSF Member #5804 | GPG Key ID: 0x8EE30EAB