New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 689259 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Task



Sign in to add a comment

need a repository for the atrusctl utility

Project Member Reported by gabeblack@chromium.org, Feb 6 2017

Issue description

We need a repository for a utility called atrusctl which will be provided by an external vendor and developed as part of the ChromeOS. It should be accessible by limesaudio@chromium.org (katierh@google.com to confirm).
 
Pardon, I mean this should be a public repository. Does it belong in the existing platform2 repository somewhere?

Comment 2 by aut...@google.com, Feb 9 2017

Owner: gabeblack@chromium.org
Are you asking for a git repo to be created? 
Please confirm the exact name to be used. 

Comment 3 by aut...@google.com, Feb 9 2017

Labels: -current-issue
I just chatted with the infra team, and they need to know two things:

1. Will the repository's initial content be from a snapshot, or will it have history pushed into it from another repository?
2. What should it be called? The thought is to put it in third_party, but we need a name beyond that. Maybe atrusctl? We might want a name with broader scope, but that might also be overkill.
Cc: -katierh@chromium.org gabeblack@chromium.org
Owner: katierh@chromium.org
Katie, could you please answer the infra teams questions?

Comment 6 by jmcgill@google.com, Feb 10 2017

Do we want one repository for each firmware updater, or all firmware
updaters in one repository?
The firmware updater itself is a generic tool, unlike the ChromeOS firmware updater which has the firmware update bundled with it. One repository should be enough, and then the firmware itself will come from the mirror.

We do know that there's no history to preserve, so now we just need confirmation on the name.
Cc: vapier@chromium.org
I chatted with Katie, and she said she was fine with the suggested name, but that we should ask Mike to make sure we're following convention, etc. We're thinking third_party/atrusctl. Could you please confirm that that follows whatever rules there might be?

Comment 9 by vapier@chromium.org, Feb 11 2017

if it's going to be public, then i think chromiumos/third_party/atrusctl/ is OK.  if it's private, then we'd want chromeos/vendor/atrusctl/.  the comments say "public", but the bug summary says "private", so i'm a bit lost.

if it's going to be open source, it's kind of weird that we'd own/host it.  shouldn't the vendor in question be owning it ?  it's pretty trivial to set things up on github.  or is it something we contracted for and it is something we now own ?
Summary: need a repository for the atrusctl utility (was: need a private repository for the atrusctl utility)
The title was wrong, and has been corrected.

My understanding is that the vendor wrote this utility specifically for ChromeOS, and that Google recently purchased them. I originally set things up as if they'd own it externally, but they want to develop it as part of ChromeOS.
chromiumos/third_party/atrusctl/ sounds fine then

would be great that we could start it with a BSD-Google license so there's no confusion in the history
Cc: bhthompson@chromium.org
sounds good, vapier

+bhthompson - can you assist please?
Repo now exists https://chromium-review.googlesource.com/#/admin/projects/chromiumos/third_party/atrusctl

It needs to be added to the manifests to begin use, it was created with an initial empty commit, if force push permissions are desired to nuke that out and replace it with an alternate git history please let me know.

FWIW if the Chromium OS repos are the upstream source here, this is Chromium OS specific code, and the authors are soon to be Chromium project members and want it to be a Chromium component and not a Github project, I would have probably put this in platform or platform2.
Status: Fixed (was: Untriaged)
Since we have this repository now, I'll mark this as closed.

Comment 15 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 16 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61

Comment 18 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment