schlitt.info - php, photography and private stuff
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

:Author: 		Tobias Schlitt
:Date:			Mon, 19 Jul 2010 10:24:24 +0200
:Revision: 		2
:Copyright:		CC by-nc-sa


======================
Arbit? Service please!
======================

:Keywords:  qafoo, arbit, project, service, php, quality, assurance, qa,
            consulting, training, support, development
:Description:
    Qafoo - passion for software quality - will provide consulting, training,
    support and payed development for Arbit, your project integration tool of
    choice.
:Abstract:
    It's only two weeks left, until Qafoo__, the company by Kore__, Manuel__
    and me, will officially start. Time to reveal another topic of our service
    repertoire: Consulting, training, support and payed development for Arbit__,
    your all round project tool of choice.

__ http://qafoo.com
__ http://kore-nordmann.de/
__ http://manuel-pichler.de
__ http://arbitracker.org

It's only two weeks left, until Qafoo__, the company by Kore__, Manuel__ and
me, will officially start. Time to reveal another topic of our service
repertoire: Consulting, training, support and payed development for Arbit__,
your all round project tool of choice.

__ http://qafoo.com
__ http://kore-nordmann.de/
__ http://manuel-pichler.de
__ http://arbitracker.org

.. image::  http://files.schlitt.info/blog/arbit_tracker_thumb.png
   :alt:    Arbit issue tracker
   :target: http://arbitracker.org/arbit/about/full/overview.html

.. note::
   As last, we founded **Qafoo - passion for software quality**.  Please refer
   to our company site, if you want to hire me, especially for services around
   `high quality PHP code`__.

   __ http://qafoo.com

Every software development project needs a bunch of tools, supporting
developers, managers, QA and others. An issue tracker, for example, or a wiki,
continuous integration and more. Arbit__ is the PHP projects tool of choice for
having all such services in a central place. With a well thought out
architecture and software design, built for modularity and extensibility, Arbit
attempts to replace solutions like Trac and phpUnderControl in one go …
some when in a not too distant future.

__ http://arbitracker.org

By now, Arbit__ is in alpha stage and still needs some love before going stable
for the first time. Its issue tracker already works nicely, although it cannot
realize complex workflows, yet. The wiki will soon support different styles
of markup, like e.g. ReStructureText, which is common choice nowadays. The code
browser allows you to browse your source code repository nicely and in
combination with the report module (attention, experimental!), it can show you 
nice and informative reports right in your code lines. A simple FAQ module also 
exists, yet.

__ http://arbitracker.org

.. image::  http://files.schlitt.info/blog/arbit_source_diff_thumb.png
   :alt:    Arbit source diff
   :target: http://arbitracker.org/arbit/about/full/sourrce_diff.html
   :class:  left

So, what is so cool about Arbit__? Basically three things: First, it is really
built for extensibility. Only highly essential code, like the MVC__, is part of
the core. Everything else is realized in pluggable modules. A `signal-slot`__
style messaging mechanism allows modules to interact arbitrarily with each
other and to issue signals other modules can work with. A good example is the
notification module, which is basically independent from any other module: It
simply gathers signals from other modules, if they are installed, and converts
them to notifications a user can subscribe to in different ways, e.g. by mail.
Oh, I missed the second and third cool thing? Well, second, Arbit is fully open
source, being GPL 3 licensed. And third: Arbit is fully written in PHP, so you
can hack your own modules and, if necessary, fix issues yourself!

__ http://arbitracker.org
__ http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller
__ http://en.wikipedia.org/wiki/Signals_and_slots

OK, now where will Arbit__ go with Qafoo__? Basically, nothing will change.
Arbit will continue to be fully open source and we, as individuals, will
continue to contribute to it. But, furthermore, we as a company will also
contribute to it. One of our major internal goals is to develop Arbit further
and to make it **the** tool of choice for any software development project.

__ http://arbitracker.org
__ http://qafoo.com

Beside that, we will offer you professional services around the tool. Do you
need to have your users trained on using Arbit__? Do you want to integrate it
into your environment, but have some issues? We'll come around to consult. Do
you need someone to kick, if something is not working properly? We'll provide
support. Do you want that specific cool feature, but don't have the resources
to realize it yourself? We'll make your wishes become true.

__ http://arbitracker.org

So, Arbit is one of the key tools supported by Qafoo. Beside that, we will also
take care and provide services for other tools in the PHP quality assurance
area, like `Kore already announced`__, and for Zeta Components, like `Manuel
wrote`__. Btw. you hopefully did notice that eZ Components have become Zeta
Components and are just incubating to become an Apache project? No? Then you
should probably `take a look here`__.

__ http://kore-nordmann.de/blog/0100_quality_assurance_tools.html
__ http://manuel-pichler.de/archives/91-Presenting-the-first-Qafoo-Service-Zeta-Components.html
__ /opensource/blog/0725_goodbye_ez_systems_hello_world.html


..
   Local Variables:
   mode: rst
   fill-column: 79
   End: 
   vim: et syn=rst tw=79


Trackbacks
==========


Comments
========