To confirm:
Phoenix DEV Meetup.
Wednesday, November 14th, 4pm, Salesforce Tower (415 Mission St.) (17th floor, 
sorry not the top floor). We'll meet in the lobby to get visitor badges.Please 
try to be on time, or let me know when you'll be later (someone will have to 
come down to let you up)
Thanks.
-- Lars
    On Friday, November 9, 2018, 10:30:09 AM PST, la...@apache.org 
<la...@apache.org> wrote:  
 
  Great.
And sorry for the folks in other TZs, it's impossible to find a time for 
everyone.I'll try to record the session via hangouts and post the recording 
here, and I will post the notes.
Here's an initial agenda, distilled and grouped from all your suggested 
topics:(I plan to keep it free-form, so we can get some good discussions, but 
if you want prepare _short_ slides/docs or proposals for the topics you care 
about that is of course very welcome!)

Intro
  
  - Open Source at Salesforce (Chris Kelly)
  - Phoenix usage at Salesforce (Lars Hofhansl)

Round-table
  
  - Introductions
  - Current thoughts and pain points

Deep Dives

(topics derived from requests from the community)

Direction and Future
  
  - Status of 4.x and master branches
  - Current challenges (public cloud?, performance?, community?, SQL coverage?, 
scale?)
  - Secondary Indexing (Lars Hofhansl)
  - Future direction. Where do we want Phoenix to be in 1 years, 2 years, 5 
years? 
  - Feature gaps in multi-tenancy. Fat client vs thin
  - Feature resiliency / hardening (general)
  - integration with Data Analytics tool like spark.

Project Management
  
  - Release cadence (need RMs that spend time on this)
  - Improve mailing list support
  - PR review rotation
  - Nominate new committers
  - Branch cleanup
  - checkin criteria and testing (IT vs. unit tests)

Project Cleanliness
  
  - Fix test flappers and overall improvements overall test infra
  - Refactoring, correctness, code extensibility
  - Potential refactoring work
  - Perf tool for Phoenix Query Server
  - Thoughts on test infra





    On Wednesday, November 7, 2018, 3:45:44 PM PST, Josh Elser 
<els...@apache.org> wrote:  
 
 My schedule may be getting switched around. Might be able to make it 
physically!

Marked myself as a "M" for maybe on the spreadsheet :)

On 11/6/18 7:07 PM, la...@apache.org wrote:
>  Ok. The room is booked for Wednesday November 14th from 4-7pm, in the 
>Salesforce Tower (but not the top floor :( )
> If you can confirm your attendance here (see the extra column on the 
> right):https://docs.google.com/spreadsheets/d/1j4QSk53B0ZIl_qq1XX3oB2f-Tyqp93ilJYZKG84_Amg/edit#gid=0
> 
> That would be great for planning food, etc. I will send out an agenda.
> Thanks.
> -- Lars
>      On Tuesday, October 23, 2018, 4:01:33 PM PDT, la...@apache.org 
><la...@apache.org> wrote:
>  
>    This is still on.
> I'm trying to get us a spot in the Salesforce tower top floor. As you can 
> imagine it's a coveted spot.If I can't get a time slot there in the next week 
> I'll book a "usual" conference room.
> Stay tuned.
> Thanks.
> -- Lars
> 
> 
>      On Friday, October 5, 2018, 1:01:06 PM PDT, la...@apache.org 
><la...@apache.org> wrote:
>  
>    Last call :)
>      On Monday, October 1, 2018, 10:15:07 AM PDT, la...@apache.org 
><la...@apache.org> wrote:
>  
>    10 people signed up so far.This is a good chance to make your voice heard, 
>give input, and help point the project in the right direction going forward.
> -- Lars
> 
>      On Friday, September 28, 2018, 10:39:41 AM PDT, la...@apache.org 
><la...@apache.org> wrote:
>  
>  Hi all,
> I'm planning to put together a Phoenix developer meetup at the Salesforce 
> office (with video conference for those who cannot attend in person) in the 
> next few weeks.
> If you're interested please put your name in this 
> spreadsheet:https://docs.google.com/spreadsheets/d/1j4QSk53B0ZIl_qq1XX3oB2f-Tyqp93ilJYZKG84_Amg/edit?usp=sharing
> 
> This is a chance to get all those who contribute to Phoenix together. There 
> will also be food. :)I will leave the spreadsheet up for one week - until 
> Friday October 5th.
> Possible agenda:- Round-table- Status of 4.x and master branches- Current 
> challenges (public cloud?, performance?, community?, SQL coverage?, scale?)- 
> Future direction. Where do we want Phoenix to be in 1 years, 2 years, 5 
> years?- more...
> Thanks.
> -- Lars
>        
> 
    

Reply via email to