I see no reason for using an external domain (or even if it was transferred to the ASF). mynewt.apache.org works today. Why can't that be used, with the same redirect scheme?
On Thu, Feb 4, 2016 at 9:19 PM, Sterling Hughes <sterl...@apache.org> wrote: > Hi Justin, > > mynewt.io would be a vanity domain to make git imports simpler, so > instead of doing: > > import ( > "git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt/cli" > ) > > You'd do: > > import ( > "mynewt.io/newt/cli" > ) > > And for installation of packages, you would do: > > go install mynewt.io/newt > > Instead of: > > go install git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git/newt > > All the cool kids are doing it :-) > > mynewt.io would just provide a set of go metadata. > > We (runtime) have purchased and set this up, because we are lazy and don't > like typing things. We'd be happy to gift this to the ASF, and run it on > ASF infrastructure (perhaps redirect to mynewt.incubator.apache.org). > > I'd be interested in your view, but to me, I feel like this is a nice > developer convenience that makes us agnostic to git structure, and if the > Mynewt project ever decided Runtime were being bad citizens, it's a very > quick change to the source code to remove these references. > > Sterling > > > > On 2/4/16 1:11 PM, Justin Mclean wrote: > >> Hi, >> >> I may be missing something but this may not be the best idea from a being >> open point of view. Who has access to mynewt.io? How are changes >> tracked? How do committers make changes? >> >> Justin >> >>
