HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
svnpenn
sage
HISTORICAL RECORD2016–2016
svnpenn / sage · Not publicly available

sage

Discover this repository through its Hacker News conversations.

2Distinct people
3Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval3 dated mentions

Observed mentions: 2016-02-02 15:26:13 UTC to 2016-02-05 08:22:13 UTC.

0122016-02-02 15:00:00 UTC to 2016-02-02 18:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsFeb 2, 15:002016-02-02 18:00:00 UTC to 2016-02-02 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-02 21:00:00 UTC to 2016-02-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-03 00:00:00 UTC to 2016-02-03 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-03 03:00:00 UTC to 2016-02-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-03 06:00:00 UTC to 2016-02-03 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-03 09:00:00 UTC to 2016-02-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-03 12:00:00 UTC to 2016-02-03 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-03 15:00:00 UTC to 2016-02-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-03 18:00:00 UTC to 2016-02-03 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-03 21:00:00 UTC to 2016-02-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 3, 21:002016-02-04 00:00:00 UTC to 2016-02-04 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-04 03:00:00 UTC to 2016-02-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-04 06:00:00 UTC to 2016-02-04 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-04 09:00:00 UTC to 2016-02-04 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-04 12:00:00 UTC to 2016-02-04 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-04 15:00:00 UTC to 2016-02-04 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-04 18:00:00 UTC to 2016-02-04 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-04 21:00:00 UTC to 2016-02-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-05 00:00:00 UTC to 2016-02-05 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-05 03:00:00 UTC to 2016-02-05 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-05 06:00:00 UTC to 2016-02-05 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 5, 06:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 2, 15:002016-02-02 15:00:00 UTC2016-02-02 18:00:00 UTC211
Feb 2, 18:002016-02-02 18:00:00 UTC2016-02-02 21:00:00 UTC000
Feb 2, 21:002016-02-02 21:00:00 UTC2016-02-03 00:00:00 UTC000
Feb 3, 00:002016-02-03 00:00:00 UTC2016-02-03 03:00:00 UTC000
Feb 3, 03:002016-02-03 03:00:00 UTC2016-02-03 06:00:00 UTC000
Feb 3, 06:002016-02-03 06:00:00 UTC2016-02-03 09:00:00 UTC000
Feb 3, 09:002016-02-03 09:00:00 UTC2016-02-03 12:00:00 UTC000
Feb 3, 12:002016-02-03 12:00:00 UTC2016-02-03 15:00:00 UTC000
Feb 3, 15:002016-02-03 15:00:00 UTC2016-02-03 18:00:00 UTC000
Feb 3, 18:002016-02-03 18:00:00 UTC2016-02-03 21:00:00 UTC000
Feb 3, 21:002016-02-03 21:00:00 UTC2016-02-04 00:00:00 UTC000
Feb 4, 00:002016-02-04 00:00:00 UTC2016-02-04 03:00:00 UTC000
Feb 4, 03:002016-02-04 03:00:00 UTC2016-02-04 06:00:00 UTC000
Feb 4, 06:002016-02-04 06:00:00 UTC2016-02-04 09:00:00 UTC000
Feb 4, 09:002016-02-04 09:00:00 UTC2016-02-04 12:00:00 UTC000
Feb 4, 12:002016-02-04 12:00:00 UTC2016-02-04 15:00:00 UTC000
Feb 4, 15:002016-02-04 15:00:00 UTC2016-02-04 18:00:00 UTC000
Feb 4, 18:002016-02-04 18:00:00 UTC2016-02-04 21:00:00 UTC000
Feb 4, 21:002016-02-04 21:00:00 UTC2016-02-05 00:00:00 UTC000
Feb 5, 00:002016-02-05 00:00:00 UTC2016-02-05 03:00:00 UTC000
Feb 5, 03:002016-02-05 03:00:00 UTC2016-02-05 06:00:00 UTC000
Feb 5, 06:002016-02-05 06:00:00 UTC2016-02-05 09:00:00 UTC101

What Hacker News says

3 sources
Steven Penny had the opportunity to explain his doings: https://github.com/svnpenn/sage/issues/2 https://github.com/svnpenn/sage/issues/3 https://github.com/svnpenn/sage/issues/4 but choose not to say more than claiming to be the sole developer of apt-cyg. This apt-cyg project has a history back to 2005, released under GPL by Stephen Jungels (according to the original code) and Stephen is also the owner of the now DCMA:ed GitHub repo. https://github.com/transcode-open?tab=repositories When apt-cyg moved from Google Code to GitHub it seems that the license changed from GPL to MIT, most likely a move by Stephen Jungels. So how can Steven Penny claim rights over apt-cyg? Maybe he did a complete rewrite of the code? One can only guess at this stage. If he did, feel free to do so, the code was MIT, improve, rewrite, re-label and try to market
Read the rest
your version. Thats all in the interest of open source movement. No harm done. But, it does not seem right, to claim something that has been open source code for more than 10 years. Not even a complete rewrite gives you the power to file a DCMA on open source project. That does not feel right and such an action can never be a positiv movement for the open source community. Something is fishy, maybe there is more than meets the eye? Still, no matter the claim, filing a DCMA on open source code where the project has thousands of active users, well, thats not good for open source.
In Steven Penny is forcefully claiming ownership of MIT code

Steven Penny is forcefully claiming ownership of MIT code

So, someone mentioned to me that Steven Penny is trying to claim the ownership of code which he did not write and code that's released under the MIT license. So what did he do? 1. Renamed apt-cyg to sage (See commits on the 24th of January https://github.com/svnpenn/sage/commits/master) 2. Filed a DMCA takedown on the original repository https://github.com/github/dmca/commit/28ceb5f8dd70b1a7f92d3f9fae053f039b2883c4 There's a counter-DMCA takedown: https://github.com/github/dmca/commit/e74005839a278219774a8c53fd57c6574b607eb0 The original source on Google Code: https://apt-cyg.googlecode.com/svn/trunk/apt-cyg So, let's get this to the top so the whole world can see what a major arsehole Steven Penny is.
15 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.