You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <ben...@id...> - 2004-05-22 12:54:15
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
From: Tom H. <sou...@to...> - 2003-07-08 03:06:48
|
All we need to do now is create a format for connections, cableing and support hardware (power supplies, UPS, etc...) -----Original Message----- From: wis...@li... [mailto:wis...@li...] On Behalf Of Tom Haynes Sent: Monday, July 07, 2003 9:58 PM To: wis...@li... Subject: RE: [Wisp-mss-general] Network description language I believe that storing the information in XML is the way to go. Since = SNMP MIB2 already has most of the information we will be needing categorized, = I think we should take the device informatin layout and naming scemes from MIB2. This way, gathering the needed information is fairly straight = forward. =20 -----Original Message----- From: wis...@li... [mailto:wis...@li...] On Behalf Of Tom Haynes Sent: Thursday, July 03, 2003 8:23 PM To: WISP-MSS General List Subject: [Wisp-mss-general] Network description language I think one of the first long-term projects that need to be worked on is = a standardized way to describe a network that a proram can read to = understand how to control, modify, manage and troubleshoot the devices and = connections. Is there any current standard? I think that XML would be a good base to start from. The basic concepts = of WISP-MSS is to allow the services to be run from any where, on any = platform. I would like to see a complete collection of services that can be run = from a central location or as standalone modeules on any network. I we can incorporate a distributed computing format, we can minimize the impact = on any one machine. |
From: Tom H. <sou...@to...> - 2003-07-08 03:02:52
|
I believe that storing the information in XML is the way to go. Since = SNMP MIB2 already has most of the information we will be needing categorized, = I think we should take the device informatin layout and naming scemes from MIB2. This way, gathering the needed information is fairly straight = forward. =20 -----Original Message----- From: wis...@li... [mailto:wis...@li...] On Behalf Of Tom Haynes Sent: Thursday, July 03, 2003 8:23 PM To: WISP-MSS General List Subject: [Wisp-mss-general] Network description language I think one of the first long-term projects that need to be worked on is = a standardized way to describe a network that a proram can read to = understand how to control, modify, manage and troubleshoot the devices and = connections. Is there any current standard? I think that XML would be a good base to start from. The basic concepts = of WISP-MSS is to allow the services to be run from any where, on any = platform. I would like to see a complete collection of services that can be run = from a central location or as standalone modeules on any network. I we can incorporate a distributed computing format, we can minimize the impact = on any one machine. |
From: Tom H. <em...@to...> - 2003-07-04 01:26:58
|
I think one of the first long-term projects that need to be worked on is = a standardized way to describe a network that a proram can read to = understand how to control, modify, manage and troubleshoot the devices and = connections. Is there any current standard? I think that XML would be a good base to start from. The basic concepts = of WISP-MSS is to allow the services to be run from any where, on any = platform. I would like to see a complete collection of services that can be run = from a central location or as standalone modeules on any network. I we can incorporate a distributed computing format, we can minimize the impact = on any one machine. |
From: Tom H. <em...@to...> - 2003-07-03 19:40:52
|
I recieved your email Lars. Configuration and Monitoring seem to be a top priorty for many people right now. There is also a need to a standardized way to describe a network. Some of the future features of the suite will require a easily parsable inventory and hookup information to help troubleshoot problems, advise on future planning, and other such things. When I get bask this evening I will add Config and Monitoring to the tasks. |
From: LarsG - email.e-nett.n. <la...@em...> - 2003-07-03 12:09:28
|
Test. -- LarsG |