What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
| Date | Action | Decided by |
|---|---|---|
| 2007-06-20 | Appointed Gregory Trubetskoy | the board, by resolution |
| Date | Decision | Item | Outcome |
|---|---|---|---|
| 2010-06-16 | Terminate the Apache Quetzalcoatl Project | special order | approved |
| 2007-07-18 | A request by the newborn Quetzalcoatl project to use the simplified subdomain python.apache.org… | discussion | discussed |
| 2007-06-20 | Establish the Apache Quetzalcoatl Project | special order | approved |
My sincere apologies to the board for missing the report deadline! Quetz continues to remain mostly dormant. Although today someone posted a mod_python bug report to the list, the first in many months. There have been suggestions regarding moving the project to the attic. I am contemplating this, it doesn't appear to be the obviously correct move at this point, because the scope of Quetzalcoatl is wider than just mod_python and it doesn't seem like there is nothing to do, the issue is mostly that the original contributors for whatever reasons have been busy and are not contributing currently. This is an on-going discussion, and I think by the next quarter report time we will have decided on what the the best thing to do is. If the board has any opinions on it, do not hesitate to email the PMC.
This report is a repeat of the previous one: No new developments to report for mod_python this quarter. No new versions released, no major issues discovered. The pace of development and Jira issues is very very slow.
This report is a repeat of the previous one: No new developments to report for Quetzalcoatl this quarter. No new versions released, no major issues discovered. The pace of development and Jira issues is very very slow.
This report is a repeat of the previous one: No new developments to report for Quetzalcoatl this quarter. No new versions released, no major issues discovered. The pace of development and Jira issues is very very slow.
No new developments to report for Quetzalcoatl this quarter. No new versions released, no major issues discovered. The pace of development and Jira issues is very very slow.
Things continue to be very quiet on the Quetz/mod_python front. No new releases have been made since the last report and none are planned for the near future. The current version of mod_python works fine with the latest Python 2.x branch, however now that Python 3.0 is out, we will try to make a new version of mod_python, however it is not clear at this point how complicated it will be and whether it is at all technically possible.
Things continue to be very quiet on the Quetz/mod_python front. No new releases have been made since the last report and none are planned for the near future.
No releases made since the last board report, no releases planned in the near future. Mod_python continues to be dormant, my recent email to the PMC received only one response, and it appears that the current development team and the PMC has either little interest or time (or both) to contribute to the project. I personally feel that we do not know how it may evolve and so we are just letting it be. Infrastructure has just created a zone for us (which only took like a year), so in the near future we will start moving modpython.org's content there.
Things continue to be very quiet on the Quetz/mod_python front. No new releases have been made since the last report and none are planned for the near future.
Finally just recently the mailing lists and other infrastructural things for the Quetz TLP have been done and so the TLP transition is nearly complete. Aside from this, not much activity, mod_python development activity is mostly dormant, no new releases in the pipeline.
Again not much to report. I am back from vacation, the TLP creation is now in the Infra queue in the form of Jira issue INFRA-1355, hopefully it will be done soon. On the development of mod_python - not much activity. Most likely in 6 months the focus will shift to adapting to Python 3K.
There is not much to report. I'm away on vacation this month with very little computer time and have not done much to advance the set up of the Quetzalcoatl infrastructure. Mod_python development is nearly dormant with last Jira issue update on Aug 7th. There are no issues or concerns to report at this time.
Mod_python ========== * No new releases, things are quiet at the moment Community ========= * No new commiters or PMC members Issues ========== * Let it be officially known that the whole thread about the Quetzalcoatl TLP (the resolution for which was officially approved by the board) domain name on the board list was rather unhelpful and completely unproductive.
