From Mark Dain to ~ancarda/vcs-autodiscovery
On Tue Nov 30, 2021 at 12:09 AM GMT, Adnan Maolood wrote: > Just wanted to let you know that I sent a patch to add forge and VCS > meta tags to git.sr.ht, and it was accepted and has been deployed! I > plan on adding support to hg.sr.ht as well. > > I've also added support for forge meta tags to godocs.io to facilitate > linking to the source code for Go files and symbols. Wow that's awesome to hear! Thank you for doing that. Do you want to send a patch to add SourceHut and godocs.io to the IMPLEMENTATIONS file? Or I can add you, I don't mind either way.
From Mark Dain to ~ancarda/vcs-autodiscovery
On Sun Nov 21, 2021 at 7:25 PM GMT, Adnan Maolood wrote: > On Sun Nov 21, 2021 at 2:16 PM EST, Mark Dain wrote: > > I agree. I've changed the RFC from "MUST" to "SHOULD" here, as > > it may be nice to keep the convention of "file" and "dir/", but > > shouldn't be required. > > This could result in inconsistent URLs depending on the implementation, > though. > > One reason we might want to mandate a trailing slash is to avoid > needless redirects for some forges which redirect dir to dir/ (e.g. > SourceForge). It also allows putting something after the end of the > directory path (e.g. /tree/{path}view => /tree/dir/view), but I am not > aware of any forge that would need this.
From Mark Dain to ~ancarda/vcs-autodiscovery
On Sun Nov 21, 2021 at 4:56 PM GMT, Adnan Maolood wrote: > Well, you could append ?dir=1 to the end of the URL, but I don't think > that this would be useful. I agree. I've changed the RFC from "MUST" to "SHOULD" here, as it may be nice to keep the convention of "file" and "dir/", but shouldn't be required.
From Mark Dain to ~ancarda/vcs-autodiscovery
On Sun Nov 21, 2021 at 4:32 PM GMT, Adnan Maolood wrote: > We could have directories not end in "/". It seems that SourceHut, > GitHub, GitLab, and Gitea don't require a trailing slash. That might be > a more elegant solution. My thinking was a trailing slash is a way to know if it's a directory, so there's always a way to detect that. But maybe that isn't so useful
From Mark Dain to ~ancarda/vcs-autodiscovery
On Sat Nov 20, 2021 at 11:38 PM GMT, Adnan Maolood wrote: > Could we get the behavior of the 'path' variable for the root directory > clarified in the RFC? > > My main concern is that some implementations will provide a path of "/", > which could result in a link with too many slashes. (e.g. > https://rfc.example/{path} => https://rfc.example//). This is why I > proposed that the the root directory should be provided as a path of "". Hi, Sorry I thought I had done this, but now I realize we only discussed it. I've put a commit up that clarifies this as an exception, so all other directories should end with "/".
From Mark Dain to ~ancarda/vcs-autodiscovery
Hi, I've pushed up a new version of the RFC that takes into account all the feedback you sent below. Sorry it took so long to do this. Thank you again for writing up your suggestions. I have one question about this part though: > {path} - the path to a file or a directory. Directories paths MUST > end with a trailing slash, except for the root directory, which MUST > be empty. This is to avoid creating links with double slashes. I'm having a hard time understanding this. Why should root be an exception? Do you mean you would prefer this:
From Mark Dain to ~ancarda/vcs-autodiscovery
On Wed Oct 27, 2021 at 1:54 PM BST, Adnan Maolood wrote: > We are looking into an alternative to go-source meta tags for godocs.io. > We think your RFC is a good starting point, but there are some things we > would like to address before adopting it. Hey, I'm glad someone has taken interest in this! I had started working on some implementations... but unfortunately never finished. I had some trouble setting up an instance of SourceHut and that really killed a lot of motivation for me. I like your suggestions and will incorporate them into the RFC. > 3. We would prefer that {} characters are used to delimit variables > instead of the % character, which is a reserved URL character. There is
From Mark Dain to ~sircmpwn/sr.ht-discuss
On Wed Sep 22, 2021 at 1:04 PM BST, Drew DeVault wrote: > The migration path is: > > - All current default ACLs other than "anonymous" permissions are > dropped. > - Any tracker for whom the "browse" permission was set for anonymous > users will default to "public" visibility, others to "unlisted". Can you clarify that task trackers with everything disabled (anonymous, submitter, and account holder) will become unlisted rather than private? It reads that way to me.
From Mark Dain to ~sircmpwn/sr.ht-discuss
On Thu Apr 22, 2021 at 8:22 AM BST, Jeroen Langeveld wrote: > Is there any possibility to integrate with Active Directory at this > moment? Mainly to allow known and authorised colleagues to login to a > private sr.ht instance... SourceHut doesn't support proprietary technology, so I can't see support for Active Directory being merged. Would something like LDAP meet your needs?
From Mark Dain to ~migadu/alps-devel
This commit introduces LibreJS compatible `@license' blocks as per https://www.gnu.org/software/librejs/free-your-javascript.html The magnet URI can be opened in a BitTorrent client to retrieve a copy of the MIT/Expat license. Section 3.2.2.1 from the above link has a list of magnet URIs for various free software licenses. --- themes/alps/assets/compose.js | 4 ++++ themes/alps/assets/helpers.js | 4 ++++ themes/alps/assets/print.js | 4 ++++ 3 files changed, 12 insertions(+) diff --git a/themes/alps/assets/compose.js b/themes/alps/assets/compose.js index 23e67b6..061016e 100644 [message trimmed]