From: Wheeler, F. W (Research) <wh...@cr...> - 2003-10-24 20:22:33
|
[ sending a 2nd time ] VXL Community, I suggest that we organize a VXL developer phone conference. Let me know what you think. It has been some time now since the last VXL meeting at Brown. It would be great to have another meeting, but that is expensive and would require much longer to plan. Seems like a good idea to me to first see what we can accomplish over the phone. What to do (assuming we decide this is a good idea): 1. If you want to participate, e-mail me (Fred Wheeler) and/or this list. 2. E-mail agenda items you would like to cover to the VXL Maintainers list. 3. If you have an idea for a good whiteboarding tool we could use, e-mail the list. This is not entirely necessary, but it might be useful to have a live drawing or text-based connection at the same time. Even a text chat tool might be nice. I can set up the conference call. Our conference call system has a toll free (800) number people can use to call in. I'm not sure if it is a toll-free call from outside the US - was it so for the Brown meeting? I'd like to e-mail the dial-in phone numbers and access code only to regular e-mail accounts, and not the web-archived mailing lists. That is why I'm asking you to e-mail me if you would like to participate. Once any preliminary planning discussion settles down, I'll keep proposing times and dates to those interested until we find a time when we're all available. Initial Half Baked Agenda Items * Configuration - Windows DLLs - Are people happy with new CMake export scheme - Are people happy with new CMake configuration - Is it OK to be so dependent on CMake? - How do people structure their internal private code that uses VXL? * Language - Is anyone interested in TCL/Python bindings * VCL * V3P - Why VCLize V3P? V3P packages are already portable. Upgrades tough. - XML in v3p * Core - Ownership of core VXL libs - discussion started on list a few months ago - vidl upgrade to vil2 - NITF support in vil * Contrib - Any upgrade candidates - What are people working on? * Communication - CVS commit mailing list painful to read Summary to VXL maintainers after major changes better (or CHANGES.txt) - New release system - To Do list may invite new users to contribute * Testing - Borland C++ dashboard build coming (Part of the "deal" with Kitware) * VXL Principles - What is the VXL copyright exactly? - Is VXL in danger of becoming like Target Jr.? Regards, Fred Wheeler |
From: Wheeler, F. W (Research) <wh...@cr...> - 2003-10-26 03:26:16
|
VXL Community, I suggest that we organize a VXL developer phone conference. Let me know what you think. It has been some time now since the last VXL meeting at Brown. It would be great to have another meeting, but that is expensive and would require much longer to plan. Seems like a good idea to me to first see what we can accomplish over the phone. What to do (assuming we decide this is a good idea): 1. If you want to participate, e-mail me (Fred Wheeler) and/or this list. 2. E-mail agenda items you would like to cover to the VXL Maintainers list. 3. If you have an idea for a good whiteboarding tool we could use, e-mail the list. This is not entirely necessary, but it might be useful to have a live drawing or text-based connection at the same time. Even a text chat tool might be nice. I can set up the conference call. Our conference call system has a toll free (800) number people can use to call in. I'm not sure if it is a toll-free call from outside the US - was it so for the Brown meeting? I'd like to e-mail the dial-in phone numbers and access code only to regular e-mail accounts, and not the web-archived mailing lists. That is why I'm asking you to e-mail me if you would like to participate. Once any preliminary planning discussion settles down, I'll keep proposing times and dates to those interested until we find a time when we're all available. Initial Half Baked Agenda Items * Configuration - Windows DLLs - Are people happy with new CMake export scheme - Are people happy with new CMake configuration - Is it OK to be so dependent on CMake? - How do people structure their internal private code that uses VXL? * Language - Is anyone interested in TCL/Python bindings * VCL * V3P - Why VCLize V3P? V3P packages are already portable. Upgrades tough. - XML in v3p * Core - Ownership of core VXL libs - discussion started on list a few months ago - vidl upgrade to vil2 - NITF support in vil * Contrib - Any upgrade candidates - What are people working on? * Communication - CVS commit mailing list painful to read Summary to VXL maintainers after major changes better (or CHANGES.txt) - New release system - To Do list may invite new users to contribute * Testing - Borland C++ dashboard build coming (Part of the "deal" with Kitware) * VXL Principles - What is the VXL copyright exactly? - Is VXL in danger of becoming like Target Jr.? Regards, Fred Wheeler |