Sorry, sounds like I hit a nerve. "No" would have been enough for me. I am more interested in what is being discussed and why.
but on the subject of the site, if I want to hack on the jobs board, is this the right repo to fork? https://github.com/python/pythondotorg On Fri, Jun 5, 2015 at 12:52 PM, VanL <van.lindb...@gmail.com> wrote: > No. I've been working on the site (picking up from the previous -redesign > efforts) for a number of months. In addition to bugs or other issues with > the site, one key problem was that we didn't have the facility to > reasonably invite others to participate. > > We are close to getting that all set. We are migrating all the work to > public repositories, we created a distributed ownership model for content, > we opened up a public bug tracker (which I believe has been announced here, > among other places), and soon we will have a public workflow that will > allow everyone to work on the site together. > > It takes planning and support to create a distributed system that isn't > frustrating... so I am working on that so we can transition to a model that > invites open participation. > > In the mean time, this hasn't been closed. We have had three or four > public working sessions, the most recent being at PyCon. We had a number of > people participate, and it was in those sessions that we made the plan so > that we could move to broader community ownership of parts of the site and > figured out what would need to be done to support that kind of > collaboration. > On Jun 6, 2015 1:37 AM, "Carl Karsten" <c...@personnelware.com> wrote: > >> >> On Fri, Jun 5, 2015 at 11:59 AM, VanL <van.lindb...@gmail.com> wrote: >> >>> We are still preparing. We will be asking everyone to participate soon. >> >> >> Is this being discussed on the board-private list? >> >> Carl K >> >> -- Carl K
_______________________________________________ pydotorg-www mailing list pydotorg-www@python.org https://mail.python.org/mailman/listinfo/pydotorg-www
