If you want to send a pull request to a certain project on GitHub, you first have to fork it to your own repository and then - in the most cases - clone it to your local machine. If you're contributing to a very active project with many commits, the size of this download will grow over the time. This is because the entire commit history of the project will be cloned to your machine as [Read more...]
On March 22nd, last Sunday, our new baby, my fourth son, gave us the honor of his presence on earth. Mom and baby are well :-) I should have informed you immediately but all my other boys before were in time or some days late - just this little man decided to be born a bit early... So I started my planned parental leave unexpectedly early, and I tell you: I was really busy in the last week [Read more...]
Yes, the rumours are true: @Hebsacker, AKA Raimund (Ray) Lang-Pantic, got a new job a while ago and it turned out that he'll have no more time for us at the OXID forums. Bummer, isn't it. I'd like to take this chance to thank him for his great job he was doing for years: perfect moderation, understanding the community quite well, dealing with fighting cocks, determining spam (quite challenging [Read more...]
In the last week, the first OXID user group meeting Leipzig took place at the office rooms of our dear partners pixi* Software. As announced, we came together in order to organize things first like topics to talk about within the next half year, how often and where to meet etc. Here are the results: 13 attendees (some of the registered excused as being ill, guests like Dennis from NRW [Read more...]
Let me trigger one of the most noteworthy pull requests to the OXID eShop repository at GitHub in the recent past. @adriankirchner, developer at dotfly (OXID solution partner) committed a fully functional Travis CI configuration. With this contribution it is not only possible to check at a glance if the unit and integration tests are presently passing. Also, contributors get notified whether [Read more...]
This is just a short note to let you know that there's a new page available at OXIDforge with a software development kit for OXID eShop. Presently you may find links to helping tools like coding standards, easy shop installation (thanks to @tabsl), module writing, testing and module certification on this page. Other tools, as announced at the last OXID Commons Unconference, will follow step by [Read more...]
Looking for the right developer can become a hard task nowadays, and very often a simple job description is not enough to attract good developers. On the other hand, you want to proof if a developer is good enough to fulfill daily tasks. Also very interesting to see that certifications, CVs and other documents are relegated to secondary significance. What really counts is what one can do for [Read more...]
OXID eShop is available under two different licenses, GPLv3 and a commercial license. That's why contributors have to sign up a so called "OXID Contributor Agreement" (OCA) before their contributions can be merged. In the past, this step was painful: most contributors didn't read the README.md file attentively enough and had to be pointed during the discussion about their contribution to the [Read more...]
Earlier this year, me and some mates attended the Symfony Live event in Berlin. As we at OXID are presently about to restructure our software architecture, we are happy to share our experience, potential pitfalls, concepts and possible resolutions. So two of us, Gigi (Product Owner) and Philip (Software Architect), held the talk "New software despite a legacy database". The talk was pretty [Read more...]
The default Azure theme, shipped with OXID eShop, uses flags instead of language names for the language changer. This makes sense when working with just two languages in your installation like English and German but quickly gets confusing when more languages are provided. In this case you most likely want to have the names of the language displayed instead of the flags. Of course you could make [Read more...]