Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Opening the doors of eZ development
by Owen Fraser-Green
Development on eZ Publish today
 is an eZ Systems-only activity
You want to change things
How do you contribute?


     ?
It should be easy to improve eZ Publish
See the changes we're making to our
development model
We've switched to GitHub to make
      it easier to contribute
We've switched to GitHub to make
      it easier to contribute
Git is better
Distributed by nature
Offline usage
Branching is cheap
See Git in action
Cloning eZ Publish
Cloning eZ Publish
Cloning eZ Publish
$ git clone http://github.com/ezsystems/ezpublish.git
Initialized empty Git repository in /scratch/tmp/...
Committing
$ cat > README.txt
All your base are belong to us!
$
$ git commit -a -m "Test"
[master 6b9e2a0] Test
 1 files c...
Committing
Visualizing branches
Visualizing branches
Visualizing branches
GitHub manages forks
Forks are evil, right?
Hosted forks
Hosted forks
Improve eZ Publish by forking
We're launching eZ Publish
   Community Edition
GitHub eZ Publish will become
     Community Edition



              =
Everything that's public today will
        continue to be so
Community Edition wants your
         patches
Nearly all code we develop will be
      in Community Edition
So why have two?



      vs
Cutting edge vs Stability



           vs
Cherry picking, QA and Support
“Enterprise features”
Community Edition is everybody's baby!
Steering committee to lead
    Community Edition
Deciding the process
Community influences Enterprise
   influences Community
Opening The Doors Of E Z Publish Development
Opening The Doors Of E Z Publish Development
Upcoming SlideShare
Loading in …5
×

Opening The Doors Of E Z Publish Development

602 views

Published on

  • Be the first to comment

  • Be the first to like this

Opening The Doors Of E Z Publish Development

  1. 1. Opening the doors of eZ development by Owen Fraser-Green
  2. 2. Development on eZ Publish today is an eZ Systems-only activity
  3. 3. You want to change things
  4. 4. How do you contribute? ?
  5. 5. It should be easy to improve eZ Publish
  6. 6. See the changes we're making to our development model
  7. 7. We've switched to GitHub to make it easier to contribute
  8. 8. We've switched to GitHub to make it easier to contribute
  9. 9. Git is better
  10. 10. Distributed by nature
  11. 11. Offline usage
  12. 12. Branching is cheap
  13. 13. See Git in action
  14. 14. Cloning eZ Publish
  15. 15. Cloning eZ Publish
  16. 16. Cloning eZ Publish $ git clone http://github.com/ezsystems/ezpublish.git Initialized empty Git repository in /scratch/tmp/ezpublish/.git/ remote: Counting objects: 280931, done. remote: Compressing objects: 100% (52494/52494), done. remote: Total 280931 (delta 212307), reused 280023 (delta 211454) Receiving objects: 100% (280931/280931), 78.56 MiB | 3.29 MiB/s, done. Resolving deltas: 100% (212307/212307), done. $
  17. 17. Committing $ cat > README.txt All your base are belong to us! $ $ git commit -a -m "Test" [master 6b9e2a0] Test 1 files changed, 1 insertions(+), 72 deletions(-) rewrite README.txt (100%) $
  18. 18. Committing
  19. 19. Visualizing branches
  20. 20. Visualizing branches
  21. 21. Visualizing branches
  22. 22. GitHub manages forks
  23. 23. Forks are evil, right?
  24. 24. Hosted forks
  25. 25. Hosted forks
  26. 26. Improve eZ Publish by forking
  27. 27. We're launching eZ Publish Community Edition
  28. 28. GitHub eZ Publish will become Community Edition =
  29. 29. Everything that's public today will continue to be so
  30. 30. Community Edition wants your patches
  31. 31. Nearly all code we develop will be in Community Edition
  32. 32. So why have two? vs
  33. 33. Cutting edge vs Stability vs
  34. 34. Cherry picking, QA and Support
  35. 35. “Enterprise features”
  36. 36. Community Edition is everybody's baby!
  37. 37. Steering committee to lead Community Edition
  38. 38. Deciding the process
  39. 39. Community influences Enterprise influences Community

×