I like the idea of a default user namespace, personally I have the feeling that it would make sense and align with user expectations compared to other platforms, let's put it in the 6.0 milestone and discuss later

Actually Duplicate to https://pagure.io/pagure/issue/1133, let's use the other Ticket to further discuss and work on this

Actually Duplicate to https://pagure.io/pagure/issue/1133, let's use the other Ticket to further discuss and work on this

No the personal projects idea was different from what is discussed in #1133

Basically a personal project was a kinda of project that:
- was in the user's namespace
- had PR disabled by default
- had docs disabled by default

Think of it like: you dots project where you store your .vimrc, .mutt,
.zshrc and so on. These are things you want to store in git, put somewhere,
you don't mind having them public, you're not trying to build a community around
them and whose name could easily impact with someone else's.

Hey @pingou I was reading through the topics again today, basically because I was thinking adding some of my repos to the pagure.io instance.
If I understand it right, we already have the option USER_NAMESPACE, which would by default create every new user project in a namespace, identical to the username, but this is disabled for pagure.io but, for example, seem to be active in the code.opensuse.org instance.
I was searching through the issues but couldn't find the reason why pagure.io does not enable this feature?
To the actual topic, the user namespace part seem already to exist and I now also see the differences between this issue and https://pagure.io/pagure/issue/1133. So not a duplicate but still things we should further take into consideration for a 6.0+ release.

Hey @pingou I was reading through the topics again today, basically because I was thinking adding some of my repos to the pagure.io instance.
If I understand it right, we already have the option USER_NAMESPACE, which would by default create every new user project in a namespace, identical to the username, but this is disabled for pagure.io but, for example, seem to be active in the code.opensuse.org instance.
I was searching through the issues but couldn't find the reason why pagure.io does not enable this feature?
To the actual topic, the user namespace part seem already to exist and I now also see the differences between this issue and https://pagure.io/pagure/issue/1133. So not a duplicate but still things we should further take into consideration for a 6.0+ release.

Pagure was built with the idea that the project is the most interesting part not
necessarily the person making it, so there would be no need to associate a
project's url with a person (or group). The USER_NAMESPACE config was added
later per a request to reproduce the now famous github/gitlab user namespacing.

The personal project idea is basically the ability to have projects that leave
under the user's namespace but these projects aren't meant to build a community
around them. So they would not have issue tracking, or no forking. They would be
there as a convenience mechanism to share or store things like .dotfiles, or
some personal ansible playbooks. The type of git repo that won't become a
project and end up in most cases being fairly "personal", thus the name.

The private project idea is a little different, since, iirc and iiuc, it's meant
for projects that are private ie not accessible/visible publicly. This is also a
feature that exists on pagure but has not been activated on pagure.io