Release new version, create a deb archive and put it on page.

Preare a bash completion script that will help user to type plugin name.

Create a plugin that will copy all dependencies libraries from local repository to target/lib.

Is the project dead? please don't be dead

Create a plugin implementation that will be capable of building RPM packages.

Make it possible to override default source directory structure. Not everyone will like src/main/vala ...

Make it possible to add a list of vala source files into recipe file by hand, model is already implemented, needs just some json deserialization code.

Add an option in plugin-build for genreating a library GIR binding file in target/gir.

Enable 'debug' mode - include valac '-g' and C compiler '-rdynamic' flags in plugin-build. Do it by reading new plugin recipe config entry.

Create a plugin that will scan local repository for defined dependencies and set custom vapi directories. It should follow recursive manner to include all nested dependencies.

Bobize Log4Vala - transform log4vala source code that Bob could build it and use it in bob itself.

https://github.com/nmelnick/Log4Vala

We try to keep Valder as simple and intuitive as possible mantaining it's elastic and quite powerful design.

Why don‘t you use for config files the Vala itself? Or .toml. https://en.m.wikipedia.org/wiki/TOML
They have much cleaner syntax than json files. I mean easier to read and write for people than json.

Currently Poulp provides almost everything Valder has + some other cool features, maybe add a comparison on the website next to the Bake (#32) one.

Implement a plugin that will be capable of creating Arch linux package descriptor.

Introduce new folder structure in src/main/resources and in src/library/resource that will be copied over in build process into target/share directory.

Think of some generic code formatting style that could be applied to any Vala file

Maybe you can take some inspiration form package.json that is used with npm. E.g. the wait version for deps are specified:
https://github.com/npm/node-semver

Implement plugin for generating valadoc configuration. I strongly recommend to rewrite this code https://github.com/GNOME/valadoc/blob/master/src/valadoc/valadoc.vala in a form of bob plugin.

Create a plugin for initializing an empty project with default folder structure and recipe.

Apply some non-destructible uncrustify rules on whole source code, right now it looks some times like ripped of from lawn mower. Indentation is completely broken and it's relatively hard to read some fragments (damn you sublime and my laziness).

There are some discrepancies in different plugins build scripts, need to be aligned.

https://launchpad.net/vala-dep-scanner already does it, rewrite it as a bob plugin.

Bake is a clear competitor for Valder, it has almost the same priorities and has a few Vala-related niceties that Valder currently lacks, but it's abandoned atm. Can you provide a comparison on the website? Thanks for your time

Fix header in Valder web page for mobile devices.

Right now any referenced .vapi file is passed as a source file for build. Change it to use rather external_package and include --vapidir equivalent in ValaCodeCompiler.

Prepare a better uncrustify configuration file that could be use to format any bob based project. I would suggest to follow Java formatting style, something similar to what is provided by defult in Eclipse or IntelliJ.

Implement a plugin for generating DEB file that could be shipped to debian/ubuntu distros.

Create a plugin for packaging output binaries produced by build plugin into archive, tar.gz or similar, or maybe give an option to choose one?

When there are no .vala files present under src/main or src/library directory just dont compile either library or runtime binary. It has to reflect also when passing parameters to runtime compiler (when lib is not generated).

Implement a plugin for running unit tests.

Introduce a way for using a gettext translation stuff.

Create new dependency attribute - scope - that could have one of three possible values:

• library - dependency will be used for compiling library binary,
• runtime - dependency will be used for compiling runtime binary,
• both - depdency will be used in both processes

Create a plugin that will 'install' build output files in local bob repository. The idea behind it is close related to what Maven is doing for java. This 'repository' will be just a directory in user home directory that will hold a list of subdirectories where each library built by Bob will place it's C headers/Vapi files/So libraries in a separate directory.

Implement an intermediate layer for using Valder in "interactive" mode. This will deliver a set of helper interfaces with some utility methods for making it easier to implement an integration layer with Valder for some other tools out there.

Update online documentation, add:

1. Information about generating GIR file,
2. Info about "sources" in recipe file

Change all references to 'Bob the Builder'. ALL.

When using Gtk annotations like [GtkTemplate] on newer versions of glibc compiler trows an error:

error: glib 2.38 is required for using Gtk templates (with --target-glib=2.38)

Implement new type of project build dependency that is a filesystem directory with vapi files at given location. It will introduce new dependency type beside "pkg". It would be nice to have an option to pass a vapi directory location, be it relative or absolute.

Add predefined dependencies while generating recipe file:

• gobject,
• glib,
• others ...