Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab is working on a tool just for data teams

about.gitlab.com

Post reply on HN
Print view View original

91–98 of 98 posts

Re: GitLab is working on a tool just for data teams

#91

Post by kakoni »

slap_shot wrote: post #75
MarHoff wrote: post #56

Earlier quoted context omitted.

Non english speaker here you mentioned an OSS solution called "Inbulk" or something like that during the conversation. Could you spell it I'm pretty interested in finding out more about that project but google return a lot of unrelated result because of the name I guess...

https://github.com/embulk/embulk

For batch-type of workloads embulk has been really excellent tool for my company (for all extract and load steps. We do most of the transformations in db/warehouse)

Re: GitLab is working on a tool just for data teams

#92

Post by veritas3241 »

numbsafari wrote: post #73
sytse wrote: post #9

Earlier quoted context omitted.

What we're doing different is making one product that does the whole lifecycle instead of having to string tools together. It took us many months to string our toolset together and we felt there had to be a better way. Just like GitLab we try to leverage existing open source projects wherever possible. I agree Fivetran also belongs in extract and load and updated it https://gitlab.com/meltano/meltano/commit/1df9813f5…

Yo. Just keep doing what you're doing. I dig it. I'm not 100% with all the tools you are using, but stringing together random SaaS tools and having to survey a random number of open source tools in order to assemble a sensible platform makes way less sense. At the very least, what we end up with is a group of folks working together in the open to surface some of the limitations and challenges and attempt to work out…

Thanks for the positive comment! We're generally taking the same approach that was taken with GitLab the product: do it out in the open, iterate constantly, and work with the community. Especially doing it out in the open enables these sorts of _awesome_ conversations! And we definitely want feedback - this needs to work for more than just us!

Re: GitLab is working on a tool just for data teams

#93

Post by hunter23 »

jramsay wrote: post #86
hunter23 wrote: post #43

Earlier quoted context omitted.

Agreed - our company moved to Gitlab about the same time (2.5 years ago) and it's very clear from their updates that their focus has splintered in different directions. Our company has recently moved to more Microsoft products so I am pushing our CTO to move to Github. If the CEO is following this, please improve basic user stories like: * As a user, I want to easily know who has approved my merge request. Note the w…

Thanks for taking the time to share your feedback. I'm the Product Manager responsible for merge requests. Approvals are such an important part of merge requests, and we are working to make them better. We've improved a number of confusing approval widget states in GitLab 11.2 ( https://gitlab.com/gitlab-org/gitlab-ee/issues/5439 ) which will ship later this month in and the ability to filter merge requests by approv…

Hi - thanks for responding!

I'd point out that if you look at issue 5439 the team itself was originally unaware of the high number of edge case states of the merge request and closed the issue prematurely. Having many code paths is a code smell so I'd suggest simplifying your UX and edge cases here.

Since you own the merge request flow, I would suggest looking at the page and all it's edge cases and seeing where you can simplify for the user. There is a dizzying large amount of info and CTAs presented to the user; it's pure information overload. Don't just measure yourself by how many features you ship but rather on how you communicate those features to your users. Simplicity is a powerful feature in itself.

Looking forward to batch comments.

The disapprove merge request is a feature available in Phabricator and other competitors so I would look to see how they've implemented it.

Re: GitLab is working on a tool just for data teams

#94

Post by hunter23 »

victorwu wrote: post #83
hunter23 wrote: post #43

Earlier quoted context omitted.

Agreed - our company moved to Gitlab about the same time (2.5 years ago) and it's very clear from their updates that their focus has splintered in different directions. Our company has recently moved to more Microsoft products so I am pushing our CTO to move to Github. If the CEO is following this, please improve basic user stories like: * As a user, I want to easily know who has approved my merge request. Note the w…

--- As a user, I want to be notified by todos that only have any pending actions on them --- Can you explain further what you mean by "pending actions on them"? We are working to simplify and streamline our notifications and todos in GitLab. In particular, the current thinking is that they are very similar. A "notification" is an email, and a "todo" is a something that GitLab calls your attention to in the Web UI to…

If I have a merge request where I am added as an approver and that code is merged in, then I don't want it to show up on my todos. A merge request has a specified amount of approvals required and when that threshold is hit and the code is merged, there is no work to be done. It is no longer a todo but a done. Unfortunately todos doesn't work this way and become useless for senior members who get listed as approvals for many merge requests.

In terms of combining them with notifications, I agree. I just need a web place to see all the "pending" action items I need to work on. A web notification feature should be the place to see all the pending notifications left for me (similar to how it would work on email except you can't expire emails).

Re: GitLab is working on a tool just for data teams

#95

Post by parasubvert »

sytse wrote: post #82
parasubvert wrote: post #68

Earlier quoted context omitted.

This is Gitlab taking stuff they were doing already internally and making it available to a broader audience. Once you take VC funding, you gotta go where the money is. Everyone wants/expects "fast, stable, like Github" for free unless you have special needs. So, you do analytics on what people are doing with your free site, you offer enterprisey features, you get into the "platform" business etc. I think Gitlab dist…

We are building a fast, stable, GitHub alternative. We have hired 3 times as many people in our security team for GitLab.com (not our product team for security) as are working on Meltano. We have hired 3 times as many people in our SRE teams as are working on Meltano. And we still have a lot of vacancies for both https://about.gitlab.com/jobs/

I meant no offense. But you’re also dabbling in building your own k8s distro / platform, you have your own CI/CD , Jira storyboard , and data science stuff, etc.

My point is that you’re aiming a lot broader than Github ever did - you are competing more as a suite than as a focused product.

And I’ve seen personally this impact the support side with customers, partnership side, etc. I help maintain a medium-large Gitlab for one of your bigger customers. Anyway this isn’t the place for me to get specific, I am just saying that you are taking a risky path in terms of sustainability IMO as a rando on the internet.

Re: GitLab is working on a tool just for data teams

#96

Post by _pmf_ »

sytse wrote: post #81
_pmf_ wrote: post #52

GitLab's usage of team members in marketing material is creeping me out (as does the whole team page[0]). [0] https://about.gitlab.com/team/

We say team members instead of employees because some are contractors. Why does it freak you out? BTW We don't call it a family https://about.gitlab.com/handbook/leadership/#management-tea...

I wouldn't want to have that level of public affiliation with my employer (no matter who that employer might be).

Re: GitLab is working on a tool just for data teams

#97

Post by sbr464 »

jakecodes wrote: post #62
sbr464 wrote: post #54

Are you releasing/sharing any of the extractors you built for various services?

All of our extractors are available in our source code, which is open source. http://gitlab.com/meltano/meltano/ . Right now we are working towards an MVP, so things might be in flux, but we value any feedback you have.

Thanks. I had looked but only saw one for fastly, am I missing others somewhere?

Re: GitLab is working on a tool just for data teams

#98

Post by sbr464 »

sbr464 wrote: post #97
jakecodes wrote: post #62

Earlier quoted context omitted.

All of our extractors are available in our source code, which is open source. http://gitlab.com/meltano/meltano/ . Right now we are working towards an MVP, so things might be in flux, but we value any feedback you have.

Thanks. I had looked but only saw one for fastly, am I missing others somewhere?

Apologies, I found them in another repo - GitLab Analytics. Thanks

https://gitlab.com/meltano/analytics/tree/master/elt

Post reply on HN