Planet eZ publish
When we create a fork of a repository on github.com our fork is just a standalone copy of the original repository as it was at that moment when we "forked". Many of us, especially at beginning of using git, expect somehow that our fork to be "in sync" with the original repo which is not the case.
For those of you who are not interested or not have time to invest learning git I put together in this post the minimal steps you need to do to synchronize your fork with original repository. (synchronize = getting the commits that where pushed on the original repository into our fork)
In case you also wonder what's the purpose of a fork my answer(not very well documented) is: to permit pull requests.
Assumptions: you have git installed on you computer, being able to use it from command line and you have the github authentication setup so that you are able to push commits into your fork (if not see this).
Thanks for spotting and fixing a typo introduced in v1.0beta8.
I have worked a bit on adding a few core features I really wanted. This mostly was around arguments with values, as well as completion for these values.
Here are the minutes of the 13th Community Project Board meeting. Our previous minutes can be found here.
eZ Systems today introduced their updated web pages. We hope you find what you need to further your business and further your relationship with eZ Systems.
eZ is really pleased to announce three new user groups in North America. Three events are planned for early December: Chicago, New York City and Washington DC.
During a recent apt-get update && apt-get dist-upgrade I suddenly found myself with the horrors that are Gnome 3 and the Gnome shell, and of course, at the least opportune moment when I was actually planning on heading into an office (more about that later). I've always been a big Sawfish fan, and was annoyed when Gnome replaced that with Metacity, but I always managed to get Sawfish back up again. No more luck now, and without a Debian package maintainer I decided to try out XFCE.
I found XFCE to be as easy to use with the keyboard as Sawfish but with one big missing issue: I couldn't change the size and position of windows at the keyboard anymore. I hardly use a mouse as it hurts too much, and always relied on those keyboard shortcuts to position my windows so I was quite a bit at a loss. After some searching I ran into a post on nabble that contained a script that almost did what I want. It uses a bunch of standard X tools (xprop and xwininfo) to find some information about the active window and its properties. Then depending on some parameters it would use wmctrl to move and/or resize the window. For example: ./bin/window-geometry-control.sh -m left would move the window 1 pixel to the left.
That's all good, but way too slow. I basically just want to bump my windows to the top, right, bottom and left sides of my screen. So besides the simple move and resize, I added what Sawfish originally also had: move left/right/top and bottom; and well as resize-to left/right/top and bottom. Now with the command ./bin/window-geometry-control -b left I can move the active window all the way to the left, and with ./bin/window-geometry-control -s bottom I can resize my window from its current position all the way to the bottom of the screen. To each of the four directions and two methods I assigned keyboard shortcuts in xfce4-settings-manager, Keyboard, Application Shortcuts.
The screenshot above shows those assigned keyboard shortcuts. I've put the modified script on github. As you can see I hardcoded the width and height of my own screen in it. Feel free to make this dynamic and send a pull request.
Using the amazing command line git client, I came to feel frustrated when I had to use scripts that don't provide arguments completion. It just feels wrong, now. And eZ Publish bin scripts are among those. And man, they do have arguments. Right ?
Last call for Open Source CMS Market Survey!
So far the main, semi-automated Twitter account was @ezcommunity. It channeled manual messages, commit messages, notifications for new forums posts, new blog posts and new tutorials. This has changed now, for the better.
