Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki

2016-01-07 Thread Bert Verhees
On 07-01-16 16:19, Bakke, Silje Ljosland wrote: I think for this to be useful, the site have to be readable without logging in… That is also true, Google must be able to reach it, and not anyone wants to be known when searching information. ___

Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki

2016-01-07 Thread Thomas Beale
Bert, were you logged in? On 06/01/2016 09:33, Bert Verhees wrote: On 06-01-16 09:07, Bakke, Silje Ljosland wrote: one of the features we don't use on the wiki is 'Questions', which you can see here . There seems to be an authorization-problem,

Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki

2016-01-07 Thread Seref Arikan
Ok, logged in, upvoted the question, then watched the question. The answer was accepted and I received an e-mail telling me that. So it all seems to be working. The point about making this publicly visible is a good one, but is it possible? Finally, even though I'm in favour of a less strict

Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki

2016-01-07 Thread Bert Verhees
On 07-01-16 19:45, Thomas Beale wrote: do you mean the 'top expert' kind of stuff? It seems pre-computed as far as I can tell. Let's play with it for a few months and see how well it works. We can always try somtehing else later if it doesn't do the job. Yes, I consider it a bit harmful. It

Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki

2016-01-07 Thread Bert Verhees
Looks good, same as stackoverflow, about. good the options to watch and share questions On 07-01-16 19:45, Thomas Beale wrote: On 07/01/2016 17:12, Bert Verhees wrote: On 07-01-16 17:28, Thomas Beale wrote: I changed the wiki so that Questions is now visible read-only to non-logged in

Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki

2016-01-07 Thread Thomas Beale
On 07/01/2016 17:12, Bert Verhees wrote: On 07-01-16 17:28, Thomas Beale wrote: I changed the wiki so that Questions is now visible read-only to non-logged in users. I have checked that this works on a test machine. Works OK now. What makes me doubt is a very obvious