I think the transparency concern is valid. I definitely did not intend to make things less transparent.
I'm not as worried about the security of the domain. There's similar concerns with all the dependencies we pull in. At least I have higher confidence in the domains we have some control over. I want to mention a couple of the benefits of using the vanity domain. I didn't even mention the main benefit in my initial email. 1.) The main benefit is to avoid confusion. The current import paths are a little unusual. Should the import paths include ".git" or not? Why does this import path include ".git" https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-newt.git;a=blob;f=newt/newt.go;h=86d32b44b6d4bea064e4628c8456c1c98316474e;hb=HEAD#l20 and why does this import path not include ".git"? <https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-newt.git;a=blob;f=newtmgr/newtmgr.go;h=7244efa474692b91b99ccc7825ec3167f5b58e63;hb=HEAD#l26> https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-newt.git;a=blob;f=newtmgr/newtmgr.go;h=7244efa474692b91b99ccc7825ec3167f5b58e63;hb=HEAD#l26 In your $GOPATH directory do you have src/ git-wip-us.apache.org/repos/asf/incubator-mynewt-newt.git or do you have src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt? These types of questions don't help people who are new to go. These questions can be avoided by using a vanity domain. 2.) I already mentioned this, but a vanity domain decouples the code from the hosting location. We're going to work very hard to remove the "incubator", so lets make an easy change now instead of a potentially painful change later. 3.) There's precedent for using vanity import domains. For example, https://github.com/kubernetes/kubernetes, a successful open source project, uses k8s.io. I think using mynewt.apache.org sounds good. Aditi and I should be able to get that working. Thanks, -Todd On Thu, Feb 4, 2016 at 8:12 PM, Sterling Hughes <sterl...@apache.org> wrote: > Well, all the cool kids are doing it. :-) > > As the import paths are kinda a PITA (not just the typing, without some > redirect go get/go install seem to be giving people problems depending on > machine), let's start with seeing if we can do this on mynewt.apache.org, > and then if we decide as a project to adopt mynewt.io, we can do that > then. > > Sterling > > > On 2/4/16 7:24 PM, Greg Stein wrote: > >> 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 >>>> >>>> >>>> >>
