sebb wrote on 4/21/17 7:42 PM: > On 21 April 2017 at 23:25, Shane Curcuru <[email protected]> wrote: >> I'd like to make a version of the /roster/orgchart public. >> >> It seems that 80%++ of all the data in there should be public. There >> are just a few bits that specific officers might not want public: >> >> - Private mailing lists - we may not want some of those public; although >> some *should* be public like trademarks@. > > I assume you mean the name of the list should be public, rather than > the messages sent to it.
Yes, obviously! I'm only working on displaying the data in roster/orgchart publicly, not changing anything else. My hope is to publish everything in the foundation/officers/personnel-duties/*.txt, with some exceptions: - private-list: would not be published by default. - Should we have an "email-private" flag? That would prevent publishing the email: attribute if the treasurer, for example, didn't want treasurer@ published. - Should the roster: attribute be public? In some cases it's clearly fine, like board. But would it be OK to publish it for group/asf-treasurer and group/asf-secretary? (on second thought, it doesn't make any sense, since the roster/group/* links are all committer-private anyway). - We need to scrub [goals] [tasks] for a few entries that have detailed descriptions that the authors might not have written for publication. Anything else I'd need to scrub before finding a way to make this stuff public? Eventually, I'd like to make it interactive and tied in with: https://www.apache.org/foundation/governance/orgchart > >> This could simply be done by adding a "private" flag or the like to the >> underlying data, which makes updates easy. >> >> >> - Some details of the free-text sections: a number of officer role >> descriptions were taken from originally-private data sources. I believe >> some of these could be made public, presuming the officer doesn't mind; >> but some will need to be private. >> >> Again, for officers who want some structured duties/roles data like this >> published privately (to committers/members), but not publicly, we can >> ask if they want a "private" flag on the current data, or if they >> instead want to store any private duties in the appropriate committers/ >> repo. >> >> Anything I've missed? Anyone want to help scrub the data? >> >> -- >> >> - Shane >> https://www.apache.org/foundation/marks/resources -- - Shane https://www.apache.org/foundation/marks/resources
