I don't think it's necessary for GG open source their own work. These days, it seems that anybody who writes a piece of code ends up pushing it right away to GitHub with an open-source license and says, “I’ve open-sourced it.” Creating an open-source project isn’t just about making your code freely available to others. Also you need to decide why you are open-sourcing the project in the first place.
A good point! I've written, and am currently run-testing, a Java-coded bot to track the prices of Nxt Assets on the HZ Asset Exchange for up to 25 HZ Assets, each of which can serve as alias Assets for any of the 500+ extant Assets on the Nxt Asset Exchange. I'm not releasing it as open-source, at least not as of yet, because it's not good enough for open-source!
In addition to being something of a disorganized mess inside
, it requires hard-coding each of the created HZ Assets, the corresponding Nxt backing accounts, and a few other parameters for each alias Asset that's been created on the HZ Exchange. Yep, hard-coding for each of them. Leaving aside the "magic number" programming no-no, it's about as user-unfriendly as you can get.
The de facto bar on open-source has been raised so much over the years, the functional but messy one-class Java script I created simply isn't ready for open-source distribution. If I re-organize, polish and add some checks to it - and make it a multi-class app with a .jar file - it could be, in some months. But as it stands now, even though it seems to be working okay, it's simply not ready for open-source prime time.
