Re: Introducing Reasonable Sourcery: a Guile/Guix hackers R&D cooperative

Dear Rutger and guixers. 

>> Sadly, I am not coder at all and more than just new in Guix.

> I hope you feel welcome anyway.

Yes, thanks a lot. :)

>> However, I do have some experience designing systems<>human
>> interaction and so I can help a tad with this. ;)

> Undoubtedly help is always welcome.

And I can certainly help with the design of the website and the 
support
options, be those options directly to the project and/or 
contracting
work from those who maintain and use the project. 

>> What I am not seeing here is how the website governance and 
>> operations
>> are defined. Who are the people that decides? How do they do 
>> it? Who
>> are the ones that implement those decisions?

> See
> https://codeberg.org/guix/guix-consensus-documents/src/branch/main/001-gcd-process.md

Ah, great, thanks a lot. /\

Reading it -and a tad more- I understand that the Guix Consensus
Document (GCD) process is used when significant enough changes 
affect
the project. When not, the rules are in the contributing section 
of the
manual
(https://guix.gnu.org/manual/devel/en/html_node/Contributing.html). 

The criteria for defining between both is: 

--8<--------------- cite ---------------start------------->8---

A change may be deemed significant when it could only be 
reverted at a
high cost or, for technical changes, when it has the potential 
to
disrupt user scripts and programs or user workflows. Examples 
include: 

+ changes that modify user-facing interfaces that may be relied 
on
  (command-line interfaces, core Scheme interfaces);
+ big restructuring of packages;
+ hard to revert changes;
+ significant project infrastructure or workflow changes;
+ governance or changes to the way we collaborate.

--8<--------------- cite ---------------end--------------->8---

I'm very new here, so in order to be helpful and learn the 
rules/
customs, may I ask if changes to the website impacting money are
significant enough or not? (I have an idea but prefer not to 
impact
other people's ideas). 


Other than that, I will gladly read the documentation available 
and
schedule some co-design (and research, if needed) sessions with 
whomever
are moving the website project ahead. :) 

Best...





PD: the definition of consensus used in these documents sounds 
more to
what I know as consent (absence of objections, understood as 
danger to
the people and/or project mission), but that could to be 
discussed in
other places/times. I hereby declare openly that I do have a 
sociocratic
background, just to be clear. ;D 



-- 
eduardo mercovich

 Donde se cruzan tus talentos 
 con las necesidades del mundo, 
 ahí está tu vocación. 
 (Anónimo)