Opening The Doors Of E Z Publish Development
•
0 likes•225 views
The document discusses how eZ Systems has switched to using GitHub for eZ Publish development to make it easier for external contributors. It explains how to clone the eZ Publish repository from GitHub and make commits. It also describes how eZ Systems is launching an eZ Publish Community Edition on GitHub that will become the main repository, intended to encourage contributions from the wider community.
![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%)
$](https://image.slidesharecdn.com/openingthedoorsofezpublishdevelopment-12854485886657-phpapp01/85/Opening-The-Doors-Of-E-Z-Publish-Development-17-320.jpg)
Opening The Doors Of E Z Publish Development
- 1. Opening the doors of eZ development by Owen Fraser-Green
- 2. Development on eZ Publish today is an eZ Systems-only activity
- 3. You want to change things
- 4. How do you contribute? ?
- 5. It should be easy to improve eZ Publish
- 6. See the changes we're making to our development model
- 7. We've switched to GitHub to make it easier to contribute
- 8. We've switched to GitHub to make it easier to contribute
- 11. Offline usage
- 13. See Git in action
- 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. 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. Committing
- 23. Forks are evil, right?
- 24. Hosted forks
- 25. Hosted forks
- 26. Improve eZ Publish by forking
- 27. We're launching eZ Publish Community Edition
- 28. GitHub eZ Publish will become Community Edition =
- 29. Everything that's public today will continue to be so
- 30. Community Edition wants your patches
- 31. Nearly all code we develop will be in Community Edition
- 32. So why have two? vs
- 33. Cutting edge vs Stability vs
- 34. Cherry picking, QA and Support
- 36. Community Edition is everybody's baby!
- 37. Steering committee to lead Community Edition
- 39. Community influences Enterprise influences Community