There is no longer any way of avoiding it: we need a Windows package maintainer.
>From time to time people have said "I'm willing to..." but for various reasons (mostly from my side, usually silly and surprisingly technical ones) it never came to pass. It's also no more than fair to make it clear what work will be involved. So this time I'll try to do it right. We are looking for a libpqxx package maintainer for the Microsoft Windows platform(s). Tasks will include: * Building and testing libpqxx pre-releases on Windows against the most popular C++ compilers on that platform, finding and fixing any problems that come up. It is particularly important to report problems that crop up during the pre-release procedure, so the release can be delayed if necessary. * Publishing ready-made Windows builds of libpqxx for download, complete with headers, documentation, and anything else the user may need, in an easy-to-use format. Publication must be clear, well-structured, and consistent like on the free platforms, so that the main site can point Windows users there without having to be on the lookout for small changes. * Keeping Windows packaging infrastructure, code, and documentation up-to-date with the rest of the library. Releases of the Windows package do not need to be perfectly synchronized, and not all "upstream" releases need to make it into Windows packages, but the Windows packaging must not fall out of date. * Developing and/or accepting, testing, and submitting patches to improve Windows support in libpqxx. That includes C++ code, documentation, Makefiles, and scripts. * Monitoring the mailing lists to help people out with Windows-specific issues, and taking charge of turning productive discussions (including third-party patches) into actual improvements to code, documentation, etc. Personally I'd like the Windows packaging to be styled after what is common in the GNU/Linux world: automated install/uninstall, minimal or no manual configuration, and automated dependency checking where needed. Of course the Windows maintainer would be free to figure out what works best for him and for the platform, and to make his own tradeoffs between friendliness and convenience. Like all other platform-specific packagings, the Windows package(s) should be hosted separately from the main (source) page. The main project site will link to there from the packaging and download pages. If you are interested and hoping to find fame and fortune, be warned: you're likely to get some fame: the main site serves perhaps a thousand downloads per week, probably largely Windows. But forget the fortune part--we don't have any either! On the other hand being a libpqxx package maintainer can gain you lots of useful experience, and it can be something to point at in job interviews--it's proof of your credibility and in my experience, it really helps. Any takers? Jeroen PS - When I call the maintainer "him," it's purely grammatical. "He" can be male, female, or of any other gender. Multi-cell lifeforms only. _______________________________________________ Libpqxx-general mailing list Libpqxx-general@gborg.postgresql.org http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
