Pretty much everything is appropriate for the dev list. (The main exception being "personnel matters", e.g. voting for new committers.) Even banal coordination, like "I've written the report but can't seem to post it. Here it is. Can y'all review? Jonas, can you post it for me?" belongs on the list. The dev list is the town square (or the local coffee shop) of a project.
On Mon, Mar 2, 2020 at 12:41 PM bernard metzler <[email protected]> wrote: > > On 3/2/2020 7:33 PM, Julian Hyde wrote: > > Thanks for getting the report done on time. > > > > Next time, consider doing it everything on the dev list. It may seem > > like a small thing, but Jonas and Bernard are clearly talking in a > > back-channel, and that is alienating to the rest of us on dev. We > > start wondering how much else we are missing. > > > > Julian > > > > On Mon, Mar 2, 2020 at 7:05 AM bernard metzler <[email protected]> wrote: > >> > >> On 3/2/2020 15:55, Jonas Pfefferle wrote: > >>> Bernard wrote the new podling report and I just added it. > >>> > >>> Thanks, > >>> Jonas > >>> > >> Thanks Jonas! I lost my Confluence password, and reset attempts > >> are currently ending up in 'internal error'. > >> > >> Thanks > >> Bernard. > >> > Hi Julian, you are saying we shall better discuss the > content on dev > before entering the report? > > Would make lots of sense to me. I asked that myself, but I was unsure > if that's appropriate. > > Thanks, > Bernard.
