You're probably right. It is hard to find the acceptable level of strategic
voting :)

On Thu, Jun 11, 2015 at 4:54 PM, David Moner <[email protected]> wrote:

> I would not do so. This is not an automatic process, this first phase is
> just a way of filtering proposals. For sure the people in StackExchange
> will evaluate each proposal in detail, and if they find that votes and
> questions are clearly addressed or governed the proposal won't be accepted.
>
> 2015-06-11 17:41 GMT+02:00 Seref Arikan <[email protected]
> >:
>
>> Thanks, can someone write a comment (shamelessly in capitals..)  under
>> the highest voted (16 the moment) question asking visitors to NOT to vote
>> for questions with > 10 votes? My user can't do it for some reason.
>>
>> There are ~19 wasted points that could have been used on other questions
>> a.t.m and people will just arrive and keep upvoting the top 5 ones. (This
>> is a weird design; if > 10 votes do not help, why let users vote beyond 10
>> at that stage?)
>>
>> On Thu, Jun 11, 2015 at 4:12 PM, Cavero Barca, Carlos <
>> [email protected]> wrote:
>>
>>>         Done! 90 followers :)
>>>
>>>         Regards.
>>>         Carlos.
>>>
>>> -----Original Message-----
>>> From: openEHR-technical [mailto:
>>> [email protected]] On Behalf Of Arild Faxvaag
>>> Sent: Thursday, June 11, 2015 3:46 PM
>>> To: For openEHR technical discussions
>>> Subject: Re: openEHR @ StackExchange - getting close
>>>
>>> done signing up and upvoting.
>>>
>>> _______________________________________________
>>> openEHR-technical mailing list
>>> [email protected]
>>>
>>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>>> This e-mail and the documents attached are confidential and intended
>>> solely for the addressee; it may also be privileged. If you receive this
>>> e-mail in error, please notify the sender immediately and destroy it.
>>> As its integrity cannot be secured on the Internet, the Atos group
>>> liability cannot be triggered for the message content. Although the sender
>>> endeavors to maintain a computer virus-free network, the sender does not
>>> warrant that this transmission is virus-free and will not be liable for any
>>> damages resulting from any virus transmitted.
>>>
>>> Este mensaje y los ficheros adjuntos pueden contener información
>>> confidencial destinada solamente a la(s) persona(s) mencionadas
>>> anteriormente y pueden estar protegidos por secreto profesional.
>>> Si usted recibe este correo electrónico por error, gracias por informar
>>> inmediatamente al remitente y destruir el mensaje.
>>> Al no estar asegurada la integridad de este mensaje sobre la red, Atos
>>> no se hace responsable por su contenido. Su contenido no constituye ningún
>>> compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
>>> Aunque se esfuerza al máximo por mantener su red libre de virus, el
>>> emisor no puede garantizar nada al respecto y no será responsable de
>>> cualesquiera daños que puedan resultar de una transmisión de virus.
>>> _______________________________________________
>>> openEHR-technical mailing list
>>> [email protected]
>>>
>>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>>>
>>
>>
>> _______________________________________________
>> openEHR-technical mailing list
>> [email protected]
>>
>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>>
>
>
>
> --
> David Moner Cano
> Grupo de Informática Biomédica - IBIME
> Instituto ITACA
> http://www.ibime.upv.es
> http://www.linkedin.com/in/davidmoner
>
> Universidad Politécnica de Valencia (UPV)
> Camino de Vera, s/n, Edificio G-8, Acceso B, 3ª planta
> Valencia – 46022 (España)
>
> _______________________________________________
> openEHR-technical mailing list
> [email protected]
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Reply via email to