How many developers are actively working on Vaultwiki?

[Alfa1]

I was wondering how many developers are actively working on VW. The upcoming VW4 is a big project which will integrate with IPB, XF as well as vb and a large number of new features will be included. Some of them are major features. Since development of VW4 has had some major delay, I wonder about the future of VW4 development speed.

I know I asked a similar question once before, but I cant find it. Sorry.

[InformationNirvana]

Hopefully you are looking for vaultWiki for xenforo

[Alfa1]

I definitely know what you mean.

[we_are_borg]

I was wondering how many developers are actively working on VW. The upcoming VW4 is a big project which will integrate with IPB, XF as well as vb and a large number of new features will be included. Some of them are major features. Since development of VW4 has had some major delay, I wonder about the future of VW4 development speed.

I know I asked a similar question once before, but I cant find it. Sorry.

Like you i am waiting for months for VW4 so that i can continue to build my new website and i need VW4 with support either for XF or IPS in it. The delays are not weeks but months at the moment and i can not afford later that development of VW4 will continue at the same pass. If it does i am better off looking for another solution.

[pegasus]

For those wondering about the number of developers, we still have about the same number that we had before we started working on version 4. This means that developer attention is currently divided by developing for both VaultWiki 3 and 4 at the same time.

See: https://www.vaultwiki.org/showgroups.php
With the exception of 2 or 3, the admins are all developers. Each one focuses on different areas, such as styling, code design, documentation, or actual programming. Some are only part-time or brought in on a limited basis, depending on the stage of the current development cycle. Some are definitely more active than others, with myself being the most active. Activity on this forum is not necessarily indicative of development activity (in fact, it's more like it's inversely proportional). We work in a small office, use an offline IDE, and commit to a private server to test changes.

Further, development has only been slow on the new VaultWiki 4 release. We have still been releasing regular maintenance updates with bug fixes or minor features for VaultWiki 3. VaultWiki 3 has been prioritized because it is the current version, and we need to always support the current version, rather than some future version.

We have been writing new features for VaultWiki 4 at about the same rate as new features on other past VaultWiki 3 releases. The only difference is that we haven't released version 4 yet.

Once VaultWiki 4 is released, updates will actually speed up, because we won't be delayed by developing for multiple versions at the same time. In the mean time, if we lose a few potential leads, so be it. We don't want to release a version 4 that doesn't work or doesn't do everything we promised, especially after the number "4" was tainted by vBulletin. It will be delivered when it's ready.

Please keep an eye on the tracker. While the launch date may not be current, the percentage completion is a much more reliable figure. We are much closer to 4.0.0 Alpha 1 release now (91%) than we were in April (<50%).

[Alfa1]

Thanks for the elaborate reply. Do you consider to take on board more developers?

[pegasus]

We would have loved to for quite some time, but it's just not economically viable to take on any more people than we currently have.

[Alfa1]

We would have loved to for quite some time, but it's just not economically viable to take on any more people than we currently have.

Well, you have a modest pricing structure in comparison to photopost and vbseo. You could consider your options to attract more income.