On Thu, Aug 11, 2022 at 12:57:15PM +0200, hellekin wrote:
> Note that this kind of project -- figuring a way to add SH to SH, ahem,
> SourceHut to Software Heritage -- is probably something that can get
> traction and funding from the upcoming NGI Zero Foundation fund. As previous
> NGI Zero funds, it will be something like 25-50K per iteration, with a
> maximum of 200,000 € per project (either SH). So if someone wants to pick
> this up, you're welcome to follow up here since it's already documented with
> the Software Heritage.

We've used in the past a number of (cascading) grants, including some
from NGI Zero, to outsource development of Software Heritage adapters to
technologies we didn't have in-house expertise about. See:
https://www.softwareheritage.org/grants/ . I confirm they could work
very well, but note that the funding is only half of the story. One also

On Mon, Aug 08, 2022 at 10:55:05AM +0200, Drew DeVault wrote:
> Such a feature is not entirely trivial for SourceHut, as we don't
> provide a list of all "public" repositories for privacy reasons -- if
> you don't know someone's username, you cannot find their repositories.

Understandable.

As a FOSS developer myself I guess I'd like to be able to configure this
(all repos / individual repos publicly listed or not), but as a default
yours totally make sense.

> However, we do have the project hub, which provides an index of all
> public "projects" (distinct from repos), which themselves may contain
> git or hg repositories.

Thanks Hellekin for starting this thread and Cc:-ing me.

On Sat, Aug 06, 2022 at 01:00:57PM +0200, hellekin wrote:
> I know the Software Heritage project (Zack Cced) exists and will probably
> benefit in a way from this situation if it has the capacity to host that
> many repositories. The Register article says that Gitlab could save a
> million dollar a year, so this service to keep less used source code
> available to the public is not something easy to replace.

As Bastien pointed out, we do not aim to be a primary hosting place for
source code, but you're totally right that, as part of our mission, we
do want to archive in the long-term as much FOSS source code as we can
manage.