Determine how to remove the many current members of the instruct-lab repo who are only members due to the project being private and those folks participating in an InnerSourcing exercise

instructlab / community

InstructLab Community wide collaboration space including contributing, security, code of conduct, etc

Apache License 2.0

70 stars 40 forks source link

Determine how to remove the many current members of the instruct-lab repo who are only members due to the project being private and those folks participating in an InnerSourcing exercise #65

Closed joesepi closed 5 months ago

joesepi commented 6 months ago

Figure out how to do it. <- @joesepi Check with Leslie that this has been communicated to RH

lhawthorn commented 6 months ago

The plan of record is to work with @mairin on the internal communication to Red Hat employees who have worked on our InnerSourcing effort so that no one is surprised. Will update this issue when communication has been sent.

lhawthorn commented 5 months ago

We still have more than 3,000 users on this repository and Red Hat's internal InnerSourcing project has closed. Can we begin to remove people from the repo now?

I assume we have some folks still working on PRs in progress, but that's definitely not all 3,000 people.

@joesepi Is there any kind of information I can track down for you so we can get the list of project members down to where it should be for launch?

lhawthorn commented 5 months ago

@ckadner has offered to help with this process.

ckadner commented 5 months ago

@lhawthorn @jjasghar

I am thinking of writing a script that will return a list of inactive "labrador-lovers" to not boot anyone who has contributed or is otherwise still active:

retrieve the list of 3010 labrador-lovers
exclude the 6 labrador-lovers/maintainers
exclude anyone who created an issue or opened a PR on CLI, taxonomy, community, ... GH repos
exclude anyone recently added (who did not have a chance to submit a PR yet, 14 days maybe)
I could also exclude anyone who commented on issues
I could also exclude anyone who forked the taxonomy repo

This should result in a list of "labrador-lovers" who have not engaged with the instruct lab project on Github -- should be more than 2000 people.

We could try to map their emails (someone from Red Hat did that before) and/or Slack IDs and let them know before booting them, if we feel strongly about that.

bjhargrave commented 5 months ago

exclude anyone who created an issue or opened a PR on CLI, taxonomy, community

I think we just need to consider open issues or PRs since, once public, those associated with closed issues and PRs can again see them.

I could also exclude anyone who commented on issues

Again I would say only for open issues or PRs.

I could also exclude anyone who forked the taxonomy repo

"If you remove a person’s access to a private repository, any of their forks of that private repository are deleted."

This is a more severe effect, but I still think we only exclude those with open issues or PRs.

lhawthorn commented 5 months ago

We are informing Red Hatters today - per plan of record - that we will begin removing them from the repositories in anticipation of public launch.

I will work with @jjasghar on this item so that IBM is not paying the bill for 3400+ people who engaged in our InnerSourcing effort to still be members of the instruct-lab repo when it is not relevant anymore.

See also we plan to rename instruct-lab to instructlab so I am assuming that the instruct-lab repo would remain in state = private and thus keep incurring costs to have those 3400+ people on it. Related issue #157

jjasghar commented 5 months ago

This first pass at 2000+ people is running as I type this. (it should be done in about an hour from now)