sytse

42 ms·

1. 421.▲
   by sytse 7y ago

   I agree that the tone of the blog post was more like an announcement than a proposal.
2. 422.▲
   by sytse 7y ago

   We made this blog post before implementing the changes so we could gather feedback. The feedback 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
3. 423.▲
   by sytse 7y ago

   Thanks for the list. I've shared this with the group responsible for pages.
4. 424.▲
   by sytse 7y ago

   And a third with only minor changes I think https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...
5. 425.▲
   by sytse 7y ago

   We added a second clarification https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...
6. 426.▲
   by sytse 7y ago

   For example I was deeply moved by Executive Order 13769 https://en.wikipedia.org/wiki/Executive_Order_13769 and posted so in our Slack. The first comment was 'F* Trump', written out. At the same time many peo
7. 427.▲
   by sytse 7y ago

   Someone at GitLab just made a suggestion to change the wording of the policy that I merged https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...
8. 428.▲
   by sytse 7y ago

   Totally agree. With GitLab you can do static and dynamic code analysis, as well as dependency and container scanning on your PR/MR out of the box. And your security team gets an organization wide overview of the security results as wel
9. 429.▲
   by sytse 7y ago

   Thanks for the tip.
10. 430.▲
    by sytse 7y ago

    I love the partitioning improvements in PostgreSQL 12 https://www.2ndquadrant.com/en/blog/partitioning-enhancement... We are planning to use them for GitLab.com, particularly for the events table. More information
11. 431.▲
    by sytse 7y ago

    Thanks for posting that. Ruby or Go experience is required for backend positions.
12. 432.▲
    by sytse 7y ago

    For our reasoning please see https://about.gitlab.com/2019/02/28/why-we-pay-local-rates/ and https://about.gitlab.com/handbook/people-operations/global-c... TLDR; we want to pa
13. 433.▲
    by sytse 7y ago

    Thank you! It has been awesome to see GNOME https://gitlab.gnome.org/explore/ Freedesktop https://gitlab.freedesktop.org/explore/ and Debian https://salsa.debian.org/public embrac
14. 434.▲
    by sytse 7y ago

    I think offices are a dead end. With 4G, Slack, Zoom, and Google Docs we're able to work from anywhere. No need to commute anymore. And no need to constrain your team to the city you have an office in. The only thing is that remote sho
15. 435.▲
    by sytse 7y ago

    Funding secured.
16. 436.▲
    by sytse 7y ago

    Thank you! GitHub is unchallenged in open source but it turns out you can change all the people in one company to a new tool without much of a problem, especially if you can replace 10 other tools.
17. 437.▲
    by sytse 7y ago

    I think the evolution is Waterfall to Agile to DevOps. 1. Waterfall is a cycle time of weeks 2. Agile is a cycle time of days 3. DevOps is the same cycle time as agile but delivering the the user instead of just showing a demo at the end of
18. 438.▲
    by sytse 7y ago

    Charing for a browser brings back memories: "For now, though, note this fact: Microsoft is giving away Internet Explorer, while Netscape's retail price for Navigator is $49.Oct 31, 1996" https://www.fastcompany.com
19. 439.▲
    Firefox Premium for Enterprises is now available(ghacks.net)

    5 points by sytse 7y ago|1 comments
20. 440.▲
    by sytse 7y ago

    I looked up our wiki direction and the ideas is to allow WYSIWYG collaboration, see https://about.gitlab.com/direction/create/wiki/ I'm surprised that this wiki bug that two people here mention has only
21. 441.▲
    by sytse 7y ago

    Code search is not good at GitLab.com at the moment. We're working to enable ElasticSearch for GitLab.com to improve the situation https://about.gitlab.com/2019/03/20/enabling-global-search-e...
22. 442.▲
    by sytse 7y ago

    I agree this issue hasn't been prioritized as high as it should. I meant to indicate that with "This bug took too long to fix." but I should have said it took to long to schedule. We concluded the same internally recently and
23. 443.▲
    by sytse 7y ago

    Thanks for submitting it!
24. 444.▲
    by sytse 7y ago

    Existing customers tend to prioritize stability (fixing bugs) over new features. Please note that even if you're not a customer our issue trackers are open so you can @mention the Product Manager to help them understand the severity an
25. 445.▲
    by sytse 7y ago

    Correct, to be specific we measure PNPS https://about.gitlab.com/handbook/product/metrics/#paid-net-... We'll try to link from the legend but since it is automatically generated this is hard.
26. 446.▲
    by sytse 7y ago

    We use Chart.js for this. Credit goes to Josh Lambert who made this.
27. 447.▲
    by sytse 7y ago

    That is still our policy but we recently added something to https://about.gitlab.com/company/strategy/#breadth-over-dept... that might be relevant: "So breadth over depth is the strategy for GitLab the compan
28. 448.▲
    by sytse 7y ago

    The Product Manager (in the case Jason Lenny who is out of office today) prioritizes between bugs, vulnerabilities, new features, and tech debt. He or she uses customer input, user input, and company input. Read more on https://a
29. 449.▲
    by sytse 7y ago

    The wiki is GitLab should not delete text, please file a bug if you had dataloss. The current state of the wiki isn't great but we're also not seeing a lot of people care about it. Many people are switching to static websites. The
30. 450.▲
    by sytse 7y ago

    This bug took too long to fix. We are not happy how we prioritized the last few releases for CI. In 12.4 we'll focus on fixing 8 of outstanding CI bugs https://gitlab.com/groups/gitlab-org/-/issues?scope=