I actually have a contrary point of view on this. Most of the content of a report is public material and I have found that having the entire community build the report (as opposed to just the PMC) can be a very good community building exercise. Moreover, it is useful to start the next report at the start of the reporting period so that info can be added as things happen.
Only a tiny fraction of the information is ever important to keep private. The fraction is roughly the same as with the mailing lists ... very little needs to be on private@ On Sat, Jul 13, 2019, 12:41 AM Daniel Gruno <[email protected]> wrote: > On 7/13/19 6:34 AM, Justin Mclean wrote: > > HI, > > > > JFYI - Wiki permissions can also be set up to allow PMC view/edit and > ASF members view access which would be similar permisisons as a projects > mailing list. There permissions can be set on a folder and all documents > under that will inherent these permissions. > > +1, I think a restricted cwiki area for preparing reports is a better > option. It would also mean you could prepare something within the PMC, > then "publish" it in place by changing the restrictions once the report > is ready. > > > > > Thanks, > > Justin > > > >
