Comments by Kamil Burzynski (Top 25 by date)

How tracking clicks on my end is related to tracking incoming traffic from your site? Those 2 topics are not the same.

Also, how am I supposed to track which link user clicked? If you have the link to ::Workspaces on left sidebar, in menu bar and below the article, there is no way for me to distinguish between them. And that is quite crucial information, as without it we're blind and just randomly add/remove various links based solely on hunch.

From my side the system is mostly implemented (events from ::Tasks and ::GitMachine are still missing), and it should be deployed today (hopefully before you read this). It will log all page loads, referrers, IPs and user agent strings. This week we'll add events from the apps, and the implementation should be complete.

Please also note, that by implementing this system, we're crossing some 'dont be evil' boundary. While technically it is the same what everybody does (basically, logging traffic & analysing it), in practice it adds very unconvenient traffic. Every time user does something we're sending ajax call to the server essentially saying 'user Z visited Y, please log this' and server answers 'ok, logged'. Some people might find it off-putting to see such traffic.

Issue is that autoforks are not visible to strangers by default.

unknown error -1 is from timeout
'code' link is not working, since this is autofork, hence invisible to others.

Duplicate of 'invite by email'

This activity will be tracked under 'Folders' task

What needs to be done here?

What is left to be done here?

- Remove AC
- Get rid of app instance loading upon cp/{get|fork}_workspace

Can we reproduce it somehow?

Please verify if this still exists.

Please verify if this still exists.

Is this still opened?

What is wrong with current descriptions, any examples?

Something more to be done for this?

I was fixing this some time ago, please verify.

Todo: change default min iframe height from 500px to 800px.

@Daniel: please try to solve this together with Piotr

http://teamreview.codeplex.com/

http://malevich.codeplex.com/

https://code.google.com/p/rietveld/

https://code.google.com/p/jupiter-eclipse-plugin/

http://sourceforge.net/projects/codestriker/

http://getbarkeep.org/

http://www.reviewboard.org/

Why this is reported here? Shouldn't be relevant to ::GitMachine/::Tasks?

Actually, the algorithm was written to find the highest empty slot. So, if there is some room on the right side, widget should be placed there, not at the bottom.

It looks, like the algorithm is not working properly, however. Need to be verified, maybe it is working, but for some reason our config causes it to place new widgets at the very bottom.