svn commit: r1915650 - in /comdev/community: ./ README.md wg-wg/ wg-wg/README.md

[rb...@apache.org]

Author: rbowen
Date: Thu Feb  8 14:29:13 2024
New Revision: 1915650

URL: http://svn.apache.org/viewvc?rev=1915650&view=rev
Log:
Adds some top-level stuff around working groups. See
https://lists.apache.org/thread/nwvr28gq51c8v0wkqjv8xvvc2xqrtf03 for
meta discussion.

Added:
    comdev/community/
    comdev/community/README.md
    comdev/community/wg-wg/
    comdev/community/wg-wg/README.md

Added: comdev/community/README.md
URL: http://svn.apache.org/viewvc/comdev/community/README.md?rev=1915650&view=auto
==============================================================================
--- comdev/community/README.md (added)
+++ comdev/community/README.md Thu Feb  8 14:29:13 2024
@@ -0,0 +1,42 @@
+# Apache Community Development
+
+This repo contains documentation and work product around the meta-task
+of building communities at the Apache Software Foundation. Community
+Development ("ComDev") is tasked with providing tools, processes, and
+advice around community building. Apache projects (and, really, any open
+source project!) is welcome to benefit from, and contribute to, this
+effort, but are not obliged to do so.
+
+## Other repos
+
+This is one of several repos that ComDev maintains. Those repos can
+mostly be found [here](https://github.com/search?q=org%3Aapache+comdev&type=repositories). 
+Most importantly, our website is [here](https://github.com/apache/comdev-site).
+
+This one is not (yet) mirrored to Git, but probably will be some day,
+once someone gets around to that. Meanwhile, it's [in
+svn](https://svn.apache.org/repos/asf/comdev).
+
+## Working Groups
+
+Some of the work of ComDev is subdivided into working groups, which you
+will find in this repo. We are still in the process of booting up this
+process, so everything is in flux. Come help.
+
+We do not, at this time, draw any distinction between SIGs (Special
+Interest Groups) and WGs (Working Groups). If you care about that kind
+of thing, come help us define this.
+
+## Contribute
+
+The first step to contributing to this effort is to join the [ComDev
+mailing list](https://lists.apache.org/list.html?dev@community.apache.org) 
+and introduce yourself.
+
+## Inspiration
+
+Some of the inspiration for this work comes from
+[Kubernetes](https://github.com/kubernetes/community), who have been
+around a much shorter time than we have, and do a better job of this.
+Thank you.
+

Added: comdev/community/wg-wg/README.md
URL: http://svn.apache.org/viewvc/comdev/community/wg-wg/README.md?rev=1915650&view=auto
==============================================================================
--- comdev/community/wg-wg/README.md (added)
+++ comdev/community/wg-wg/README.md Thu Feb  8 14:29:13 2024
@@ -0,0 +1,48 @@
+# Working Groups Working Group
+
+This working group exists to define how working groups should operate.
+
+This is *NOT* intended to be any kind of top-down governance telling people
+what they can or cannot do. Rather, it's hoped that if we create a
+general structure for how to do these things, we'll encourage more
+people to start work, without having to figure out how to organize that
+work.
+
+## Proposal
+
+A working group is a small group of individuals who are in some level of
+agreement about what work needs to be done around a particular topic.
+
+Examples include:
+
+* Website WG - Maintenance and improvement of https://community.apache.org/
+* Welcome WG - Tools and process to welcome first-time contributors in a
+  consistent and friendly fashion
+* Communication WG - Tools and process around "internal" communication
+  with projects at the ASF
+
+etc.
+
+## Membership
+
+Anyone can volunteer to participate in a WG. They need not be an ASF
+member, a committer on an Apache project, or any other criteria, other
+than a willingness to discuss politely and work towards agreed-upon
+goals.
+
+A WG may maintain a public list of their membership.
+
+## Communication
+
+Each WG shall designate a place that they're going to keep in touch on a
+regular basis, for some definition of "regular" that they agree upon.
+They'll also maintain some kind of record of work in *this* repository,
+so that newcomers can catch up on the discussion so far, and find their
+place.
+
+Email communications should happen on the main dev@community.apache.org
+mailing list, and use a Subject line tag (eg [WG: Website]) to indicate
+that the thread is related to that WG's work. In this way, the entire
+community will be aware of the work that WGs are doing, without having
+to subscribe to additional mailing lists.
+