this post was submitted on 17 Jun 2023
7 points (100.0% liked)

Programming

13391 readers
1 users here now

All things programming and coding related. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

I just joined a new team (very small: four developers in total, with two of those leaving soon). The two original developers set up the git repo on a folder in a Windows network share.

Am I taking crazy pills, or is that a bad idea? Our organization does have github/gitlab/bitbucket available, so is there any good reason not to use those hosted solutions?

you are viewing a single comment's thread
view the rest of the comments
[–] Grishaix@feddit.de 3 points 1 year ago (2 children)

Our organization does have github/gitlab/bitbucket available

Do you mean "cloud services"? Maybe your colleagues don't want them there.

For PCI-DSS relevant code, we only use internal systems.

[–] preciouspupp@sopuli.xyz 4 points 1 year ago (1 children)

I don’t see how would this be compliant with literally anything.

[–] TheTrueLinuxDev@beehaw.org 1 points 1 year ago

I would have to agree on this, it seems rather odd if the code repo is confidential or classified to be shared on a Windows Share. The reason why we would use Git services (self-hosted) is so that we have multitude of security services/layers maintained by dedicated team of system administrators such as firewall, service update, data redundancy, backup, active directory and so forth.

I can see a scenario where people accidentally put classified repos or information that aren't supposed to be shared on Windows Share where unauthorized users could view that repos.

[–] Zargontapel@latte.isnot.coffee 2 points 1 year ago (1 children)

That may be the case, but the original engineers have made other highly questionable decisions: the backend service was written in Java 8...just last year!

[–] aksdb@feddit.de 1 points 1 year ago

That doesn't sound questionable, but somewhere between stubborn and stupid. Unless that thing is supposed to be deployed to a heavily outdated system where nothing newer than Java8 will run, that is.