I had a chat with Infra and they do not like automated posts to the mailing list. I am going to set up some alarms for me to remind me to do weekly roundups. That also means I get to curate the stuff I think is important.
On 9 March 2013 22:27, Benoit Chesneau <[email protected]> wrote: > i will have a look to see if it can be automatised. If not i can > probably do the weekly summary. > > - benoit > > On Sat, Mar 9, 2013 at 8:31 PM, Noah Slater <[email protected]> wrote: > > Benoit, > > > > As you seem to be a steward of the Google+ community, I was wondering > this > > morning if you would consider doing a weekly roundup of the activity > > happening over there? > > > > See my recent posts to the user list with links to StackOverflow > questions. > > > > Do you think this would be valuable? > > > > > > On 5 March 2013 20:27, Noah Slater <[email protected]> wrote: > > > >> We are the community organisers for CouchDB. This list. Everyone reading > >> this email. > >> > >> And the ASF tools might be clunky and whatever, but we have to make do > >> with them. And the ASF community guidelines dictate to us that we must > keep > >> project activity happening on the lists where it can be seen by > everyone. > >> > >> These guidelines are not arbitrary either. Their goal is not to suppress > >> any discussion of a project outside of the project. Their goal is to > make > >> sure that communities do not become fractured. Which is, again, a > problem > >> that we ought to take seriously. How do we get as much of the project > >> activity happening in a single place so people can follow it? > >> > >> Benoit, I think a weekly news thing is a great idea. And I've been > >> considering this for a few weeks now. Check out what CloudStack do. > It's a > >> weekly roundup of all the things going on on the lists, and off the > lists. > >> > >> > https://blogs.apache.org/cloudstack/entry/apache_cloudstack_weekly_news_11 > >> > >> I asked a few questions about how this is being put together. Response > >> here: > >> > >> http://markmail.org/message/d5td5ysoxonm7lvl > >> > >> Now, who wants to take this idea and run with it? > >> > >> Matt, if you make a request to infra they might consider removing your > >> mail. > >> > >> > >> On 5 March 2013 16:34, matt j. sorenson <[email protected]> wrote: > >> > >>> also - invariably i will forget to rip my phone # out of my email sig > when > >>> responding to a publicly archived mailing list! gah! > >>> > >>> -- > >>> *matt * > >>> > >>> > >>> On Tue, Mar 5, 2013 at 10:29 AM, matt j. sorenson < > [email protected] > >>> >wrote: > >>> > >>> > 1) community growth will happen organically (as it ought), or it > won't > >>> > happen. > >>> > > >>> > 2) I believe email is the least best "single" canonical destination. > >>> > > >>> > Not least of all because the mailing list and the apache web > interface > >>> to > >>> > the mailing list is a lousy news, information, and knowledge archive. > >>> That > >>> > in itself is enough of a limiting factor. > >>> > > >>> > I think Benoit's on the right track - on the website, s/Mailing > >>> > List/Community and build the couchdb "planet", which aggregates the > >>> pockets > >>> > of couchdb cliques (as you refer to them) around the web as they > emerge > >>> > and/or are discovered. Then encourage more cliques and more sharing. > The > >>> > web decentralizes naturally and if someone thinks they can buck that > and > >>> > control it, it will probably do more harm than good. > >>> > > >>> > p.s. who *is* (are) the community organizer(s) for couchdb? > >>> > > >>> > > >>> > > >>> > -- > >>> > *matt j. sorenson* > >>> > mobile: 320-424-0309 > >>> > > >>> > phone calls always welcome :) > >>> > > >>> > > >>> > On Tue, Mar 5, 2013 at 10:04 AM, Noah Slater <[email protected]> > >>> wrote: > >>> > > >>> >> I would never say to someone "do not talk about CouchDB on Twitter > or > >>> >> Google+ or your own blog." No way! But I'd like to think that the > >>> really > >>> >> important conversations are finding their way to the mailing lists. > You > >>> >> know. If you do a blog post, or you there's a really interest > >>> discussion > >>> >> happening on StackOverflow... Share it with us here. > >>> >> > >>> >> How can we encourage this sort of activity? For things to filter > back > >>> >> upstream to the project, where the majority of the community can see > >>> it? > >>> >> It > >>> >> is beneficial for both parties. The wider community finds out about > >>> more > >>> >> things going on. And the blog post, or the conversation gets more > >>> >> exposure, > >>> >> and perhaps more contributions. > >>> >> > >>> >> > >>> >> On 5 March 2013 15:54, Benoit Chesneau <[email protected]> wrote: > >>> >> > >>> >> > imo the more media we spread on, the better it is. > >>> >> > > >>> >> > Ayway I can understand your concern (i'm more worried to have > support > >>> >> > done on stackoverflow instead of proper mls and jira but ...) . > >>> >> > > >>> >> > One of the good thing today in the web is that we can mashup most > of > >>> >> > the services around in a website . I would find interesting to > have > >>> >> > the current website reworked to display informations coming from > >>> >> > different sources: twitter, g+, of course ml (maybe more) and > allows > >>> >> > people to search into that. I think it would solve your concern > and > >>> >> > let others post on their preferred media. > >>> >> > > >>> >> > - benoît > >>> >> > > >>> >> > > >>> >> > > >>> >> > On Tue, Mar 5, 2013 at 4:41 PM, Noah Slater <[email protected]> > >>> wrote: > >>> >> > > Community cohesion is a big concern for me. Historically, we've > >>> >> struggled > >>> >> > > with this. And I think we could get a lot better at it. There > >>> should > >>> >> be a > >>> >> > > single obvious place you can go to to be a part of the > community, > >>> and > >>> >> > that > >>> >> > > should be the project mailing lists, blog, etc. That doesn't > mean > >>> >> there > >>> >> > > cannot or should not be pockets of activity in other places. > But I > >>> am > >>> >> > > concerned if those pockets of activity mean that cliques are > >>> forming. > >>> >> > > Because that would be a detriment to the work we're doing here. > >>> >> > > > >>> >> > > > >>> >> > > On 5 March 2013 15:36, matt j. sorenson <[email protected]> > >>> >> wrote: > >>> >> > > > >>> >> > >> sure, just encourage more sharing... the more the better, and > stop > >>> >> being > >>> >> > >> fearful about it. you said it right yourself, if you'd just > left > >>> it > >>> >> at > >>> >> > >> this... > >>> >> > >> > >>> >> > >> ------------------------- > >>> >> > >> Hey, > >>> >> > >> > >>> >> > >> Saw this post this morning: > >>> >> > >> > >>> >> > >> > >>> >> > > >>> >> > >>> > https://plus.google.com/u/0/101311778896778283942/posts/iZgMeo5oGst?cfem=1 > >>> >> > >> > >>> >> > >> I think it's great that stuff is happening around CouchDB on > >>> Google+ > >>> >> > >> ------------------------- > >>> >> > >> > >>> >> > >> -- > >>> >> > >> *matt j. sorenson* > >>> >> > >> mobile: 320-424-0309 > >>> >> > >> > >>> >> > >> phone calls always welcome :) > >>> >> > >> > >>> >> > >> > >>> >> > >> On Tue, Mar 5, 2013 at 9:32 AM, Noah Slater < > [email protected]> > >>> >> wrote: > >>> >> > >> > >>> >> > >> > Hey, > >>> >> > >> > > >>> >> > >> > Saw this post this morning: > >>> >> > >> > > >>> >> > >> > > >>> >> > >> > >>> >> > > >>> >> > >>> > https://plus.google.com/u/0/101311778896778283942/posts/iZgMeo5oGst?cfem=1 > >>> >> > >> > > >>> >> > >> > I think it's great that stuff is happening around CouchDB on > >>> >> Google+, > >>> >> > but > >>> >> > >> > it concerns me that news like this is posted away from the > >>> project > >>> >> > lists, > >>> >> > >> > and way from the project. > >>> >> > >> > > >>> >> > >> > Obviously, we can't dictate to people where they should talk > >>> about > >>> >> > >> CouchDB. > >>> >> > >> > But I am very concerned about us diluting our community. > >>> >> > >> > > >>> >> > >> > Thoughts on this? > >>> >> > >> > > >>> >> > >> > Thanks, > >>> >> > >> > > >>> >> > >> > -- > >>> >> > >> > NS > >>> >> > >> > > >>> >> > >> > >>> >> > > > >>> >> > > > >>> >> > > > >>> >> > > -- > >>> >> > > NS > >>> >> > > >>> >> > >>> >> > >>> >> > >>> >> -- > >>> >> NS > >>> >> > >>> > > >>> > > >>> > >> > >> > >> > >> -- > >> NS > >> > > > > > > > > -- > > NS > -- NS
