2011/5/4 Michael Shuler :
> On 05/04/2011 08:28 AM, Soren Hansen wrote:
>> 2011/5/4 Michael Shuler :
>>> Additionally, there [are] zero readability reasons to move to multiple
>>> channels at this time. At no time since its inception (and sadly quite
>>> the opposite during the summit...)
>> The w
http://www.google.com/url?sa=t&source=web&cd=10&ved=0CEMQtwIwCQ&url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Ddl9kp2Pu6qs&ei=46TBTaHmHcPjiALx3cmtAw&usg=AFQjCNHBUlq_XwbLgm--C-euGXLVTSxBAQ
I don't care who you are, that 'tag line' is funny!
Duane E. Green
Cell (636)633-1480
duane_gree...@hotmail
Yup, seems to work for Django.
From: Josh Kearney [j...@jk0.org]
I like this approach.
On Wed, May 4, 2011 at 1:19 PM, Ant Messerli
mailto:amess...@rackspace.com>> wrote:
So it sounds like the better path would be to just keep two channels for
now, see how that
I like this approach.
On Wed, May 4, 2011 at 1:19 PM, Ant Messerli wrote:
> So it sounds like the better path would be to just keep two channels for
> now, see how that goes, and then maybe revisit splitting out by project if
> it comes to that in the future?
>
> #openstack - Help and Support
>
Sounds reasonable.
-- Sent from my Tandy 1000sx
Jesse Andrews
anotherje...@gmail.com
On May 4, 2011, at 11:19 AM, Ant Messerli wrote:
> So it sounds like the better path would be to just keep two channels for
> now, see how that goes, and then maybe revisit splitting out by project if
> it co
So it sounds like the better path would be to just keep two channels for
now, see how that goes, and then maybe revisit splitting out by project if
it comes to that in the future?
#openstack - Help and Support
#openstack-dev - All Openstack Development
Anyone should be able to participate in any
On 05/04/2011 08:28 AM, Soren Hansen wrote:
> 2011/5/4 Michael Shuler :
>> Additionally, there [are] zero readability reasons to move to multiple
>> channels at this time. At no time since its inception (and sadly quite
>> the opposite during the summit...)
>
> The whole point of a summit is to t
This concerns me, as its not scalable. Yes, a few users might pick up some
valuable information "by osmosis," but as the use of OpenStack grows, it
will require massive amounts of repetition to ensure that the same
knowledge goes to all users. IRC is *not* the proper medium for capturing
user infor
2011/5/4 Michael Shuler :
> Additionally, there no zero readability reasons to move to multiple
> channels at this time. At no time since its inception (and sadly quite
> the opposite during the summit...)
The whole point of a summit is to take typing speed out of the
equation and have discussion
On 05/04/2011 12:34 AM, Wayne A. Walls wrote:
> I'm not against an #OpenStack and an #OpenStack-dev/whatever, but
> being a non-dev, I pick up a ton of good information just lurking
> and following conversation. I love eavesdrop for locating past
> discussions, and adding more channels doesn't st
On May 4, 2011, at 4:36 AM, Soren Hansen wrote:
> I think that's because the majority of traffic is related to Nova. So,
> for Nova devs, it's relatively easy to ignore the small amount of
> Swift stuff, but for Swift devs, I suspect it's annoying to have weed
> through a bunch of things that aren'
2011/5/4 Vishvananda Ishaya :
> Agreed, we still have a lot of cross project discussions, especially around
> things like auth/etc. Admittedly the specific questions about swift vs.
> nova are usually isolated, but I don't think I've found it to be
> particularly annoying to have them going on in
> Can't we just have a #openstack-dev to cover them all ?
+1
--
Christian Berendt
Linux / Unix Consultant & Developer
Tel.: +49-171-5542175
Mail: bere...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG:
On May 3, 2011, at 5:22 PM, Ant Messerli wrote:
> Hey all,
>
> I wanted to see what everyones opinions were on separating out some of the
> IRC channels. When the project started we decided to keep #openstack as the
> primary channel since the project was small at the time. Over the last yea
What's this forum stuff that is going on? ;). AnywaysI'm not against an
#OpenStack and an #OpenStack-dev/whatever, but being a non-dev, I pick up a ton
of good information just lurking and following conversation. I love eavesdrop
for locating past discussions, and adding more channels does
If we do create any new IRC channels I would rather see a #openstack-ops or
#openstack-deploy than an #openstack-dev but I do agree that the forum plans
should be finalized first.
--J
Sent from my iPad
On May 3, 2011, at 22:47, Todd Willey wrote:
> I think we should finalize a plan for the
I think we should finalize a plan for the forum before we start
changing IRC. I'd hate to become unresponsive on many fronts at once,
and I think growing just one of those communities will be hard enough.
On Tue, May 3, 2011 at 8:23 PM, Devin Carlen wrote:
> +1 to not splitting everything up.
>
+1 to not splitting everything up.
On May 3, 2011, at 5:03 PM, Eric Day wrote:
> I would vote for no separation yet, but I understand everyone has
> a different threshold. If we do separate, +1 on #openstack-dev,
> #openstack- seems a bit excessive.
>
> -Eric
>
> On Tue, May 03, 2011 at 07:34
I would vote for no separation yet, but I understand everyone has
a different threshold. If we do separate, +1 on #openstack-dev,
#openstack- seems a bit excessive.
-Eric
On Tue, May 03, 2011 at 07:34:30PM -0400, Jay Pipes wrote:
> On Tue, May 3, 2011 at 7:16 PM, Ken Pepple wrote:
> > Do we have
On Tue, May 3, 2011 at 7:16 PM, Ken Pepple wrote:
> Do we have to break out all the projects into their own development channels
> ?
> Can't we just have a #openstack-dev to cover them all ?
> There are a lot of cross-project discussions (especially between
> nova/glance, but I think NaaS will als
Agreed, we still have a lot of cross project discussions, especially around
things like auth/etc. Admittedly the specific questions about swift vs. nova
are usually isolated, but I don't think I've found it to be particularly
annoying to have them going on in the shared channel. Splitting out
On May 3, 2011, at 3:22 PM, Ant Messerli wrote:
> #openstack – Help and Getting Started
> #openstack-meeting – Community Meetings
> #openstack-nova – All Nova Development
> #openstack-swift – All Swift Development
> #openstack-glance – All Glance Development
Do we have to break out all the project
Hey all,
I wanted to see what everyones opinions were on separating out some of the IRC
channels. When the project started we decided to keep #openstack as the
primary channel since the project was small at the time. Over the last year
with the project growing, the traffic in the #openstack c
23 matches
Mail list logo