<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 09/08/16 18:19, Manik Taneja wrote:<br>
</div>
<blockquote
cite="mid:CAEQrNmuVqeYvB9bDxcqA6WvJfYC46pXoJECcstyEgY2UTq3L+g@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra">
<div>will this allow them to claim the reserved name? <br>
</div>
</div>
</div>
</blockquote>
<br>
We can allocate a name to a publisher very easily, just need the
authoritative upstream to ask on this mailing list.<br>
<br>
In this case we should probably use the new 'collaborators' feature
in the store, which lets multiple accounts (the 'collaborators')
push a snap on behalf of the actual publisher. That way the
community person who leads the setup of the snap and the CI with
Travis and Github integration can shepherd things along until folks
upstream have the hang of it. Then we could remove the snapcrafter
from the collaborators list, which means the upstream publisher has
exclusive ability to release new revisions, once they have a good
upstream process for daily builds (edge) and betas and the actual
candidate/stable releases too.<br>
<br>
Mark<br>
</body>
</html>