Best way to have new features included...

[Merlin]

I would suggest this list as the best place, hands down.  I particularly
don't like RentACoder and doubt you'll find anyone there (or anywhere else)
skilled with nginx that ISN'T here on this list.

That said, I know C and am learning how to make modules.  I would not mind
checking out a few simple tasks that I could apply as a module/patch and
submit to the list for use or maybe if it's really good and useful possible
inclusion in release; however, ultimately, Igor determines what goes into a
release we can only ask.  He has little time, though, so maybe we can help
crank out simple things.

Anything at all non-trivial, I would still be willing to work on, but I
would probably want some compensation as my free time is not in high
supply.  I would guess most anyone else on this list in similar situation as
myself (knows C, played with NginX modules, wants to learn more) would be
willing to work under the same terms.

If nothing else, you can always hone your skills with C and we can learn how
to make NginX modules together :).

On Wed, Jan 14, 2009 at 4:29 PM, mike <mike503 at gmail.com> wrote:

> I've been trying to get a couple modifications done too.
>
> Best thing would be probably ask this list, *maybe* #nginx on
> freenode, and try out rentacoder.com and maybe other sites, or look
> for people who know C well enough to adapt to nginx module coding...
>
> On Wed, Jan 14, 2009 at 2:16 PM, Resicow <resicow at gmail.com> wrote:
> > Hello,
> >
> > As you may know I have been asking about certain features from time to
> time
> > on this list.
> >
> > What would be the best way to go about having features added to nginx,
> > either core of as optional modules. There are some rather basic features
> > that I would love to see included, but I do not believe I have the skill
> to
> > develop these modules. Are there developers that are for hire that can
> > contribute to the code, that would of course benefit the entire project?
> >
> > Thanks,
> >
> > John
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20090114/b4a0cd8d/attachment.html>