Email list hosting service & mailing list manager

forge.scheme.org or sourcehut.scheme.org Amirouche (25 Apr 2021 18:51 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Arthur A. Gleckler (25 Apr 2021 18:56 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Amirouche (25 Apr 2021 19:27 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Marc Feeley (25 Apr 2021 19:43 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Amirouche (25 Apr 2021 19:59 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Marc Feeley (25 Apr 2021 20:36 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Lassi Kortela (25 Apr 2021 21:27 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Amirouche (26 Apr 2021 07:36 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Lassi Kortela (26 Apr 2021 07:57 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Amirouche (26 Apr 2021 07:29 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Amirouche (21 May 2021 09:52 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Amirouche (01 Aug 2021 07:25 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Vasilij Schneidermann (01 Aug 2021 07:56 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Amirouche (02 Aug 2021 06:34 UTC)
Re: forge.scheme.org or sourcehut.scheme.org Lassi Kortela (06 Aug 2021 10:28 UTC)

Re: forge.scheme.org or sourcehut.scheme.org Amirouche 26 Apr 2021 07:29 UTC

On 2021-04-25 22:36, Marc Feeley wrote:
> I think another pro for sourcehut is that it is small/minimal, which
> is something I appreciate.

It is minimal... so far. The project is still alpha and in development.
It should be easier to navigate the codebase for me, and probably others
since it is mostly Python.

> However, if this source code hosting
> service on scheme.org is meant to be used for hosting portable Scheme
> code and libraries,

I will prefer to not officially add that constraint. #scheme on freenode
does not mention it, but most people in there have a focus on
portability,
or interop.

> then we should make sure it is something library
> users/authors will be comfortable using.

Yes.

> One reason why I like the idea of a source code hosting service on
> scheme.org is that it would allow a simple integration with
> try.scheme.org (by avoiding CORS related issues).

Indeed.

> However, this would
> imply that all code hosted there is “trusted”.

That will be a lot of work, even with account creation safe-guard.

> Will there be a mechanism to control account creation and what
> will be required to be “approved”?

Yes, I need to investigate this. That is especially a problem regarding
the paste service and the build service that may be used to mine crypto.

I would prefer to have no safe-guard, but keep an eye on usage, at least
to
get started.

I am not sure how upstream handle paste service, but the build service
will require
payment soon, among other things because it is above the average
compared
to the competition, but also to avoid cryptominers.

>
> Marc
>
>
>
>> On Apr 25, 2021, at 3:59 PM, Amirouche <xxxxxx@hyper.dev> wrote:
>>
>> On 2021-04-25 21:43, Marc Feeley wrote:
>>> How does sourcehut compare to gitlab (which would be another option)?
>>> Marc
>>
>> Sourcehut, pros:
>>
>> - Use Python
>> - Simple UI/UX
>> - Mailing list support
>> - Build support
>>
>> Sourcehut, cons:
>>
>> - No social features except the ML (no stars, no watch, no fork
>> button)
>> - No review UI except ML
>> - It also rely Go
>>
>> gitlab, pros:
>>
>> - social features
>> - review UI
>>
>> gitlab cons:
>>
>> - Use mostly ruby, and I have zero ruby experience, and everybody told
>> me it is pain to host.
>>
>> I have not a lot of experience with gitlab, I find their GUI too
>> confusing.
>>

--
Amirouche ~ https://hyper.dev