Re: [PR] What makes a good report? (comdev-site)
In the past we have avoided linking to whimsy in public facing documentation. It encourages people to dig to find what they can find. Whimsy is *not* a place that we want people digging, IMHO, and if there's alternate (there is) we should use it. On Fri, Jun 23, 2023, 19:47 sebb wrote: > On Sat, 24 Jun 2023 at 00:28, Rich Bowen wrote: > > > > On Fri, Jun 23, 2023, 06:10 rlenferink (via GitHub) > wrote: > > > > > > > > rlenferink commented on code in PR #125: > > > URL: > https://github.com/apache/comdev-site/pull/125#discussion_r1239637617 > > > > > > > > > > > > Review Comment: > > >Great addition! Should we maybe link to > > > https://whimsy.apache.org/board/minutes/ if people want to easily > select > > > another project and have a look at their past reports ? > > > > > > > That's private but yeah I will link to the public version of that. > > $ curl -I https://whimsy.apache.org/board/minutes/ > HTTP/1.1 200 OK > > Looks public to me ... > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: [PR] What makes a good report? (comdev-site)
> On Jun 26, 2023, at 05:29, Rich Bowen wrote: > > In the past we have avoided linking to whimsy in public facing > documentation. It encourages people to dig to find what they can find. > Whimsy is *not* a place that we want people digging, IMHO, and if there's > alternate (there is) we should use it. I completely agree. The board minutes are published here: https://apache.org/foundation/board/calendar.html > > On Fri, Jun 23, 2023, 19:47 sebb wrote: > >> On Sat, 24 Jun 2023 at 00:28, Rich Bowen wrote: >>> >>> On Fri, Jun 23, 2023, 06:10 rlenferink (via GitHub) >> wrote: >>> rlenferink commented on code in PR #125: URL: >> https://github.com/apache/comdev-site/pull/125#discussion_r1239637617 Review Comment: Great addition! Should we maybe link to https://whimsy.apache.org/board/minutes/ if people want to easily >> select another project and have a look at their past reports ? >>> >>> That's private but yeah I will link to the public version of that. >> >> $ curl -I https://whimsy.apache.org/board/minutes/ >> HTTP/1.1 200 OK >> >> Looks public to me ... >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> Craig L Russell c...@apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] What makes a good report? (comdev-site)
psteitz commented on PR #125: URL: https://github.com/apache/comdev-site/pull/125#issuecomment-1608391078 This is really nice work. On first read, I though there were things missing re challenges, but everything is there. I guess people who know how to write know how to write :) Re Bertrand's excellent suggestion of including links to good reports and explaining why, I kind of tried to do that for a year or so in my Chairman's reports. So there may be some examples or at least some inspiration there. See, e.g. https://svn.apache.org/repos/private/foundation/board/archived_agendas/board_agenda_2018_04_18.txt That is all old stuff, but the same kind of approach could be taken with newer reports. Maybe even just using some of the ones I called out might work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
