[chromium-dev] Another issue closed from non googlers

[Alexander Yashkin]

Hi all.
Can the sync owners, please, open the following issue and design document to non-googlers.
https://bugs.chromium.org/p/chromium/issues/detail?id=870624
https://docs.google.com/document/d/14ScYZ0sop921gjBwXuReIEuQJlwftqkuSM1jMK_A_x4

Is where an open version of this document?

What's the purpose of closing such issues from non-google project members? It does not look like security issue to me.
We (members of yandex team) are also implementing sync server and client functionality and going through a lot of frustration(and pain)
while supporting our code. Problem is we have to guess where design and refactoring of sync component is heading looking only at code diff and patches description.

WBR
Alexander Yashkin

[Mikel Astiz]

Hi Alexander,

Post by Alexander Yashkin
Hi all.
Can the sync owners, please, open the following issue and design document to non-googlers.
https://bugs.chromium.org/p/chromium/issues/detail?id=870624

I'll take care of this.

Post by Alexander Yashkin
https://docs.google.com/document/d/14ScYZ0sop921gjBwXuReIEuQJlwftqkuSM1jMK_A_x4
Is where an open version of this document?

There isn't such a document, but there probably should be, since chromium
does have commitment to make design docs publicly available. Let me see
what I can do.

Post by Alexander Yashkin
What's the purpose of closing such issues from non-google project members?
It does not look like security issue to me.

The reason for the crbug is that, if the type "Launch" (which our policies
require for A/B testing), it gets automatically restricted to Googlers.

I will downgrade the bug to feature request and then file a new bug for the
launch itself.

Post by Alexander Yashkin
We (members of yandex team) are also implementing sync server and client
functionality and going through a lot of frustration(and pain)
while supporting our code. Problem is we have to guess where design and
refactoring of sync component is heading looking only at code diff and
patches description.

Sorry for the inconveniences, and thanks for the reminder.

Here's some summary of ongoing sync-related migrations:
1. We will migrate passwords to USS (engineering work is expected to start
now).
2. We hope to use pseudo-USS to wrap all remaining datatypes into USS
architecture (M72 or M73).
(we do have a pseudo-USS codepath for passwords too, but hope to never
launch it)
3. We plan to dismantle the sync-directory codepath somewhere around
2019-Q2.
4. We plan to remove support for directory itself in the second half of
2019.

These changes are not expected to be noticeable server-side. We also do not
commit to specific timelines, the dates above are rough estimations.

Let me know if you have specific questions.

Cheers,
Mikel

Post by Alexander Yashkin
WBR
Alexander Yashkin

[Mikel Astiz]

Hi Alexander,

Post by Mikel Astiz
Hi Alexander,

Post by Alexander Yashkin
Hi all.
Can the sync owners, please, open the following issue and design document
to non-googlers.
https://bugs.chromium.org/p/chromium/issues/detail?id=870624

I'll take care of this.

The bug should be accessible publicly now.

Post by Mikel Astiz

Post by Alexander Yashkin
https://docs.google.com/document/d/14ScYZ0sop921gjBwXuReIEuQJlwftqkuSM1jMK_A_x4
Is where an open version of this document?

There isn't such a document, but there probably should be, since chromium
does have commitment to make design docs publicly available. Let me see
what I can do.

Because of technical issues, I cannot share the original document publicly,
so I created a copy:
https://docs.google.com/document/d/1Pd3bTBnk2RhVdYsnFPdvtTtAms_OPEBUO7Sp3cjlyyM


Cheers,
Mikel

Post by Mikel Astiz

Post by Alexander Yashkin
What's the purpose of closing such issues from non-google project
members? It does not look like security issue to me.

The reason for the crbug is that, if the type "Launch" (which our policies
require for A/B testing), it gets automatically restricted to Googlers.
I will downgrade the bug to feature request and then file a new bug for
the launch itself.

Post by Alexander Yashkin
We (members of yandex team) are also implementing sync server and client
functionality and going through a lot of frustration(and pain)
while supporting our code. Problem is we have to guess where design and
refactoring of sync component is heading looking only at code diff and
patches description.

Sorry for the inconveniences, and thanks for the reminder.
1. We will migrate passwords to USS (engineering work is expected to start
now).
2. We hope to use pseudo-USS to wrap all remaining datatypes into USS
architecture (M72 or M73).
(we do have a pseudo-USS codepath for passwords too, but hope to never
launch it)
3. We plan to dismantle the sync-directory codepath somewhere around
2019-Q2.
4. We plan to remove support for directory itself in the second half of
2019.
These changes are not expected to be noticeable server-side. We also do
not commit to specific timelines, the dates above are rough estimations.
Let me know if you have specific questions.
Cheers,
Mikel

Post by Alexander Yashkin
WBR
Alexander Yashkin

[Alexander Yashkin]

Thanks a lot Mikel.

Post by Mikel Astiz
Hi Alexander,
Hi Alexander,
On Wed, Nov 7, 2018 at 12:46 PM Alexander Yashkin
Hi all.
Can the sync owners, please, open the following issue and design
document to non-googlers.
https://bugs.chromium.org/p/chromium/issues/detail?id=870624
I'll take care of this.
The bug should be accessible publicly now.
https://docs.google.com/document/d/14ScYZ0sop921gjBwXuReIEuQJlwftqkuSM1jMK_A_x4
Is where an open version of this document?
There isn't such a document, but there probably should be, since
chromium does have commitment to make design docs publicly
available. Let me see what I can do.
Because of technical issues, I cannot share the original document
https://docs.google.com/document/d/1Pd3bTBnk2RhVdYsnFPdvtTtAms_OPEBUO7Sp3cjlyyM
Cheers,
Mikel
What's the purpose of closing such issues from non-google
project members? It does not look like security issue to me.
The reason for the crbug is that, if the type "Launch" (which our
policies require for A/B testing), it gets automatically restricted
to Googlers.
I will downgrade the bug to feature request and then file a new bug
for the launch itself.
We (members of yandex team) are also implementing sync server
and client functionality and going through a lot of
frustration(and pain)
while supporting our code. Problem is we have to guess where
design and refactoring of sync component is heading looking only
at code diff and patches description.
Sorry for the inconveniences, and thanks for the reminder.
1. We will migrate passwords to USS (engineering work is expected to
start now).
2. We hope to use pseudo-USS to wrap all remaining datatypes into
USS architecture (M72 or M73).
(we do have a pseudo-USS codepath for passwords too, but hope to
never launch it)
3. We plan to dismantle the sync-directory codepath somewhere around
2019-Q2.
4. We plan to remove support for directory itself in the second half
of 2019.
These changes are not expected to be noticeable server-side. We also
do not commit to specific timelines, the dates above are rough
estimations.
Let me know if you have specific questions.
Cheers,
Mikel
WBR
Alexander Yashkin
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google
Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAAy826eR2ZksXGSk5-Q15%2BSdMJ1T%2BRhW4joyN7Ae%3DE_BNWd6Og%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAAy826eR2ZksXGSk5-Q15%2BSdMJ1T%2BRhW4joyN7Ae%3DE_BNWd6Og%40mail.gmail.com?utm_medium=email&utm_source=footer>.

--
С уважением,
Александр Яшкин,
разработчик Нашего Браузера
http://staff.yandex-team.ru/a-v-y/