On Monday, November 09, 2015 07:54:54 PM Simon Hobson wrote: >skee...@skeeved.org 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 !
That being said, allworldit.com do offer commercial support. It makes no difference as you said. Its not widely advertised either as I'm not really one to push commercial options. I can however say quite a bit of my work on policyd has been and is funded through this, and there does exist large companies and providers that would rather just say "sort it out for me please, here, there, fix". Or ... "add this feature please". By default I prefer to push committing to the development branch, but in some cases (and at a huge increase in rates) we have time limits when the feaures can be made public or if they're maintained in a private repository (here is our repo, make this change here). Some may cringe at this, but at the end of the day the more people with a commercial interest the livelier the project is and eventually everything makes its way back upstream. I was also consulted regarding a kind of kickstarter-type project site for new features and version releases, where 100% of the funds gathered goes into the project. Also allowing for things like very low monthly recurring amounts around the $5 or so region. >> 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 <anth...@mindmedia.com.sg> 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. Thanks Simon :) As for development progress, I have a largish update which I still need to push... among other things it adds alot more error checks to startup to help if you're missing modules, has the rename to policyd-cluebringer, few more changes I pulled from the enterprise repository. $ git diff origin/master --stat | tail -1 This took me a full two weeks and I made the changes both in v2.0 and v2.1. I just need to finish off the packaging and sort out some CI build systems going forward. -N
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Users mailing list Users@lists.policyd.org http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
