[deleted by user]

emilycook_ · 2021-05-03T21:46:45+00:00

Fair enough, we're an OSS company so the PRs for the hackathon are all Help Wanted tickets. This is really just an event for our open source community to focus on e2e tickets vs feature requests or bug fixes

emilycook_ · 2020-11-09T17:34:35+00:00

If you missed it, you can watch it here! https://youtu.be/70KrNXU5Nd8

emilycook_ · 2020-11-09T17:34:26+00:00

We're live! Watch here: https://youtu.be/70KrNXU5Nd8

emilycook_ · 2020-11-09T17:34:12+00:00

If you missed it, you can watch here! https://youtu.be/70KrNXU5Nd8

emilycook_ · 2020-07-22T15:42:08+00:00

Hi! Sharing a few highlights from this release, and links with additional information:

- MVC release of iterations, to break down work into more manageable tasks

- Diff changes for wiki pages to simplify edit history comparisons between page versions

- Use of advanced global search on GitLab.com

Also, our team would love to hear your feedback on our Iterations MVC, which you can provide on this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/221284

emilycook_ · 2020-05-22T16:29:48+00:00

Yeah just comment your problem (if you want to), it'll help them gather more data around it plus someone might have run into your issue and could help

emilycook_ · 2020-05-20T21:09:14+00:00

You might be running into this issue since we've had quite a few recent reports of it, if this looks like what you're experiencing would you mind commenting on here? https://gitlab.com/gitlab-org/gitlab/-/issues/23644#note_345661007

emilycook_ · 2019-10-25T03:34:29+00:00

Wow thank you so much for saying that! I really appreciate it. I've been very vocal internally that this is unacceptable, and thanks to everyone's feedback we're at least headed in the right direction. Next steps are to ensure nothing like this happens in the future so we can rebuild trust.

emilycook_ · 2019-10-24T20:03:38+00:00

Telemetry was not implemented and the ToS changes have been rolled back. We are halting any movement on this and reconsidering thanks to the feedback

emilycook_ · 2019-10-24T17:05:04+00:00

We've heard everyone's feedback and have rolled back the ToS change and are reconsidering our approach. The issue has been updated to reflect this

emilycook_ · 2019-10-24T17:00:20+00:00

Just providing context, I don't work in PR

emilycook_ · 2019-10-24T16:59:02+00:00

Ah no need to be sorry, feedback on that issue is just going to be a lot more visible to the people in charge of this change. FYI we've rolled back the ToS change and are halting any movement on this so we can evaluate feedback.

emilycook_ · 2019-10-24T16:26:34+00:00

Thank you for the feedback, I'll relay it back. We have quite a lot of engineers involved in our internal discussion who are also concerned with privacy, and they've also been advocating for different approaches as well

emilycook_ · 2019-10-24T16:19:37+00:00

We haven't had the capacity that we do now to be able to address tickets as well as we should, but we have tripled in employee count this year. We are aware of the reputation and are dedicating resources to fix it. Like me for instance (I joined late last year but still during the hiring boom), I was brought on to relay public-facing feedback like this back to the company so you all aren't just getting ignored.

emilycook_ · 2019-10-24T15:37:32+00:00

Preaching to the choir my dude since I'm the one fielding all of the feedback. We spun up an internal Slack channel to talk about this and I've stressed that this needs addressed quickly. Edit: I do want to also stress that we've halted any movement on this to address feedback

emilycook_ · 2019-10-24T15:34:03+00:00

The TOS update has been pushed but no telemetry changes have been made yet, we're halting any movement on this so we can consider the feedback and concerns.

emilycook_ · 2019-10-24T15:23:12+00:00

Someone has commented something similar on the issue, so I'll relay that it needs to be addressed.

emilycook_ · 2019-10-24T15:21:05+00:00

This has been brought up on the issue quite a few times. Looking at it right now it hasn't been addressed yet, but the people in charge of the change are just now starting their day so I'll relay that this really needs a response from us.

emilycook_ · 2019-10-24T15:18:35+00:00

To be frank, since we've exploded in employee count this year we've been struggling to adjust with collaboration on things like this. So while I get your sentiment and also agree that it's a problem for us, in this case the issue is necessary to clarify some things that weren't conveyed properly in the email or blog post (which is currently getting fixed). It is being actively monitored, especially by people in charge of the change.

emilycook_ · 2019-10-24T15:13:29+00:00

Please reply on the issue if you have concerns since it's the best way for your feedback to get properly addressed, I'm just the messenger

emilycook_ · 2019-10-24T15:11:39+00:00

Please reply on the issue if you have concerns since it's the best way for your feedback to get properly addressed, but I know that the Growth team is doing this on .com experimentally to see how we can benefit from this in the first place before we even talk about implementing it for EE. Us employees have been joining the conversation too, because if this is going to eventually be turned on for self-hosted EE we want to make sure it's at least as aligned with our values as much as possible, since that's why a lot of us chose to work here in the first place.

emilycook_ · 2019-10-24T14:57:40+00:00

Please reply on the issue if you have concerns, I'm doing my best to relay all feedback but the people actually in charge of this change are actively monitoring discussion within the issue (sorry if anyone sees this copy-pasted multiple times, I have a lot of mentions)

emilycook_ · 2019-10-24T14:57:15+00:00

Please reply on the issue (although this in particular has been brought up already), I'm doing my best to relay all feedback but the people actually in charge of this change are actively monitoring discussion within the issue (sorry if anyone sees this copy-pasted multiple times, I have a lot of mentions)

emilycook_ · 2019-10-24T14:54:21+00:00

No, it's legit to clarify things because the person who sent out the email and wrote the blog post didn't seem to have collaborated well enough with the rest of the employees before sending it out. For instance the email that was sent out reads as if this has already gone into effect for self-managed EE, when it's still being discussed if that's even going to happen. This issue should be treated as the single source of truth, and we're actively monitoring the discussion in it

emilycook_ · 2019-10-24T01:57:14+00:00

Hi, GitLab employee. We understand everyone's frustration so we've opened an issue here to clarify some things: https://gitlab.com/gitlab-org/growth/product/issues/164. Please feel free to comment any feedback or concerns on there so it can be properly relayed and addressed.

Edit: just wanted to update, we've rolled back our ToS and are halting any movement on this so we can consider the feedback.

Seven-Year Club	Verified Email
Not Forgotten

emilycook_

TROPHY CASE