On 11/09/2015 02:12 PM, Nigel Kukard via Users wrote:
I have abosolutely no obligation whatsoever to provide you or anyone
else with any kind of support, nor am I obligated in any way to maintain
any number of public commits over any time frame. I do however take time
away from my family and answer requests that I want to, when I want to
and I will work on the project in my free time when I am in the mood to
do so.
You are not privy to any development currently happening or the number
of hours spent on it, nor do you have access to the enterprise
repository. Your consideration that the project is dead is based on your
own personal assumption which has no factual merrit and is quite
disrespectful.
Its a shame I have to waste my time answering mails like this.
Firstly, let me just say that I mean no disrespect to Mr. Kunard or the
policyd project. The company that I work for has been using policyd v1
for many years. Any frustration that I may have displayed is entirely
due to my recent workload and in no way should anyone think it was
directed towards Nigel Kunard.
And I will state for the record that what I say is absolutely my own
opinion and is of importance only to myself. And, that is to say, not
of much importance at all.
I will respond to Mr. Kunard's response though as he was kind enough to
provide it in this instance.
It is true that you have no responsibility to provide support,
information or anything else to anyone if you so choose to withhold it.
I will contrast your statement though against other open-source projects
where the authors, developers and users of the software in question do
provide best-effort support via mailing-list, IRC etc. This is a
portion of how a community is formed around a software/development
project. A thriving community is generally considered a desirable
attribute of an open-source project.
You are also not under any obligation to show anyone what super-secret
code you are working on, nor provide any additional upgrades, updates or
bug fixes in any specific time frame or indeed ever. I will again,
however, contrast this attitude against other numerous open-source
projects where code development happens more or less 'in the open'.
That is, after all, what open-source development is all about.
I am not aware of any development happening to policyd and could not be
as it is not publicly available so obviously I could not be aware of how
many hours development time is being applied to it. I also do not have
access to an enterprise repository, would that I did.
As stated above, my opinion regarding the liveliness of the policyd
project is entirely my own. However, seeing as:
* there is only a small amount of mailing-list traffic and the traffic I
do see is usually someone asking a question or reporting a potential bug
and, only rarely, getting any sort of meaningful response
* there have been no substantive code commits in two years
I stand by my statement that, as an open-source project, policyd seems
to be dead. It's status as a closed-source commercial project I have
absolutely no knowledge of and, therefore, decline to offer an opinion.
Again, I say it is a shame because there really is nothing out there
that offers the features that policyd does. I spent weeks attempting to
get policyd v2 running in a new environment simply because I WANTED it
to work in the worst way. I need these features.
I have a feeling that in many environments it works well. In fact, I
exchanged emails with several people that are using it apparently
without issue. The details of their implementations however differ from
mine in ways that made it apparent that it wasn't going to work in my
environment.
I am curious as to who is using policyd, in what environments and at
what scale. Indeed, I asked this mailing-list that very question weeks
ago. A dearth of responses I got.
I also attempted, albeit in a cursory fashion, to engender some response
regarding commercial support for policyd. Again, no response from
anyone. So, if there is a commercial/enterprise version of policyd I
fail to see why there would be any need to keep it secret. It must be
difficult indeed to derive a suitable income from software that doesn't
want to be sold and supported.
This response is already too long, and I apologize for that. I've moved
on to other solutions because I had too not because I wanted to.
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
