New "Inline Install" Review Process

[Simon Knott]

Hi,

I know that many other people in this group have, or are currently, experiencing a manual review after ticking the "Inline Installation" checkbox and I was wondering whether you could clarify what the new review process is and why ticking the checkbox triggers a manual review?

A few questions which come to mind:

• Is there anyway to not trigger a manual review, for test releases, when we still require inline installation?  I'd assumed (hoped) that a manual review would only occur on the first time you ticked the box, but it seems that once it's ticked a manual review is required for the smallest of updates. Doing rapid releases into a test team is fairly critical; since we're fairly restricted to delivering updates to a test team through the webstore with the new policies, if we have to take into account a manual review it would be better to start taking it into consideration now rather than later.
• Will extensions in the future have to tick this box to have inline installation?  Currently only 1 out of my 17 extensions has this ticked, but all of them still currently support inline installations.  Am I going to find that my customers suddenly can't carry out inline installations because I haven't ticked the boxes against all of them?
• Is there any guidance as to how long a manual review can take?  Releasing into the Apple app store, it's fairly common for it to take a week, but they at least allow you to remove and re-publish an update mid-process, should it be required.

Cheers,

Simon

[Or Hiltch]

+1 for this, I too would be happy to hear some official Google information about this new process. I have to say that I expected more transparency from Google. I mean, people are trying to figure out - is this a bug? is this intentional behaviour to better control extensions? 

The idea of manual review is not unreasonable, it's just that right now everything around it is fairly vague. 

[Dick Hardt]

+1 for some transparency on this process

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/88743847-f457-4a68-ba82-45db38610062%40chromium.org.

For more options, visit https://groups.google.com/a/chromium.org/groups/opt_out.

[Spoi Ice]

we are also interested in this, but more importantly (for us), if anyone in power is reading this, please un-pend-the-review or cancel the request or whatever it takes to return bdokagampppgbnjfdlkfpphniapiiifn to the land of the living.  we have updates to publish and have no interest in an inline install if this kind of thing is going to happen.

thank you for your assistance.

[Lukas Zugge]

Yes, we experience the same problem. We develop an extension which is designed to be installed inline. I first thought it might be due to the nature of our extension, but now that I read about other people's problems with the recent changes of Google.

It would be very helpful to get to know the new policy. We are heavily developing and would like to push updates very frequently. Now it seems that we are stuck. This is very frustrating. Googlers, please take some time and write up a guide explaining what sort of extensions will still be fine with automatic checking. 

Lukas

[Spoi Ice]

a HUGE thank you to whomever for finally ending the review process!

[Lukas Zugge]

Same here! Thx, too.

Still, I would be very interested in a catalog of things that will trigger a manual review process. Since We do plan on continuing our programming efforts and wish to push new updates fairly frequently. Our service is currently in beta and reacting to feedback is important to us.

Regards,

Lukas

[Joe Marini]

I've been going through and notifying the team about items that were not properly put into the official review queue. It's rare, but it does happen.

There's no list of things that will trigger a review. If there was, the malicious people that needed to be caught would just get around it.

--

You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/844b90e7-7055-4d9b-b164-f4f2609d1342%40chromium.org.

For more options, visit https://groups.google.com/a/chromium.org/groups/opt_out.

--

Joe Marini

Developer Advocate / Chrome Apps, Extensions, Web Store

joem...@google.com | +Joe Marini | @joemarini

[Lukas Zugge]

I understand your point, but I firmly don't believe in security by obscurity. Google is free to do as they please, and they surely have the market power to do pretty much whatever comes in their minds, but for us developers here in my small company this situation is very frustrating. I am glad that our extension is now back to normal, but we already have again updates ready. I hold them back in the moment because of this unclear review process. It would be helpful to know at least some of your certain gotchas. How about answers to this list:

- will inline installation trigger the manual review for certain?

- will the use of general permissions like http://*/ and https://*/ trigger a manual review?

What are the certain things we can try to avoid, if there is no clear guideline?

Lukas

On Tuesday, February 18, 2014 8:25:37 PM UTC, Joe Marini wrote:

I've been going through and notifying the team about items that were not properly put into the official review queue. It's rare, but it does happen.

There's no list of things that will trigger a review. If there was, the malicious people that needed to be caught would just get around it.

On Tue, Feb 18, 2014 at 12:12 PM, Lukas Zugge <ma...@tyldasoft.com> wrote:

Same here! Thx, too.

Still, I would be very interested in a catalog of things that will trigger a manual review process. Since We do plan on continuing our programming efforts and wish to push new updates fairly frequently. Our service is currently in beta and reacting to feedback is important to us.

Regards,

Lukas

On Friday, February 14, 2014 11:51:57 PM UTC, Simon Knott wrote:

Hi,

I know that many other people in this group have, or are currently, experiencing a manual review after ticking the "Inline Installation" checkbox and I was wondering whether you could clarify what the new review process is and why ticking the checkbox triggers a manual review?

A few questions which come to mind:

• Is there anyway to not trigger a manual review, for test releases, when we still require inline installation?  I'd assumed (hoped) that a manual review would only occur on the first time you ticked the box, but it seems that once it's ticked a manual review is required for the smallest of updates. Doing rapid releases into a test team is fairly critical; since we're fairly restricted to delivering updates to a test team through the webstore with the new policies, if we have to take into account a manual review it would be better to start taking it into consideration now rather than later.
• Will extensions in the future have to tick this box to have inline installation?  Currently only 1 out of my 17 extensions has this ticked, but all of them still currently support inline installations.  Am I going to find that my customers suddenly can't carry out inline installations because I haven't ticked the boxes against all of them?
• Is there any guidance as to how long a manual review can take?  Releasing into the Apple app store, it's fairly common for it to take a week, but they at least allow you to remove and re-publish an update mid-process, should it be required.

Cheers,

Simon

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.

To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/844b90e7-7055-4d9b-b164-f4f2609d1342%40chromium.org.

For more options, visit https://groups.google.com/a/chromium.org/groups/opt_out.

[Alexandre Barreira]

Also holding back on updates until we get more details about this new policy concerning inline installs.. 

I guess we'll have to wait Chrome 33 release and the official blog post that will come along.