DomainKey-Signature: a=rsa-sha1; c=nofws; d=toastin.space; h=subject:to
	:cc:references:from:message-id:date:mime-version:in-reply-to
	:content-type:content-transfer-encoding; q=dns; s=ml; b=ZXkngoFX
	xPvxeGifAhz18rb4EH5rSbVNCFfzM0WtA9hDl15Ce6jTfR/cVRsg4mwS27gkQOuu
	njzYZG+pseUSdprgchQXYDq/DiZvjqWh0VYW3JI7nNCnI77FnBtMip3VDCgiC219
	UsM2/cDCU/oF3cTP7GmF+sNXfUquLLGUZ4Y3sMKM/Il7KCmrP/CLTtnQLgfFL3Ch
	tN3U0C4NYbzcfQ1WOtfV1+W15wbXAEpHjIQVZnYYLUCw/Fly2GES8r7yISi1cvjp
	s063+4ue4l7fSa/NFTxGGaDw9syur60YoJhUUxDrmn6T+AEWjhaURuhoa7VYj2lg
	9L2cisNBt5m0ag==
Subject: Re: [alpine-devel] Teams and organisation
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: alpine-devel@lists.alpinelinux.org, Daniel Isaksen <d@duniel.no>
References: <20190301214806.47a05e54@ncopa-desktop.copa.dup.pw>
 <X0NH0pqQNbp4KxGwVG0Vn8SxS6ZzVGgyLPIU1oBkJTew3rJcfgNBPK7fuPAicqZPwBbf3bDLsm3TE2M_qMcVBvOvbWBLuWnMH1DuFu37-oY=@duniel.no>
 <809b52be-9b7a-6e9b-4a57-0ea1c0118954@toastin.space>
 <20190314171131.5afe7af0@ncopa-desktop.copa.dup.pw>
From: Chloe Kudryavtsev <toast@toastin.space>
Message-ID: <7d0e3f9f-8f5a-1926-02c8-4fdee7a614c0@toastin.space>
Date: Thu, 14 Mar 2019 20:16:00 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:66.0) Gecko/20100101
 Thunderbird/66.0
Precedence: list
MIME-Version: 1.0
In-Reply-To: <20190314171131.5afe7af0@ncopa-desktop.copa.dup.pw>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit

On 3/14/2019 12:11 PM, Natanael Copa wrote:
> This has been suggested before. Wilcox had some good points and
> suggestions[1].

I agree with the following points:
- People can often identify with their specific project even moreso than 
with the distribution.
- Having dedicated teams for languages - this isn't necessary, but is 
very useful when there is sufficient interest.

However, I have several issues with the idea being presented there.
Specifically:
- Some level of formality is needed - this helps avoid a bottlenecking 
situation, and enforces separation of tasks (minimizing 
context-switching and thus increasing total throughput).
- A license-oriented team likely isn't needed per-se. We have since 
started using the SPDX license list, so the remaining bits can be 
handled by the core and aports teams (depending on the specifics).

The reality is that that suggestion was made in the middle of 2017, and 
the situation has changed, but it's certainly something to look at.

> And we need this badly. We are not lacking volunteers, but problem is
> that I have become in a position that everything blocks on me. I want
> fix that.

It also means that you (and other core/infra developers) tend to be 
extremely busy.
One of the goals would be to lessen your load (and allow you to, at the 
same time, be more efficient at the things that you *do* still do :) ).

> What would be the simplest way to get this started? We already have a
> semi-team for infra, with Carlo as team lead.
> 
> We could probably also get a docs team running immediately, with Chloe
> as team lead.
> 
> That would be a good start I think.

Currently, the plan (as discussed in #alpine-docs, because that's where 
the conversation happened to have happened) is to have a meeting on 
Sunday, 14:00 GMT.
I'm currently composing a proposed agenda for it.

During it, things such as the initial teams should be decided, after 
which (likely Monday) a final version would be submitted for approval by 
the core team.

Once approval happens, I'll initialize a developer-handbook repository 
(even if it'll likely be a bit until more things get added to it) and 
populate it with everything that'll have been decided during the meeting 
(and potentially revised during the, hopefully short, approval process).

As a side note, I agree with your initial set of teams, though I think 
the core and aport teams should also be made at the start, along with a 
full member listing.


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---