rkorach
commented
12 years ago It is just criteria that could be taken into account to give some content (a paragraph...) a better score. Just like highlighting, except that this time it is not user behavioral data, but editorial data. (Thus should be probably have less importance)
The thing is that stack is to me just "features that at some point we'll want to implement" Github issues are better than a mail thread (remember we're trying to get less of them) because issues are here very accessible. Emails get lost. Ideas in it too.
If you think github issues as something that has to be cleared as quick as possible, I totally understand your point of view. Le 10 août 2012 10:20, "Raphael Moutard" notifications@github.com a écrit :
@rkorach https://github.com/rkorach could you try to explain a bit more. It's easy to detect * and , but what do you want to do after ? Do you want to keep it into the database ? Do you use it for dbscan2 or just to display the visitItem ?*
In my opinion, this shouldn't be in git issues. we should open a thread in coding@ct.com to talk about it, then when we exactly know what we want to do, we had a complete issue, with a precise descripion. For the moment I don't know what I have to do with it. So it's just noise in the stack.
Do you agree with that ?
— Reply to this email directly or view it on GitHubhttps://github.com/moutard/SubZoom-Proto1/issues/39#issuecomment-7637797.
HadrienR
@rkorach could you try to explain a bit more. It's easy to detect strong and em, but what do you want to do after ? Do you want to keep it into the database ? Do you use it for dbscan2 or just to display the visitItem ?
In my opinion, this shouldn't be in git issues. we should open a thread in coding@ct.com to talk about it, then when we exactly know what we want to do, we had a complete issue, with a precise descripion. For the moment I don't know what I have to do with it. So it's just noise in the stack.
Do you agree with that ?