Re: [ros-dev] Opening up #reactos-dev to the public

[Michael Fritscher]

Too many chans will clutter it, in the end the devs will have to join 10
chans. The chans aren't that high-traffic ones.

I think we should yust try to do a -m and see what happens.
> Yes, that's a better idea. #reactos-gsoc
>
> On Fri, Mar 24, 2017 at 6:53 PM, Alex Ionescu [e-mail] wrote:
> > I don't agree. Maintain the auto-voice lists and get someone in charge
> > of
> > operations, like I used to be for many years on IRC.
> >
> > Instead, why not create a #reactos-gsoc or something?
> >
> > Best regards,
> > Alex Ionescu
> >
> > On Fri, Mar 24, 2017 at 11:19 AM, Mark Jansen [e-mail]
> > wrote:
> > > We can always try it out?
> > > If it doesnt work, restoring it is a simple as setting a flag on the
> > > channel.
> > >
> > > On 24 March 2017 at 16:31, David Quintana (gigaherz)
> > > [e-mail]
> > > wrote:
> > > > I disagree -- if we can be firm about the channel being only for
> > >
> > > development
> > > > talk, things should remain mostly as they are now.
> > > >
> > > > In any community, there's inevitably going to be idle talk, offtopic
> > > > conversations, etc. If you only have ONE place to talk in, all those
> > >
> > > thigns
> > > > are going to be mixed in with actual dev talk, but if you have clear
> > >
> > > rooms
> > > > set for each thing, the majority of people will be happy to leave all
> > >
> > > the
> > > > offtopic talk to the main channel, and dev talk to the dev channel.
> > > >
> > > > It works for plenty other projects and communities so there's no
> > >
> > > reason
> > > to
> > > > be pessimistic and think that "our idiots are worse". It's simply not
> > >
> > > true.
> > > > I vote for trying, and we can always put back the +m if things get
> > >
> > > out
> > > of
> > > > hand.
> > > >
> > > > On 24 March 2017 at 16:13, Hermès BÉLUSCA-MAÏTO
> > >
> > > [e-mail]
> > > > wrote:
> > > > > I don’t approve the idea. The fact is that if the devs quit
> > >
> > > originally
> > > > > #reactos, it’s because it was generally too noisy, etc… . If we
> > >
> > > remove
> > > the
> > > > > moderation irc bit in #reactos-dev, you may expect the same
> > >
> > > phenomenon
> > > to
> > > > > occur in #reactos-dev too.
> > > > >
> > > > > De : Ros-dev [mailto:[e-mail]] De la part de
> > >
> > > David
> > > > > Quintana (gigaherz)
> > > > > Envoyé : vendredi 24 mars 2017 11:35
> > > > > À : ReactOS Development List
> > > > > Objet : Re: [ros-dev] Opening up #reactos-dev to the public
> > > > >
> > > > > I approve the idea.
> > > > >
> > > > > On 24 March 2017 at 11:21, Colin Finck [e-mail] wrote:
> > > > >
> > > > > Hi all!
> > > > >
> > > > > As you all know, our #reactos-dev IRC channel has been a moderated
> > >
> > > IRC
> > > > > channel for decades, and only operators (devs) and voiced people can
> > > > > talk. While we always tried to keep discussions dev-related there,
> > >
> > > no
> > > > > topic has ever been enforced on #reactos. The result is that I see a
> > > > > notable number of developers only on #reactos-dev these days.
> > > > >
> > > > > This is a pretty bad situation! Emerging developers hardly have a
> > >
> > > way
> > > to
> > > > > interact with all existing devs on IRC. Often enough, legitimate
> > > > > questions from them remain unanswered on #reactos. Moreover, we
> > >
> > > don't
> > > > > maintain the list of voiced people thoroughly, so even some
> > >
> > > contributors
> > > > > have to ask for temporary voice on #reactos-dev.
> > > > >
> > > > > Keep in mind that we're currently in the GSoC phase where students
> > >
> > > shall
> > > > > submit their proposals and get in touch with the developers.
> > > > > How are they going to do this on IRC if #reactos-dev continues to be
> > >
> > > an
> > > > > exclusive club?
> > > > >
> > > > > Because of these reasons, I'm proposing to remove the moderation bit
> > >
> > > on
> > > > > #reactos-dev and let everybody talk there.
> > > > > Its development topic should be enforced though! As soon as people
> > >
> > > get
> > > > > too off-topic, they should be directed to #reactos and kicked if
> > >
> > > nothing
> > > > > else helps. Given that all devs are already operators on
> > >
> > > #reactos-dev,
> > > > > it's fully in their hands.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Colin
> > > > >
> > > > > Ros-dev mailing list
> > > > > [e-mail]
> > > > > http://www.reactos.org/mailman/listinfo/ros-dev
> > > > >
> > > > > Ros-dev mailing list
> > > > > [e-mail]
> > > > > http://www.reactos.org/mailman/listinfo/ros-dev
> > > >
> > > > Ros-dev mailing list
> > > > [e-mail]
> > > > http://www.reactos.org/mailman/listinfo/ros-dev
> > >
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev