[Users] Summary of March 17, 2016 - Tele-Conference

[Adam Cody]

Summary of March 17, 2016 - Tele-Conference 


    1. [ Blocking ] Waiting for zimbra to approve their channel members to join Alliance if they desire 



* Quanah - lead 

* They are some big channel partners that feel they can only lurk at this point. Don't want to risk violating their contracts since the Alliance has to do with the OSE version of ZCS. 

* Show stopper for Alliance moving forward with Member/Board voting since it would prevent full participation of those channel members. It would be unfair. 

** We'll continue with 'founders' until that issue can be resolved. 


    1. [ Blocking ] Zimbra Inc. Developer Contribution Agreements 



* Quanah - lead 

* Critical Issue to get resolved. 

** Until then, zimbra dev's can't, legally, review/see/etc anything community wants to contribute. 

** There is no "open source" project until this gets resolved. 

* Waiting on legal [currently tied up with other corporate matters] 

** Started under Telligent, but wasn't finished/resolved before Synacor purchase. Attorney that started has since left. 

* Even licence questions on Zimbra Zimlets in gallery are stuck right now by legal department 

** Community can't resurrect the zimlets until we have confirmation on the license they currently are under 

** Barry submitted bug - no response yet 

*** "Zimbra policy to update outdated license blocks" https://bugzilla.zimbra.com/show_bug.cgi?id=100404 


    1. Getting developers to volunteer for roles in the alliance 



* Barry - lead 

* Add your details and role [Member, BoD || Team Lead / Team Member] your interested in at: 

** https://docs.google.com/spreadsheets/d/1QnJctY-giMckMPnFMRNC8KmFTmL-RrbC2CliSyHi1OE/edit#gid=1324336217 


    1. What isn't being targeted by Zimbra Inc. and what the community could focus on to help? 



* Quanah/Barry/Malte - lead 

* 8.7's essentially closed at this point except for blocker problems 

* Zimbra Inc. is moving from bugzilla to jira 

** Will migrate all bugs into jira . There will be one instance for FOSS and Network. 

* 3rd party for 8.7 

** Still a lot of 3rd jars that will need to be moved to github/etc. That could be something 'community' could help with [packaging them]. 

* Community developers will need a process/method for how to engage Zimbra Inc. developers on issues. 

** Sometimes even simple fixes hang around for a long time. eg. https://bugzilla.zimbra.com/show_bug.cgi?id=102931 

* A list of items from Zimbra's bugzilla based upon votes that Adam started. [Still not finished in processing search results] 

** https://docs.google.com/spreadsheets/d/1Txe-r1Ao4EvcNjuIn9Ix5UheihxNgFJyVHwDkDNSpHY/edit#gid=1277134976 


    1. Bountysource options 



* Seems like a viable method 

* Needs umbrella organization around our Alliance to fully engage its potential 

* Helps redirect issues that companies can't commit to as priorities 


    1. Umbrella Organization 



* Cine - lead 

* SPI is currently being consider for Alliance - http://www.spi-inc.org/ umbrella org 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zetalliance.org/pipermail/users_lists.zetalliance.org/attachments/20160318/250d784e/attachment.html>