From mdean at bbn.com Mon Jul 21 02:07:02 2014 From: mdean at bbn.com (Mike Dean) Date: Sun, 20 Jul 2014 20:07:02 -0400 Subject: [oor-dev] new oor-dev test Message-ID: <6B9C6776-5646-4362-811F-63E6EC915792@bbn.com> This is a test of the migrated oor-dev email list. See [1]. Mike [1] http://ontolog.cim3.net/forum/oor-forum/2014-07/msg00008.html -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4449 bytes Desc: not available URL: From mdean at bbn.com Mon Jul 21 14:04:58 2014 From: mdean at bbn.com (Mike Dean) Date: Mon, 21 Jul 2014 08:04:58 -0400 Subject: [oor-dev] new oor-dev test In-Reply-To: <6B9C6776-5646-4362-811F-63E6EC915792@bbn.com> References: <6B9C6776-5646-4362-811F-63E6EC915792@bbn.com> Message-ID: This is a second test to check the updated footer. Mike On Jul 20, 2014, at 8:07 PM, Mike Dean wrote: > This is a test of the migrated oor-dev email list. See [1]. > > Mike > > [1] http://ontolog.cim3.net/forum/oor-forum/2014-07/msg00008.html > > > _________________________________________________________________ > Message Archives: http://ovgu.de/forum/oor-dev/ > Config/Unsubscribe: http://ovgu.de/mailman/listinfo/oor-dev/ > Shared Files: http://ovgu.de/file/work/OOR/dev/ > Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4449 bytes Desc: not available URL: From peter.yim at cim3.com Mon Jul 21 18:37:40 2014 From: peter.yim at cim3.com (Peter Yim) Date: Mon, 21 Jul 2014 09:37:40 -0700 Subject: [oor-dev] new oor-dev test In-Reply-To: References: <6B9C6776-5646-4362-811F-63E6EC915792@bbn.com> Message-ID: Mike & All, Thanks, Mike and Stephan, Till & Oliver. 1. For now, the footer: // _________________________________________________________________ Message Archives: https://listserv.ovgu.de//pipermail/oor-dev Config/Unsubscribe: https://listserv.ovgu.de/mailman/listinfo/oor-dev Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository // looks good. 2. By the time the wiki content has migrated, the "wiki" url should become: // Wiki: http://ontolog-02.cim3.net/wiki/OpenOntologyRepository // ... and then, by the time the wiki is migrated to the new host, it should point to something else (depending on the host) again. 3. As discussed, with the confirmation with the host (this should be more straight forward, as the host(s) would be a member of the OOR team) maybe we could also add: // Community Homepage: http://www.oor.net ... [or even http://oor.net ... check out the difference how they're done now, but, of course, this can be tweaked too.] // 4. As for the replacement for, which is dependent on who will be hosting the shared-file repositories (webdav servers) >> Shared Files: http://ovgu.de/file/work/OOR/dev/ ... that needs to be identified, and added back in. To make things simple, I suggest whoever is hosting and maintaining the wiki, should consider hosting the webdav servers as well, ok? ... [ KenBaclawski, TillMossakowski, MichaelGruninger & MarkMusen: please consider and confirm.] 5. Just as a reminder for the future, when tweaking the footer, please make sure that is done (twice, both) for (a) the "Non-digest options" and (b) the "Digest options" ... (Stephan has done it perfectly this time!) Thanks & regards. =ppy -- On Mon, Jul 21, 2014 at 5:04 AM, Mike Dean wrote: > This is a second test to check the updated footer. > > Mike > > > On Jul 20, 2014, at 8:07 PM, Mike Dean wrote: > >> This is a test of the migrated oor-dev email list. See [1]. >> >> Mike >> >> [1] http://ontolog.cim3.net/forum/oor-forum/2014-07/msg00008.html >> >> _________________________________________________________________ >> Message Archives: http://ovgu.de/forum/oor-dev/ >> Config/Unsubscribe: http://ovgu.de/mailman/listinfo/oor-dev/ >> Shared Files: http://ovgu.de/file/work/OOR/dev/ >> Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository > > _________________________________________________________________ > Message Archives: https://listserv.ovgu.de//pipermail/oor-dev > Config/Unsubscribe: https://listserv.ovgu.de/mailman/listinfo/oor-dev > Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository > From peter.yim at cim3.com Mon Jul 21 19:35:31 2014 From: peter.yim at cim3.com (Peter Yim) Date: Mon, 21 Jul 2014 10:35:31 -0700 Subject: [oor-dev] migration status & archiving options In-Reply-To: References: <004301cfa282$4ea443b0$ebeccb10$@informatik.uni-leipzig.de> <011a01cfa29e$8018b8b0$804a2a10$@ovgu.de> <005101cfa4ae$efea2cc0$cfbe8640$@ovgu.de>

Message-ID: For the rocord ... ---------- Forwarded message ---------- From: Peter Yim Date: Mon, Jul 21, 2014 at 10:30 AM Subject: Re: migration status & archiving options To: Mike Dean Cc: Stephan Jacob , Till Mossakowski , "[cwe-imp]" , Oliver Kutz , Frank Loebe , OpenOntologyRepository-development Mike, Stephan & All, > [ppy / 2014.07.20-20:15PDT] ... I am away from my computer now. > ... Please take this as a quick acknowledgement, and allow me > to respond to you tomorrow morning. [ppy] apologies for the delayed response. Further to my response (just now, ref. https://listserv.ovgu.de/pipermail/oor-dev/2014-July/000002.html ) , may I suggest you conside the following process (which is probably how I would do it) ... 1. that server related tasks (like creating new lists; removing spam from the msg-database and msg-archives, tweaking anti-spam measures, etc.) to be handled by the ListAdmin (in this case, StephanJacob and OliverKutz, if my earlier suggestion is adopted.) 2. that subscriber maintenance, and list-content related tasks (nominally those which are accessible via the list-admin GUI after the list has been created) - e.g. https://listserv.ovgu.de/mailman/admin/oor-dev - to be handled by the ListAdmin (in this case, TillMossakowski and MikeDean, if my earlier suggestion is adopted.) 2.1 In particular, relevant to this conversation, that the tweaking of the "footer" would fall under the auspices of the ListAdmins too. 2.2 That would include adding/removing subscribers, helping and answering questions subscribers may have, helping them add aliases (which I used to implement by adding their aliases to the "accept_these_nonsubscribers" in the "Sender filters" under "Privacy options..." .) 3. Since I had been running the OOR-list myself, I actually did not have a separate password for the oor lists before (I was only using the master password myself then.) Now that the [oor-dev], [oor-forum] and [oor-users] lists have migrated to ovgu.de, StephanJacob or OliverKutz (assuming they are the SysAdmins) will need to create a new set of (List)Admin password(s) (I'd probably use the same pw for the oor set) and pass that to the new ListAdmins. This is done at the admin-GUI, e.g. https://listserv.ovgu.de/mailman/admin/oor-dev/passwords ... (I assume the case for the other IAOA and OntoIOp lists, the migration had moved the ListAdmin passwords over as well, and we do not have this issue.) If I missed something here, feel free to contact me. Thanks & regards. =ppy p.s. Btw, Stephan, ... just out of curiosity, how frequently are posts to the ovgu.de lists being archived (we used to do it once every 15 minutes on ontolog.cim3.net). -- On Mon, Jul 21, 2014 at 5:46 AM, Mike Dean wrote: > You may also want to remove the extraneous / before pipermail in the Archives links. > > Thanks! > > Mike > On Jul 21, 2014, at 8:17 AM, Mike Dean wrote: > >> Stephan, >> >> Thanks for your updates. All 3 lists now look good. >> >> A minor nit: I see that oor-users and oor-forum have Subscribe links in the footer, while oor-dev does not. I assume they all should. >> >> Mike >> On Jul 21, 2014, at 2:42 AM, "Stephan Jacob" wrote: >> >>> Hello Mike, >>> >>> I've updated the configuration. >>> >>> Admin's of the 3 OOR lists are now till.mossakowski at ovgu.de and >>> mdean at bbn.com >>> >>> I've also updated the links in the footer. >>> >>> Regards >>> >>> Stephan >>> >>> Stephan Jacob >>> >>> Otto-von-Guericke Universit?t Magdeburg >>> Universit?tsrechenzentrum (URZ) >>> >>> Universit?tsplatz 2 >>> Geb?ude 26 - 035 >>> >>> 39106 Magdeburg >>> >>> Tel.: 0391-67-58572 >>> Fax: 0391-67-11134 >>> -----Urspr?ngliche Nachricht----- >>> Von: Mike Dean [mailto:mdean at bbn.com] >>> Gesendet: Montag, 21. Juli 2014 02:22 >>> An: Stephan Jacob >>> Cc: 'Peter Yim'; 'Till Mossakowski'; '[cwe-imp]'; 'Oliver Kutz'; 'Frank >>> Loebe' >>> Betreff: Re: migration status & archiving options >>> >>> Stephan, >>> >>> Thanks for all your help with migrating the OOR email lists.. >>> >>> The archive and config/unsubscribe links in the footer of a test message I >>> just sent to oor-dev (far below) are inconsistent with those in your message >>> below (and unresolvable). Can you update the mailman configuration? >>> >>> Also, [1] and its counterparts still list Peter, Leo, and me as >>> administrators. Peter had suggested that it just be Till and me. >>> >>> Mike >>> >>> [1] https://listserv.ovgu.de/mailman/listinfo/oor-dev >>> >>> >>> On Jul 18, 2014, at 11:39 AM, "Stephan Jacob" wrote: >>> >>>> Hello everyone, >>>> >>>> I've just migrated the 3 OOR Lists. Again old archives are not available >>> at the moment here at Uni Magdeburg. But archiving is turned on in every >>> list. So new Messages are archived within mailman on the server. At the >>> moment the archive of each list is public accessible. Please check if this >>> fits to your intention. >>>> >>>> @ admin of all lists we will migrate: By fixing the URL of the list, the >>> footer will be adjusted with wrong links. This happens, because in the >>> footer variables like host_name are used to build the links. Please have a >>> look in the web UI at Non-diggest options and set the footer in correct >>> manner. You also could tell me the correct links and I can set it up. >>>> >>>> @ admin of all lists we will migrate: I 'll remove the two addresses >>> admin at cim3.com & mharc-ontolog at ontolog.cim3.net from every list, like Peter >>> pointed out. >>>> >>>> The OOR lists are now available under the addresses >>>> oor-dev at ovgu.de >>>> oor-forum at ovgu.de >>>> oor-users at ovgu.de >>>> >>>> The web UI's are available here: >>>> https://listserv.ovgu.de/mailman/admin/oor-dev >>>> https://listserv.ovgu.de/mailman/admin/oor-forum >>>> https://listserv.ovgu.de/mailman/admin/oor-users >>>> >>>> I send a help request to each list and got a correct answer. So you should >>> try a posting over the list if you want. The posted massages are archived >>> here: >>>> https://listserv.ovgu.de//pipermail/oor-dev/ >>>> https://listserv.ovgu.de//pipermail/oor-forum >>>> https://listserv.ovgu.de//pipermail/oor-users >>>> >>>> >>>> >>>> >>>> >>>> >>>> Stephan Jacob >>>> >>>> Otto-von-Guericke Universit?t Magdeburg >>>> Universit?tsrechenzentrum (URZ) >>>> >>>> Universit?tsplatz 2 >>>> Geb?ude 26 - 035 >>>> >>>> 39106 Magdeburg >>>> >>>> Tel.: 0391-67-58572 >>>> Fax: 0391-67-11134 >>>> -----Urspr?ngliche Nachricht----- >>>> Von: peter.yim at gmail.com [mailto:peter.yim at gmail.com] Im Auftrag von Peter >>> Yim >>>> Gesendet: Freitag, 18. Juli 2014 15:39 >>>> An: Frank Loebe; Stephan Jacob >>>> Cc: Till Mossakowski; [cwe-imp]; Oliver Kutz; Mike Dean >>>> Betreff: Re: migration status & archiving options >>>> >>>> Hello All, >>>> >>>> >>>> >>>> ... This will have to be brief as I have a meeting (IAOA Election >>>> Committee) to attend in less than 30 minutes. >>>> >>>> >>>> 1. Congratulations to Stephan for the successful migration of the >>> ontoiop-forum list. ... This is IMPRESSIVE! >>>> >>>> 2. I agree with all of Frank's dispositions, especially the part about >>>> (a) minimizing the system downtime, and (b) going with the native >>> mailman/pipermail archival for now >>>> >>>> 2.1 ... I am also in favor of (c) doing whatever Magdeburg/Stephan is most >>> familiar/comfortable with and try *not* to do any customization (otherwise, >>> things will get difficult to maintain, unless one is willing to put in the >>> resources.) >>>> >>>> 3. One other thought ... if search is your only issue, for public lists >>> (with open archives), one can always use google as your search engine. (I am >>> not familiar enough with Nabble to tell if or how well it works with >>> "private" archives.) >>>> >>>> 3.1 I can see that the admin at cim3.com & mharc-ontolog at ontolog.cim3.net are >>> automatically migrated over from the config files. Please make sure you >>> (whoever the ListAdmin is) remove those two subscribers from the list >>> management GUI first. >>>> >>>> 3.2 I noticed a couple of irregularities in the message footer (where you >>> point people to the listinfo page, etc. ... ListAdmin: please review and >>> clean up. >>>> >>>> 4. I have re-packaged a for the OntoIOp list >>> migration - complete with: archives lists mbox subscribers - this is more >>> for completeness and archival reasons. You can find it now, >>>> under: http://ontolog.cim3.net/file/community/project/OntoIOp/ as: >>>> cim3-ontoiop-lists.tar.gz >>>> >>>> 5. I have also finished rolling-up for the OOR list >>> migration - for oor-dev oor-forum oor-users ; complete with: >>>> archives lists mbox subscribers. You can find it now, under: >>>> http://ontolog.cim3.net/file/community/project/OOR/ as: >>>> cim3-oor-lists.tar.gz >>>> >>>> 6. (while we are probably already good with admins for OntoIOp and >>>> IAOA) for OOR, I suggest we officially designate the following admins: >>>> - SysAdmin: StephanJacob & OliverKutz >>>> - ListAdmin: TillMossakowski & MikeDean >>>> >>>> 7. (Like Frank, but maybe for a different reason) I am not so sure about >>> "address forwarding" any more. Thanks to Stephan for pointing out about the >>> need to disable "explicit addressing" before that would work. I think >>> disabling "explicit addressing" is a bad idea ... this feature is there to >>> fight spammers (a lot of spammers use bcc to spam >>>> people) and dealing with spam is the single most time consuming item in >>> maintaining these lists (esp. open lists) if one is conscientious and try to >>> keep the archives "clean" all the time. >>>> >>>> 8. I am now working on getting the IAOA list migration package together, >>> will let everyone know as soon as I am done. >>>> >>>> >>>> Thanks & regards. =ppy >>>> -- >>>> On Fri, Jul 18, 2014 at 5:17 AM, Frank Loebe >>> wrote: >>>>> Hello Stephan, >>>>> >>>>>> 1) [...] >>>>>> @Frank: Are you one of the admins of IAOA-Lists? >>>>> >>>>> Yes, I'm an admin for all IAOA lists. >>>>> >>>>> >>>>>> 2) Archiving: I can activate archiving in the configuration. If I do >>>>>> so, the mail should be archived in mailman (which uses pipermail). >>>>>> [...] I'll additionally switch on private archiving in mailman, so >>>>>> the mails should also be archived there. >>>>> >>>>> Ok, thanks, please do so. >>>>> >>>>> Just for my information: is this fully controlled by the setting on page >>> [Archiving Options] in the Mailman Web UI? I.e., if "Archive messages?" is >>> set to "Yes", messages should be archived "automatically" via pipermail? Or >>> is there anything else required by you, via access at the operating systems >>> level? >>>>> >>>>> Please also note the remarks/connection to 3) below. >>>>> >>>>>> As I >>>>>> understand mharc documentation, in mharc archiving works through an >>>>>> special mail-address which is member of the lists. It seems to me, as >>>>>> if we don't remove this special mailaddress from the lists, the mails >>>>>> are archived within the old archive infrastructure. So they can be >>>>>> migrated to us after building up a suitable archive infrastructure here >>> in Magdeburg. >>>>>> Please correct me if I'm wrong... I'll additionally switch on private >>>>>> archiving in mailman, so the mails should also be archived there. >>>>> >>>>> @Peter: >>>>> If I understood this correctly: >>>>> >>>>>>> [PPY] >>>>>>> Yes, the ontolog.cim3.net archived mailing list system will continue >>>>>>> to serve the (more active) ONTOLOG mailing list (maybe even for >>>>>>> OntologySummit; but not the ones for other related communities which >>>>>>> Ontolog used to host - like IAOA, OOR, UoM, BSP, etc.) >>>>> >>>>> the mail server ontolog.cim3.net itself won't work for non-Ontolog >>> mailing lists, e.g. for message distribution. Insofar I could well image >>> that also posts to the special mharc addresses on that server don't work any >>> more. Is that right, Peter? >>>>> >>>>> >>>>>> 3) Archiving (in mailman) of the ontoiop-forum (and generally all >>>>>> lists) here in Magdeburg should work for new mails. >>>>> >>>>> That's very good, thanks a lot. >>>>> >>>>>> When I wrote "archiving is >>>>>> not working/available" I mean, the old archives are not available >>>>>> here in Magdeburg and archiving with mharc ist not working. >>>>> >>>>> Ok, I see - thanks for the clarification. >>>>> >>>>> >>>>>> @all: Maybe we should change the configuration of ontoiop-forum from >>>>>> public to private. In the configuration file of Peter the archiving >>>>>> mode seem to be public. I don't know if that is what it is expected. >>>>> >>>>> I cannot speak for ontoiop. For the IAOA mailing lists, the settings need >>> to be adapted individually. I could do that, if it works via the Mailman Web >>> UI, page [Archiving Options]. The standard setting at ontolog.cim3.net seems >>> to be: >>>>> (a) Archive messages?: Yes >>>>> (b) Is archive file source for public or private archival?: public >>>>> (c) How often should a new archive be started: Monthly >>>>> >>>>> I'm fine with (a) and (c) for all lists, and would have to modify (b) >>> individually. Alternatively, I could let Stephan know which lists should be >>> privately or publically archived. >>>>> >>>>> >>>>> Just to mention, recently I thought it would be most useful to have a >>> system with a basic archiving mode (either public or private), but with the >>> option to set individual messages in the archive to be either publicly or >>> privately accessible. (E.g., public announcements distributed via >>> [iaoa-member] need not be restricted to the membership (i.e., to private >>> archiving), more of "internal" discussion should be.) It would be >>> interesting to know whether anyone is aware of a mailhandling/archiving >>> system with such features. >>>>> >>>>> >>>>> Thanks for your work & best regards, >>>>> Frank >>>>>> -----Original Message----- >>>>>> From: Stephan Jacob [mailto:stephan.jacob at ovgu.de] >>>>>> Sent: Friday, July 18, 2014 12:20 PM >>>>>> To: 'Frank Loebe' >>>>>> Cc: 'Till Mossakowski'; '[cwe-imp]'; 'Peter Yim'; 'Oliver Kutz' >>>>>> Subject: AW: migration status & archiving options == RE: progress on >>>>>> mailing lists >>>>>> >>>>>> Hi, >>>>>> >>>>>> some remarks to Frank's mail: >>>>>> >>>>>> 1) Transferring the mailinglists without archives should work and I >>>>>> would prefer that way. Maybe you can use the old mharc infrastructure >>>>>> for a while so we can win some time to set up an equivalent >>>>>> infrastructure. I'll follow the order Frank described below. >>>>>> @Frank: Are you one of the admins of IAOA-Lists? If yes, I'll send >>>>>> you a short message after migrating each list, so you can try using it. >>>>>> >>>>>> 2) Archiving: I can activate archiving in the configuration. If I do >>>>>> so, the mail should be archived in mailman (which uses pipermail). As >>>>>> I understand mharc documentation, in mharc archiving works through an >>>>>> special mail-address which is member of the lists. It seems to me, as >>>>>> if we don't remove this special mailaddress from the lists, the mails >>>>>> are archived within the old archive infrastructure. So they can be >>>>>> migrated to us after building up a suitable archive infrastructure here >>> in Magdeburg. >>>>>> Please correct me if I'm wrong... I'll additionally switch on private >>>>>> archiving in mailman, so the mails should also be archived there. >>>>>> >>>>>> 3) Archiving (in mailman) of the ontoiop-forum (and generally all >>>>>> lists) here in Magdeburg should work for new mails. When I wrote >>>>>> "archiving is not working/available" I mean, the old archives are not >>>>>> available here in Magdeburg and archiving with mharc ist not working. >>>>>> @all: Maybe we should change the configuration of ontoiop-forum from >>>>>> public to private. In the configuration file of Peter the archiving >>>>>> mode seem to be public. I don't know if that is what it is expected. >>>>>> >>>>>> >>>>>> >>>>>> Stephan Jacob >>>>>> >>>>>> Otto-von-Guericke Universit?t Magdeburg Universit?tsrechenzentrum >>>>>> (URZ) >>>>>> >>>>>> Universit?tsplatz 2 >>>>>> Geb?ude 26 - 035 >>>>>> >>>>>> 39106 Magdeburg >>>>>> >>>>>> Tel.: 0391-67-58572 >>>>>> Fax: 0391-67-11134 >>>>>> -----Urspr?ngliche Nachricht----- >>>>>> Von: Frank Loebe [mailto:frank.loebe at informatik.uni-leipzig.de] >>>>>> Gesendet: Freitag, 18. Juli 2014 11:09 >>>>>> An: 'Stephan Jacob' >>>>>> Cc: 'Till Mossakowski'; '[cwe-imp]'; 'Peter Yim'; Oliver Kutz >>>>>> Betreff: RE: migration status & archiving options == RE: progress on >>>>>> mailing lists >>>>>> >>>>>> Hi, >>>>>> >>>>>> first of all, many thanks to everyone for keeping working on this >>>>>> transfer issue, and to Stephan Jacob and Peter in particular. >>>>>> >>>>>> Let me summarize the main points that follow below: >>>>>> >>>>>> 1.) I suggest an order in which to re-establish the IAOA mailing >>>>>> lists, see the table below. >>>>>> >>>>>> 2.) I suggest to get the "standard way of archiving" (pipermail?) to >>>>>> work at Magdeburg with the new lists as a basic step that allows us >>>>>> to complete the migration with short downtime soon, and deal with >>>>>> more advanced archiving options (mharc, Nabble, etc.) later. >>>>>> >>>>>> 3.) I propose to skip a transfer of the old archives for now and rely >>>>>> on their availability through CIM3.net. >>>>>> >>>>>> >>>>>> >>>>>> Now with details: >>>>>> >>>>>>> [SJ] >>>>>>> It took approx. 20 minutes to import the list (I had to adjust >>>>>>> various file-permissions after coping the data) >>>>>> >>>>>> Given that the import takes a while, I'd like to propose an order for >>>>>> the IAOA mailing lists, assuming these are set up one-by-one instead >>>>>> of all- at-once. If that happens one after the other, perhaps we >>>>>> could follow this order, please: >>>>>> >>>>>> Nr. Description >>>>>> --- ------------------------ ----------------------------------------- >>>>>> 01 iaoa-infrastructure IAOA Infrastructure Committee >>>>>> 02 iaoa-council IAOA Executive Council >>>>>> 03 iaoa-swao IAOA Semantic Web - Applied Ontology SIG >>>>>> 04 iaoa-member IAOA Members >>>>>> 05 iaoa-general IAOA followers >>>>>> 06 iaoa-advisor IAOA Advisory Board >>>>>> 07 iaoa-admin IAOA Administrators >>>>>> 08 iaoa-bylaws IAOA ByLaws >>>>>> 09 iaoa-conceptual-modeling IAOA Conceptual Modeling SIG >>>>>> 10 iaoa-design-semantics IAOA Design Semantics SIG >>>>>> 11 iaoa-education IAOA Education Committee >>>>>> 12 iaoa-election IAOA Election Committee >>>>>> 13 iaoa-geosemantics IAOA GeoSemantics SIG >>>>>> 14 iaoa-international IAOA International Promotion Committee >>>>>> 15 iaoa-membership IAOA Membership Committee >>>>>> 16 iaoa-publicity IAOA Publicity >>>>>> 17 iaoa-repository IAOA Ontology Registry and Repository >>>>>> 18 iaoa-standards IAOA Standardization Coordination >>>>>> >>>>>> The order is based on the importance, frequency of use, and >>>>>> appropriateness for testing. Especially, 01 and 02 are suitable >>>>>> testing candidates, 03 possibly, as well. The two lists with many >>>>>> more subscribers than all others are 04 and 05. When migrating these, >>>>>> we should be rather sure that the procedure works as intended and >>>>>> which settings require modification before announcing the lists as >>>>>> working. I would prefer to avoid test messages to 04 and 05, but >>>>>> rather send the announcement of successful transfer to them as first >>>>>> message on the newly established lists. >>>>>> >>>>>>> [SJ] >>>>>>> A help request to ontoiop-forum-request at ovgu.de worked well, so I >>>>>>> think normal postings should also work. Maybe someone could test it!? >>>>>> >>>>>> I'm neither list member nor list admin there and would leave this to >>>>>> someone else. >>>>>> >>>>>>> [SJ] >>>>>>> But archvies are not working/available at the Moment. I had a look >>>>>>> to the configuration and found out, that at Archiving Options >>>>>>> "Archive >>>>>> messages" >>>>>>> is on Yes and Archive Type is public. Is this configuration >>>>>>> correct, is it needed for mharc? Maybe one of the list-admins can >>>>>>> have a short look on the configuration. >>>>>> >>>>>> First, as just stated, I cannot check matters via the admin UI of the >>>>>> new list [1], insofar I would wait for a first IAOA list before I >>>>>> could start going through the web UI for further options. >>>>>> >>>>>> However, it seems strange to me why the "archives are not >>>>>> working/available", but the settings are as stated ("'Archive >>>>>> messages' is on Yes and Archive Type is public"). I would have >>>>>> expected that those settings "automatically" lead to archiving "as is >>>>>> usual" for the OVGU mailing lists. >>>>>> >>>>>> @Stephan Jacob: >>>>>> Independently of mharc, is it unclear to you, as well, why no >>>>>> archives are produced? Do you share the expectation that it should work >>> already? >>>>>> >>>>>> [1] https://listserv.ovgu.de/mailman/admin/ontoiop-forum >>>>>> >>>>>> >>>>>>> [SJ] >>>>>>> There are also a lot of administrator task tending. >>>>>> >>>>>> Just to be sure, this refers to administrator tasks on the mailing >>>>>> list server via its operation system, correct? Instead of mail admin >>>>>> tasks to be performed via the web UI. >>>>>> >>>>>> >>>>>>> [SJ] >>>>>>> The question is what we do with archives? Peter, do you have a >>>>>>> documentation how you set up your mharc environment? I tried to >>>>>>> install mharc on a testserver yesterday night at home, but >>>>>>> following the official documentation on the mharc homepage failed. >>>>>>> Especially the installation of a prerequisite package Namazu with cpan >>> failed. >>>>>>> (I used a centos 6.5 system. This is our server os here) >>>>>> >>>>>> Technically, I'm the wrong person to reply to this. Just to mention >>>>>> that I noted Peter's most recent proposal (cf. message fragment at >>>>>> the bottom) _not_ to go with mharc+mhpurple, but possibly to refer to >>>>>> a Nabble interface to the "regular mailman archive" (if I understand >>>>>> matters correctly, which I'm not sure about): >>>>>> >>>>>>>> [PPY] >>>>>>>> further to Stephan's response the the magdeburg list archives are >>>>>>>> not searchable at this point (and that I do not recommend setting >>>>>>>> up similar mharc+mhpurple archives after the migration,) one >>>>>>>> alternative/reference to look into is what TaraAthan had done for >>>>>>>> the CL (Common Logic) list which ChrisMenzel at TexasA&M has been >>>>>>>> hosting all along - see: >>>>>>>> http://philebus.tamu.edu/pipermail/cl/2012-October/002691.html ... >>>>>>>> >>>>>>>> this would probably be a good approach for, at least, the future, >>>>>>>> open, mailing list content (to better support search and >>>>>>>> web-access.) >>>>>> >>>>>> The main content at the mentioned link is: >>>>>> >>>>>>>>> On Oct 6, 2012, at 12:08 PM, Tara Athan >>>>>> wrote: >>>>>>>>> I have arranged for a Nabble forum >>>>>>>>> (http://common-logic.1085828.n5.nabble.com/) for the Common Logic >>>>>>>>> mailing list. This is an alternate interface to this mailing list >>>>>>>>> (as opposed to a separate mailing list.) As a result, the Common >>>>>>>>> Logic mailing list archives, back to 2003, are now searchable - a >>>>>>>>> Nabble login is not necessary to do such searches. >>>>>> >>>>>> I do not yet have any experience with that myself, a first quick >>>>>> search appeared ok to me. However, if I understand Peter correctly, >>>>>> this is limited to public archives only (and thus wouldn't work for >>>>>> e.g. (at least >>>>>> my) main use case of searching the [iaoa-council] mailing list). >>>>>> >>>>>> >>>>>> Anyway, for completing the migration at a basic level, I would prefer >>>>>> to have the mailing lists set up rather sooner than later such that >>>>>> they work for distributing messages and with the archiving that is >>>>>> available "easily"(?), even if the archives are not searchable in that >>> setup. >>>>>> (Again, I appreciate all efforts taken so far, so "rather sooner than >>>>>> later" just means that I'd prefer to keep the downtime of the lists >>>>>> short and see whether we can take care of more advanced archiving >>>>>> later. But basic archiving should be switched on (public for public >>>>>> lists, restricted to list members for member-only lists), please, and >>>>>> it should be clear/tested that it works as intended.) >>>>>> >>>>>> Regarding the old archives, I'd live with having them available >>>>>> through CIM3.net, thanks to Peter. (cf. the message fragment at the >>>>>> bottom) >>>>>> >>>>>> >>>>>> NB on my availability: >>>>>> I need to restrict my time spent on these matters, I'm sorry, due to >>>>>> other obligations. I will be completely offline between Saturday >>>>>> afternoon, Jul 19, (CEST) and Monday morning, Jul 21 (CEST). >>>>>> >>>>>> >>>>>> Many thanks and best regards, >>>>>> Frank >>>>>> >>>>>> >>>>>> [1] https://listserv.ovgu.de/mailman/admin/ontoiop-forum >>>>>>> -----Original Message----- >>>>>>> From: Stephan Jacob [mailto:stephan.jacob at ovgu.de] >>>>>>> Sent: Friday, July 18, 2014 8:04 AM >>>>>>> To: 'Peter Yim' >>>>>>> Cc: 'Till Mossakowski'; 'Frank Loebe'; '[cwe-imp]' >>>>>>> Subject: AW: progress on mailing lists == RE: (urgent, please) >>>>>>> hosting mailing lists for IAOA (& wiki?) >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> the migration of the ontoiop-forum yesterday was successful. So the >>>>>>> list is available at the address ontoiop-forum at ovgu.de. >>>>>>> A help request to ontoiop-forum-request at ovgu.de worked well, so I >>>>>>> think normal postings should also work. Maybe someone could test it!? >>>>>>> >>>>>>> You can have look to the configuration here: >>>>>>> https://listserv.ovgu.de/mailman/admin/ontoiop-forum >>>>>>> The admin-password should be the same as before migration. >>>>>>> >>>>>>> But archvies are not working/available at the Moment. I had a look >>>>>>> to the configuration and found out, that at Archiving Options >>>>>>> "Archive >>>>>> messages" >>>>>>> is on Yes and Archive Type is public. Is this configuration >>>>>>> correct, is it needed for mharc? Maybe one of the list-admins can >>>>>>> have a short look on the configuration. >>>>>>> >>>>>>> There are also a lot of administrator task tending. >>>>>>> >>>>>>> It seems that migrating the list without archives is working (maybe >>>>>>> you could give a feedback after testing the list, if everything >>>>>>> works >>>>>> fine). >>>>>>> It took approx. 20 minutes to import the list (I had to adjust >>>>>>> various file-permissions after coping the data) >>>>>>> >>>>>>> The question is what we do with archives? Peter, do you have a >>>>>>> documentation how you set up your mharc environment? I tried to >>>>>>> install mharc on a testserver yesterday night at home, but >>>>>>> following the official documentation on the mharc homepage failed. >>>>>>> Especially the installation of a prerequisite package Namazu with cpan >>> failed. >>>>>>> (I used a centos 6.5 system. This is our server os here) >>>>>>> >>>>>>> >>>>>>> >>>>>>> Stephan Jacob >>>>>>> -----Original Message----- >>>>>>> From: peter.yim at gmail.com [mailto:peter.yim at gmail.com] On Behalf Of >>>>>>> Peter Yim >>>>>>> Sent: Thursday, July 17, 2014 8:18 PM >>>>>>> To: Frank Loebe >>>>>>> Cc: Stephan Jacob; Till Mossakowski; Oliver Kutz; IAOA >>>>>>> Infrastructure; cwe-imp >>>>>>> Subject: Re: progress on mailing lists >>>>>>> >>>>>>> Responding inline below ... Tx. =ppy >>>>>>> -- >>>>>>> On Thu, Jul 17, 2014 at 5:31 AM, Frank Loebe >>>>>>> wrote: >>>>>>>> Dear Peter and Stephan, >>>>>>>> [...] >>>>>>>>>>> [PPY] >>>>>>>>>>> 3.3.1 we do not use mailman to produce our message archives >>>>>>>>>>> (we use >>>>>>>>>>> mharc+mhpurple). Therefore, for those lists which you plan to >>>>>>>>>>> mharc+rebuild >>>>>>>>>>> an archive, I will provide you with the mbox contents ... >>>>>>>>>>> >>>>>>>>>>> in: mig/mbox/{listname} >>>>>>>> >>>>>>>> [...] >>>>>>>> My conditioned response variants on 3.3 are thus: >>>>>>>> >>>>>>>> 3.3.FL-A: If archives at Magdeburg are searchable and transfer is >>>>>>> feasible, please transfer the archives to Magdeburg. They could >>>>>>> then be removed from Peter's server (maybe after some time, e.g. by >>>>>>> the end of 2014). >>>>>>>> >>>>>>>> 3.3.FL-B: If archives at Magdeburg are not searchable and >>>>>>>> transfer is >>>>>>> feasible, please transfer the archives to Magdeburg, but also keep >>>>>>> the version of the archives on Peter's server. >>>>>>>> >>>>>>>> 3.3.FL-C: If transfer is not feasible, please keep the archives >>>>>>>> on >>>>>>> Peter's server in the future. >>>>>>> >>>>>>> [ppy] further to Stephan's response the the magdeburg list archives >>>>>>> are not searchable at this point (and that I do not recommend >>>>>>> setting up similar mharc+mhpurple archives after the migration,) >>>>>>> one alternative/reference to look into is what TaraAthan had done >>>>>>> for the CL (Common Logic) list which ChrisMenzel at TexasA&M has >>>>>>> been hosting all along - see: >>>>>>> http://philebus.tamu.edu/pipermail/cl/2012-October/002691.html ... >>>>>>> this would probably be a good approach for, at least, the future, >>>>>>> open, mailing list content (to better support search and >>>>>>> web-access.) >>>>>>> >>>>>>> ... As noted before: either way, all historic archives of the work >>>>>>> on the ONTOLOG-CWE (which include the message (html) archives, >>>>>>> Ontolog-website, OntologWiki and webdav server content) will >>>>>>> continue to be hosted on CIM3.NET (indefinitely,) as part of the >>>>>>> preservation of the body-of- knowledge accumulated by the broader >>>>>>> Ontology community on the CWE (collaborative work environment) over >>>>>>> the past 12+ >>>>>> years. >>> Begin forwarded message: >>> >>>> From: Mike Dean >>>> Subject: [oor-dev] new oor-dev test >>>> Date: July 20, 2014 8:07:02 PM EDT >>>> To: oor-dev at ovgu.de >>>> Reply-To: OpenOntologyRepository-development >>>> >>>> This is a test of the migrated oor-dev email list. See [1]. >>>> >>>> Mike >>>> >>>> [1] http://ontolog.cim3.net/forum/oor-forum/2014-07/msg00008.html >>>> >>>> >>>> _________________________________________________________________ >>>> Message Archives: http://ovgu.de/forum/oor-dev/ >>>> Config/Unsubscribe: http://ovgu.de/mailman/listinfo/oor-dev/ >>>> Shared Files: http://ovgu.de/file/work/OOR/dev/ >>>> Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository From mossakow at iws.cs.uni-magdeburg.de Mon Jul 21 21:12:51 2014 From: mossakow at iws.cs.uni-magdeburg.de (Till Mossakowski) Date: Mon, 21 Jul 2014 21:12:51 +0200 Subject: [oor-dev] new oor-dev test In-Reply-To: References: <6B9C6776-5646-4362-811F-63E6EC915792@bbn.com> Message-ID: <53CD6633.3010907@iws.cs.uni-magdeburg.de> Dear Peter, yes, if we agree to host the wiki in Magdeburg, we can also host the webdav. Best, Till Am 21.07.2014 18:37, schrieb Peter Yim: > Mike & All, > > > Thanks, Mike and Stephan, Till & Oliver. > > 1. For now, the footer: > // > _________________________________________________________________ > Message Archives: https://listserv.ovgu.de//pipermail/oor-dev > Config/Unsubscribe: https://listserv.ovgu.de/mailman/listinfo/oor-dev > Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository > // > looks good. > > 2. By the time the wiki content has migrated, the "wiki" url should become: > // > Wiki: http://ontolog-02.cim3.net/wiki/OpenOntologyRepository > // > > ... and then, by the time the wiki is migrated to the new host, it > should point to something else (depending on the host) again. > > 3. As discussed, with the confirmation with the host (this should be > more straight forward, as the host(s) would be a member of the OOR > team) maybe we could also add: > // > Community Homepage: http://www.oor.net ... [or even http://oor.net ... > check out the difference how they're done now, but, of course, this > can be tweaked too.] > // > > 4. As for the replacement for, which is dependent on who will be > hosting the shared-file repositories (webdav servers) >>> Shared Files: http://ovgu.de/file/work/OOR/dev/ > ... that needs to be identified, and added back in. > To make things simple, I suggest whoever is hosting and maintaining > the wiki, should consider hosting the webdav servers as well, ok? ... > [ KenBaclawski, TillMossakowski, MichaelGruninger & MarkMusen: please > consider and confirm.] > > 5. Just as a reminder for the future, when tweaking the footer, please > make sure that is done (twice, both) for (a) the "Non-digest options" > and (b) the "Digest options" ... (Stephan has done it perfectly this > time!) > > > Thanks & regards. =ppy From peter.yim at cim3.com Mon Jul 21 21:32:46 2014 From: peter.yim at cim3.com (Peter Yim) Date: Mon, 21 Jul 2014 12:32:46 -0700 Subject: [oor-dev] new oor-dev test In-Reply-To: <53CD6633.3010907@iws.cs.uni-magdeburg.de> References: <6B9C6776-5646-4362-811F-63E6EC915792@bbn.com> <53CD6633.3010907@iws.cs.uni-magdeburg.de> Message-ID: Great! Thank you, Till. ... the latter should come from the OOR team! :-) Regards. =ppy -- On Mon, Jul 21, 2014 at 12:12 PM, Till Mossakowski wrote: > Dear Peter, > > yes, if we agree to host the wiki in Magdeburg, we can also host the webdav. > > Best, Till > > Am 21.07.2014 18:37, schrieb Peter Yim: >> Mike & All, >> >> >> Thanks, Mike and Stephan, Till & Oliver. >> >> 1. For now, the footer: >> // >> _________________________________________________________________ >> Message Archives: https://listserv.ovgu.de//pipermail/oor-dev >> Config/Unsubscribe: https://listserv.ovgu.de/mailman/listinfo/oor-dev >> Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository >> // >> looks good. >> >> 2. By the time the wiki content has migrated, the "wiki" url should become: >> // >> Wiki: http://ontolog-02.cim3.net/wiki/OpenOntologyRepository >> // >> >> ... and then, by the time the wiki is migrated to the new host, it >> should point to something else (depending on the host) again. >> >> 3. As discussed, with the confirmation with the host (this should be >> more straight forward, as the host(s) would be a member of the OOR >> team) maybe we could also add: >> // >> Community Homepage: http://www.oor.net ... [or even http://oor.net ... >> check out the difference how they're done now, but, of course, this >> can be tweaked too.] >> // >> >> 4. As for the replacement for, which is dependent on who will be >> hosting the shared-file repositories (webdav servers) >>>> Shared Files: http://ovgu.de/file/work/OOR/dev/ >> ... that needs to be identified, and added back in. >> To make things simple, I suggest whoever is hosting and maintaining >> the wiki, should consider hosting the webdav servers as well, ok? ... >> [ KenBaclawski, TillMossakowski, MichaelGruninger & MarkMusen: please >> consider and confirm.] >> >> 5. Just as a reminder for the future, when tweaking the footer, please >> make sure that is done (twice, both) for (a) the "Non-digest options" >> and (b) the "Digest options" ... (Stephan has done it perfectly this >> time!) >> >> >> Thanks & regards. =ppy >