<div dir="ltr">My apologies, I had thought they weren't but clearly they are.</div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Nov 18, 2017 at 6:10 PM, Stephan Oepen <span dir="ltr"><<a href="mailto:oe@ifi.uio.no" target="_blank">oe@ifi.uio.no</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="auto">thanks for the reminder, francis.</div><div dir="auto"><br></div><div dir="auto">i believe someone voiced the impression at the summit already that the DELPH-IN wiki is not indexed by search engines. i admit i never looked into interactions with search engines specifically, but i would be very surprised if there were any settings on the oslo DELPH-IN servers that would scare off search engines.</div><div dir="auto"><br></div><div dir="auto">why do you believe we are not indexed? i just did a quick test, which seems to give the result one would expect (see below).</div><div dir="auto"><br></div><div dir="auto">all best, oe</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div><img src="cid:15fce9ab1134a1f74271" style="max-width:100%"></div><br></div><div><div class="h5"><br><div class="gmail_quote"><div>On Sat, 18 Nov 2017 at 10:08 Francis Bond <<a href="mailto:bond@ieee.org" target="_blank">bond@ieee.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thank you for taking the initiative Olga! I hope that this make<br> information flow even better.<br> <br> I think one of the problems with the wiki is that it does not seem to<br> be indexed by, e.g. google. Stephan: is there a setting you can<br> change to get it indexed? I think this would make the information<br> there a lot more discoverable, ...<br> <br> On Sat, Nov 18, 2017 at 7:02 AM, Olga Zamaraeva <<a href="mailto:olzama@uw.edu" target="_blank">olzama@uw.edu</a>> wrote:<br> > Dear developers,<br> ><br> > In the last summit in Oslo, we discussed a possibility of having a Q&A forum<br> > in stackexchange style.<br> ><br> > Many people were enthusiastic, and, thanks to University of Washington<br> > staff, we were able to set up a forum powered by Discourse:<br> ><br> > <a href="https://delphinqa.ling.washington.edu/" rel="noreferrer" target="_blank">https://delphinqa.ling.<wbr>washington.edu/</a><br> ><br> > I would like to invite each of you to create an account and try it out!<br> ><br> > The forum was created very recently, but at this point, there should not be<br> > too many hiccups. We need to decide a few things soon (see below), so, we<br> > want to involve the entire community at this point, even if we are still<br> > testing the forum.<br> ><br> > A few notes, for those inclined to read them :).<br> ><br> > 1) The primary purpose of this forum is to accumulate concrete solutions to<br> > technical problems and make them easily discoverable. So the primary<br> > scenario is for one to encounter an error message, and, instead of trying to<br> > locate the answer somewhere on the wiki or in the email archives and ending<br> > up emailing the list for the 100th time anyway, one would query the forum<br> > (using e.g. the text of the error message). If their question was already<br> > answered, the assumption is they will be able to immediately find out what<br> > the working solution is. This is, in my opinion, the most important feature<br> > of stackexchange Q&A style, and one that other types of support lack.**<br> > Moreover, the forum is also a fine platform for open-ended discussions, with<br> > a nice addition of the upvote button which makes better, clearer posts more<br> > salient in the thread.<br> ><br> > **(Some people oppose this style since, in their opinion, finding the right<br> > solution "too easily" leads to lack of understanding of why the right answer<br> > is the right answer. I agree that there may be some truth to that but I<br> > also think that this ultimately depends on the user and how much and in what<br> > style they are willing to learn; there is also a question of priorities:<br> > sometimes what is needed the most is to fix the problem asap.)<br> ><br> > 2) I will be the admin of the forum for now. This means I am the person to<br> > whom you can complain about things if something is not working for you. It<br> > also means I can do various things for you, such as create/merge categories<br> > and so forth. If you would like to also be an admin or a moderator, let me<br> > know. It will probably help to have more admins, especially in other time<br> > zones.<br> ><br> > 3) You do not need to monitor the forum or anything like that, unless you<br> > would like to. Instead, you can subscribe to categories or tags, and the<br> > forum will email you when a new post is created in the category or with that<br> > tag. You can choose whether you will be notified about the first post only<br> > or each reply.<br> ><br> > 4) Some developers expressed concern that we are thus fragmenting our<br> > support platforms. I understand this concern and would like to address it by<br> > both making an effort to import the email archives into the new forum<br> > (unless it proves too messy) and by pointing out that the email+wiki do not<br> > and cannot really serve the purpose that I think this forum will serve. It<br> > seems that the wiki, the email list, and the forum can very happily coexist,<br> > just like python documentation and python-related sections of stackoverflow<br> > (and presumably some people exchange emails about python when they want to<br> > discuss something in a manner they don't think the general public will<br> > necessarily benefit from). Obviously, the wiki should be linked to from the<br> > forum (and vice versa) and instructions on the wiki can be updated whenever<br> > it makes sense to do so.***<br> ><br> > ***(Note however that it can be rather impractical to try and incorporate<br> > every single detail into the wiki, especially if the detail only makes sense<br> > in the context of a concrete question. In fact, every time one adds<br> > something to the wiki, one in a way is adding a new dimension to the space<br> > in which people will be searching for solutions... without adding a starting<br> > point for the search, necessarily.)<br> ><br> > 5) The forum is hosted by the University of Washington, so, there is no<br> > danger of some external host interfering in our affairs. Discourse is<br> > open-source software. It is also a very flexible system already, with<br> > various plugins etc. We can customize it as we like.<br> ><br> > If you would like to discuss any of this, we can do it here over email or on<br> > the forum; there is already a topic there regarding the email archives:<br> > <a href="https://delphinqa.ling.washington.edu/t/importing-email-archives/28/5" rel="noreferrer" target="_blank">https://delphinqa.ling.<wbr>washington.edu/t/importing-<wbr>email-archives/28/5</a> In<br> > particular, that topic invites you to participate in a poll.<br> ><br> > Thank you for considering,<br> ><br> > Olga<br> ><br> > P.S.: You will see that there are already some users and topics; I hadn't<br> > advertised the forum here earlier because it was not yet working in a stable<br> > fashion, but it should be now :). Note also that for now, this is all in the<br> > testing stage. For example, if we do decide to import the mailing list<br> > archives, we may need to purge the existing content.<br> <br> <br> <br> --<br> Francis Bond <<a href="http://www3.ntu.edu.sg/home/fcbond/" rel="noreferrer" target="_blank">http://www3.ntu.edu.sg/home/<wbr>fcbond/</a>><br> Division of Linguistics and Multilingual Studies<br> Nanyang Technological University<br> </blockquote></div></div></div></div> </blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Francis Bond <<a href="http://www3.ntu.edu.sg/home/fcbond/" target="_blank">http://www3.ntu.edu.sg/home/fcbond/</a>><br>Division of Linguistics and Multilingual Studies<br>Nanyang Technological University<br></div> </div>