We should add some documentation that answers "How do you open-source something via equinix-labs". Maybe it already exists: if so, just a link from the README would be nice.
Questions I would love to see covered:
How to get added to the organization
How to create a new repository
Suggested LICENSE's to use (probably the typical lawyer-friendly ones: Apache, BSD)
How to handle copyright notices
The ask that repositories should be checked for references to internal Equinix tools/names/services before being released to open-source
When Equinix employees go through the SSO they see Equinix Metal logo/name and this should be just Equinix. I also think this may be visible externally.
We link to it from a variety of places and it would be good to replace Packet with Equinix Metal. (fine to mention Packet as in “formerly Packet” etc).
"Elastic Block Storage is only available in Core Legacy Sites: AMS1, DFW2, EWR1, NRT1, SJC1. If you do not have access to these sites, you may reach out to our support team to request it."
The Deprecated tier would serve as a gateway to the end-of-life tier.
In the deprecated tier recommendations should be made about alternatives.
The deprecation date and sunset date should be made clear, linking to any public posts or issues available.
Go package projects have a close relationship with the URLs they are served on.
One project that we may wish to move to equinix-labs is github.com/t0mk/gometal. This project is still in an experimental phase, but it is easy to see a promotion of this project to a packngo successor (packethost/packngo#215).
I think it would be preferable for an official, preferred, SDK to live on equinix/ rather than equinix-labs/. I believe we will continue to see Go projects incubate in equinix-labs and be promoted to equinix.
Should we set up a domain name to avoid breaking go.mod when/if this happens?
Is a CNAME sufficient?
Can we leverage GH package facilities?
Do we need a more featureful redirector, like gopkg.in? Should we just rely on gopkg.in?
Packet was acquired by Equinix in March. To help make our vision for global, interconnected bare metal a reality, we've rebranded Packet as Equinix Metal™ and introduced new locations and features. Login, sign up, and say hello at metal.equinix.com. Example rebrands:
At the moment we don't see any obvious places to add automation but it's possible that @matoszz has some useful elements from the Equinix Metal internal GH org that could be beneficial.
https://github.com/packet-labs is going to be deprecated as an actively-used place to host repos. There are a lot of repos on it that we need to assess as to whether they are worth pulling across into equinix-labs.
This will be raised as an agenda item in the next Equinix Labs administrator meeting (date TBC).
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent