+1 Please count me in this WG. Below is my thoughts: > I would hope that a WG would have regular checkins (could be email, Slack, > Google Meet
For an async group, we can use ASF Slack with a new channel. #zookeeper-release is in this flavor and it works well. For any actionable items we can discuss on GitHub Issues, JIRA tickets, or GitHub PRs correspondingly. For a sync meeting, I may prefer an on-demand meeting to a "regular meeting" due to my proactive nature...And I'm in the +08:00 timezone so in my previous experience, the regular schedule is often unfriendly to me. For certain site updates and maintenance, I share the feeling that we have scattered knowledge as I state in this blog draft [1]. Besides, I'm tracking two concrete improvements related to foundation level website topics: * Update Website Template [2] * Update project maturity model to include trademark and branding [3] I wonder if these tasks are under the WG objects - we can start the WG effectively now to see if it's valuable to establish a formal structure. Best, tison. [1] https://github.com/tisonspieces/www-site/pull/8/files#diff-e57a0db6bf085338381727205cda6daef8f930a4b5059b58093cadd2889d6ae5R316-R324 [2] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx [3] https://lists.apache.org/thread/oc9jft1tyo7cbphcyrtwobf4w5rcbhfw Trista Pan <panj...@apache.org> 于2024年2月8日周四 17:06写道： > > > Ensure that we don’t duplicate, contradict, or confuse. > > > Agreed, I’d like to be part of it if. Please let me know if there are > anything I can give a hand. Thanks. > > > > ------------------------------------------------------------------------------ > Trista Pan > Twitter & Github: tristaZero > > > > > On 02/8/2024 00:11，Rich Bowen<rbo...@rcbowen.com> wrote： > Proposed: Form a formal Website working group. > > (I am aware that I haven’t defined “working group” yet, and I do, in fact, > intend to propose a Working Groups Working Group which could possibly > formalize what a working group looks like. I have some ideas, but no desire > to go define it on my own.) > > The Website WG would, obviously, be responsible for the maintenance of the > website. I am aware that some folks think I’m just off doing that on my own, > and that’s part of what I’m trying to avoid (see > https://lists.apache.org/thread/nwvr28gq51c8v0wkqjv8xvvc2xqrtf03 for further > commentary). I would like to gather a group of people who 1) care about it > and 2) are willing to do some of (NOT ALL) the work. > > Specific things that I believe we should tackle include > > * Long-term maintenance of the site. This involves regular audits, > implementing metrics, and perhaps other things > * Reorg - this is a short-term task that I’ve been just doing on my own, > which ensures it will never get done, and if it did, there may be some > disagreement about how I did it. > * Deduplication - work closely with MarkPub to figure out the *right* place > for certain information; work through the policy/best-practice dichotomy and > ensure that we are *not* duplicating policy docs; Work on content on www.a.o > <http://www.a.o/> that is closely related to content on community.a.o - which > one is authoritative? Ensure that we don’t duplicate, contradict, or confuse. > > There’s probably more. > > I would hope that a WG would have regular checkins (could be email, Slack, > Google Meet, I really don’t care, as long as everyone is engaging with the > conversation.) > > If you are interested in helping form this group, please speak up in this > thread, and help us help one another. > > — > Rich Bowen > rbo...@rcbowen.com > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
