The Github organization

Stream: PhysLean

[Joseph Tooby-Smith]

On GitHub PhysLean currently lives under an 'organization' called 'HEPLean'. This is for historical reasons. But I've been thinking about the possibility of changing it. I think there are essentially four main options:

1. Leave it as it is as HEPLean
2. Change it to something which is specific for example: PhysLeanOrg
3. Creating a general organization like: leanprover-phys-community or leanprover-sci-community and advocate for similar projects to be moved under the same github organization. (May help with long-term maintenance)
4. Advocate for it to be moved under: leanprover-community

Naturally 1 is easiest, and I think 2-4 each have their own advantages and disadvantages. I would be very glad to hear peoples thoughts.

[Alfredo Moreira-Rosa]

If it's just about naming, option 2 should be easy.
Option 3 is challenging but may open new opportunities for funding.
I'm not sure about option 4.

[Fabio Anzà]

I think for now we should leave it as HEPLean. But, the issue at hand is to start collecting all different projects under the same umbrella, to avoid the doubling of efforts and the scattering of intent. In my opinion we should

• Know what are all the active projects
• Talk to their developers/maintainers about synchronizing efforts
• Build an organization for the community, like mathlib did. Doesn't have to be an FRO. Could be as simple as a US 501(c3).
  I've heard about this point from various folks I've talked to, and it looks like people mostly agree that something like this has to happen. And, it will surely help with funding

[Joseph Tooby-Smith]

I had been putting together a list of projects here:

https://github.com/HEPLean/ITPsInPhysicsArchive

(to which PRs are more then welcome). I agree with all the points here. Although I personally would be somewhat against making it anything formal like US 501(c3), basically because I don't think it is necessary, and I strongly suspect the existing leanprover-community isn't registered in formal any way.

(I think we should probably be careful with the distinction between a GitHub organization and an organization as a legal entity, I was not careful in my initial message).

[Fabio Anzà]

Ah, I guess you were talking explicitly about a github organization in the tecnical sense. I interpreted it broadly. I think for this kinds of things we should make a decision based on whatever is less painful. I agree with @Alfredo Moreira-Rosa that if it's just about naming, I'd go with option 2