cli-dev@ community, as we polled over the past few months, it seems that most of the dev interest on this forum remains centered around mod_aspdotnet, and using mono or aspdotnet tools to proide ASP.NET services from Apache httpd server. It's the decision of the httpd PMC to fold all efforts around mod_aspdotnet into the httpd core community.
You can get a jump on this by subscribing to dev@httpd.apache.org, if you are not already. We will move mod_aspdotnet development discussion on Monday, so email [EMAIL PROTECTED] now to ensure you miss nothing. This move offers several advantages - better oversight by httpd, better communications between mod_aspdotnet development and httpd core development, and so forth. The core developers learn more about mod_aspdotnet, the mod_aspdotnet developers learn more about how Apache httpd server is evolving. And as simultaniously announced, cli-users@ moves to users@ at the same time, for very similar reasons. The repository won't move, it will remain a seperate svn module, because it is built only for one platform using one set of compiler tools. The binaries would move directly into the http://www.apache.org/dist/httpd/binaries/win32/ download location, once voted to release. In moving, a new release will be submitted Monday for consideration based on the most recent snapshot (which many already use). Once it's done, this will be branched to a vs2002 specific branch, and the main code upgraded for the new C++ API in Visual Studio 2005. This should permit more users to roll-their-own based on the Visual Studio 2005 express edition, and catches up to Microsoft's current C++.NET programming language (which as some already know, looks little like the original iteration of C++.NET). This also catches us up to .NET 2.0. We hope to see a strong showing in the release vote process, because the release process is the one and only metric of project health; it will determine if the mod_aspdotnet continues to survive as an effort of the ASF and the Apache HTTP Project. Although non-PMC votes aren't binding, they are very much needed for other PMC members to guide their votes, please consider testing this candidate early next week. (This process, of course, will occur on dev@httpd.apache.org). On the long-term roadmap, one possibility for Apache 2.2 and onwards is a brand new mod_proxy_asp implementation, similar to the other proxy connectors; and the possibility of rebirthing cli-dev soley to focus on developing .NET-authored Apache HTTP Server module extensions still exists. However, re-sparking cli-dev in that form would entail entering the incubator as a new effort, one I'm happy to contribute to, and mentor, but will not solo. Ping me if you have interest. Yours, Bill
