| 13 Jul 2022 |
 infinisil | Instead the article suggests to try to first reach consensus, but if it can't be reached, do a vote (e.g. 2/3 majority) | 16:55:29 |
| infinisil | Here's a quote from the article:
-
A proposal is made, the group tries to reach consensus. Modifications may be made to the proposal. Consensus may be reached, or it may be decided that no consensus is necessary in this case – a few members of the group can implement the decision without bothering the others.
-
If, after reasonable attempts by all sides to accommodate each other have been made, no consensus is reached, a vote is taken using the agreed voting method. The facilitator will decide the right moment for the vote. The right moment can be the subject of debate, and people may raise objections, but if you have a facilitator who can be held accountable then they need to be trusted to make the final decision. Making a group decision on how to make a group decision when in the middle of a contentious meeting is not a viable option.
-
The group considers how those who lost the vote can be accommodated – this may have been dealt with already in the stage 1 discussions but it is often worth raising again after the vote.
-
The debate between differing views continues over the long term, and decisions can always be re-considered if appropriate.
| 16:56:01 |
| infinisil | This sounds very reasonable and I think it's a good idea to adapt the workings of this team to this strategy | 16:56:57 |
 Sandro | In reply to @infinisil:matrix.org
Instead the article suggests to try to first reach consensus, but if it can't be reached, do a vote (e.g. 2/3 majority) Isn't that how it always works? | 17:07:51 |
| infinisil | Sandro: I think the difference is that in this case a vote is only used as a last-resort option when consensus fails, whereas usually a vote is used as the default mechanism | 17:09:36 |
 Rick (Mindavi) | Consensus should be the goal and voting is a type of making a compromise when you follow that | 17:11:08 |
| Sandro | to much bureaucracy for me | 17:14:29 |
| infinisil | A necessary evil for such a team! | 17:17:14 |
| Sandro | yeah, maybe. Coudln't join the meeting because I had work to do | 17:18:34 |
| infinisil | I would've liked to keep voting out of this, because it comes with a lot of problems, but I guess it's fine if it's only used as a last-resort | 17:19:03 |
 problems | i think the big takeaway i have from the article is that no matter what decision-making process you use, the decision doesn't need to be final, it can be valuable to keep it an open conversation even after a plan of action is decided | 17:20:46 |
| Rick (Mindavi) | I also think that requiring some technical implementation to go with your arguments helps weed out at least impossible or very impractical things | 17:22:08 |
|  mkaito left the room. | 17:23:46 |
| 14 Jul 2022 |
 tomberek | infinisil: Requesting to join the team:
- motivation: Unify the disparate ways package sets are defined, improve quality and maintainability of Nixpkgs, participate in large-scale improvements to Nixpkgs.
- github username: tomberek
- sponsored by Flox
- best times would be apx 1800-0200 UTC Wed-Sun
| 16:36:53 |
| 18 Jul 2022 |
| infinisil | tomberek: Thanks, Request accepted! | 15:20:38 |
| infinisil | tomberek: From your availability, it looks like the current time of 15:00 UTC doesn't work for you right? Moving it to 18:00 UTC is quite late though, that would be 20:00 for most European people | 15:22:07 |
|  Andreas Schrägle left the room. | 15:31:34 |
| infinisil | For transparency, I am currently contracting part-time (25%) for Flox (also did on and off in the past). My past work for Flox is where a part of the motivation for an architectural nixpkgs redesign comes from, since they're heavy users of nixpkgs and have run into problems with its inconsistencies | 15:33:26 |
| infinisil | My time on this team however is sponsored by Tweag, and all my opinions are my own, I started this team from my own motivation, it's not something Tweag asked me to do :) | 15:34:46 |
| infinisil | Having worked with tomberek in the past I think he's a good fit for the team from his experience and motivation for Nix and nixpkgs :D | 15:36:02 |
| infinisil |
- Added an entry for tomberek to https://github.com/nixpkgs-architecture/team-log
- Added to the current team list: https://github.com/nixpkgs-architecture#current-team
- Invited to the github organization
| 15:40:57 |
| infinisil | The team is still a bit shorthanded though, anybody considering to join? Alternatively, do you have anybody else you'd like to see on the team? | 15:43:04 |
| problems | i'm considering joining but not sure what i can commit to atm | 15:50:00 |
 K900 | Same | 15:57:03 |
| K900 | I've got like negative free time | 15:57:13 |
| K900 | Realistically | 15:57:16 |
| infinisil | Awesome! Some commitment is required, but as long as you're responsive and can keep in touch with the team it should be fine | 16:05:02 |
| infinisil | Feel free to hang around and apply to the team when you feel like it :) | 16:06:16 |
|  ryantm joined the room. | 16:34:14 |
|  Robert Hensing (roberth) joined the room. | 16:41:16 |
