Clone

HTTPS: git clone https://vervis.peers.community/repos/yEzqv

SSH: git clone USERNAME@vervis.peers.community:yEzqv

Branches

master

19.mdwn

[[!template id=ticket class=task assigned=fr33domlover done=yes]]

[[!meta title=“Consider putting both repos and projects under users”]]

Issue

In most cases, people have single-repo projects. And these repos may have issues, snippets and wiki pages attached. This use case must work without any added inconvenience! This includes:

Convenient URLs
Quick transparent management without touching the “project” concept
Friendly transition to multi-repo projects

Idea: Put repos right under users. Then a repo URL will look like /u/john/r/myrepo and a project URL like /u/john/p/myproj. For single-repo projects, a URL like /u/john/r/myrepo/issues can display the issue tracker for a project attached to the repo. The same page is then also available at /u/john/p/myrepo/issues. Then, if more repos are added to the project, both URLs continue working and you don’t need to worry about fixing URLs everywhere they’re hardcoded (e.g. in your README).

Progress

I moved repos to be right under users. But project access still happens just via u/?/p/?, i.e. issues would be accessed by specifying the project name in the URL.

So I need to make r/?/issues work too, if I decide I like the idea.

Result

Closing for now to clear the view. I’ll handle the project related URL issues when I start adding project features.