Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EthicalSource belongs on GitLab, not GitHub #46

Closed
robbyoconnor opened this issue Mar 11, 2020 · 7 comments
Closed

EthicalSource belongs on GitLab, not GitHub #46

robbyoconnor opened this issue Mar 11, 2020 · 7 comments

Comments

@robbyoconnor
Copy link

robbyoconnor commented Mar 11, 2020

If Ethical Source's goal is to stop those who support ICE and the DOD, then why are you hosting everything on here? Use GitLab.

GitHub is owned by MS, who has ICE contracts.

@zspencer
Copy link
Contributor

zspencer commented Mar 14, 2020

This is an excellent question. I believe there is one reason that GitHub was chosen, and another reason for why moving may not be an effective use of the organizations limited time and attention.

  1. Moving to GitLab or a self-hosted option would be more ideologically pure; but ideological purity is only so effective at shifting the Overton window. To engage with the existing developer community in good-faith, we must show up where the community exists. This may include using products or services that are also used by organizations which we would not work with directly.

  2. Migrating from Vendor A to Vendor B is unlikely to significantly reduce the amount of "water" the ethical source movement carries for actors whose ethics we disagree with. For example, GitLab demonstrates sexism.

There is a saying: "There is no ethical consumption under capitalism." This is not an excuse, but to the best of my knowledge there is not an intersectional, community-owned and operated alternative to GitHub or GitLab. It there were, I would be happy to explore, advocate for and perform the work to migrate to such a platform so long as it does not reduce community engagement and is within the movements financial means.

@robbyoconnor
Copy link
Author

This is an excellent question. I believe there is one reason that GitHub was chosen, and another reason for why moving may not be an effective use of the organizations limited time and attention.

  1. Moving to GitLab or a self-hosted option would be more ideologically pure; but ideological purity is only so effective at shifting the Overton window. To engage with the existing developer community in good-faith, we must show up where the community exists. This may include using products or services that are also used by organizations which we would not work with directly.
  2. Migrating from Vendor A to Vendor B is unlikely to significantly reduce the amount of "water" the ethical source movement carries for actors whose ethics we disagree with. For example, GitLab demonstrates sexism.

There is a saying: "There is no ethical consumption under capitalism." This is not an excuse, but to the best of my knowledge there is not an intersectional, community-owned and operated alternative to GitHub or GitLab. It there were, I would be happy to explore, advocate for and perform the work to migrate to such a platform so long as it does not reduce community engagement and is within the movements financial means.

Well...not quite. You don't want ICE using tech right? MS has an ICE contract....

@zspencer
Copy link
Contributor

@robbyoconnor, this reply fails to address my statements in any meaningful way; and simply re-asserts your conclusion. Would you be willing to respond to the comments I made in a meaningful and direct way?

If not, I would request that we close this issue so that we can move forward with the task at hand of withholding the public commons from abusive actors.

Otherwise, the goalposts will continuously shift as we learn more and more about how broadly human rights abusers permeate the technology service provider landscape.

@robbyoconnor
Copy link
Author

All licenses like this will do is create business risks and kill off projects entirely.

@zspencer
Copy link
Contributor

I agree that is a valid risk that we should work to mitigate. It does not appear to be related to the issue at hand, so I appreciate you choosing to close this topic.

I have created the following issue to discuss the relative important of mitigating these risks; as well as what tactics we can evaluate in order to do so: #51

@decentral1se
Copy link

Hey y'all just to mention, that it is important to consider that we shouldn't be on Github. I work-own at https://autonomic.zone and we'd be interested in discussing taking on hosting this organisation over at https://git.autonomic.zone. There are other hosting providers that would work.

@decentral1se
Copy link

Opened #61 to follow up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants