171–180 of 356 posts
I really liked Gitlab when last I tried it, but in the end I went with https://gogs.io/ instead. For a small-ish team this felt like the most straight forward self-hosted solution. Still missing LFS though, which sucks, but it's being worked on.
Earlier quoted context omitted.
We removed our project and never used github again. That seems like a totally disproportionate approach versus responding with a polite 'this is a legitimate use of the word, thanks' message.
I stopped using Github when they hired blatant racists as part of their 'social outreach' team. The infestation of politically-correct politics drives talent that can't be bothered with such cruft away. I was there to code. Not worry about if I hurt some oversensitive person's feelings for referring to master/slave copies.
Earlier quoted context omitted.
I find that github's point of view on those problems are very hard to understand. For example, I once read a github's blog complaints that they don't have enough black, women leaders in github company. But if they really think all races/genders are equal, why they care about how many percent of leaders are non-white, or women?
I'm confused by your question. A lot of organizations have similar concerns. Do you believe that all discussion of diversity is equally nonsensical, or is there something about Github's stance that strikes you as especially so?
Interesting. For projects that don't need a "community" we've been using Amazon CodeCommit. We don't like to use Github anymore because of the politics there. Example: We had a project involving software filters that included this sentence in the description: > Phase is related to time, but a pure time delay does not involve any phase shift. A pure time delay or "group delay" is constant with frequency. Phase shift v…
We removed our project and never used github again. That seems like a totally disproportionate approach versus responding with a polite 'this is a legitimate use of the word, thanks' message.
Phabricator is a great alternative, by the way. Really stable and has the best code review interface / workflow I've ever used.
Customizable Task Management
Plan features, track bugs, and award tokens. Maniphest lets you customize input forms, use custom fields, and has a rich API.
Keeps track of lots of bugs.
You can assign them to people.
Maybe you could fix them, eventually. (optional)
Build unique task forms for every department.
For example, look at this feature in Phabricator itself: T6526
Business Rules
As your company scales, keep track of activity with Herald, which notifies you when things you care about happen (like a specific file being changed).
Write business rules.
Everyone loves business rules.
Keep an eye on suspicious new hires.
Warns you about plotting and scheming.
Build triggers on tasks, commits, revisions, and more.Earlier quoted context omitted.
Maybe she actually could've read the text and figured it out herself before sending out the note? Just firing off a warning based on a simple text match seems high-handed and/or incompetent enough to consider leaving.
Presumably it was an automated message.
Earlier quoted context omitted.
Any hope to get improvements on the issue tracker?
We hope to ship Issue boards[1] this months, which will be a mayor improvement! But maybe you could be more specific to what you're missing? We'd love to hear your feedback! [1] https://gitlab.com/gitlab-org/gitlab-ce/issues/17907
Mostly, we need a way to defined custom fields to be able to triage, query and reassign automatically. Like for example components or platform. And labels are clearly not enough for that.
Interesting. For projects that don't need a "community" we've been using Amazon CodeCommit. We don't like to use Github anymore because of the politics there. Example: We had a project involving software filters that included this sentence in the description: > Phase is related to time, but a pure time delay does not involve any phase shift. A pure time delay or "group delay" is constant with frequency. Phase shift v…
I posted before[0] about why I moved to gitlab; I'm using a self-hosted instance and the only real complaint I have is resource consumption. But if you bite the bullet a bit it's a really great product. The other thing would be "ease of deployment" or lack thereof- if you're going for anything other than omnibus installs or docker images then it can be a bit painful. (I wanted to run on freebsd for example). But, yes…
How has your experience of installing gitlab on freebsd been? Anything in particular that can be improved? I'm pretty sure the gitlab team is open for all kind of improvements. :)
it also suggests operating under bad practices like running gitlab from /home/
I guess I could write a decent salt-formula to do all this, but I can't handle upgrading of gitlab easily, it always breaks when I take a new branch from git and run a gitlab-ctl reconfigure.
[0]: https://github.com/gitlabhq/gitlab-recipes/blob/master/insta...