MaintainersApr2023 - Revision history

Tomh: /* Handling dormant issues and MRs */

2023-04-03T22:31:43Z

Handling dormant issues and MRs

← Older revision		Revision as of 22:31, 3 April 2023
Line 49:		Line 49:
	We discussed whether issues should be closed if a time limit (e.g. 6 months) elapsed. Eduardo said that GitLab.com has some automated tools that could be used for automating policies such as this.		We discussed whether issues should be closed if a time limit (e.g. 6 months) elapsed. Eduardo said that GitLab.com has some automated tools that could be used for automating policies such as this.

	Peter shared a concern about the ~~balance~~ of effort (disincentives) we place on new submitters to update documentation and tests, vs. the effort that falls on maintainers to handle reports without easy ability to reproduce. Alberto stated that he felt that asking for a working example is a good balance of these concerns.		Peter shared a concern about balancing 1) the amount of effort (disincentives) we place on new submitters to update documentation and tests with their patches and MRs, vs. the effort that falls on maintainers to handle reports without easy ability to reproduce, and the need for maintainers to do more work to finish off these MRs. Alberto stated that he felt that asking for a working example is a good balance of these concerns, but not necessarily documentation updates and new test case code.

	There was some discussion on the burden of submission on new submitters (students) needing to install and configure clang-tidy, documentation packages, etc. to be able to pass submission checks. Eduardo felt that integrations were now good enough that it was less of a burden to ask people to use these tools, and proposed, in the past, a settings.json to help with VS Code integration. Alberto said that for students and inexperienced programmers, this may ~~also~~ be hard.		There was some discussion on the burden of submission on new submitters (students) needing to install and configure tooling such as clang-tidy, Latex documentation packages, etc. to be able to pass submission checks. Eduardo felt that tool integrations were now good enough that it was less of a burden to ask people to use these tools, and proposed, in the past (!1103), a settings.json to help with VS Code integration. Alberto said that for students and inexperienced programmers, this may still be hard.

	The discussion ended seemingly without a strong consensus on next steps, so Tom proposed to take a pass through the tracker and come back to the list and Zuiip with a concrete proposal.		The discussion ended seemingly without a strong consensus on next steps, so Tom proposed to take a pass through the tracker and come back to the list and Zuiip with a concrete proposal.

Tomh: add minutes

2023-04-03T22:28:28Z

add minutes

@@ Line 4: / Line 4: @@
 Topic: ns-3.39 and future plans
 * April 3, 2023 08:00 AM Pacific Time (US and Canada), '''15h00 UTC'''
 == Agenda ==
@@ Line 27: / Line 21: @@
 == Materials ==
 == Minutes ==
 == Recent maintainers meetings ==

Tomh: create maintainer meeting for April 3

2023-03-25T23:57:14Z

create maintainer meeting for April 3

New page

{{TOC}}

== Date/Time/Venue ==

Topic: ns-3.39 and future plans

* April 3, 2023 08:00 AM Pacific Time (US and Canada), '''15h00 UTC'''

== Zoom meeting info ==

Join Zoom Meeting
https://washington.zoom.us/j/98173968509?pwd=U2pBQjBxbU5jVmc3ZVgxNnVXeVBUZz09

Meeting ID: 981 7396 8509
Passcode: 904566

== Agenda ==

1) ns-3.39 plans: schedule for release, and any plans by maintainers (that they wish to socialize in this meeting)?

2) Alberto Gallegos would like to discuss the plan for abandoned issues or MRs in the tracker; could dormant or abandoned issues and MRs be marked as such in the tracker, or closed?

3) current plans for the annual meeting (Washington DC and virtual, June 26-29)

4) longer-term issues (TBD)

== Materials ==

== Minutes ==

== Recent maintainers meetings ==

* [[MaintainersJan2023]]
* [[MaintainersSept2022]]
* [[MaintainersMay2022]]
* [[MaintainersApr2021]]
* [[MaintainersJan2021]]
* [[MaintainersSept2020]]
* [[MaintainersJune2020]]