Main rockstor.com webpage. As a community endeavour we welcome contributions / corrections. Be sure to add your name to the AUTHORS file when submitting changes.
License: Other
Update the English text re the modifications detailed and proposed in:
rockstor/rockstor-installer#84
Which for this repo means the same simple substitutions are applied to our copy of the same post edited license.
Relates to content/eula.md
In some instances it has been observed that chome at least fails to 'connect' the drop down menu items with their targets. This is thought to be down to a cache state within the browser, as clearing this for the site, or dev tools cache off, fixes this situation.
It is proposed that we remove both a dependency and some animation via our use of a CSS/JS plugin that does menu fade-in/animation: over an above what is offered by our base bootstrap (no fade-in). Dropping this animation is preferable to failed drop-down target function and is the current candidate for this failure.
See config.toml for plugins used.
There may also then be redundant custom options within our menu definitions which should be removed if they exist.
Best we reduce our complexity/dependencies before then moving froward with updating our bootstrap version etc.
Our existing "Built on openSUSE" Leap 15.3 stable installer downloads are now based on an EOL OS. We are however not yet at our next stable release stage!
But we are at Stable Release Candidate 2 as of: https://forum.rockstor.com/t/v4-5-testing-channel-changelog/8546/6
It is proposed that we offer, in addition to the existing 15.3 downloads based on 4.1.0-0 our latest 4.5.5-0 installers (15.3 and 15.4 based), with provisos that they are Release Candidate 2 currently. This will help with final testing and for folks doing installer testing on the form.
It is further proposed that these newer entries are presented above our existing 4.1.0-0 based entries, if possible.
Can be self hosted but they have hosting possibility. They may be open to hosting free for Open Source projects, but they don't mention this.
It is now some time since we refreshed the stats/contents of this GitHub table. A quick refresh would be good to give folks a more modern idea of what the project consists of code repo and contributor count wise.
We have already referenced, and marked legacy, our prior ISO building mechanism. But we have yet to reference our new https://github.com/rockstor/rockstor-installer repository / recipe. Given this pertains to our ongoing re-release this should be prioritised.
Our forum already has this arrangement, likewise our install Web-UI: plus it underlies/supports the entire project. A consistent far right placement is a more consistent arrangement.
Note the following was based on a test performed prior to our move to https. Some factors may have changed but copying in here from our prior closed repo to keep a note of this performance orentated test facility.
Note also that we are likely to gain some sanity / speed from completing the following issue in this repo:
Migrate to Hugo #1
So we may be better off returning to this issue once we are Hugo generated.
Apparently we are a little behind the times: From a quick test we have have a couple of easy speed-ups:
https://gtmetrix.com/enable-gzip-compression.html
In .htaccess
<IfModule mod_deflate.c>
# Compress HTML, CSS, JavaScript, Text, XML and fonts
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/vnd.ms-fontobject
AddOutputFilterByType DEFLATE application/x-font
AddOutputFilterByType DEFLATE application/x-font-opentype
AddOutputFilterByType DEFLATE application/x-font-otf
AddOutputFilterByType DEFLATE application/x-font-truetype
AddOutputFilterByType DEFLATE application/x-font-ttf
AddOutputFilterByType DEFLATE application/x-javascript
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE font/opentype
AddOutputFilterByType DEFLATE font/otf
AddOutputFilterByType DEFLATE font/ttf
AddOutputFilterByType DEFLATE image/svg+xml
AddOutputFilterByType DEFLATE image/x-icon
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/javascript
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/xml
# Remove browser bugs (only needed for really old browsers)
BrowserMatch ^Mozilla/4 gzip-only-text/html
BrowserMatch ^Mozilla/4\.0[678] no-gzip
BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
Header append Vary User-Agent
</IfModule>
Potential issues, we also serve Rock-ons and older CentOS base repos from this domain.
And:
https://gtmetrix.com/leverage-browser-caching.html
again in .htaccess
<IfModule mod_expires.c>
ExpiresActive On
# Images
ExpiresByType image/jpeg "access plus 1 year"
ExpiresByType image/gif "access plus 1 year"
ExpiresByType image/png "access plus 1 year"
ExpiresByType image/webp "access plus 1 year"
ExpiresByType image/svg+xml "access plus 1 year"
ExpiresByType image/x-icon "access plus 1 year"
# Video
ExpiresByType video/mp4 "access plus 1 year"
ExpiresByType video/mpeg "access plus 1 year"
# CSS, JavaScript
ExpiresByType text/css "access plus 1 month"
ExpiresByType text/javascript "access plus 1 month"
ExpiresByType application/javascript "access plus 1 month"
# Others
ExpiresByType application/pdf "access plus 1 month"
ExpiresByType application/x-shockwave-flash "access plus 1 month"
</IfModule>
"Depending on your website's files you can set different expiry times. If certain types of files are updated more frequently, you would set an earlier expiry time on them (ie. css files)"
and:
Recommendations
Be aggressive with your caching for all static resources
Expiry at a minimum of one month (recommended: access plus 1 year)
Don't set your caching more than a year in advance!
Be careful
You want to be careful when enabling browser caching as if you set the parameters too long on certain files, users might not be getting the fresh version of your website after updates.
It is proposed that we make available on the "Downloads" page a Tumbleweed based installer. With a label such as:
Intended for Development/Advanced-user/Rescue use only
Given we are again looking at TW for that the future may hold re upstream changes. Hence the development element. Plus in situations where one need a very recent kernel/btrfs version such an installer may help in pool/s rescue scenarios.
On Tumbleweed we already use the preferred zypper dup when doing Web-UI initiated OS updates. But as of our first 4.5.8-0 installer version uploaded we have inadvertently, and unnecessarily, sourced our kiwi package from the upstream Virtualisation repo. This in turn means our Web-UI initiated update fails due to a 'vendor' change requirement.
IGNORE THIS ISSUE IF IT IS CLOSED
Via cli:
zypper dup
Computing distribution upgrade...
3 Problems:
Problem: problem with the installed dracut-kiwi-lib-9.24.57-1.1.aarch64
Problem: problem with the installed dracut-kiwi-oem-dump-9.24.57-1.1.aarch64
Problem: problem with the installed dracut-kiwi-oem-repart-9.24.57-1.1.aarch64
Problem: problem with the installed dracut-kiwi-lib-9.24.57-1.1.aarch64
Solution 1: install dracut-kiwi-lib-9.24.57-1.1.aarch64 from vendor openSUSE
replacing dracut-kiwi-lib-9.24.57-1.1.aarch64 from vendor obs://build.opensuse.org/Virtualization:Appliances
Solution 2: keep obsolete dracut-kiwi-lib-9.24.57-1.1.aarch64
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): 1
with the same answer for the other 2 vendor change Solutions and we have:
The following 3 packages are going to be reinstalled:
dracut-kiwi-lib dracut-kiwi-oem-dump dracut-kiwi-oem-repart
The following 3 packages are going to change vendor:
dracut-kiwi-lib
obs://build.opensuse.org/Virtualization:Appliances -> openSUSE
dracut-kiwi-oem-dump
obs://build.opensuse.org/Virtualization:Appliances -> openSUSE
dracut-kiwi-oem-repart
obs://build.opensuse.org/Virtualization:Appliances -> openSUSE
We use Zulip currently for a subset of side channel developer discussion and notes. In time we hope to also use it for support purposes: once our new fiscal arrangements are in place. The Rockstor Project, as a community focused open source endeavour, have service sponsorship from Zulip via the following program they offer:
https://zulip.com/for/open-source/
This issue is to address a, requested by both parties, cross promotion effort: on our part to add a Zulip Logo to our main website's (source in this repo) front page "Our Partners" section using the newly updated instructions available in the following link:
Now this repo is public we can reference it's existence on the About Us page with a note indicating that it is the place to visit for website errors or additions. Although this may be self evident / redundant.
It is advised by Shopify, who currently host our shop, that we should add a link to our shops California Consumer Privacy Act (CCPA) opt-out page.
We already have the related setting for EU visitors of:
"Limit data collection for EU buyers is Activated." for EU GDPR compliance on the shop.
and our Current California setting is:
"Limit data collection for California buyers is Activated."
We do not knowingly have any tracking settings active within our Shopify hosted shop.
Shopify reference for this issue: https://help.shopify.com/en/manual/your-account/privacy/cookies
A trivial change that should bring the website 'front' content in line with this same normalisation carried out in our Web-UI & documentation by @jonpwilson
Web-UI
pr: Replace 'e-mail' with 'email'. rockstor/rockstor-core#2124
issue: 'Email' or 'E-mail' wording rockstor/rockstor-core#2122
Docs:
pr:Replaced 'e-mail' with 'email' rockstor/rockstor-doc#232
issue: "normalise on email, replacing e-mail" rockstor/rockstor-doc#230
During a typical Rockstor install we link to the EULA hosted at rockstor.com: https://rockstor.com/eula.html contained within this repo. However there are no links within the main site content to this page. It is proposed that we 'surface' this EULA so that folks are not necessarily presented with this text for the first time during install.
It may also be advisable to update the existing text to address our more recent release candidate installs. Essentially still GPLv2 however but with additional 'Marks' references inherited from our sed of our "Built on openSUSE" upstream base.
See: https://github.com/rockstor/rockstor-installer/blob/master/config.sh
for the referenced Stream Edit re Trade Marks.
As of 1st July 2023 we no longer use our now legacy subdomain of 'shop' (https://shop.rockstor.com): a Shopify backed shop-front previously used to take financial contributions and, in-turn, via API polling from our Appliance ID manager 'Appman' (https://appman.rockstor.com), play a part in fulfilling Stable Update subscription memberships via activation code issuance via email.
We have now begun the process of enabling Appman's interoperability instead with our new Fiscal arrangements managed, in the open, by our newly established Open Collective:
https://opencollective.com/the-rockstor-project
See the following forum thread for context of this earlier-than-planned transition:
https://forum.rockstor.com/t/appman-rockstor-com-maintenance-open-collective-integration/8867
It is proposed that, in the context of the above, we establish a new landing page for those visiting shop.rockstor.com to explain the now differing arrangements regarding fiscal contributions - and differing requirements regarding activation code emails.
Our prior shop took Appliance ID entry via Web-UI or url 'applianceid' specification. This has yet to be established in our Open Collective Stable Updates subscription tier - but is believed to be possible via customFields and their consequent order values presented in order.customData. However this Open Collective counterpart has yet to be enabled on the front-end but is partially implemented in our Appman back-end. So for now we have implemented, within Appman, the ability to enter an initial Appliance ID on newly created (via WebHook initiated call backs from Open Collective) orders.
So we now have two Stable Updates subscription membership activation code receipt paths:
(2.) is akin to our prior arrangement - as detailed earlier - but we are currently developing 1. for overall flexibility and because we have yet to establish the associated tier customFields. There is also the potential for less friction/fuss when less elements are involved in any one step - even if further steps will ultimately include the otherwise complicating info: read Appliance ID requirement being dropped as an option in our Open Collective tier membership. However optional entry would be good for convenience renewal links and the like.
As per #49 we should now favour a RC* on a non EOL base os to a prior year old stable on an EOL base. Thus we should update our "Built on openSUSE Rpm" instructions accordingly to use Leap 15.4 and 4.5.5-0 (Release Candidate 2).
And endeavour to update as we develop further our Release Candidate versions in the testing channel.
Replace currently unused Twitter account/link with newly created Mastodon account/link:
See also: https://docs.joinmastodon.org/user/profile/#verification
We have soon to address a non trivial forum migration that will incur several possibly hours long outages and likely some periods of read-only access. With the forum down it would be reasuring for folks to have clear feedback on this process being underway/planned.
This issue is likely to come into relevant within the next few days, depending on resources. Creating here ready for the required changes to be made website wise.
In line with rockstor-core modifications below, it is proposed that we surface the newer paypal.me donate link either in just the Readme.md in this repo or also in our "About Us" page.
pr: Update Readme.md and add paypal.me donate link rockstor/rockstor-core#2257
which was followed up by removing the long standing and ineffectual Rockstor Web-UI donate components:
pr: Remove donate menu item and update legacy paypal mechanism rockstor/rockstor-core#2262
To aid in further significant development, and ease community contribution, including translations, it is proposed that we transition this now hard-coded site to Hugo (Syna theme).
This should be done, given it's breadth, via a dedicated branch. Upon completion we then transition over and remove all hard coding to return again to leaveraging the advantages of a Static Site Generator. Prior now defunct/orphaned generator was thought to be hyde.
Please update the Readme.md file while tending to this issue.
Ongoing progress/TODO list:
On the downloads page we have several indicators that our Stable Kernel Backports howto is out-of-date. As of:
rockstor/rockstor-doc#413
It now pertains to 15.4, and likely also 15.5 as we leave the new URL uncommitted with a note to adjust accordingly.
Update our downloads page accordingly as our caveat is not longer relevant.
Currently our commercial support page has the following statement re downloads:
"Our downloadable installers contains the first v4 stable release."
Where-as of late, we have taken to offering stable release candidates as they appear. It would be an improvement in consistency to also note the same in this sentence linking to the downloads page.
Our Downloads page currently states:
“Built on openSUSE” installers are Stable or RC status.*
We have recently released the 4.1.0-0 rpm into testing and it's promotion to the stable channel is imminent. We should consequently correct the Release Candidate reference and update the included rpm version (installer version) available in the various downloads.
Depends on #30
The business interests related to commercial support (pending reactivation now v4 stable is out), maintenance, server costs, and package distribution are in the process of relocating. In the interests of transparency is it proposed that the About-Us page be updated accordingly regarding the pending &/or completed move.
Currently we have:
"Sole trader (UK): Philip Paul Guyton - ..."
It is proposed that this be transitioned to:
""Empresário em Nome Individual (Portugal): Philip Paul Guyton - ..."
During this transition in updating the relevant payment systems etc it is anticipated that the shop may have to momentarily pause transactions. If this pause is significant, as things are necessarily lined up behind the scenes, we should also pop-up a notification here on the main website. This issue could also serve to document the changes necessary here in the website repository to enact this temporary notification.
Apologies in advance for those that may be inconvenienced by this move. Only the shop is expected to be affected, and then only for a short time is the hope.
On the About Us page we now have outdated contributor counts referenced for our various repos. It would be good to have this be more representative of our current contributor count.
On the Downloads page we have the following:
Transfer to (sdX): xzcat Rockstor-Leap15.3-RaspberryPi4.aarch64-4.1.0-0.raw.xz | dd bs=4M of=/dev/sdX iflag=fullblock conv=notrunc status=progress
But unless this is executed as root it will fail, and few linux distros use this default.
It is proposed that we instead add the sudo command such that it reads:
(with in this example our newer installer specified)
Transfer to (sdX): xzcat Rockstor-Leap15.4-RaspberryPi4.aarch64-4.5.4-0.raw.xz | sudo dd bs=4M of=/dev/sdX iflag=fullblock conv=notrunc status=progress
We have recently updated to Stable Release Candidate 3 within our testing channel. Update the downloads page accordingly.
See: https://forum.rockstor.com/t/v4-5-testing-channel-changelog/8546/7 for the 4.5.6-0 RC3 anouncement.
Replace or augment existing Signal link with Mastodon DM suggestion. Our newly established Mastodon ID enables a further option for when our new fiscal existence is finalised.
In/on our About-Us page we have the following:
Our website uses the “rockstor” domain, while support uses the “linuxlines” domain. We hope to further rationalise these ‘mixed’ domains as we work towards sustainable Open Source development.
Due to recent efforts on behalf of the project founder @schakrava we are now in a position to loose the linuxlines.com 'shadow' domain and properly re-establish on the rockstor.com for support emails.
This issue is to address this poor 'optic' and make nice around the canonical domain.
This JavaScript library back-ports/enables CSS3 Media Queries in older browsers such as IE8. It is proposed, as part of reducing our dependencies and preparing for the update of our bootstrap dependency that we drop this now hopefully no longer required library.
May also relate to #35
Library reference: https://github.com/scottjehl/Respond
As we are currently pre-release in the Rockstor 4 "Built on openSUSE" endeavour, and intend to make pre-build installers available only once we reach our next designated "Stable" release, it may well be useful to have a place holder of sorts on our Downloads page that references our DIY installer repo for the time being. At least until we have publicly available downloads in place. Or an official OBS url resourcing our kiwi-ng config.
We have a reference to CentOS, our near legacy Rockstor 3 OS base, on the following page:
https://rockstor.com/linux-btrfs-nas-server.html
As per our similarly scoped doc issue "Update base OS info" rockstor/rockstor-doc#268 we should now present this as pertaining only to our Rockstor 3 variant, accompanied by a "Built on openSUSE" phrase to show our new base OS for the new Rockstor 4 endeavour.
This issue also relates to the just merged/published:
"Add Rockstor 4 installer download place-holder links #7" #16
JetBrains has recently sponsored "The Rockstor Project" via their Open Source support initiative. We have, in response to our request, received permission to indicate this arrangement. In keeping with our obligations as a non-profit Open Collective re support arrangements.
Two "All Products Pack" Licenses were awarded initially as we find-our-feet in the first year of our new Open Collective standing.
Thanks again to JetBrains for this sponsorship, and their special accommodation in our case, and my apologies for the delay in the creation and execution of this issue. A GitHub search of our organisation indicates our years long use and recommendation for particularly PyCharm Pro - a favoured IDE of both the maintainer and the senior developer.
Proposed link: https://www.jetbrains.com
Requested icon: (JetBrains): https://www.jetbrains.com/company/brand/#logos-and-icons-jetbrains-logos
As digital laws vary around the world, it is proposed that we identify on our "About Us" page the current residency status of the projects:
"Current maintainer, project lead, packager, distributor, and subscription shop owner/admin"
This is now: Portugal.
Not likely relevant to the vast majority of our users/interested parties, but could be important for some business/fiscal backing entities in the near future. We do however already identify the GitHub Organisation as European.
As of December 2022, openSUSE Leap 15.3 is EOL. We should consequently remove our downloads' page entries built on this now deprecated OS version.
https://en.opensuse.org/Portal:15.3
https://en.opensuse.org/openSUSE:Roadmap
An edit of the "downloads_os_order" line in config.toml should accomplish this.
As of 31st December 2021, openSUSE Leap 15.2 is EOL. We should consequently remove our downloads' page entries built on this now deprecated OS version.
https://en.opensuse.org/Portal:15.2
An edit of the following line in config.toml should accomplish this:
# use lowercase version of frontmatter os
downloads_os_order = ["leap15.3","leap15.2", "diy", "centos7.1511", "rpm"]
As per rockstor-installer issue:
"Update default version to 4.0.8-0 ...":rockstor/rockstor-installer#77
we should harmonise our web site download page text similarly.
When I attempt to load https://rockstor.com/dls.html in my browser (Firefox 95.0.1 (64-bit) on Ubuntu 20.04.3), I am greeted by many offset titles where I would presume a logo should be:
However, I see that that this is specifically done without an image here: https://github.com/rockstor/rockstor-website/blob/master/layouts/dls/list.html#L26-L29
In my mind, if the header was not squished to the left side but rather only left-justified, it would look better than it does now. Why was col-sm-4 chosen as the width for the "Built on" header? Could it be extended to at least col-6 for a 50% width?
We have recently updated to Stable Release Candidate 5 within our testing channel, and rebuilt 15.3 & 15.4
downloadable installers to include this new version. Update the downloads page accordingly.
Update the downloads page accordingly.
See: https://forum.rockstor.com/t/v4-5-testing-channel-changelog/8546/10
We may also want to indicate a recent bug re our EOL 15.3 based installers:
rockstor/rockstor-core#2516
It is proposed that we now link, on our downloads page, to the new v3 to v4 migration howto. This helps to inform folks who visit the downloads page that are already running a v3 and know little of our CentOS to openSUSE Leap transition.
Commerce/Commercial is associated with large scale exchanges, lets be plain speaking on this front. We intend to offer "Paid" support via an "Incident Based Support subscription" Tier at our new Open Collective:
https://opencollective.com/the-rockstor-project
This issue should also rename the link involved:
https://rockstor.com/commercial_support.html
and ensure the old link, embedded within our older Web-UI's, redirects to the new link of say:
https://rockstor.com/paid_support.html
Hugo "Aliases" should take care of this redirect:
https://gohugo.io/content-management/urls/#aliases
In our docs, release package, and rockstor-jslibs we have more recently been far more exhaustive/detailed about our overall License re moving to SPDX and properly including the licenses associated with our jslibs as per:
It is proposed that, now we have the following doc section:
https://rockstor.com/docs/interface/system/update_channels.html for our package make-up which is in turn linked to form our FAQ here:
How is Rockstor licensed? : https://rockstor.com/docs/faq.html#how-is-rockstor-licensed
that we use this FAQ entry as a link within our EULA given it also includes a reference to the Installer License - as the EULA is linked to within our installer:
Our prior wordpress blog at https://rockstor.com/blog/ is no longer integrated within our main site. Displaying only:
"Apologies, our blog has passed-away."
It would be preferable if we had this as a page within our new Hugo site, post issue #1 resolution. It may then also be possible to re-publish our last two post there:
and
All other posts are now way too dated, or no longer relevant.
which would, in turn, restore our blog but this time under the umbrella of our regular website. We will not be re-instating a word-press instance.
Under prior maintainer-ship there was a YouTube channel "rockstorinc"; this fell into disrepair and has since been removed entirely with the loss of it's entire library. There is still a "rockstor" YouTube channel but it is very sparsely populated and also in a state of neglect / limbo.
Given the above it is proposed that we remove our existing broken link to this now defunct channel. Link instance found to date in header under YouTube icon.
https://www.youtube.com/user/rockstorinc
Since our more recent move to hosting via https, see: rockstor/rockstor-core#2226 we are generating mixed content warning/erros in browsers. Notably, and likely redundant, is an http font link thus:
Blocked loading mixed active content “http://fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,600italic,700italic,800italic,400,600,700,300,800”
This should be resolved or removed as appropriate; along with all other hard coded http links, where possible.
We now already have, on the About-Us page, a reference to our new Open Collective status. However it would be good to also include this within our Community menu item, especially given it is the key driver for sustainability and is very definitely a community element to the project: given we are community funded.
We have likely a css issue in the colour combination used in these buttons. The are OK before use but on hover and active their text is too close to background:
Unused
Documentation button hover or already clicked:
As these buttons add complexity and are now in keeping with our front page buttons we might also consider removing them entirely given they repeat links already provided by the text links they immediately follow.
It is proposed that we move to a minimal cost for "Incident based support" as it is postulated that this will encourage (and enable) more Stable subscribers to pay for this support plan. And in turn help with our aim of achieving sustainable Open Source development.
"Support is charged on a per bundle basis (pricing unavailable until service reinstated: estimated at £200 / incident)."
Related to the ongoing issue #36:
"Support is charged on a per incident basis, expected re-launch price €99 + tax (if applicable) per incident."
The Rockstor Project is now officially a non-profit/non-business via the Open Collective / Open Collective Europe (Fiscal host). It is proposed that we update the About-Us page to reflect this major development in our status.
Links to include:
The Rockstor Project's Open Collective page: https://opencollective.com/the-rockstor-project
The Open Collective's page: https://opencollective.com/
Open Collective Europe's page: https://opencollective.com/europe
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.