[email protected] wrote: > There's your answer as to whether you can depend on policyd for (insert your > concern here). Sooner than what, I might ask. > > With two years without any substantive progress and/or support to show for > it, I consider policyd dead.
Well here's something that apparently could be news to you. It's an open source project, and not supported by any commercial backing (that I know of) - not that commercial backing makes any difference to the fundamental argument. Nigel has written it in his own time and supports it in his own time. He does not owe anything to you or me. If there's a feature you want in the package, then like everyone else you have a number of options open to you : 1) You can wait until the project author(s) get round to it, if they want to do it. 2) You can sponsor the project author(s) to do it, if they have the time and it's something they want to do. 3) You can grab the source and fix it yourself. 4) You can pay someone else to do it - and contribute the fixes back to the project. The one thing you have no right to do is : complain that no-one else has done it for you. If you're not happy with that, you can always have your money back ! > It's a shame really because there's not much out there with the (purported) > feature set of policyd. I'm not aware of anything with that feature set. P.V.Anthony <[email protected]> wrote: >> Its a shame I have to waste my time answering mails like this. I think I'd be inclined not to. > I do not know how to say this but here goes. > > I really appreciate the work you have done. I am using policyd on my servers > and it is helping me very much. There is so much less stress for me with > policyd doing its work. > > I thank you for the work you have done. More importantly, that you shared > policyd's code with the community. +1 on that. _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
