Think about moving to the Technical Excellence organization about generics

[StabbyCutyou]

Thank you for bestowing upon me the honor of being an innaugural member of the technicalexcellence organization.

I'll have to weigh this very heavily, as moving the repo would potentially change import paths, which would be backwards incompatible.

As stated in the readme, living up to the high standards of the golang backwards compatibility promise is incredibly important to me, and I do not want to cause problems for the millions of people (in theory - we really have no way of knowing) relying on this project for providing generics.

As go has foregone a solution for managing dependencies until just recently, I'm not certain if I can bear the guilt and shame of breaking this promise, even for such an honor as this.

Potentially I could leave this repo up, deprecated, with a notice to point to the new one. This may be an acceptable solution, providing it is in keeping with the ethos and guidelines of the technicalexcellence organization.

Thoughts?

[dlsniper]

Hi,

Given that soon Go will have an "experimental" alias feature for interfaces, I do not see a reason why moving to a different org would be a bad thing.
I'll probably have to do some renaming in my code as I've already used this in a few places but I can leave with this for now.
Hope this helps making a decision.

Cheers.