Set up a .github repository on GitHub

Let's set up a GitHub config repository at .github : https://help.github.com/en/github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization

Then we can:

• Copy CODE_OF_CONDUCT
• Merge FUNDING.yml from https://github.com/torproject/tor/pull/1482
• Edit CONTRIBUTING
• Link SECURITY to our security page
• Link SUPPORT to our support page

changed milestone to %Tor: unspecified

added 043-deferred component::core tor/tor milestone::Tor: unspecified points::1 priority::medium reviewer::nickm severity::normal status::needs-review tor-github type::task labels

I added https://github.com/torproject/.github and gave the network team push access.

People can now submit pull requests for the files listed above.

https://github.com/torproject/.github/pull/1

Trac:
Status: new to needs_review

This page is supposed to be "global" and be informative about all Tor-related projects we have on github.com/torproject right?

Replying to ahf:

This page is supposed to be "global" and be informative about all Tor-related projects we have on github.com/torproject right?

Replying to ahf:

This page is supposed to be "global" and be informative about all Tor-related projects we have on github.com/torproject right?

Yes, it's global.

So before we merge, we should:

• check FUNDING with Sarah

And after we merge, we can add other projects to:

• CONTRIBUTING
• SECURITY
• SUPPORT (Or we could ask them to review this pull request, and add commits. But that might get messy.)

I asked for some specific changes to CONTRIBUTING and SUPPORT to allow multiple projects.

Trac:
Status: needs_review to needs_revision

I requested a new URL for the FUNDING section after talking to Sarah.

All 0.4.3.x tickets without 043-must, 043-should, or 043-can are about to be deferred.

Trac:
Keywords: N/A deleted, 043-deferred added

Trac:
Milestone: Tor: 0.4.3.x-final to Tor: unspecified

Trac:
Status: needs_revision to needs_review

Trac:
Reviewer: N/A to catalyst

Thanks! It looks like all of the outstanding comments have been addressed. I don't see any obvious problems. I'm not very familiar with the functioning of the .github repository. It seems that we can't really preview its effect on how other repositories in the org look, so we might have to merge it to see?

Trac:
Status: needs_review to merge_ready

Replying to teor:

I added https://github.com/torproject/.github and gave the network team push access.

People can now submit pull requests for the files listed above. Just checking: the github.com copy is authoritative and there is no git.torproject.org repository?

Replying to catalyst:

Replying to teor:

I added https://github.com/torproject/.github and gave the network team push access.

People can now submit pull requests for the files listed above. Just checking: the github.com copy is authoritative and there is no git.torproject.org repository?

.github is a GitHub-specific configuration repository.

So I didn't set up a canonical repository on git.torproject.org, and I don't think we need one.

Replying to teor:

Replying to catalyst:

Replying to teor:

I added https://github.com/torproject/.github and gave the network team push access.

People can now submit pull requests for the files listed above. Just checking: the github.com copy is authoritative and there is no git.torproject.org repository?

.github is a GitHub-specific configuration repository.

So I didn't set up a canonical repository on git.torproject.org, and I don't think we need one. Thanks!

Given that this change affects more than the network team, maybe we should ask other teams for objections before merging?

Sure, let's send out an email to tor-project, or the internal list?

It's a shame we can't show people a preview.

Replying to teor:

Sure, let's send out an email to tor-project, or the internal list? I'd suggest the internal list, at least initially.

It's a shame we can't show people a preview. Yeah.

Replying to teor:

Sure, let's send out an email to tor-project, or the internal list? Sent an email to the internal list a little while ago.

Trac:
Status: merge_ready to needs_information

Replying to teor:

I asked for some specific changes to CONTRIBUTING and SUPPORT to allow multiple projects.

It's still not clear that the Tor GitHub has multiple projects and teams.

Let's add a sentence at the start that says we have multiple teams, and link to the list of teams on our wiki: https://trac.torproject.org/projects/tor/wiki/org/teams

After this PR merges, other teams can:

• add their own sections to CONTRIBUTING and SUPPORT, or
• override CONTRIBUTING and SUPPORT in their own repositories.

Trac:
Status: needs_information to needs_revision

Trac:
Status: needs_revision to needs_review

Trac:
Reviewer: catalyst to N/A

Trac:
Reviewer: N/A to nickm

I think the license file is wrong, it says: "Copyright (c) 2019, Tor Project — Unofficial repositories"

Maybe we want to delete it, or copy the one from the tor repository?

Good catch! The license file isn't part of this PR, though; it looks like github provided it with the initial repository.

Given the history of this ticket, I think our best bet is for me to raise this for more general discussion again and propose a way forward. Namely, I think we should merge the PR, and then fix up whatever remaining issues we find.

I'll bring this up at the all-hands on wednesday and propose that we go ahead that way.

Some issues I would fix post-merge are:

• Stop recommending trac as a support forum.
• Explicitly list which repositories are "owned"/maintained by which teams, with a table or list covering every repo we have.

Sent an email to tor-internal@, giving a last chance to object before we merge, and asking whether we shouldn't just give ownership of this component to the web team.

changed time estimate to 8h

moved to tpo/core/tor#32335 (closed)