On Mon, 26 Apr 2021 22:09:24 +0900
Alex Shinn <xxxxxx@gmail.com> wrote:

> On Sun, Apr 25, 2021 at 6:57 PM Lassi Kortela <xxxxxx@lassi.io> wrote:
> >
> > > Isn't "just contributing to a Scheme system" or "writing a library for
> > > snow-fort/akku.scm" essentially the "lightweight design process"?
> >
> > Nope, those are missing the social element which is the main ingredient.
>
> FWIW, snow-fort was originally intended to be social, and there
> were hints of this in the original package format (sibling repos and
> ratings), I just haven't had time to implement it.
>
> The traditional package system is an outdated concept.  Issue
> tracking systems are outdated.  We should have "live" packages
> which can have comments, questions, feature requests, patches,
> test cases, bug reports with automated stack traces, benchmarks,
> reviews and ratings tied directly to the code and documentation.
>
> We don't have to program alone anymore.

Can you explain how rating and social aspect would work? I think that you
don't want anyone to modify meta description file to add issues, don't you?
Then how do you think this should work. I really curious, because this sound
interesting, but I don't see how this would possibly work. This would require
to be like distributed network.

--
Jakub T. Jankiewicz, Web Developer
https://jcubic.pl/me