This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-14
Channels
- # announcements (10)
- # architecture (4)
- # atom-editor (1)
- # babashka (53)
- # babashka-sci-dev (118)
- # beginners (91)
- # biff (12)
- # calva (19)
- # clara (13)
- # clerk (20)
- # clj-commons (25)
- # clj-kondo (6)
- # cljdoc (19)
- # cljs-dev (3)
- # clojars (2)
- # clojure (71)
- # clojure-art (2)
- # clojure-europe (68)
- # clojure-nl (1)
- # clojure-norway (6)
- # clojure-uk (3)
- # clojured (19)
- # clojurescript (34)
- # clr (19)
- # cursive (11)
- # emacs (14)
- # fulcro (3)
- # helix (2)
- # holy-lambda (2)
- # honeysql (27)
- # hyperfiddle (39)
- # malli (2)
- # off-topic (83)
- # polylith (4)
- # rdf (22)
- # re-frame (20)
- # reitit (4)
- # rewrite-clj (14)
- # shadow-cljs (17)
- # slack-help (2)
- # tools-deps (45)
- # xtdb (3)
I'd like to start looking into moving clojure-humanize under clj-commons; as i understand it, the first step is to fork the existing repo under clj-commons? To do so, I need to be added as a member, or some existing member could do it and add me to the forked project.
If possible, it's better to transfer the repo, so that GitHub provides redirects on the old location.
If no current maintainer has permission to transfer the repo, then we'd have to fork it into clj-commons -- but we should try to reach the various current maintainers to double-check first.
(and if we have to fork it, it would be nice for someone to then update the README in the original repo to add a note stating the clj-commons version is the definitive, maintained version going forward)
'k... when did you last email <mailto:[email protected]|[email protected]> about possibly transferring the repo?
I don't see the settings wheel here: https://github.com/trhura/clojure-humanize so I assume I don't have admin rights either
Well, try emailing them directly and give them a week to respond, just to be polite.
Here's the discussion thread from back in October 2022: https://github.com/trhura/clojure-humanize/pull/28
Yeah, so he was active in October... I would directly email him, in case he has notifications from GH suppressed (which we've seen is fairly common when maintainers decide to "abandon" projects).
(I have set a reminder to revisit this on Monday)
Thura Hlaing has been in contact with me; they're attempting to xfer the original repo to me so that I can xfer it to clj-commons.
Great news! Let us know if you need any additional help.
Ok, Thura xfered the repo to me, and I'm ready to xfer it to clj-commons, but I don't seem to have the necessary access.
> To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.
Sent you an invite to join the org. Once you're in, I'll make sure you have the right permissions.
I suspect it will xfer in as a private repo, and we can make it public once it is done.