Hi,

while I contacted the release team previously[0] there was no response
so far.  I tried to establish this first contact since I consider the
release team of really high relevance.  Meanwhile I have added some
more information to my contact mails including advertising a DebConf
event (see below).  I also added some question and tried to keep every
team member in CC.  I'd be really happy if you would find some time
to answer my questions at the end of this mail (preferably in public
on the list but private answers are fine as well.

I'd like to officially contact all our teams to learn about potential
issues that might affect your work.  I would love to learn how you
organise / share your workload.  If you do some regular meetings - be it
on IRC, video conference or whatever I'm interested in joining one of
your next meetings.

Like previous DPLs, I'm open to any inquiries or requests for
assistance. I personally prefer public discussion whenever possible, as
they can benefit a wider audience. You can find a list of contact
options at the bottom of my page on people.d.o[1].

I prefer being offline when I'm away from my keyboard, so I don't carry
a phone. In urgent situations, I can provide the number of my dumb
phone, though it may not always be within reach. Feel free to ping me
via email if I don't respond promptly to ensure I address your concerns.

Please let me know whether I can do something for you.  I'm fine joining
your IRC channel if needed but please invite me in case I should be
informed about some urgent discussion there since I normally do not lurk
on this channel.

I'd also like to inform you that I've registered a BoF for DebConf24 in
Busan with the following description:

  This BoF is an attempt to gather as much as possible teams inside
  Debian to exchange experiences, discuss workflows inside teams, share
  their ways to attract newcomers etc.

  Each participant team should prepare a short description of their work
  and what team roles (“openings”) they have for new contributors. Even
  for delegated teams (membership is less fluid), it would be good to
  present the team, explain what it takes to be a team member, and what
  steps people usually go to end up being invited to participate. Some
  other teams can easily absorb contributions from salsa MRs, and at some
  point people get commit access. Anyway, the point is that we work on the
  idea that the pathway to become a team member becomes more clear from an
  outsider point-of-view.

I'm sure not everybody will be able to travel this distance but it would
be great if you would at least consider joining that BoF remotely.  I'll
care for a somehow TimeZone aware scheduling - if needed we'll organise
two BoFs to match all time zones.  I'm also aware that we have pretty
different teams and it might make sense to do some infrastructure
related BoF with your team and other teams that are caring for Debian
infrastructure.

I have some specific questions to the Debian Boot team.

  - Do you feel good when doing your work in Debian Boot team?
  - Do you consider the workload of your team equally shared amongst its
    members and who actually is considered a team member?  (I added some
    persons in CC who have recently answered to questions on the mailing
    list.)
  - Do you have some strategy to gather new contributors for your team?
  - Can you give some individual estimation how many hours per week you
    are working on your tasks in youre team?  Does this fit the amount of
    time you can really afford for this task?
  - I recently had some discussion on Chemnitzer Linuxtage what might
    be the reason for derivatives to write their own installers.  While
    I'm personally perfectly happy with the way I can install Debian I'm
    somehow wondering why others are spending time into a problem we
    are considering "solved" and whether we can learn something from this,
  - I once had a amr64 based laptop (Pinebook) and had to learn that I
    can't use the Debian installer which was frustrating.  I was told
    that this is the case for hardware that is not featuring some BIOS-like
    boot system.  Do you see any chance to let the installer work for
    non-Intel architectures (or should I rather ask this question on
    Debian CD (sorry for my ignorance if I miss responsibility here.)
  - Can I do anything for you?

Kind regards and thanks a lot for your work
   Andreas.


[0] https://lists.debian.org/debian-release/2024/05/msg00114.html
[1] https://people.debian.org/~tille/

-- 
https://fam-tille.de

Attachment: signature.asc
Description: PGP signature

Reply via email to