[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Committee Role: Helping build the debconf-team

On Thu, Nov 14, 2019 at 10:41:05AM -0500, Sam Hartman wrote:
> >>>>> "Paulo" == Paulo Henrique de Lima Santana <phls@debian.org> writes:
>     Paulo> Everytime we talk about the role of DebConf Committee, there
>     Paulo> is a consensus about: the Committee should solve conflicts
>     Paulo> and keep the environment healthy and nice to everybody.
>     Paulo> So, why you (Daniel) as a DebConf Committee member still
>     Paulo> creating conflicts with us from DC19 local team and make this
>     Paulo> kind of statement: "the local team" try and throw jobs they
>     Paulo> don't want to do "over the fence".
> I heard Daniel differently.
> I heard him making a statement about what he saw the role of the DCC as.
> He specifically focused on the role rather than on any specifics.
> We could have had a discussion about what we want the DCC to do.
> Why is it important to bring it back to specifics?  Why is it important
> to bring it back to past conflicts?

I think the specifics in this case exemplify a general issue, which is
the fact that the global team is understaffed. For exemple, in DC19 the
local team had to put signifficant effort into tasks that could -- and
probably should -- very well be handled by others while the local team
concentrates on the local issues. The later are enough work already.

For example most of my available time was sucked up by:

- seeking international sponsors, many of which are regular sponsors;
  talking to them would have been

- content (sending out CFP, coordinating the reviews, publishing
  schedules etc)

- maintenance of the website

Because I had to work on all that, I kind of alienated myself from most
of the local tasks, to the point that the fact that I live in Curitiba
was pretty much irrelevant most of the time.

So, coming back to the general issue which is the understaffing of the
debconf team, I believe we want the DebConf committee to actively make
sure that we have enough people working on the tasks that don't need
feet on the ground, so that the local team does not get swamped by them.

And FWIW, IMO characterizing the local team attitude as "trying to throw
tasks over the fence" is not fair.

Attachment: signature.asc
Description: PGP signature

Reply to: