[ I'm pulling this out from the configuration database thread, as I
think there are some interesting issues here, but
I don't want to muddy that thread ]
On 16 May 2009, at 14:17, Michael Joyner ᏩᏯ wrote:
And speaking of feature requests... is there a way to add "hooks"
into the pts security database lookups?
Roughly speaking, there are two mechanisms through which code gets
written for OpenAFS. The first is that fixing a particular problem
interests a developer ("scratches an itch"), and so they do so and
contribute it upstream. The second is that a developer is commissioned
by a client to produce a particular solution (there's a list at http://www.openafs.org/support.html
of companies providing this service)
Unfortunately, there aren't a huge number of us in the "scratches an
itch" category, and generally speaking we have our (and our employers)
itches to scratch. Unless you can convince someone that adding hooks
to the pts database is an interesting problem, simply posing it as a
feature request is unlikely to see it implemented in a reasonable
timeframe.
However, what I am very keen to do is to grow the pool of people
writing code for OpenAFS. If you, or a colleague, have the inclination
to dive into adding the support yourself, I'd be happy to help you
here, on IRC, or on Jabber, with any development questions you might
have and to assist with the whole process of steering your
contribution into something that can make it into the codebase.
Cheers,
Simon.
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
