Project status?

[lmmx]

A lot of people have been talking about the recent archival of the jemalloc/jemalloc parent repo, and I saw some suggestion that development (having been maintained within Meta since 2017) had moved to this repo, but I can see that it’s not set up as such exactly (e.g. issues are disabled). Can anyone give an update on the project status? @interwq perhaps?

[guangli-dai]

This is Meta's fork of jemalloc and the team is still actively developing here. "Issues" are not enabled because Github doesn't allow its enablement on a forked repo. Please use "Discussions" until issues are enabled.

[asmeurer]

Unfortunately it's almost never a good idea to use GitHub's "fork" feature for an actual OSS "fork". The feature is not designed for it.

Some other reasons "fork"ing is a bad idea:

• there is now a permanent banner at the top of this repo telling how many commits ahead of the "upstream" it is
• the upstream can mess with its forks in certain ways. See for instance https://docs.github.com/en/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets#about-push-rulesets-for-forked-repositories. I don't know if that's a concern here, but it just shows how the GitHub "fork" feature isn't really designed for OSS "forks".
• GitHub search does not include forks in search results by default (see https://docs.github.com/en/search-github/searching-on-github/searching-in-forks)

The only upsides to forking with a "fork" are it shows a little link back to the original repo, and it makes it possible to make PRs across the repos.

[asmeurer]

With that being said, you should be able to enable issues on a forked repo in the settings.

[guangli-dai]

"Issues" are enabled now.

[06kellyjac]

The parent project didn't require signing the Meta CLA. Can this repository use DCO instead?