I apologize for the lack of updates recently. I was feeling pretty unwell in the middle of this month and it lingered longer than I would have liked. AMO status was somewhat paralyzed while Mozilla was internally discussing resource allocations. We had a meeting about this today and they don't feel like they can allocate the ops resources necessary to put up the temporary site of AMO by themselves. The issues that made us choose this solution remain, however, so, since I'm a mozilla foundation contractor, I offered to do the ops work within their infrastructure. They agreed that this was a reasonable solution. We'll be using a thunderbird.net domain and certificate, and since I'll need to set this up on our infrastructure later on, the scripts and deployment procedures I develop and learn will be applicable to our own setup later on, so this is still a relatively reasonable use of my time. We had put together a requirements document and schedule for the original effort, you can find that here <https://docs.google.com/document/d/1FIu9Wh18rsgeZibYCOcX2H13ZeSQTgVS3PUn1GrRFAU/edit>. The schedule in particular is probably no longer realistic, but it should give an idea of what is involved for those who would like to know. Also, I should be back to doing weekly updates going forward.

Andrei Hajdukewycz wrote on 26.09.17 08:04: > > I apologize for the lack of updates recently. I was feeling pretty > unwell in the middle of this month and it lingered longer than I would > have liked. > > AMO status was somewhat paralyzed while Mozilla was internally > discussing resource allocations. We had a meeting about this today and > they don't feel like they can allocate the ops resources necessary to > put up the temporary site of AMO by themselves. The issues that made > us choose this solution remain, however, so, since I'm a mozilla > foundation contractor, I offered to do the ops work within their > infrastructure. They agreed that this was a reasonable solution. We'll > be using a thunderbird.net domain and certificate, and since I'll need > to set this up on our infrastructure later on, the scripts and > deployment procedures I develop and learn will be applicable to our > own setup later on, so this is still a relatively reasonable use of my > time. > This is great! It's much better for you to set it up, for the reasons you mentioned. > We had put together a requirements document and schedule for the > original effort, you can find that here > <https://docs.google.com/document/d/1FIu9Wh18rsgeZibYCOcX2H13ZeSQTgVS3PUn1GrRFAU/edit>. > I can't access that, it demands a Google account. Could you please make the doc viewable by everybody? I can see and edit other Google docs, without login. Alternatively, could you post the relevant contents here, please? Ben

On 2017-09-25 11:10 PM, Ben Bucksch wrote: > > I can't access that, it demands a Google account. Could you please > make the doc viewable by everybody? I can see and edit other Google > docs, without login. Alternatively, could you post the relevant > contents here, please? > Sorry about that. Jorgev on the AMO team created the doc and made it Mozilla-only, I gave it a quick once-over and there isn't anything in there that is problematic to share publicly so I just made a copy of the doc. If there are any major changes I'll make another copy and link it with the status report next week. https://docs.google.com/document/d/1_fs6FA7KlZsU9Jozyj6AcbmuP8ra3nODrp036w-rFuU/