Zarafa Communities & Development Rémon van Gijn – Ivo Timmermans Zarafa
Dec 17, 2014
Zarafa Communities & Development
Rémon van Gijn – Ivo Timmermans
Zarafa
Where do we come from?
Condensed geographical plot of 1 year downloads by originating IP’s
• Community feedback used to expand on business goals
• Building for many distributions
• Provide a reliable partner relation
• Provide a stable product
• Be interactive in new innovations
• Be open to connect
Our development focus
Coordinating communities & Resources
Forums
Wiki
Community HUB - Projects
GIT
IRC
JIRA
Pootle
Events Projects
Sites
*.Zarafa.com
Taking directions, using our ears, read your mail, and chat interactively.
– Created JIRA advanced tracker
– Opened WebApp Tracker
– GIT repo for direct source access
– IRC publishing of forum threads
– +8 Contributors of relevant substantial code
– Translators +25
– Visited 5 Major Events
– +16 Community projects and collections
– Forum refactor and renew
– Pushed community projects
Listening and taking directions with community
Diverse projects with real user value and applications!
• PAM_MAPI for Zarafa
• SABREDAV
• SCRIPTS TOOLBOX
• MAILBRIDGE
• Zarafa Cluster Backup
• Fail2Ban integration
• Zarafa for Synology NAS
• ESET Linux Mailscanner integration
• Z-PUSH 2.0
• WebApp snapshots
Community HUB - Projects
JIRA , GIT , FORUMS
Track, Search, View releases, Read developer comments
JIRA , GIT , FORUMS
JIRA , GIT , FORUMS
• Streamlining code contributions via GIT
Research an integration with JIRA tracker
• Integrate IRC & Forums more
• Stabilize Event presence
• Stimulate the Community projects
• Create Zarafa package Repo’s
for finals and beta’s + Nightly trunks
• More Community Hub functions,
antiSpam and Storage solution
Keep building structures
Everyday we grow
Development process, How does a Giraffe tick
a line of code?
Development & Release management
Development at Zarafa
• How do bug reports
become releases?
• How do bug reports
and feature ideas
differ?
• How can I contribute
with high possibility of
acceptance?
• How do bug reports become releases?
Issues
Phone
...
Portal
Sales
IRC
Support
Forum
How do bugreports become releases?
• Check that issues are fixed
• Check that feature is implemented correctly
• Verify completeness of release
• Fix bugs
• Implement features
• Accept input, create issues
Support Development
QA Release
How do bugreports become releases?
• Check that issues are fixed
• Check that feature is implemented correctly
• Verify completeness of release
• Implement • Accept input, create issues
Support Development
QA Release
How do bugreports become releases?
Planning
Support
• Create Jira issues
Daily
Review
• Quality check
• Release outline
Sprint
planning
• For next 2 weeks
Merge
• Merge if “open”
Beta
• Development on trunk only
Release
• Release from branch
How do bugreports become releases?
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
How do bugreports become releases?
7.1.x 7.1.x+1 beta 7.1.x+1 final
QA cutoff
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
How do bugreports become releases?
7.1.x 7.1.x+1 beta 7.1.x+1 final
QA cutoff
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
How do bugreports become releases?
7.1.x 7.1.x+1 beta 7.1.x+1 final
QA cutoff
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
How do bugreports become releases?
7.1.x 7.1.x+1 beta 7.1.x+1 final
QA cutoff
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
How do bugreports become releases?
7.1.x 7.1.x+1 beta 7.1.x+1 final
QA cutoff
Beta2?
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
Sprint
• 2 weeks
How do bugreports become releases?
7.1.x 7.1.x+1 beta 7.1.x+1 final
QA cutoff
Beta2?
• Q: How do bug reports and feature ideas differ?
• A: Not at all
• A: They all start out as bug reports
• A: They all start out as feature ideas
Version planning and sprints
First planning round
FEAT project Feature
Landed Planned
Unstable Supported
Discarded Cloud
How do bug reports and features differ?
• How can I contribute with high possibility of acceptance?
Total issues with input from
community:
31
Issues still open: 3
Issues accepted: 25
Issues rejected: 3
• Proprietary
• Multiple projects
• Only truth: releases are built from this svn
• Completely open: accepts merge requests
• Multiple projects
• Copy of svn for ZCP and WA projects git
Contribution agreement
• Publish the contribution,
both in source and binary
forms;
• Modify and maintain the
contribution, to ensure
continued quality and
performance;
• Relicense the
contribution, both in open
source and closed source
variants, also for OEM
distributors.
Open source; includes all
contributions Closed source and binary; includes all contributions, also
OEM
Zarafa You
How do bugreports become releases?
Remarks & questions?