Perhaps the core team wants a hipchat room or irc channel or something else. It's their club that we all want to be allowed to join; not our club that we wish they'd attend :)

Once we do have one club, can we have club t-shirts? :)
Dr Nic Williams
Stark & Wayne LLC - the consultancy for Cloud Foundry
+1 415 860 2185
twitter: drnic
On Fri, Apr 12, 2013 at 6:28 AM, Matt Reider wrote:

Makes sense.
During yesterday's retrospective we talked about this very issue - engineers having time to visit the google groups. We made a decision to allocate time especially for that purpose. Hopefully you will experience a difference in attentiveness as soon as next week.
Sent from my iPhone
On Apr 12, 2013, at 4:04 AM, David Laing wrote:
+1 for encouraging the core teams to talk shop & post build server notifications on the -dev lists.

As an external person trying to participate in CF dev I often feel excluded - I can see the source code, but none of the "mechanics" around it; so I'm less guessing what the intentions of stuff is.

On 11 April 2013 22:44, Dr Nic Williams wrote:
I'd like bosh-dev to stay and for the actual bosh developers - notably the core team who work on it all day - to talk shop on it. Perhaps jenkins build failures go there too?

We can educate people who cross-post (I've done it plenty of times, sorry).

If the core bosh devs aren't going to write emails on the bosh-dev list; I guess it can be deleted; and we can just discuss user problems only on bosh-users :D

On Thu, Apr 11, 2013 at 1:37 PM, Matt Reider wrote:
A few weeks ago I asked if we could both move and consolidate our mailing lists because of 1) How Google Group search is biased against groups created within the context of Google Apps and 2) because it's hard for people to know which list to check for what (sometimes).

There were only a few responses - but it seemed like people wanted to keep things separate. One thing I am noticing, though, is that there are many posts in bosh-dev that could go in bosh-users, and vice versa. I also see a lot of cf-dev that are either better suited for, or naturally bleed into bosh-dev.

Should we at least merge bosh-dev and bosh-users? Seems practical. The number of Cloud Operators that are not at all concerned with the architecture of BOSH, at least conceptually, seems like nil.

Sorry to be hung up on this one.


Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry users
cell +1 (415) 860-2185
twitter @drnic

David Laing
Trading API @ City Index
Twitter: @davidlaing

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 8 of 14 | next ›
Discussion Overview
groupbosh-dev @
postedApr 11, '13 at 8:37p
activeApr 16, '13 at 10:34p



site design / logo © 2021 Grokbase