Commitments

LedgerSMB

As the lead developer and main (code) contributor to the LedgerSMB project since 2015, I'm committed to continued maintenance and improvement of the LedgerSMB ERP application with a roadmap balancing technological advancement and development of new features and user experience. Modernization of the code base has been a theme since before I joined the project (in 2013) and that will remain a priority for the future. The on-going effort aims to achieve - among others - the following results:

1. Continues expansion of options for customization
2. A continuous flow of new or improved features through yearly releases and regular patch updates
3. Improved integration of new features into existing workflows
4. Development of features based on business use-cases

New features need to be integrated in all aspects of the application. In my drive to achieve that, I come up with and realize flexible application architecture in combination with business use-case (i.e. business process) driven requirements analysis. This approach applies both to features still to be implemented as well as some features which were implemented in the past -- with a less holistic approach.

Spin-off projects

I have the philosophy that "a good developer doesn't just develop the application, but builds the tools which let him/her do so efficiently" and I'm no exception to that rule myself.

To help me build the application, I've initiated:

• Weasel project

Taken on (co-)maintainership of

• Test::BDD::Cucumber
• Gherkin and friends
• PGObject::*
• Authen::SASL
• LaTeX::Driver and friends
• Robot (JS state machines)

And contributed to:

• Workflow
• Test::Harness
• Test2::Harness
• Project::Pod
• Perl
• Robot (JavaScript)
• Dojo Toolkit

Other projects

Next to the projects in support of LedgerSMB, I've contributed to or taken ownership of e.g. Rex, Promises, Test::Dependencies, perl-json-schemavalidator, Email::Sender, Class::Observable, Test::Harness, Sys::Virt, Authen::SASL::SCRAM.