On Thu, Feb 05, 2026 at 01:44:46PM -0800, Vagrant Cascadian wrote:
> On 2026-02-05, Cayetano Santos wrote:
> >>jeu. 05 févr. 2026 at 11:57, Nguyễn Gia Phong <[email protected]> wrote:
> >> On 2026-02-04 at 15:02+01:00, Cayetano Santos wrote:
> >>> mer. 04 févr. 2026 at 11:03, Nguyễn Gia Phong wrote:
> >>> > Relevant to my $dayjob (research on software engineering) and interests,
> >>> > I want to create a team taking care of the following packages modules
> >>> > (with overlapping teams):
> ...
> >>> To me, the idea of teams is building a group of people interested on a
> >>> common subject. The previous list being somehow orthogonal to different
> >>> topics, it is going to be difficult to motivate some other people to
> >>> join such a team based on one’s personal interests.
> ...
> > Teams are positive (we have more than 50 at this point !), and avoiding
> > orphaned packages is a nice initiative. Feel free to propose a pr with a
> > coherent list of modules, including yourself in the corresponding team.
> >
> > Just remember that a single person team has little utility, and you’ll
> > have to gather extra manpower around the team, which will strongly
> > depend on its interest for a larger community.
> 
> While it is not the ideal, as a member of at least two one-person
> teams... even a single-person team has the immediate benefit of getting
> notified when pull requests are submitted in that particular area of
> interest... and to be able to look for issues and pull requests tagged
> with that team... in fact, that latter part would even be useful in some
> cases for some zero-person teams, as ridiculous as that may sound at
> first glance! :)
(...)

Agreed on the notifications being useful. I don't think there's any point 
having a team where there aren't any committers. Technically people can leave a 
review and test the package which I think is useful (not everyone agrees), but 
it still leaves the PR without anyone to actually push it.


> Makes me wonder if any issues or pull requests not covered by any team
> should be tagged "no-team" or some such... as they would at least be
> searchable that way if someone wanted to do some triage on things likely
> to get neglected...
(...)

At least it would be easy to see them.

Steve / Futurile

Attachment: signature.asc
Description: PGP signature

Reply via email to