sytse

37 ms·

1. 391.▲
   What Tracking Down Missing TCP Keepalives Taught Me About Docker, and Golang(about.gitlab.com)

   3 points by sytse 7y ago|1 comments
2. 392.▲
   by sytse 7y ago

   Indeed. This is about residence not about nationality. As for making this public we are public by default. But we are learning that anything involving countries needs to be communicated with a lot of context. Countries are a core part of pe
3. 393.▲
   by sytse 7y ago

   If an issue is public everyone can comment on it until it is locked. I don't think there is another setting.
4. 394.▲
   by sytse 7y ago

   GitLab | Remote only | Full time - It’s an exciting time to join GitLab. As a fast-growing, all-remote company, GitLab is a place where you can contribute and make an impact from anywhere in the world. You’ll be part of an ambitious, produc
5. 395.▲
   by sytse 7y ago

   It would be strange to not accept code from certain countries since we are an open core company that gets contributions from around the world. There are other ways to prevent supply chain attacks. A difference with data is that there are al
6. 396.▲
   by sytse 7y ago

   You mentioned https://about.gitlab.com/handbook/ceo/#flaws I hoped that people would use the sentences I proposed on that page but that never happened. What is helpful is that when people raise a concern I can rec
7. 397.▲
   by sytse 7y ago

   Thanks! We try to be transparent by default and even when it is difficult. I think the OP is a good example of something that is hard to be transparent about because the decision isn't obvious and it takes discussion to come to the bes
8. 398.▲
   by sytse 7y ago

   Correct, this block would be for two functions (Site Reliability Engineer and Support) and we currently have no people in that role in China and Russia. Please note that we're still discussing this change. We work out in the open so yo
9. 399.▲
   by sytse 7y ago

   Apart from Python coders also hiring engineer proficient in Go and ElasticSearch experts.
10. 400.▲
    by sytse 7y ago

    Is it possible to make a valid QR code that is human readable by manipulating the size, weight, greyscale?, and positioning of letters?
11. 401.▲
    by sytse 7y ago

    How can we make it more helpful?
12. 402.▲
    by sytse 7y ago

    Further follow-up https://news.ycombinator.com/item?id=21390563
13. 403.▲
    by sytse 7y ago

    We recently launched a simple stock option value calculator on our jobs pages https://about.gitlab.com/handbook/people-group/global-compen... that has a few scenarios. I love how this calculator gives a lot more v
14. 404.▲
    by sytse 7y ago

    What can you do with Jenkins and not GitLab CI that made you go back to Jenkins?
15. 405.▲
    by sytse 7y ago

    Thanks, we started our retro 3:44pm Pacific, slightly before your post. We looked into making it public at 4:05pm but by then it already had confidential security information and customer names in it. There will be multiple lessons, right n
16. 406.▲
    by sytse 7y ago

    I'm sorry our plans were so far off the mark.
17. 407.▲
    by sytse 7y ago

    That is a great summary of why the backlash was so big. We have a lot of data in the DB of GitLab.com but it was hard to understand it. Using a third-party service with client side tracking saves a lot of time and effort.
18. 408.▲
    by sytse 7y ago

    There are multiple decisions: opt-in vs. opt-out, GitLab.com vs. self-hosted, DNT vs. in-app, first-party vs. third-party, aggregated data vs. user data. As an example that we won't do opt-out self-hosted third party with user data doe
19. 409.▲
    by sytse 7y ago

    Ah, thanks. I only looked at the first post https://cmpwn.com/@sir/103018233505800721 not the rest of the thread.
20. 410.▲
    by sytse 7y ago

    We didn't expect praise but many more people expressed concern than we expected.
21. 411.▲
    by sytse 7y ago

    Thanks, we'll make sure to detail what data is collected when we rethrought our plans.
22. 412.▲
    by sytse 7y ago

    We called out the increasing signups at GitLab when GitHub got acquired, so from our side it is more than fair that Drew is posting this. BTW As Drew said https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests
23. 413.▲
    by sytse 7y ago

    We also called out our signups at GitLab when GitHub got acquired, so it is more than fair that Drew is posting this. BTW As Drew said https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/... we'r
24. 414.▲
    by sytse 7y ago

    Thanks, we're pumping the breaks on this change completely, see https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...
25. 415.▲
    by sytse 7y ago

    I agree that user advocates are our lifeblood and we're risking alienating them. There were many more concerns than we expected. We’re going to process the feedback and rethink our plan. We will not activate product usage tracking on G
26. 416.▲
    by sytse 7y ago

    As said we didn't expect praise. We published this change in a blog post and sent an email.
27. 417.▲
    by sytse 7y ago

    Thanks. We will revisit opt-in vs. opt-out, especially for self-hosted installations. We didn't expect praise for more telemetry from the developer audience but we did underestimate the reaction. There were many more concerns than we e
28. 418.▲
    by sytse 7y ago

    "Not sure why the "opt-in" option isnt more apparent as a less hostile UX?" do you mean having to use DNT to opt out?
29. 419.▲
    by sytse 7y ago

    The feedback to this change is very negative. And some of the things we thought would help (respecting DNT) don't seems to matter much. We'll have a look at all the feedback and see what we can learn and adjust. First change to th
30. 420.▲
    by sytse 7y ago

    We're updating the blog post with https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...