Robert Basic's blog

Posts tagged 'contributing'

Contributing to Zend Framework 2

by Robert Basic on November 10, 2011.
Heads-up! You're reading an old post and the information in it is quite probably outdated.

Today a pretty big news hit the interwebs: as of today, the CLA is not required any more to contribute to Zend Framework 2! This means anyone can issue pull requests and submit patches to the new version. Note that if you want to contribute to Zend Framework 1, you still need a signed CLA. I’ve decided to write a quick post with additional information and links, to make it easier getting started with the contributions!

Back in July I wrote a post on helping out with Zend Framework 2, so consider this post as a second part of that post ;)

The development is on git. The original repo is http://git.zendframework.com/?a=summary&p=zf, while the one on Github is a mirror which gets updated twice a day. Not that it matters much, as everyone forks the Github version and sends pull requests against that.

The issues are kept on a Jira instance: http://framework.zend.com/issues/browse/ZF2. Please make sure you are actually on the Zend Framework 2 project, as we have a separate project for ZF 1. Create an account on Jira and off you go. If I’m not mistaken, it is connected to the ZF wiki, so you can use that too.

All ZF2 related stuff on the wiki is located in it’s own section. It’s full of goodies, so take your time to browse it.

We hold biweekly IRC meetings: every second Wednesday, 17:00 UTC. The next one is going to be on November 23rd. Prior to each meeting we set up an agenda, vote on it, decide who will be moderator and then just discuss whatever is there to discuss. The meetings are held on the #zf2-meeting channel, on Freenode. All agendas and logs from previous meetings can also be found on the wiki.

We have a separate #zftalk.2 IRC channel devoted to discussing all things ZF2!

Subscribe to the mailing lists; you’ll be especially interested in the “Contributors” section; all big and small things are discussed there.

A new “thing” introduced to the ZF ecosystem are the RFCs. We’re using those when a new architecture is discussed or a rewrite/refactor of an existing component is to be done.

New components need to go through a proposal process. The proposal process is rumoured to get an overhaul, but (hopefully!) it won’t be going away.

There is also a blog set up, so be sure to subscribe to the feed.

Great and exciting times are ahead of us and I welcome all new ZF contributors! :)

Happy hackin’!

Tags: cla, contributing, zend framework 2, zf.
Categories: Development, Programming.

Helping out with Zend Framework 2

by Robert Basic on July 27, 2011.
Heads-up! You're reading an old post and the information in it is quite probably outdated.

OK, here are some tips and resources so you can start helping out and contributing to Zend Framework 2.0 :)

First, here’s a nice wiki page with some links on how to start with Zend Framework 2. Be sure to check out the Zend Framework 2.0 patterns tutorial slides and the webinar on the same topic (you need to log in to watch it, but the registration is free, so no excuses).

The development is happening on github, so that’s a nice starting point to get your hands dirty with some code. On the wiki there’s a Zend Framework Git Guide to get you started. Pay close attention to the “Working on Zend Framework” chapter.

As Matthew noted in this thread you can:

Fix unit tests!

Once you forked and cloned the github repo, cd to the zf2/tests directory and simply make the tests there pass! Of course, there are a lot of tests there, so you might want to start with something easy and small; for example I picked the Zend\Dojo component :P

Anyway, once you’re in the tests directory, just type:

robert@odin:~/www/zf2/tests$ phpunit --verbose Zend/Dojo

or:

robert@odin:~/www/zf2/tests$ phpunit --verbose Zend/Dojo/DojoTest.php

and watch the tests pass or fail. If they pass, good, if they fail, try to fix them and make them pass! I tell you, it’s fun! By using the “–verbose” flag you’ll get more (helpful) info about the tests.

Port Zend\Service

I haven’t look into it yet, so just quoting from the mailing list:

* Port Zend\Service classes that interest you to namespaces, new
exception usage, etc.

but I believe if you start from the tests for the services too, you should be all set!

Port ZF1 patches to ZF2!

Even if ZF2 is under development, ZF1 is still taken care of: that means, a lot of patches are present in ZF1 which are not in ZF2 (cause they were added after ZF2 branched off of ZF1, obviously…). Some patches will probably not be needed thanks to the rewrite, but some patches will be! So head over to the issue tracker, search for recently (where recently is, say… this year?) resolved and fixed issues, see if they have a patch attached, if yes, open the patch, see if that patch is already in ZF2, if not, add it, issue a pull request, move on to the next issue.

Play with the existing code!

The official Zend Framework Quickstart is also on github, with different features on different branches! Fork it, clone it, test it, make it, break it, fix it… I myself am rewriting a ZF1 based application to ZF2, so you can have a look at that too!

I have also created a few gists about using the new helper loaders/brokers/plugins.

That’s it for now, if I remember/find anything else, I’ll update the post. Of course, if you have to add something, fire away! :)

Happy hackin’! :)

Tags: contribute, contributing, help, zend framework, zend framework 2, zf.
Categories: Development, Programming.

Contributing to open source

by Robert Basic on March 17, 2011.
Heads-up! You're reading an old post and the information in it is quite probably outdated.

Often times people ask me why do I contribute to open source, why do I “waste money and time” on free stuff when I could easily do the same thing for money? Don’t have I enough of staring at the computer at work where, well, I do the same thing - hack on code? Ummm. No.

Honestly, I don’t earn much. Enough for the rent, bills, food, but giving the fact that I don’t have a family, it’s enough for me, for now. So, I don’t make a s**t loads of money, but am still willing to work for free? Ummm. No.

Thing is, I really don’t consider this to be work. This is fun. This is hacking. This is creating stuff. This is solving problems. This is my passion. So no, I don’t work for free. I don’t work. I code, I hack.

But why open source?

Giving back

Giving back is nice. Not necessarily giving back to the same project, but just giving back to the open source community in general. It just makes you a better and nicer person :)

Knowledge

Both in high school and in college the fastest way for me to gain knowledge was to learn, collaborate with other students. Open source gives me the chance to share knowledge with hackers from all over the world; from Portugal, via Nova Scotia to Texas. It gives me the chance to be taught and to teach.

Experience

Open source gives the opportunity to work with people from every part of the globe. Getting ideas across by the means of email, chat, irc can be hard. Open source gives me the chance to improve my communication skills. Heck, I sometimes even have troubles explaining my ideas to my co-workers who sits right next to me.

Reading other peoples code, fixing bugs, writing documentation, adding new features, testing. Hack skills ++

Also, each and every accepted patch and merged pull request gives me that warm and fuzzy feeling inside.

Contacts

Open source introduces you to new people. Who knows what can come out of these random introductions? Can’t be bad, that’s for sure.

This is why I contribute to open source: it is fun, it is hacking, it is creating stuff, it is solving problems.

It is my passion.

Tags: contributing, hack, hacking, open source, random.
Categories: Blablabla.