Date   

Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Jory Burson
 

Of course! Naina, you have been added to the invite - I've also updated the meeting so you should be able to add others as well.

- Jory

On Mon, Dec 9, 2019 at 12:32 PM Raghu Simha <rsimha@...> wrote:
Thanks for setting up this meeting, Jory.

Would it be possible to add +Naina Raisinghani to this meeting as well?

On Mon, Dec 9, 2019 at 12:31 PM <kris.borchers@...> wrote:

I have accepted the invite but just FYI, I will also be dialing in. Thanks!

 

Kris

 

From: Greg Grothaus <greggrothaus@...>
Sent: Monday, December 9, 2019 11:27 AM
To: Tobie Langel <tobie@...>
Cc: Jory Burson <jory@...>; Daniel Rozenberg <rodaniel@...>; Esther Kim <esth@...>; Kris Borchers <kris.borchers@...>; Myles Borins <mborins@...>; Raghu Simha <rsimha@...>; Ryan Cebulko <rcebulko@...>; Tierney Cyren <Tierney.Cyren@...>; amp-onboarding-infrastructure@...
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

 

No problem. I assume this is using the hangouts ID in the meeting for the connection. If there is something else I need to set up in advance, let me know.

 

-Greg

 

On Mon, Dec 9, 2019 at 6:51 AM Tobie Langel <tobie@...> wrote:

Yes, Greg will need to dial in.

 

Can we make sure to have 60 minutes available for this?

 

Thanks,

 

—tobie 

 

On Mon, Dec 9, 2019 at 15:49 Jory Burson <jory@...> wrote:

Hi all! 

 

Wanted to let you know that we've got space & time reserved for this on the collaborator summit agenda: 

 

Room: 512DH 

Date: Friday, 12/13

Time: 4:00 PM EST

 

I'll send this as a calendar invite to everyone as well. Do we think we'll want to dial anyone in to the conversation? Let me know & I'll see what we can do. 

 

- Jory

 

On Sat, Dec 7, 2019 at 2:10 AM Tobie Langel <tobie@...> wrote:

Thanks, Tierney.

 

Given the main point of this exercise is to move towards consensus upstream of graduation, who else should involved to have a better sense of what the CPC and foundation’s positions are?

 

—tobie

 

On Sat, Dec 7, 2019 at 01:58 Tierney Cyren <Tierney.Cyren@...> wrote:

Definitely want to assert that my views/thoughts should be taken with a grain of salt and validated with the overall CPC/OpenJS Foundation folks, but I would generally agree that those points align with my understanding of the state of the world for other projects _and_ generally assert that they align with the goals/intents of the Foundation.

 

From: Tobie Langel <tobie@...>
Date: Friday, December 6, 2019 at 12:48 PM
To: Greg Grothaus <greggrothaus@...>
Cc: Raghu Simha <rsimha@...>, Esther Kim <esth@...>, Ryan Cebulko <rcebulko@...>, Daniel Rozenberg <rodaniel@...>, amp-onboarding-infrastructure@... <amp-onboarding-infrastructure@...>, Jory Burson <jory@...>, Kris Borchers <kris.borchers@...>, Tierney Cyren <Tierney.Cyren@...>, Myles Borins <mborins@...>
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Thanks for raising those questions again here, Greg.

 

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

 

It's clear for the CPC that the actual implementation is going to take longer.

 

My understanding from chatting with Tierney during the AMP Contributor Summit is that:

·       It would be ideal if the runtime was served from a Foundation-owned domain.

·       The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.

·       It is absolutely OK if Google uses its own infrastructure to serve the runtime.

·       It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).

·       Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.

Tierney (others on the CPC), please feel free to correct the above.

 

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

 

Thanks,

 

--tobie

 

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:

There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

 

What domain name will we serve the runtime from?

What infrastructure will serve the content on that domain name?

 - Is Google infrastructure acceptable for the initial rollout?

 - If not, who will manage the serving infrastructure, and what CDN will be used?

 

-Greg

 

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:

Thanks for kicking this off, Tobie.

 

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

 

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

 

Let me know what you think.

 

Raghu.

 

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:

Hi folks,

 

AMP's Infra WG will be in Montreal for the Collab Summit next week.

 

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:

Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

 

Looking forward to catching up with you all.

 

Best,

 

--tobie

 

---

Tobie Langel

Principal, UnlockOpen

 


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

rsimha Simha
 

Thanks for setting up this meeting, Jory.

Would it be possible to add +Naina Raisinghani to this meeting as well?

On Mon, Dec 9, 2019 at 12:31 PM <kris.borchers@...> wrote:

I have accepted the invite but just FYI, I will also be dialing in. Thanks!

 

Kris

 

From: Greg Grothaus <greggrothaus@...>
Sent: Monday, December 9, 2019 11:27 AM
To: Tobie Langel <tobie@...>
Cc: Jory Burson <jory@...>; Daniel Rozenberg <rodaniel@...>; Esther Kim <esth@...>; Kris Borchers <kris.borchers@...>; Myles Borins <mborins@...>; Raghu Simha <rsimha@...>; Ryan Cebulko <rcebulko@...>; Tierney Cyren <Tierney.Cyren@...>; amp-onboarding-infrastructure@...
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

 

No problem. I assume this is using the hangouts ID in the meeting for the connection. If there is something else I need to set up in advance, let me know.

 

-Greg

 

On Mon, Dec 9, 2019 at 6:51 AM Tobie Langel <tobie@...> wrote:

Yes, Greg will need to dial in.

 

Can we make sure to have 60 minutes available for this?

 

Thanks,

 

—tobie 

 

On Mon, Dec 9, 2019 at 15:49 Jory Burson <jory@...> wrote:

Hi all! 

 

Wanted to let you know that we've got space & time reserved for this on the collaborator summit agenda: 

 

Room: 512DH 

Date: Friday, 12/13

Time: 4:00 PM EST

 

I'll send this as a calendar invite to everyone as well. Do we think we'll want to dial anyone in to the conversation? Let me know & I'll see what we can do. 

 

- Jory

 

On Sat, Dec 7, 2019 at 2:10 AM Tobie Langel <tobie@...> wrote:

Thanks, Tierney.

 

Given the main point of this exercise is to move towards consensus upstream of graduation, who else should involved to have a better sense of what the CPC and foundation’s positions are?

 

—tobie

 

On Sat, Dec 7, 2019 at 01:58 Tierney Cyren <Tierney.Cyren@...> wrote:

Definitely want to assert that my views/thoughts should be taken with a grain of salt and validated with the overall CPC/OpenJS Foundation folks, but I would generally agree that those points align with my understanding of the state of the world for other projects _and_ generally assert that they align with the goals/intents of the Foundation.

 

From: Tobie Langel <tobie@...>
Date: Friday, December 6, 2019 at 12:48 PM
To: Greg Grothaus <greggrothaus@...>
Cc: Raghu Simha <rsimha@...>, Esther Kim <esth@...>, Ryan Cebulko <rcebulko@...>, Daniel Rozenberg <rodaniel@...>, amp-onboarding-infrastructure@... <amp-onboarding-infrastructure@...>, Jory Burson <jory@...>, Kris Borchers <kris.borchers@...>, Tierney Cyren <Tierney.Cyren@...>, Myles Borins <mborins@...>
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Thanks for raising those questions again here, Greg.

 

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

 

It's clear for the CPC that the actual implementation is going to take longer.

 

My understanding from chatting with Tierney during the AMP Contributor Summit is that:

·       It would be ideal if the runtime was served from a Foundation-owned domain.

·       The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.

·       It is absolutely OK if Google uses its own infrastructure to serve the runtime.

·       It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).

·       Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.

Tierney (others on the CPC), please feel free to correct the above.

 

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

 

Thanks,

 

--tobie

 

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:

There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

 

What domain name will we serve the runtime from?

What infrastructure will serve the content on that domain name?

 - Is Google infrastructure acceptable for the initial rollout?

 - If not, who will manage the serving infrastructure, and what CDN will be used?

 

-Greg

 

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:

Thanks for kicking this off, Tobie.

 

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

 

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

 

Let me know what you think.

 

Raghu.

 

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:

Hi folks,

 

AMP's Infra WG will be in Montreal for the Collab Summit next week.

 

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:

Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

 

Looking forward to catching up with you all.

 

Best,

 

--tobie

 

---

Tobie Langel

Principal, UnlockOpen

 


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Kris Borchers
 

I have accepted the invite but just FYI, I will also be dialing in. Thanks!

 

Kris

 

From: Greg Grothaus <greggrothaus@...>
Sent: Monday, December 9, 2019 11:27 AM
To: Tobie Langel <tobie@...>
Cc: Jory Burson <jory@...>; Daniel Rozenberg <rodaniel@...>; Esther Kim <esth@...>; Kris Borchers <kris.borchers@...>; Myles Borins <mborins@...>; Raghu Simha <rsimha@...>; Ryan Cebulko <rcebulko@...>; Tierney Cyren <Tierney.Cyren@...>; amp-onboarding-infrastructure@...
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

 

No problem. I assume this is using the hangouts ID in the meeting for the connection. If there is something else I need to set up in advance, let me know.

 

-Greg

 

On Mon, Dec 9, 2019 at 6:51 AM Tobie Langel <tobie@...> wrote:

Yes, Greg will need to dial in.

 

Can we make sure to have 60 minutes available for this?

 

Thanks,

 

—tobie 

 

On Mon, Dec 9, 2019 at 15:49 Jory Burson <jory@...> wrote:

Hi all! 

 

Wanted to let you know that we've got space & time reserved for this on the collaborator summit agenda: 

 

Room: 512DH 

Date: Friday, 12/13

Time: 4:00 PM EST

 

I'll send this as a calendar invite to everyone as well. Do we think we'll want to dial anyone in to the conversation? Let me know & I'll see what we can do. 

 

- Jory

 

On Sat, Dec 7, 2019 at 2:10 AM Tobie Langel <tobie@...> wrote:

Thanks, Tierney.

 

Given the main point of this exercise is to move towards consensus upstream of graduation, who else should involved to have a better sense of what the CPC and foundation’s positions are?

 

—tobie

 

On Sat, Dec 7, 2019 at 01:58 Tierney Cyren <Tierney.Cyren@...> wrote:

Definitely want to assert that my views/thoughts should be taken with a grain of salt and validated with the overall CPC/OpenJS Foundation folks, but I would generally agree that those points align with my understanding of the state of the world for other projects _and_ generally assert that they align with the goals/intents of the Foundation.

 

From: Tobie Langel <tobie@...>
Date: Friday, December 6, 2019 at 12:48 PM
To: Greg Grothaus <greggrothaus@...>
Cc: Raghu Simha <rsimha@...>, Esther Kim <esth@...>, Ryan Cebulko <rcebulko@...>, Daniel Rozenberg <rodaniel@...>, amp-onboarding-infrastructure@... <amp-onboarding-infrastructure@...>, Jory Burson <jory@...>, Kris Borchers <kris.borchers@...>, Tierney Cyren <Tierney.Cyren@...>, Myles Borins <mborins@...>
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Thanks for raising those questions again here, Greg.

 

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

 

It's clear for the CPC that the actual implementation is going to take longer.

 

My understanding from chatting with Tierney during the AMP Contributor Summit is that:

·       It would be ideal if the runtime was served from a Foundation-owned domain.

·       The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.

·       It is absolutely OK if Google uses its own infrastructure to serve the runtime.

·       It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).

·       Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.

Tierney (others on the CPC), please feel free to correct the above.

 

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

 

Thanks,

 

--tobie

 

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:

There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

 

What domain name will we serve the runtime from?

What infrastructure will serve the content on that domain name?

 - Is Google infrastructure acceptable for the initial rollout?

 - If not, who will manage the serving infrastructure, and what CDN will be used?

 

-Greg

 

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:

Thanks for kicking this off, Tobie.

 

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

 

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

 

Let me know what you think.

 

Raghu.

 

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:

Hi folks,

 

AMP's Infra WG will be in Montreal for the Collab Summit next week.

 

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:

Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

 

Looking forward to catching up with you all.

 

Best,

 

--tobie

 

---

Tobie Langel

Principal, UnlockOpen

 


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Greg Grothaus
 

No problem. I assume this is using the hangouts ID in the meeting for the connection. If there is something else I need to set up in advance, let me know.

-Greg

On Mon, Dec 9, 2019 at 6:51 AM Tobie Langel <tobie@...> wrote:
Yes, Greg will need to dial in.

Can we make sure to have 60 minutes available for this?

Thanks,

—tobie 

On Mon, Dec 9, 2019 at 15:49 Jory Burson <jory@...> wrote:
Hi all! 

Wanted to let you know that we've got space & time reserved for this on the collaborator summit agenda: 

Room: 512DH 
Date: Friday, 12/13
Time: 4:00 PM EST

I'll send this as a calendar invite to everyone as well. Do we think we'll want to dial anyone in to the conversation? Let me know & I'll see what we can do. 

- Jory

On Sat, Dec 7, 2019 at 2:10 AM Tobie Langel <tobie@...> wrote:
Thanks, Tierney.

Given the main point of this exercise is to move towards consensus upstream of graduation, who else should involved to have a better sense of what the CPC and foundation’s positions are?

—tobie

On Sat, Dec 7, 2019 at 01:58 Tierney Cyren <Tierney.Cyren@...> wrote:

Definitely want to assert that my views/thoughts should be taken with a grain of salt and validated with the overall CPC/OpenJS Foundation folks, but I would generally agree that those points align with my understanding of the state of the world for other projects _and_ generally assert that they align with the goals/intents of the Foundation.

 

From: Tobie Langel <tobie@...>
Date: Friday, December 6, 2019 at 12:48 PM
To: Greg Grothaus <greggrothaus@...>
Cc: Raghu Simha <rsimha@...>, Esther Kim <esth@...>, Ryan Cebulko <rcebulko@...>, Daniel Rozenberg <rodaniel@...>, amp-onboarding-infrastructure@... <amp-onboarding-infrastructure@...>, Jory Burson <jory@...>, Kris Borchers <kris.borchers@...>, Tierney Cyren <Tierney.Cyren@...>, Myles Borins <mborins@...>
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Thanks for raising those questions again here, Greg.

 

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

 

It's clear for the CPC that the actual implementation is going to take longer.

 

My understanding from chatting with Tierney during the AMP Contributor Summit is that:

  • It would be ideal if the runtime was served from a Foundation-owned domain.
  • The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.
  • It is absolutely OK if Google uses its own infrastructure to serve the runtime.
  • It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).
  • Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.

Tierney (others on the CPC), please feel free to correct the above.

 

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

 

Thanks,

 

--tobie

 

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:

There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

 

What domain name will we serve the runtime from?

What infrastructure will serve the content on that domain name?

 - Is Google infrastructure acceptable for the initial rollout?

 - If not, who will manage the serving infrastructure, and what CDN will be used?

 

-Greg

 

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:

Thanks for kicking this off, Tobie.

 

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

 

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

 

Let me know what you think.

 

Raghu.

 

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:

Hi folks,

 

AMP's Infra WG will be in Montreal for the Collab Summit next week.

 

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:

Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

 

Looking forward to catching up with you all.

 

Best,

 

--tobie

 

---

Tobie Langel

Principal, UnlockOpen

 


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

 

I will call in as well, I will be gone by then.

Thank you for setting this up, Jory. 

Best,
Brian

--

Brian Warner
The Linux Foundation
bwarner@...
+1 724 301-6171


On Mon, Dec 9, 2019, 9:55 AM Jory Burson <jory@...> wrote:
We have a confirmed 60 minutes, and if we need more time, I'm confident we can take more.

On Mon, Dec 9, 2019 at 9:51 AM Tobie Langel <tobie@...> wrote:
Yes, Greg will need to dial in.

Can we make sure to have 60 minutes available for this?

Thanks,

—tobie 

On Mon, Dec 9, 2019 at 15:49 Jory Burson <jory@...> wrote:
Hi all! 

Wanted to let you know that we've got space & time reserved for this on the collaborator summit agenda: 

Room: 512DH 
Date: Friday, 12/13
Time: 4:00 PM EST

I'll send this as a calendar invite to everyone as well. Do we think we'll want to dial anyone in to the conversation? Let me know & I'll see what we can do. 

- Jory

On Sat, Dec 7, 2019 at 2:10 AM Tobie Langel <tobie@...> wrote:
Thanks, Tierney.

Given the main point of this exercise is to move towards consensus upstream of graduation, who else should involved to have a better sense of what the CPC and foundation’s positions are?

—tobie

On Sat, Dec 7, 2019 at 01:58 Tierney Cyren <Tierney.Cyren@...> wrote:

Definitely want to assert that my views/thoughts should be taken with a grain of salt and validated with the overall CPC/OpenJS Foundation folks, but I would generally agree that those points align with my understanding of the state of the world for other projects _and_ generally assert that they align with the goals/intents of the Foundation.

 

From: Tobie Langel <tobie@...>
Date: Friday, December 6, 2019 at 12:48 PM
To: Greg Grothaus <greggrothaus@...>
Cc: Raghu Simha <rsimha@...>, Esther Kim <esth@...>, Ryan Cebulko <rcebulko@...>, Daniel Rozenberg <rodaniel@...>, amp-onboarding-infrastructure@... <amp-onboarding-infrastructure@...>, Jory Burson <jory@...>, Kris Borchers <kris.borchers@...>, Tierney Cyren <Tierney.Cyren@...>, Myles Borins <mborins@...>
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Thanks for raising those questions again here, Greg.

 

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

 

It's clear for the CPC that the actual implementation is going to take longer.

 

My understanding from chatting with Tierney during the AMP Contributor Summit is that:

  • It would be ideal if the runtime was served from a Foundation-owned domain.
  • The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.
  • It is absolutely OK if Google uses its own infrastructure to serve the runtime.
  • It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).
  • Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.

Tierney (others on the CPC), please feel free to correct the above.

 

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

 

Thanks,

 

--tobie

 

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:

There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

 

What domain name will we serve the runtime from?

What infrastructure will serve the content on that domain name?

 - Is Google infrastructure acceptable for the initial rollout?

 - If not, who will manage the serving infrastructure, and what CDN will be used?

 

-Greg

 

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:

Thanks for kicking this off, Tobie.

 

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

 

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

 

Let me know what you think.

 

Raghu.

 

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:

Hi folks,

 

AMP's Infra WG will be in Montreal for the Collab Summit next week.

 

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:

Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

 

Looking forward to catching up with you all.

 

Best,

 

--tobie

 

---

Tobie Langel

Principal, UnlockOpen

 


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Jory Burson
 

We have a confirmed 60 minutes, and if we need more time, I'm confident we can take more.


On Mon, Dec 9, 2019 at 9:51 AM Tobie Langel <tobie@...> wrote:
Yes, Greg will need to dial in.

Can we make sure to have 60 minutes available for this?

Thanks,

—tobie 

On Mon, Dec 9, 2019 at 15:49 Jory Burson <jory@...> wrote:
Hi all! 

Wanted to let you know that we've got space & time reserved for this on the collaborator summit agenda: 

Room: 512DH 
Date: Friday, 12/13
Time: 4:00 PM EST

I'll send this as a calendar invite to everyone as well. Do we think we'll want to dial anyone in to the conversation? Let me know & I'll see what we can do. 

- Jory

On Sat, Dec 7, 2019 at 2:10 AM Tobie Langel <tobie@...> wrote:
Thanks, Tierney.

Given the main point of this exercise is to move towards consensus upstream of graduation, who else should involved to have a better sense of what the CPC and foundation’s positions are?

—tobie

On Sat, Dec 7, 2019 at 01:58 Tierney Cyren <Tierney.Cyren@...> wrote:

Definitely want to assert that my views/thoughts should be taken with a grain of salt and validated with the overall CPC/OpenJS Foundation folks, but I would generally agree that those points align with my understanding of the state of the world for other projects _and_ generally assert that they align with the goals/intents of the Foundation.

 

From: Tobie Langel <tobie@...>
Date: Friday, December 6, 2019 at 12:48 PM
To: Greg Grothaus <greggrothaus@...>
Cc: Raghu Simha <rsimha@...>, Esther Kim <esth@...>, Ryan Cebulko <rcebulko@...>, Daniel Rozenberg <rodaniel@...>, amp-onboarding-infrastructure@... <amp-onboarding-infrastructure@...>, Jory Burson <jory@...>, Kris Borchers <kris.borchers@...>, Tierney Cyren <Tierney.Cyren@...>, Myles Borins <mborins@...>
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Thanks for raising those questions again here, Greg.

 

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

 

It's clear for the CPC that the actual implementation is going to take longer.

 

My understanding from chatting with Tierney during the AMP Contributor Summit is that:

  • It would be ideal if the runtime was served from a Foundation-owned domain.
  • The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.
  • It is absolutely OK if Google uses its own infrastructure to serve the runtime.
  • It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).
  • Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.

Tierney (others on the CPC), please feel free to correct the above.

 

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

 

Thanks,

 

--tobie

 

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:

There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

 

What domain name will we serve the runtime from?

What infrastructure will serve the content on that domain name?

 - Is Google infrastructure acceptable for the initial rollout?

 - If not, who will manage the serving infrastructure, and what CDN will be used?

 

-Greg

 

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:

Thanks for kicking this off, Tobie.

 

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

 

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

 

Let me know what you think.

 

Raghu.

 

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:

Hi folks,

 

AMP's Infra WG will be in Montreal for the Collab Summit next week.

 

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:

Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

 

Looking forward to catching up with you all.

 

Best,

 

--tobie

 

---

Tobie Langel

Principal, UnlockOpen

 


Invitation: AMP Infra WG @ Collab Summit @ Fri Dec 13, 2019 4pm - 5pm (EST) (amp-onboarding-infrastructure@lists.openjsf.org)

Jory Burson
 

You have been invited to the following event.

AMP Infra WG @ Collab Summit

When
Fri Dec 13, 2019 4pm – 5pm Eastern Time - New York
Where
Room 512DH (map)
Joining info
Or dial: +1 513-970-0851  PIN: 120060695#
Calendar
amp-onboarding-infrastructure@...
Who
jory@... - organizer
rcebulko@...
Myles Borins
Raghu Simha
amp-onboarding-infrastructure@...
kris.borchers@...
tierney.cyren@...
Greg Grothaus
esth@...
Daniel Rozenberg
tobie@...

Going (amp-onboarding-infrastructure@...)?   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account amp-onboarding-infrastructure@... because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.

Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More.


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Tobie Langel
 

Yes, Greg will need to dial in.

Can we make sure to have 60 minutes available for this?

Thanks,

—tobie 

On Mon, Dec 9, 2019 at 15:49 Jory Burson <jory@...> wrote:
Hi all! 

Wanted to let you know that we've got space & time reserved for this on the collaborator summit agenda: 

Room: 512DH 
Date: Friday, 12/13
Time: 4:00 PM EST

I'll send this as a calendar invite to everyone as well. Do we think we'll want to dial anyone in to the conversation? Let me know & I'll see what we can do. 

- Jory

On Sat, Dec 7, 2019 at 2:10 AM Tobie Langel <tobie@...> wrote:
Thanks, Tierney.

Given the main point of this exercise is to move towards consensus upstream of graduation, who else should involved to have a better sense of what the CPC and foundation’s positions are?

—tobie

On Sat, Dec 7, 2019 at 01:58 Tierney Cyren <Tierney.Cyren@...> wrote:

Definitely want to assert that my views/thoughts should be taken with a grain of salt and validated with the overall CPC/OpenJS Foundation folks, but I would generally agree that those points align with my understanding of the state of the world for other projects _and_ generally assert that they align with the goals/intents of the Foundation.

 

From: Tobie Langel <tobie@...>
Date: Friday, December 6, 2019 at 12:48 PM
To: Greg Grothaus <greggrothaus@...>
Cc: Raghu Simha <rsimha@...>, Esther Kim <esth@...>, Ryan Cebulko <rcebulko@...>, Daniel Rozenberg <rodaniel@...>, amp-onboarding-infrastructure@... <amp-onboarding-infrastructure@...>, Jory Burson <jory@...>, Kris Borchers <kris.borchers@...>, Tierney Cyren <Tierney.Cyren@...>, Myles Borins <mborins@...>
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Thanks for raising those questions again here, Greg.

 

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

 

It's clear for the CPC that the actual implementation is going to take longer.

 

My understanding from chatting with Tierney during the AMP Contributor Summit is that:

  • It would be ideal if the runtime was served from a Foundation-owned domain.
  • The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.
  • It is absolutely OK if Google uses its own infrastructure to serve the runtime.
  • It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).
  • Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.

Tierney (others on the CPC), please feel free to correct the above.

 

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

 

Thanks,

 

--tobie

 

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:

There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

 

What domain name will we serve the runtime from?

What infrastructure will serve the content on that domain name?

 - Is Google infrastructure acceptable for the initial rollout?

 - If not, who will manage the serving infrastructure, and what CDN will be used?

 

-Greg

 

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:

Thanks for kicking this off, Tobie.

 

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

 

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

 

Let me know what you think.

 

Raghu.

 

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:

Hi folks,

 

AMP's Infra WG will be in Montreal for the Collab Summit next week.

 

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:

Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

 

Looking forward to catching up with you all.

 

Best,

 

--tobie

 

---

Tobie Langel

Principal, UnlockOpen

 


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Jory Burson
 

Hi all! 

Wanted to let you know that we've got space & time reserved for this on the collaborator summit agenda: 

Room: 512DH 
Date: Friday, 12/13
Time: 4:00 PM EST

I'll send this as a calendar invite to everyone as well. Do we think we'll want to dial anyone in to the conversation? Let me know & I'll see what we can do. 

- Jory

On Sat, Dec 7, 2019 at 2:10 AM Tobie Langel <tobie@...> wrote:
Thanks, Tierney.

Given the main point of this exercise is to move towards consensus upstream of graduation, who else should involved to have a better sense of what the CPC and foundation’s positions are?

—tobie

On Sat, Dec 7, 2019 at 01:58 Tierney Cyren <Tierney.Cyren@...> wrote:

Definitely want to assert that my views/thoughts should be taken with a grain of salt and validated with the overall CPC/OpenJS Foundation folks, but I would generally agree that those points align with my understanding of the state of the world for other projects _and_ generally assert that they align with the goals/intents of the Foundation.

 

From: Tobie Langel <tobie@...>
Date: Friday, December 6, 2019 at 12:48 PM
To: Greg Grothaus <greggrothaus@...>
Cc: Raghu Simha <rsimha@...>, Esther Kim <esth@...>, Ryan Cebulko <rcebulko@...>, Daniel Rozenberg <rodaniel@...>, amp-onboarding-infrastructure@... <amp-onboarding-infrastructure@...>, Jory Burson <jory@...>, Kris Borchers <kris.borchers@...>, Tierney Cyren <Tierney.Cyren@...>, Myles Borins <mborins@...>
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Thanks for raising those questions again here, Greg.

 

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

 

It's clear for the CPC that the actual implementation is going to take longer.

 

My understanding from chatting with Tierney during the AMP Contributor Summit is that:

  • It would be ideal if the runtime was served from a Foundation-owned domain.
  • The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.
  • It is absolutely OK if Google uses its own infrastructure to serve the runtime.
  • It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).
  • Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.

Tierney (others on the CPC), please feel free to correct the above.

 

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

 

Thanks,

 

--tobie

 

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:

There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

 

What domain name will we serve the runtime from?

What infrastructure will serve the content on that domain name?

 - Is Google infrastructure acceptable for the initial rollout?

 - If not, who will manage the serving infrastructure, and what CDN will be used?

 

-Greg

 

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:

Thanks for kicking this off, Tobie.

 

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

 

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

 

Let me know what you think.

 

Raghu.

 

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:

Hi folks,

 

AMP's Infra WG will be in Montreal for the Collab Summit next week.

 

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:

Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

 

Looking forward to catching up with you all.

 

Best,

 

--tobie

 

---

Tobie Langel

Principal, UnlockOpen

 


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Tobie Langel
 

Thanks, Tierney.

Given the main point of this exercise is to move towards consensus upstream of graduation, who else should involved to have a better sense of what the CPC and foundation’s positions are?

—tobie

On Sat, Dec 7, 2019 at 01:58 Tierney Cyren <Tierney.Cyren@...> wrote:

Definitely want to assert that my views/thoughts should be taken with a grain of salt and validated with the overall CPC/OpenJS Foundation folks, but I would generally agree that those points align with my understanding of the state of the world for other projects _and_ generally assert that they align with the goals/intents of the Foundation.

 

From: Tobie Langel <tobie@...>
Date: Friday, December 6, 2019 at 12:48 PM
To: Greg Grothaus <greggrothaus@...>
Cc: Raghu Simha <rsimha@...>, Esther Kim <esth@...>, Ryan Cebulko <rcebulko@...>, Daniel Rozenberg <rodaniel@...>, amp-onboarding-infrastructure@... <amp-onboarding-infrastructure@...>, Jory Burson <jory@...>, Kris Borchers <kris.borchers@...>, Tierney Cyren <Tierney.Cyren@...>, Myles Borins <mborins@...>
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Thanks for raising those questions again here, Greg.

 

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

 

It's clear for the CPC that the actual implementation is going to take longer.

 

My understanding from chatting with Tierney during the AMP Contributor Summit is that:

  • It would be ideal if the runtime was served from a Foundation-owned domain.
  • The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.
  • It is absolutely OK if Google uses its own infrastructure to serve the runtime.
  • It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).
  • Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.

Tierney (others on the CPC), please feel free to correct the above.

 

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

 

Thanks,

 

--tobie

 

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:

There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

 

What domain name will we serve the runtime from?

What infrastructure will serve the content on that domain name?

 - Is Google infrastructure acceptable for the initial rollout?

 - If not, who will manage the serving infrastructure, and what CDN will be used?

 

-Greg

 

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:

Thanks for kicking this off, Tobie.

 

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

 

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

 

Let me know what you think.

 

Raghu.

 

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:

Hi folks,

 

AMP's Infra WG will be in Montreal for the Collab Summit next week.

 

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:

Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

 

Looking forward to catching up with you all.

 

Best,

 

--tobie

 

---

Tobie Langel

Principal, UnlockOpen

 


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Tierney Cyren
 

Definitely want to assert that my views/thoughts should be taken with a grain of salt and validated with the overall CPC/OpenJS Foundation folks, but I would generally agree that those points align with my understanding of the state of the world for other projects _and_ generally assert that they align with the goals/intents of the Foundation.

 

From: Tobie Langel <tobie@...>
Date: Friday, December 6, 2019 at 12:48 PM
To: Greg Grothaus <greggrothaus@...>
Cc: Raghu Simha <rsimha@...>, Esther Kim <esth@...>, Ryan Cebulko <rcebulko@...>, Daniel Rozenberg <rodaniel@...>, amp-onboarding-infrastructure@... <amp-onboarding-infrastructure@...>, Jory Burson <jory@...>, Kris Borchers <kris.borchers@...>, Tierney Cyren <Tierney.Cyren@...>, Myles Borins <mborins@...>
Subject: Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Thanks for raising those questions again here, Greg.

 

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

 

It's clear for the CPC that the actual implementation is going to take longer.

 

My understanding from chatting with Tierney during the AMP Contributor Summit is that:

  • It would be ideal if the runtime was served from a Foundation-owned domain.
  • The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.
  • It is absolutely OK if Google uses its own infrastructure to serve the runtime.
  • It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).
  • Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.

Tierney (others on the CPC), please feel free to correct the above.

 

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

 

Thanks,

 

--tobie

 

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:

There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

 

What domain name will we serve the runtime from?

What infrastructure will serve the content on that domain name?

 - Is Google infrastructure acceptable for the initial rollout?

 - If not, who will manage the serving infrastructure, and what CDN will be used?

 

-Greg

 

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:

Thanks for kicking this off, Tobie.

 

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

 

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

 

Let me know what you think.

 

Raghu.

 

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:

Hi folks,

 

AMP's Infra WG will be in Montreal for the Collab Summit next week.

 

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:

Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

 

Looking forward to catching up with you all.

 

Best,

 

--tobie

 

---

Tobie Langel

Principal, UnlockOpen

 


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Tobie Langel
 

Filed https://github.com/openjs-foundation/summit/issues/226 to request time during the summit for this session.

--tobie

On Fri, Dec 6, 2019 at 9:14 PM Myles Borins <mylesborins@...> wrote:
Did someone make an issue on the summit repo to request time during the summit for this session?

On Fri, Dec 6, 2019, 12:13 PM Greg Grothaus <greggrothaus@...> wrote:
There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

What domain name will we serve the runtime from?
What infrastructure will serve the content on that domain name?
 - Is Google infrastructure acceptable for the initial rollout?
 - If not, who will manage the serving infrastructure, and what CDN will be used?

-Greg

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:
Thanks for kicking this off, Tobie.

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

Let me know what you think.

Raghu.

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:
Hi folks,

AMP's Infra WG will be in Montreal for the Collab Summit next week.

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:
Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

Looking forward to catching up with you all.

Best,

--tobie

---
Tobie Langel
Principal, UnlockOpen


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Greg Grothaus
 

I can answer for the infra/cache side.

This sounds fine. 
The privacy policy would typically include securely short-term logging of IP addresses for security/privacy purposes only.  For example to handle DOS attacks. No cookies or other user data would be logged however. That's probably something that could be reconsidered if needed.

-Greg

On Fri, Dec 6, 2019 at 12:48 PM Tobie Langel <tobie@...> wrote:
Thanks for raising those questions again here, Greg.

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

It's clear for the CPC that the actual implementation is going to take longer.

My understanding from chatting with Tierney during the AMP Contributor Summit is that:
  • It would be ideal if the runtime was served from a Foundation-owned domain.
  • The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.
  • It is absolutely OK if Google uses its own infrastructure to serve the runtime.
  • It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).
  • Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.
Tierney (others on the CPC), please feel free to correct the above.

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

Thanks,

--tobie

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:
There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

What domain name will we serve the runtime from?
What infrastructure will serve the content on that domain name?
 - Is Google infrastructure acceptable for the initial rollout?
 - If not, who will manage the serving infrastructure, and what CDN will be used?

-Greg

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:
Thanks for kicking this off, Tobie.

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

Let me know what you think.

Raghu.

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:
Hi folks,

AMP's Infra WG will be in Montreal for the Collab Summit next week.

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:
Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

Looking forward to catching up with you all.

Best,

--tobie

---
Tobie Langel
Principal, UnlockOpen


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Tobie Langel
 

Thanks for raising those questions again here, Greg.

To clarify, the goal of the effort leading to graduation is scoped to building a collective agreement on how to answer those questions and document it.

It's clear for the CPC that the actual implementation is going to take longer.

My understanding from chatting with Tierney during the AMP Contributor Summit is that:
  • It would be ideal if the runtime was served from a Foundation-owned domain.
  • The foundation doesn't have the resources to fund nor manage the infrastructure necessary to serve the runtime, so it's great if Google continues supporting this.
  • It is absolutely OK if Google uses its own infrastructure to serve the runtime.
  • It is important to have a plan in place to continue to serve the runtime should Google no longer want to continue to host it (e.g. have the server be open source).
  • Whatever privacy policy is put in place to serve the runtime should limit data collection to security and performance purposes and only deal with anonymized data.
Tierney (others on the CPC), please feel free to correct the above.

Folks on the Google infra/cache side, does this look reasonable? Are there caveats with this?

Thanks,

--tobie

On Fri, Dec 6, 2019 at 9:13 PM Greg Grothaus <greggrothaus@...> wrote:
There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

What domain name will we serve the runtime from?
What infrastructure will serve the content on that domain name?
 - Is Google infrastructure acceptable for the initial rollout?
 - If not, who will manage the serving infrastructure, and what CDN will be used?

-Greg

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:
Thanks for kicking this off, Tobie.

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

Let me know what you think.

Raghu.

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:
Hi folks,

AMP's Infra WG will be in Montreal for the Collab Summit next week.

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:
Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

Looking forward to catching up with you all.

Best,

--tobie

---
Tobie Langel
Principal, UnlockOpen


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Myles Borins <mborins@...>
 

Did someone make an issue on the summit repo to request time during the summit for this session?


On Fri, Dec 6, 2019, 12:13 PM Greg Grothaus <greggrothaus@...> wrote:
There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

What domain name will we serve the runtime from?
What infrastructure will serve the content on that domain name?
 - Is Google infrastructure acceptable for the initial rollout?
 - If not, who will manage the serving infrastructure, and what CDN will be used?

-Greg

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:
Thanks for kicking this off, Tobie.

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

Let me know what you think.

Raghu.

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:
Hi folks,

AMP's Infra WG will be in Montreal for the Collab Summit next week.

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:
Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

Looking forward to catching up with you all.

Best,

--tobie

---
Tobie Langel
Principal, UnlockOpen


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Greg Grothaus
 

There are a handful of questions on that thread that would be useful to me to have answered. I don't think we can make progress until then. I'll repeat them here for clarity:

What domain name will we serve the runtime from?
What infrastructure will serve the content on that domain name?
 - Is Google infrastructure acceptable for the initial rollout?
 - If not, who will manage the serving infrastructure, and what CDN will be used?

-Greg

On Fri, Dec 6, 2019 at 11:56 AM Raghu Simha <rsimha@...> wrote:
Thanks for kicking this off, Tobie.

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

Let me know what you think.

Raghu.

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:
Hi folks,

AMP's Infra WG will be in Montreal for the Collab Summit next week.

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:
Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

Looking forward to catching up with you all.

Best,

--tobie

---
Tobie Langel
Principal, UnlockOpen


Re: OpenJSF CPC / AMP Infra WG meeting during Collab Summit

rsimha Simha
 

Thanks for kicking this off, Tobie.

Looking forward to sitting down and talking about AMP's infrastructure and how it can integrate with Open JS. The infra WG can certainly provide input for https://github.com/ampproject/wg-infra/issues/19.

For https://github.com/ampproject/wg-infra/issues/18, I think it might be useful to have +Greg Grothaus (or if he's busy, someone else from the caching WG) dial in to the meeting, since they have significantly more knowledge about the AMP cache and its plans for the future.

Let me know what you think.

Raghu.

On Tue, Dec 3, 2019 at 7:25 PM Tobie Langel <tobie@...> wrote:
Hi folks,

AMP's Infra WG will be in Montreal for the Collab Summit next week.

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:
Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

Looking forward to catching up with you all.

Best,

--tobie

---
Tobie Langel
Principal, UnlockOpen


OpenJSF CPC / AMP Infra WG meeting during Collab Summit

Tobie Langel
 

Hi folks,

AMP's Infra WG will be in Montreal for the Collab Summit next week.

This feels like a great opportunity to meet in person and make progress on the open issues around AMPs infrastructure:
Jory volunteered to help schedule a session/meeting to make this happen. This email is to get this started.

Looking forward to catching up with you all.

Best,

--tobie

---
Tobie Langel
Principal, UnlockOpen