GDB BoF Agenda for GNU Cauldron 2022?

GDB BoF Agenda for GNU Cauldron 2022?

[Pedro Alves]

Hi!

Once again, we'll have a gdb BoF session in the Cauldron this year:

  https://gcc.gnu.org/wiki/cauldron2022#cauldron2022talks.the_gdb_bof

As in previous years, the intention is to discuss whatever gdb-related topics people feel like
needs discussing, hence no agenda listed in the schedule (I didn't have a list of topics in mind
when I proposed the slot).  As before, I intend to collect topics of interest at the start of the
session, and then try to cover them all.  That seems to have worked OK in the past.

However, if anyone has topics they already know they'd like to see brought up, please feel
free to let me know in advance.

Hope to see you there!

Cheers,
Pedro Alves

Re: GDB BoF Agenda for GNU Cauldron 2022?

[Luis Machado]

Hi,

On 9/12/22 16:43, Pedro Alves wrote:
> Hi!
> 
> Once again, we'll have a gdb BoF session in the Cauldron this year:
> 
>    https://gcc.gnu.org/wiki/cauldron2022#cauldron2022talks.the_gdb_bof
> 
> As in previous years, the intention is to discuss whatever gdb-related topics people feel like
> needs discussing, hence no agenda listed in the schedule (I didn't have a list of topics in mind
> when I proposed the slot).  As before, I intend to collect topics of interest at the start of the
> session, and then try to cover them all.  That seems to have worked OK in the past.
> 
> However, if anyone has topics they already know they'd like to see brought up, please feel
> free to let me know in advance.
> 
> Hope to see you there!
> 
> Cheers,
> Pedro Alves

One topic GDB developers might be interested in (but feel free to skip it otherwise), is patch reviewing.

- Timing

Everyone's busy schedules aside, is there a way to improve the time it takes for patches to get reviewed? Do we need to seek
(to appoint) more maintainers?

- Tracking

Is there a better patch-tracking system so contributions don't get forgotten (better than pinging patches once a week).

It would be nice to have a clear list of contributions waiting to be reviewed, as opposed to having to go through mailing
list entries.

- Pre-commit testing

Some sort of infrastructure that just build-tests the patch/series to hopefully speed-up reviewing. Possibly using our current
sourceware buildbot infrastructure?

Regards,
Luis

Re: GDB BoF Agenda for GNU Cauldron 2022?

[Luis Machado]

On 9/12/22 17:24, Luis Machado wrote:
> Hi,
> 
> On 9/12/22 16:43, Pedro Alves wrote:
>> Hi!
>>
>> Once again, we'll have a gdb BoF session in the Cauldron this year:
>>
>>    https://gcc.gnu.org/wiki/cauldron2022#cauldron2022talks.the_gdb_bof
>>
>> As in previous years, the intention is to discuss whatever gdb-related topics people feel like
>> needs discussing, hence no agenda listed in the schedule (I didn't have a list of topics in mind
>> when I proposed the slot).  As before, I intend to collect topics of interest at the start of the
>> session, and then try to cover them all.  That seems to have worked OK in the past.
>>
>> However, if anyone has topics they already know they'd like to see brought up, please feel
>> free to let me know in advance.
>>
>> Hope to see you there!
>>
>> Cheers,
>> Pedro Alves
> 
> One topic GDB developers might be interested in (but feel free to skip it otherwise), is patch reviewing.
> 
> - Timing
> 
> Everyone's busy schedules aside, is there a way to improve the time it takes for patches to get reviewed? Do we need to seek
> (to appoint) more maintainers?
> 
> - Tracking
> 
> Is there a better patch-tracking system so contributions don't get forgotten (better than pinging patches once a week).
> 
> It would be nice to have a clear list of contributions waiting to be reviewed, as opposed to having to go through mailing
> list entries.
> 
> - Pre-commit testing
> 
> Some sort of infrastructure that just build-tests the patch/series to hopefully speed-up reviewing. Possibly using our current
> sourceware buildbot infrastructure?
> 
> Regards,
> Luis

Sorry, remembered another one:

- Discuss adopting an auto-formatting tool for source code in the future (clang-format?), so developers/reviewers
don't need to spend time spotting such things. The experience with python black has been nice.

Re: GDB BoF Agenda for GNU Cauldron 2022?

[Tom Kacvinsky]

[-- Attachment #1: Type: text/plain, Size: 451 bytes --]

On Tue, Sep 13, 2022 at 6:48 AM Luis Machado via Gdb <gdb@sourceware.org>
wrote:

<snip>


> - Discuss adopting an auto-formatting tool for source code in the future
> (clang-format?), so developers/reviewers
> don't need to spend time spotting such things. The experience with python
> black has been nice.
>

Though I am not a GNU developer, I have to say +1 to this - clang-format
and black have been great for
code formatting I do at my job.

Tom