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

Would you be willing to transfer ownership of this repo to the clj-commons Github organization? #110

Open
jafingerhut opened this issue Nov 6, 2022 · 4 comments

Comments

@jafingerhut
Copy link
Contributor

Matthias:

First, thanks for starting this repo and maintaining it for several years!

I wanted to ask whether you might be interested in transferring ownership of this repository to the https://github.com/clj-commons organization. This is completely up to you, with no pressure from me. It simply seemed to me that perhaps your software development interests may have moved on to other programming languages than Clojure, which the current collection of articles is fairly focused on.

Things that would change:

  • The repo would be accessible under the new URL https://github.com/clj-common/talk-transcripts (but see below about redirects)
  • Others in the clj-commons group would be able to approve PRs and make commits. Likely I would become the primary point of contact for approving future PRs, but that could change over time if others became interested in taking over that role.

Things that would stay the same:

  • The current commit history, issues, and PRs would remain unchanged. Your contributions would remain as they are, and we would be happy to mention you prominently in the README as the originator of this collection.
  • All links to https://github.com/matthiasn/talk-transcripts would be redirected by Github to the new URL above, so that existing links to the current repo will still work.

If you have any questions about this, please ask.

@NoahTheDuke
Copy link

@matthiasn ping

@jiacai2050
Copy link

@jafingerhut I think we can fork this repo now, isn't it the recommended way for open source work?

@jafingerhut
Copy link
Contributor Author

Anyone can fork a public Github repo any time they want, and I have done so long ago in order to create PRs on this repo.

Anyone is free to copy the files and put them elsewhere subject to applicable copyright, licenses, and other intellectual property issues, too.

The contents of all of these transcripts remain public, and any links to them on other web site in the world remain working (which is important), and transitioning this particular repository to a new Github organization would also preserve the property that links to it from elsewhere would be forwarded/translated by Github's site to the new URL.

I do not see my request as urgent in time, or even that it must happen. If another N years goes by and someone (perhaps me) decides they want to make copies of the contents of this repo in another public repo, I do not see any problem with that.

@seancorfield
Copy link

@jiacai2050 See the clj-commons for accepting maintenance of projects: https://clj-commons.org/accepting-projects.html -- transferring is preferred because GitHub will handle redirects to the new repo location.

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

4 participants