From klm@CNRI.Reston.Va.US Fri May 17 18:42:49 1996 From: klm@CNRI.Reston.Va.US (Ken Manheimer) Date: Fri, 17 May 1996 13:42:49 -0400 Subject: [PYTHON META-SIG] SIG Coordinator control of python.org SIG dir contents Message-ID: <199605171742.NAA05779@glyph.CNRI.Reston.Va.US> For those of you on the meta-sig who are managing a PSA SIG: As threatened for a while now, i've set something up by which SIG coordinators can upload stuff to their own SIG Web directories on Python.org. I needed to do this in a secure way, without enabling login-style privileges - the setup is a uses special group privileges under anonymous ftp to python.org, restricted by the password each SIG coordinator has for their majordomo list. Rather than go into the details here, you can check the web document for full instructions: This lightly covers the majordomo list management, as well (and has a pointer to an htmlized version of the full majordomo man page). It is linked into a somewhat reworked SIGs index page: I expect a shaking-out period as we put this system into use. Please let me know about problems, questions, and suggestions on any part of the setup, and bear with me as we get it working smoothly. I'd also particularly be interested in any aspects of the system which you see as being unsafe - please do not be shy about relating any suspicions of susceptabilitties in the system. We are trying to provide more control to the SIG managers, around the world, without compromising the security of our gracious host site! One more item - it turns out that there is a SITE-OUTAGE at my site, SCHEDULED FOR THIS EVENING, starting at around 5:30 PM EDT (i believe that translates to 21:30 GMT). So if you're trying it out, do not expect any joy (or any contact with meaningful contact with python.org) between 5:30 PM and midnight, EDT! Thanks, Ken Manheimer klm@cnri.reston.va.us 703 620-8990 x268 (orporation for National Research |nitiatives 1895 Preston White Drive, Suite 100 Reston, VA 22091 ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From fdrake@CNRI.Reston.Va.US Tue May 28 22:21:06 1996 From: fdrake@CNRI.Reston.Va.US (Fred L. Drake) Date: Tue, 28 May 1996 17:21:06 -0400 (EDT) Subject: [PYTHON META-SIG] Preparing for IPC-IV Message-ID: <199605282121.RAA21104@weyr.CNRI.Reston.Va.US> To SIG Coordinators: We are working to finish the program for the Python conference next week, and are attempting to define the schedules for the Tuesday morning and Thursday morning sessions more clearly. Since these times are dedicated to SIG activities, we would like input from each of the SIG coordinators. Tuesday morning, there is a 2 1/2 to 3 hour time period available for SIGs to make reports on work performed since the December '95 workshop, or a summary of goals for the group if there hasn't been any progress. Thursday morning, there is a 2 to 3 hour period available during which SIGs may hold working meetings to support activities which are either difficult to perform by email or otherwise benefit from in-person meetings. (This could include just chatting about where the SIG should be headed, possible projects, or something similar.) These working groups may meet in parallel, but some members may be interested in attending the working groups for other SIGs as well, so please prepare a (brief) agenda if possible. We are planning to allow 30 minutes to an hour for "meta" SIG discussions; what is needed from the PSA or python.org as support for the SIGs, etc. (Do we need more than 2 - 3 hours for all this?) I need the following information from each SIG coordinator for each SIG you coordinate: 1. How much time you need to present the work of the SIG on Tuesday morning, 2. Who will be available to make the presentation if you won't be attending the conference, 3. How long you would like your SIG to meet on Thursday, 4. Which SIGs you can't work in parallel with. (If you coordinate more than one SIG, you don't need to tell me.) Please send this information directly to me to be sure I get it as quickly as possible (fdrake@cnri.reston.va.us). We would like to have this information no later than Thursday morning so that it can make it into the conference program. Thank you for your time in responding to this late request. -Fred -- Fred L. Drake, Jr. Corporation for National Reseach Initiatives 1895 Preston White Drive Reston, VA 22091 ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From klm@CNRI.Reston.Va.US Fri May 31 22:38:07 1996 From: klm@CNRI.Reston.Va.US (Ken Manheimer) Date: Fri, 31 May 1996 17:38:07 -0400 Subject: [PYTHON META-SIG] Refinement of guidelines for sig-manager web dir maintenance Message-ID: <199605312138.RAA07633@glyph.CNRI.Reston.Va.US> For all you sig managers out there just aching to try out remote administration of your sig dir contents, i've added a bit to the instructions. A maintainer of one of www.python.org mirrors encountered some problems with rooted paths in sig document URLs - you have to be careful *not* to assume the location of the document, and use relative URLs instead. (For instance, to get to the NewHi.gif picture, the URL would be "../../pics/NewHi.gif", rather than "/pics/NewHi.gif".) I've included some explanation of this, as well as a more consolidated overview of the setup, in the coordinator's doc: As before, please try it out, and let me know how the scheme works, and how it doesn't work, for you. Ken ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From klm@CNRI.Reston.Va.US Fri May 17 18:42:49 1996 From: klm@CNRI.Reston.Va.US (Ken Manheimer) Date: Fri, 17 May 1996 13:42:49 -0400 Subject: [PYTHON META-SIG] SIG Coordinator control of python.org SIG dir contents Message-ID: <199605171742.NAA05779@glyph.CNRI.Reston.Va.US> For those of you on the meta-sig who are managing a PSA SIG: As threatened for a while now, i've set something up by which SIG coordinators can upload stuff to their own SIG Web directories on Python.org. I needed to do this in a secure way, without enabling login-style privileges - the setup is a uses special group privileges under anonymous ftp to python.org, restricted by the password each SIG coordinator has for their majordomo list. Rather than go into the details here, you can check the web document for full instructions: This lightly covers the majordomo list management, as well (and has a pointer to an htmlized version of the full majordomo man page). It is linked into a somewhat reworked SIGs index page: I expect a shaking-out period as we put this system into use. Please let me know about problems, questions, and suggestions on any part of the setup, and bear with me as we get it working smoothly. I'd also particularly be interested in any aspects of the system which you see as being unsafe - please do not be shy about relating any suspicions of susceptabilitties in the system. We are trying to provide more control to the SIG managers, around the world, without compromising the security of our gracious host site! One more item - it turns out that there is a SITE-OUTAGE at my site, SCHEDULED FOR THIS EVENING, starting at around 5:30 PM EDT (i believe that translates to 21:30 GMT). So if you're trying it out, do not expect any joy (or any contact with meaningful contact with python.org) between 5:30 PM and midnight, EDT! Thanks, Ken Manheimer klm@cnri.reston.va.us 703 620-8990 x268 (orporation for National Research |nitiatives 1895 Preston White Drive, Suite 100 Reston, VA 22091 ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From fdrake@CNRI.Reston.Va.US Tue May 28 22:21:06 1996 From: fdrake@CNRI.Reston.Va.US (Fred L. Drake) Date: Tue, 28 May 1996 17:21:06 -0400 (EDT) Subject: [PYTHON META-SIG] Preparing for IPC-IV Message-ID: <199605282121.RAA21104@weyr.CNRI.Reston.Va.US> To SIG Coordinators: We are working to finish the program for the Python conference next week, and are attempting to define the schedules for the Tuesday morning and Thursday morning sessions more clearly. Since these times are dedicated to SIG activities, we would like input from each of the SIG coordinators. Tuesday morning, there is a 2 1/2 to 3 hour time period available for SIGs to make reports on work performed since the December '95 workshop, or a summary of goals for the group if there hasn't been any progress. Thursday morning, there is a 2 to 3 hour period available during which SIGs may hold working meetings to support activities which are either difficult to perform by email or otherwise benefit from in-person meetings. (This could include just chatting about where the SIG should be headed, possible projects, or something similar.) These working groups may meet in parallel, but some members may be interested in attending the working groups for other SIGs as well, so please prepare a (brief) agenda if possible. We are planning to allow 30 minutes to an hour for "meta" SIG discussions; what is needed from the PSA or python.org as support for the SIGs, etc. (Do we need more than 2 - 3 hours for all this?) I need the following information from each SIG coordinator for each SIG you coordinate: 1. How much time you need to present the work of the SIG on Tuesday morning, 2. Who will be available to make the presentation if you won't be attending the conference, 3. How long you would like your SIG to meet on Thursday, 4. Which SIGs you can't work in parallel with. (If you coordinate more than one SIG, you don't need to tell me.) Please send this information directly to me to be sure I get it as quickly as possible (fdrake@cnri.reston.va.us). We would like to have this information no later than Thursday morning so that it can make it into the conference program. Thank you for your time in responding to this late request. -Fred -- Fred L. Drake, Jr. Corporation for National Reseach Initiatives 1895 Preston White Drive Reston, VA 22091 ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From klm@CNRI.Reston.Va.US Fri May 31 22:38:07 1996 From: klm@CNRI.Reston.Va.US (Ken Manheimer) Date: Fri, 31 May 1996 17:38:07 -0400 Subject: [PYTHON META-SIG] Refinement of guidelines for sig-manager web dir maintenance Message-ID: <199605312138.RAA07633@glyph.CNRI.Reston.Va.US> For all you sig managers out there just aching to try out remote administration of your sig dir contents, i've added a bit to the instructions. A maintainer of one of www.python.org mirrors encountered some problems with rooted paths in sig document URLs - you have to be careful *not* to assume the location of the document, and use relative URLs instead. (For instance, to get to the NewHi.gif picture, the URL would be "../../pics/NewHi.gif", rather than "/pics/NewHi.gif".) I've included some explanation of this, as well as a more consolidated overview of the setup, in the coordinator's doc: As before, please try it out, and let me know how the scheme works, and how it doesn't work, for you. Ken ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org =================