Hi @barni2000,

this project is not dead. But the people with commit powers have little time to work on it.

There are indeed a few open PRs, but not all of them are "ready to merge". Getting features included is a matter of getting the following checkboxes right:

Without this changeset, SIPp is worse than the previous version.
The changeset follows coding standards, is self documenting and has a good commit message (the "why").
The code does not simply add yet another feature, but consolidates the existing features to make the codebase maintainable in the long run.
Documentation about changes and backwards compatibilities is available both in the CLI help and the RST.
It tries to make upgrading to the next SIPp version not too much of a hassle.
The change does not raise expectations of what SIPp can do without living up to its promise.
One of the committers is affected by this change or knows someone who is. Or the PR is accompanied by a compelling argument.

Getting more checkboxes ticked means someone is more likely to invest time in code review and merging. Not all of those criteria are objective, I know. But you have to remember that no one is getting paid directly to work on this (although they might get paid by their employer or customer).

To many of us, SIPp is a necessary evil. We use it because we haven't found a suitable alternative and we have invested time into getting it into our (or our customers') test procedures. There are some fundamental flaws, the code is supposedly C++ but it uses verbose and error-prone C much of the time, there is feature bloat where new things have been added in an inconsistent manner. But when it works, it works.

So yes: keep sending us your bug fixes and feature improvements. But try to get most of the checkboxes checked.

Cheers,
Walter

Is this project (fork) still alive? #457

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions