4 ms·

Congrats on the milestone. This is a huge boon to the open source community. I love the pricing model. Are there any plans or ideas for a migration path from G

Congrats on the milestone. This is a huge boon to the open source community. I love the pricing model. Are there any plans or ideas for a migration path from GitHub to sir.ht? I would imagine that if there was a way to transfer issues and discussions it would encourage more users to make the switch. Here's one data point for you: zig programming language. Influencing factors: * If we had syntax highlighting in the file browser, that would be a win over GitHub, which insists that there be "hundreds of GitHub repositories" before accepting a syntax highlighting pull request for a new language. I could imagine it would be reasonable to support "repository-local" highlighting configuration. * Transferring existing content as mentioned above. It would be unwise for us to give up all the issues and discussion. * The fact that the build service supports FreeBSD is already a win. However, to switch from Azure DevOps we would lose Windows builds. Is that ruled out due to the open source nature of sr.ht, or is that planned? Related, it would be attractive if sir.ht offered more architectures, e.g. i386, ARM, RISC-V (I believe this was mentioned but I could not find it in the docs)

Sir_Cmpwn 8y ago
>* If we had syntax highlighting in the file browser, that would be a win over GitHub, which insists that there be "hundreds of GitHub repositories" before accepting a syntax highlighting pull request for a new language. I could imagine it would be reasonable to support "repository-local" highlighting configuration. We use pygments, so patches to pygments would make it to sr.ht's syntax highlighting. >* Transferring existing content as mentioned above. It would be unwise for us to give up all the issues and discussion. Planned. Also planned to let you sync between both. >* The fact that the build service supports FreeBSD is already a win. However, to switch from Azure DevOps we would lose Windows builds. Is that ruled out due to the open source nature of sr.ht, or is that planned? Related, it would be attractive if sir.ht offered more architectures, e.g. i386, ARM, RISC-V (I believe this was mentioned but I could not find it in the docs) Eventually users will be able to add custom base images, which will permit the use of Windows (if you can get an sshd running there, at least). As for multi-arch, experimental support for aarch64 is there, and by the end of the year I expect to have RISC-V builds backed by HiFive hardware.
- greglindahl 8y ago
  > We use pygments, so patches to pygments would make it to sr.ht's syntax highlighting. I really appreciate this response! That encourages improvements that benefit everyone, not just sr.ht users.
- jancsika 8y ago
  > Eventually users will be able to add custom base images, which will permit the use of Windows (if you can get an sshd running there, at least). msys2 has an sshd. I use it on a Windows VM runner with Gitlab CI. It's not easy to set up but it can be done.
  - detaro 8y ago
    Microsoft has ported OpenSSH, at least on Windows 10 you can install it as a Windows feature, or pull it from GitHub https://github.com/PowerShell/Win32-OpenSSH/releases https://github.com/PowerShell/Win32-OpenSSH/releases
    - kodablah 8y ago
      I have also successfully run it from WSL
- mikepurvis 8y ago
  Nonetheless, it'd be nice to have some way of plugging in more of this kind of functionality at the instance, user, and possibly repo levels. Obviously syntax highlighting is one use case, but some others: - Sophisticated cross-referencing tools like Kythe and SourceGraph - Linking stdlib functions and imports to public documentation, like cppreference.com, python.org, etc. - Linking ticket/user names to my non-srht bug tracking tool (especially JIRA, but there are lots of possibilities). - Linking to public or self-hosted generated API docs (doxygen, swagger, sphinx, etc). - Linking to info pages generated from metadata-type files such a PKG-INFO (for example containing dependency tree information). - Propagating back information gathered from build or test runs, for example highlighting areas missing test coverage, or which are "hot" from a perf point of view. Only some of these would be appropriate to go into the mainline version of the tool, which is why it's important to support plugging in these capabilities for the users which need/want them.
mrec 8y ago
> I love the pricing model. I'm sure it's lovely, but where is it? I can't see any mention of pricing in the blog entry, or in https://meta.sr.ht/ https://meta.sr.ht/, and the top hit in Google for "sr.ht pricing" is... your comment.
- climb_stealth 8y ago
  At this point you have to be signed in to see it. See this comment for a screenshot and details: https://news.ycombinator.com/item?id=18460244 https://news.ycombinator.com/item?id=18460244

Sir_Cmpwn 8y ago

>* If we had syntax highlighting in the file browser, that would be a win over GitHub, which insists that there be "hundreds of GitHub repositories" before accepting a syntax highlighting pull request for a new language. I could imagine it would be reasonable to support "repository-local" highlighting configuration. We use pygments, so patches to pygments would make it to sr.ht's syntax highlighting. >* Transferring existing content as mentioned above. It would be unwise for us to give up all the issues and discussion. Planned. Also planned to let you sync between both. >* The fact that the build service supports FreeBSD is already a win. However, to switch from Azure DevOps we would lose Windows builds. Is that ruled out due to the open source nature of sr.ht, or is that planned? Related, it would be attractive if sir.ht offered more architectures, e.g. i386, ARM, RISC-V (I believe this was mentioned but I could not find it in the docs) Eventually users will be able to add custom base images, which will permit the use of Windows (if you can get an sshd running there, at least). As for multi-arch, experimental support for aarch64 is there, and by the end of the year I expect to have RISC-V builds backed by HiFive hardware.

greglindahl 8y ago
> We use pygments, so patches to pygments would make it to sr.ht's syntax highlighting. I really appreciate this response! That encourages improvements that benefit everyone, not just sr.ht users.
jancsika 8y ago
> Eventually users will be able to add custom base images, which will permit the use of Windows (if you can get an sshd running there, at least). msys2 has an sshd. I use it on a Windows VM runner with Gitlab CI. It's not easy to set up but it can be done.
- detaro 8y ago
  Microsoft has ported OpenSSH, at least on Windows 10 you can install it as a Windows feature, or pull it from GitHub https://github.com/PowerShell/Win32-OpenSSH/releases https://github.com/PowerShell/Win32-OpenSSH/releases
  - kodablah 8y ago
    I have also successfully run it from WSL
mikepurvis 8y ago
Nonetheless, it'd be nice to have some way of plugging in more of this kind of functionality at the instance, user, and possibly repo levels. Obviously syntax highlighting is one use case, but some others: - Sophisticated cross-referencing tools like Kythe and SourceGraph - Linking stdlib functions and imports to public documentation, like cppreference.com, python.org, etc. - Linking ticket/user names to my non-srht bug tracking tool (especially JIRA, but there are lots of possibilities). - Linking to public or self-hosted generated API docs (doxygen, swagger, sphinx, etc). - Linking to info pages generated from metadata-type files such a PKG-INFO (for example containing dependency tree information). - Propagating back information gathered from build or test runs, for example highlighting areas missing test coverage, or which are "hot" from a perf point of view. Only some of these would be appropriate to go into the mainline version of the tool, which is why it's important to support plugging in these capabilities for the users which need/want them.

mrec 8y ago

> I love the pricing model. I'm sure it's lovely, but where is it? I can't see any mention of pricing in the blog entry, or in https://meta.sr.ht/ https://meta.sr.ht/, and the top hit in Google for "sr.ht pricing" is... your comment.

climb_stealth 8y ago
At this point you have to be signed in to see it. See this comment for a screenshot and details: https://news.ycombinator.com/item?id=18460244 https://news.ycombinator.com/item?id=18460244