[hipl-dev] Re: IRC channel
- From: René Hummen <rene.hummen@xxxxxxxxxxxxxxxxx>
- To: hipl-dev@xxxxxxxxxxxxx
- Date: Tue, 25 May 2010 16:00:03 +0200
On May 25, 2010, at 1:21 PM, Diego Biurrun wrote:
> On Tue, May 25, 2010 at 01:16:36PM +0200, René Hummen wrote:
>> On May 25, 2010, at 12:33 PM, Diego Biurrun wrote:
>>> On Tue, May 25, 2010 at 01:13:22PM +0300, Miika Komu wrote:
>>>> On 05/25/2010 11:48 AM, Tobias Heer wrote:
>>>>
>>>>> Am 25.05.2010 um 08:52 schrieb Miika Komu:
>>>>>
>>>>>>> What's bad about that? It's not uncommon for people to lurk on
>>>>>>> dev lists, some of them even appear some day to provide
>>>>>>> patches...
>>>>>>
>>>>>> I noticed some discussion on the IRC channel on this topic. If you
>>>>>> really want to make hipl-dev public, we should give up on
>>>>>> hipl-users list completely and transition all users to hipl-dev.
>>>>>> Based on my earlier experience with the HIPL mailing lists, people
>>>>>> would be only subscribing to hipl-dev, which would leave users list
>>>>>> effectively dead.
>>>>>>
>>>>> I guess if we want to have some serious support for users we cannot
>>>>> merge the two. Otherwise users will be doomed to go through tons of
>>>>> tech brabble. I think the split dev/users isn't that bad at all.
>>>>> Opening dev doesn't change things for me here.
>>>>
>>>> What I am saying is that people will subscribe to the tech babble list
>>>> anyway and will notice this too late. This is what happened earlier when
>>>> I advertised hipl-dev list in the web even though it was invite only. A
>>>> public dev list will just act as a honey pot for newbie people who will
>>>> ask basic usage questions and the users list will just die.
>>>
>>> No, this does not have to be the case. You must *clearly* label
>>> what is ontopic and offtopic for each list. If people ask offtopic
>>> questions, tell them to go elsewhere. If need be, flame them.
>>>
>>> For additional effect make sure that their questions do *not* get
>>> answered on the wrong list. People work like dogs essentially.
>>> If you give them food and then kick them and shout they must go
>>> away, they will come back for the food anyway.
>>
>> What about having HIPL dev world-readable, but only writable by actual
>> developers? Do you think that this could be a viable option? Then
>> there would be no need to flame and scare away possible contributers.
>
> If your possible contributors cannot post, how do you expect them
> to contribute? Telepathy?
Well, they can see the email address of the sender, right!? So we could ask
them (at the webpage) to submit patches to active members of list. These in
turn can post them... Maybe it's more complicated and less open this way,
though.
---
Dipl.-Inform. Rene Hummen, Ph.D. Student
Distributed Systems Group
RWTH Aachen University, Germany
tel: +49 241 80 20772
web: http://ds.rwth-aachen.de/members/hummen
Other related posts:
