Le 9 oct. 05, à 00:39, Antonio Gallardo a écrit :
...I though we were against providing IRC support...
I don't think we can be against someone giving answers there - but it
would be cool, when people find solutions via IRC (or any other media
), to post them on the lists or on the wiki.
Christoph Hermann wrote:
And hey, you get really good support on IRC when you have enough time to
wait :)
I though we were against providing IRC support. Because it is exactly
the same as providing private support. We find your self giving the same
answer over and over, no archives and so
Too bad you cannot cross-post between the two lists, that alone
could have made things easier.
The developer list should receive mails also from the user list
with [Users] prepended. In this way developers get user mails, but
users don't need to read all the longwinding discussions
Le 6 oct. 05, à 10:04, Torsten Curdt a écrit :
...Let's better have a few more developer subscribed
to users again
Yes, after this discussion I think it's good enough - and I like the
idea of filtering both lists to the same folder in my mail client, so
as not to overlook user's
you want to reduce that count, I am still interested in hints on
- why I'm getting Attempted to release a $Proxy20 but its handler
could not be located. messages in my logs. [1]
- why the ComponentManager appears to be null in my
transformers' (SitemapComponentTestCase subclass) unit tests
In my experience, it doesn't matter which list I ask for help on, it still gets ignored.
That sounds really frustrated.Sorry about that.
My experience (although probably not objectively realistic, and biased
by bad experiences) is that my first request for help is usually
answered, even by a few
From: Jorg Heymans [EMAIL PROTECTED]
Date: Tue, 04 Oct 2005 11:06:17 +0200
Bertrand Delacretaz wrote:
(snip)
You are trying to remedy the fact that many developers (not all of them)
don't look at [EMAIL PROTECTED] I say those developers need to change their
view/attitude towards user@ and
Hi,
I'm mainly active on the users list, but being a full-time developer I am also monitoring the dev
mailing list, just to keep my eyes open for new interesting features..
I do think that the feedback on the users list is rather low. Traffic on that list is usually much
lower on the users
On Tuesday 04 October 2005 15:51, Geert Josten wrote:
1. Rename the list support@ or some similarly positive term.
2. Route all support@ mails to dev@ with a [SUPPORT] subject marker.
That keeps users who want to be protected from the RTs, wild dev
discussions and so on.
+1 to this
Mark Leicester wrote:
Hi all,
When we discussed the issue of declining posts to the users list earlier
this year (http://www.planetcocoon.com/node/1755 - the trend was visible
back then too), I suggested interviewing subscribers about what they
want, what they don't like, their level of
Bertrand Delacretaz wrote:
I think I have a few good reasons for this:
One: The line between cocoon users and developers is fairly thin, it is
not as in Open Office for example, where most users do not even know
what the C language is. Our users are more and more competent software
Jorg Heymans wrote:
Splitting up mailinglists works for other OS projects because either
1) they have a self sustaining user list with a lot of advanced users
willing to help out eg Spring forums
2) the developers *actively* help out on every post eg maven-users
As an active Cocoon user I
I'd like to chime in here.
Your points make perfect sense, But as a user ( I say user because
cocoon internals are beyond my capability/time constraints to figure
out) I get stuck with a WTF moment, struggle, struggle, struggle,
Email users@, wait maybe 3-4 days, rewrite the mail because
Geert Josten wrote:
...
Too bad you cannot cross-post between the two lists, that alone could
have made things easier.
The developer list should receive mails also from the user list with
[Users] prepended. In this way developers get user mails, but users
don't need to read all the
On Oct 4, 2005, at 8:51 AM, JD Daniels wrote:
I figured out how to use it, I am off making my own POJO's to plug
into the basic cocoon install I have settled on. I have a suspicion
that the drop in traffic is attributable to this - users simply
evolve. The questions I have to ask now (As
Mark Lundquist wrote:
On Oct 4, 2005, at 8:51 AM, JD Daniels wrote:
I figured out how to use it, I am off making my own POJO's to plug
into the basic cocoon install I have settled on. I have a suspicion
that the drop in traffic is attributable to this - users simply
evolve. The questions I
Thomas Lutz schrieb:
Hello list,
Although I am not sure wether I know how this framework works yet :-), I
am quite sure the drop in traffic has a lot to do with it. So +1 for me.
Where are the new users that start with cocoon ? I think, whoever starts
with cocoon has enough webexperience to
In these days of wild thoughts, here's another one: how about closing
the users@ list and having just one list for cocoon-related
discussions?
I think I have a few good reasons for this:
One: The line between cocoon users and developers is fairly thin, it is
not as in Open Office for
Bertrand Delacretaz wrote:
In these days of wild thoughts, here's another one: how about closing
the users@ list and having just one list for cocoon-related discussions?
I think I have a few good reasons for this:
eight: by having one list, it would be easier to lead by example, and
Bertrand Delacretaz wrote:
So, WDYT?
Big +1!
Keep it simple, and that goes for the mailing lists too.
Bye, Helma
Bertrand Delacretaz wrote:
In these days of wild thoughts, here's another one: how about closing
the users@ list and having just one list for cocoon-related discussions?
So, WDYT?
-Bertrand
I have no objection, but I think you are asking the question on the
wrong list. Take a poll on
On Oct 3, 2005, at 1:53 PM, Ralph Goers wrote:
Take a poll on the users list.
But please don't use the term close down, instead say merge or
consolidate :-)
—ml—
Bertrand Delacretaz wrote:
In these days of wild thoughts, here's another one: how about closing
the users@ list and having just one list for cocoon-related discussions?
I think I have a few good reasons for this:
One: The line between cocoon users and developers is fairly thin, it
is not
Bertrand Delacretaz wrote:
Le 3 oct. 05, à 22:56, Mark Lundquist a écrit :
...But please don't use the term close down, instead say merge or
consolidate :-)
You're right, of course, merge is much more appropriate.
-Bertrand
Before going too far with this proposal, consider the impact of
Le 4 oct. 05, à 00:00, Sylvain Wallez a écrit :
...I don't have that many reasons, but I don't think this is a good
idea:
One: Marketing wise, this will be a very bad sign, and would give to
the outside world the impression that the Cocoon acceptance has shrunk
so much than two lists are too
Le 4 oct. 05, à 07:13, Berin Loritsch a écrit :
...Before going too far with this proposal, consider the impact of
Stefano's latest thread on the average user. Esp. in light of the
fact that there are several more people who simply lurk than who
actually participate
I'm not going to
On Tuesday 04 October 2005 13:19, Bertrand Delacretaz wrote:
Thanks for your comments, let's see what others think.
I am also against user list. It has a degenerating tone to it, and the fact
that many developers are not subscribed to user@ seems to promote that notion
further.
My suggestion;
27 matches
Mail list logo
