Re: who maintains NSS

Melvin, you (or anyone) can easily contribute to NSS without any sort of
bureaucracy by submitting PRs to the github repo.  You (or anyone) can
see who has been  maintaining NSS, by looking at github blame or at the
assignees/authors of closed PRs.  A simple glance at those sources will
tell you that for several years Alain Bourgeois is essentially the only
person submitting PRs.

On Sat, Oct 28, 2023 at 5:40 AM Melvin Carvalho <melvincarvalho@gmail.com>
wrote:

>
>
> pá 27. 10. 2023 v 17:08 odesílatel Michiel de Jong <
> michiel@pondersource.com> napsal:
>
>>
>>
>> On Fri, 27 Oct 2023 at 16:02, Melvin Carvalho <melvincarvalho@gmail.com>
>> wrote:
>>
>>> I've been asking the question of who maintains NSS since January
>>>
>>> I asked on the chat, I also raised an issue here which was not answered
>>> for several weeks:
>>>
>>>
>>> https://github.com/nodeSolidServer/node-solid-server/issues/1740#issue-1931389217
>>>
>>> A JS solid server and an active maintenance team are crucial for our
>>> project.
>>>
>>> Would anyone in the community be interested in contributing to this
>>> initiative?
>>>
>>> Michiel, can you give a status update please?
>>>
>> Since you asked for my personal opinion here, I'll add it:
>> In 2019, Jackson and I announced EOL for NSS. But then it didn't happen.
>> And I think NSS has been bravely maintained by Alain Bourgeois over the
>> years.
>> Now, however, I think it's finally time to EOL it and move all our
>> efforts to CSS.
>> CSS is not perfect, but it's in TypeScript and the code is cleaner, more
>> performant, and less buggy.
>> We're already seeing developers walk away from solidcommunity.net
>> because it's running NSS which cannot do all the things CSS can.
>> So in my opinion, it's now finally time to:
>> 1) Add Mahdi Baghbani as a sysadmin on solidcommunity.net (sponsored by
>> Ponder Source to contribute to its maintenance during work time)
>> 2) Migrate solidcommunity.net to CSS v7.0.0
>> 3) See if anybody else is still using NSS for anything, warn them about
>> the EOL plans which, four years later than planned, will finally happen
>> now, and help them migrate too.
>> 4) Once everybody has found an alternative to whatever they were using
>> NSS for, we set the GitHub repo to 'archived' and update the readme to say
>> the project is no longer maintained, pointing people to
>> https://solidservers.org/#table to help them switch to one of the other
>> five Solid server implementations.
>>
>> That's my personal answer to your question, since you asked. Other people
>> may have different answers! :)
>>
>
> By the way you havent answered the question.  I have over the last 10
> months asked a simple question as to who is maintaining one of our main
> servers.
>
> I have sent X chat messages, Y emails, Z issues over 9 months to find
> out.  9 months!
>
> https://github.com/nodeSolidServer/node-solid-server/teams
>
> This team is only visible to insiders.
>
> It's impossible for the grass roots to participate in such a ridiculous
> bureaucracy.  Something needs to change, and quickly.
>
> Timbl:  please can you help here.  Im not asking for the world.  Just to
> find out who is looking after something as a means to help use and
> contribute to the software.  It should not take 9 months.
>
>
>>
>>
>> Cheers,
>> Michiel
>>
>>
>