Announcing new tools, forums, and features • Hacker News Board

Re: Announcing new tools, forums, and features

#261

Post by w_t_payne » Thu, Sep 15, 2016, 1:15 PM UTC

sytse wrote: post #190

old-gregg wrote: post #183

This is the example of how hard it can be for companies, especially successful companies, to alter their course even slightly. Github success was about making code repositories pretty and social. But this is no longer enough to keep evolving as a company of their size. Yet the internal product DNA still revolves around repos, so as a result, issues, wikis and now Projects (!) live under a single repository. This is b…

I agree that putting projects under repositories looks counterintuitive. In BitBucket you have multiple repositories under one project https://confluence.atlassian.com/bitbucket/projects-79249795... We at GitLab are trying to keep it simple by having only one repository, one wiki, one issue tracker, one CD pipeline, and one set of milestones per project. Projects always below to a group. We aggregate on the group lev…

It would be nice if there were a taxonomy of different organisational approaches so that we could have a common terminology to discuss the pros and cons of each.

E.g. I come at things from the intersection of (embedded) product line engineering and continuous integration, which leads me towards a different place than somebody coming at things from (e.g.) consulting or web services ... but it is difficult to have a meaningful discussion about the pros & cons of each approach without the language / terminology that we need.

Re: Announcing new tools, forums, and features

#262

Post by kalleboo » Thu, Sep 15, 2016, 1:43 PM UTC

fredsir wrote: post #249

kalleboo wrote: post #243

Earlier quoted context omitted.

Client/Server is one case where I think having multiple repos under one project makes a lot of sense. Another one is where we have forks of libraries with minor patches to suit our needs.

Multiple codebases for multiple platforms also deserve multiple repositories.

Agreed. Depending on how much code is shared it could be one repo, or n+1 (n=platforms 1=shared code)

Re: Announcing new tools, forums, and features

#263

Post by gitdude » Thu, Sep 15, 2016, 2:01 PM UTC

samblr wrote: post #153

Can't seem to find free private repos and unlimited collaborators ? But good to see GitHub responding - would be keen to hear from bitbucket which I personally use for private repos.

Here is a list of features we shipped in the last 12 months: https://blog.bitbucket.org/2016/09/07/bitbucket-cloud-5-mill...

Re: Announcing new tools, forums, and features

#264

Post by detaro » Thu, Sep 15, 2016, 3:08 PM UTC

sytse wrote: post #142

bentlegen wrote: post #131

Earlier quoted context omitted.

Yeah, I just chose some random features that I may have interpreted incorrectly. There are others; people can read the features page for themselves. And FWIW, I admire GitLab for their open source work. I just think it's worth distinguishing that it's not entirely open source.

Thanks for the admiration. If there are features that people think that should belong in the open source edition we're all ears. We've done so before https://news.ycombinator.com/item?id=10931347 A feature comparison between CE and EE can be found on about.gitlab.com/features/#compare

Since I'm not sure were else to report this:

When googling for the fast-forward feature one of the top results was this GitHub thread, which had quite a bit of activity fairly recently: https://github.com/gitlabhq/gitlabhq/issues/2324

It seems like many posting there are not aware that this repository/bug tracker is not an official channel anymore -> maybe posting an automated comment in all issues with recent activity or locking them could help avoid confusion? If you arrive via search, you don't see the notice in the main repository description.

Re: Announcing new tools, forums, and features

#265

Post by moby » Thu, Sep 15, 2016, 4:16 PM UTC

inopinatus wrote: post #198

moby wrote: post #141

Earlier quoted context omitted.

Thanks for providing the feedback here - I've passed it along to the Engineering team building out Projects.

I'm curious as to whether you are dogfooding Projects, especially when feature work spans multiple repos. If so a "how Github uses Projects" tutorial may be worth considering.

Indeed, many teams are - the original iteration of Projects was released to staff a few months ago (as is common with many of our product releases), so we're continuing to learn how teams are using it most effectively. Yesterday's release to the public will help with that effort too.

I personally use it on my team at the moment - it's been pretty useful and we've passed along frequent feedback to the platform team responsible for it.

Re: Announcing new tools, forums, and features

#266

Post by misiti3780 » Thu, Sep 15, 2016, 4:48 PM UTC

majewsky wrote: post #177

misiti3780 wrote: post #162

Earlier quoted context omitted.

d) create issue templates also, i have to currently cut and paste the same markdown into every issue e) create user-level permissions - i work on a team where everyone would use this, but currently not everyone can have access to the code base so we have to say in trello until you can allow me the ability to turn off code access to "non-engineers"

Issue templates have been a thing for some months now. https://help.github.com/articles/creating-an-issue-template-...

no shit! thanks for showing me this.

Re: Announcing new tools, forums, and features

#267

Post by moby » Thu, Sep 15, 2016, 5:13 PM UTC

gohwell wrote: post #208

moby wrote: post #154

Earlier quoted context omitted.

I want to make sure I capture your feedback correctly, so let me know if this doesn't help: we recently released the ability to change your base branch on a PR. https://github.com/blog/2224-change-the-base-branch-of-a-pul... Let me know if that helps!

Here's an example. It's meant to illustrate 2 developers working on a feature branch based on master and one pulls their code in before the other. https://github.com/jparmstrong/gittest/pull/3/files - Two feature branches were created based on master at the same time. - Branch1: committed a change to readme and it's pulled into master via PR. - Branch2: committed a change to readme, raised a pull request (PR#3), and…

Got it - very helpful. Thanks for clarifying! I've copied this verbatim and sent across to our Platform team.

Re: Announcing new tools, forums, and features

#268

Post by moby » Thu, Sep 15, 2016, 5:39 PM UTC

exception_e wrote: post #194

moby wrote: post #169

Earlier quoted context omitted.

Ah, noted - so you'd like to have some customization on what you choose to show on your profile?

No, I'm saying that the "contribution activity" timeline thing is leaning towards information overload (hard to follow; there is a lot to look at). I felt that the last implementation (which focused on the high-level activities that one could click into) made sense. I'm not a designer or anything so take my feedback with a grain of salt.

Got it - appreciate the feedback! We've been hearing some requests to provide flexibility over what's shown on the profile timeline, so your sentiments are being echoed.

Thanks again!

Re: Announcing new tools, forums, and features

#269

Post by empath75 » Thu, Sep 15, 2016, 5:54 PM UTC

luikore wrote: post #229

old-gregg wrote: post #183

This is the example of how hard it can be for companies, especially successful companies, to alter their course even slightly. Github success was about making code repositories pretty and social. But this is no longer enough to keep evolving as a company of their size. Yet the internal product DNA still revolves around repos, so as a result, issues, wikis and now Projects (!) live under a single repository. This is b…

One project with multiple repos just adds unnecessary work of integration and management. Or, your definition of project is something big, vague and blurry. Some people are eager to divide their project into multiple repos in spite of git being a distributed version control system. Having many teams doesn't mean you should have many repos. Why not just let your team work on one small directory inside the repo?

https://github.com/spinnaker

Spinnaker is comprised of a bunch of quasi-independent microservices, designed to work together. I don't think it would necessarily make sense to have them all in the same repo, when they could be swapped out or even used separately in another project.

Re: Announcing new tools, forums, and features

#270

Post by midwestcode » Thu, Sep 15, 2016, 7:41 PM UTC

imsodrunklol wrote: post #150

scrollaway wrote: post #11

Impressive. I have to think that this is all competition fostered by Gitlab - all those features were present in Gitlab. Competition at work :)

I have been a huge pusher for GitLab, and my basic reasoning was that GitHub isn't open sourced like GitLab. GitHub was going awfully slow and no communication to its customers in new features. Looks like GitLab lit a fire underneath them. I wonder which one is "better". Nevertheless, at least there is competition now. SCM is the biggest component in any coding practices, I'm that it is finally getting attention.

Hopefully the community forum will help GitHub to keep in touch with the community!