Points of contact to the team

[Joe Witt <jo...@gmail.com>]

Hello

So this dev mailing list is a great start and probably sufficient right
now.  But wanted to start thinking about the forms of communication we
should also support as we progress.

IRC appears to be a must if not for any other reason than Tony seems to
live in IRC.

What about something like HipChat?  That seems to  be gaining favor.
Perhaps we can do both.  It is really just a matter of where folks can have
some sort of presence.

I've noticed some projects also do things like keep an eye on Stackoverflow
and the like.

Not entirely sure of what is acceptable from an Apache perspective.  I know
there are a lot of considerations to ensuring that all communications are
public to the greatest extent possible and that they're memorialized.

Other thoughts?

Thanks
Joe

Re: Points of contact to the team

[Benson Margulies <bi...@gmail.com>]

As an Apache culture point, it's preferable to do as much via
archived, email, mailing list stuff as possible. If you want a
real-time channel when you are hacking on the fly, sure, but just keep
in mind that decisions, and discussions that lead towards decisions,
should show up here.


On Wed, Nov 26, 2014 at 11:24 AM, Tony Kurc <tr...@gmail.com> wrote:
> I plan to man #nifi on freenode. I like irc, because to some extent it is
> 'traditional', many OSS projects have official irc channels that have been
> active for over a decade. There are clients of many varieties, web clients,
> graphical clients and command line clients (i use irssi [2], which is a
> command line tool). There is an ASFBot [1] which can hop in the room and
> record meetings for memorializing. freenode has nice nickserv and chanserv
> features [3].
>
>
> [1] http://apache.org/dev/asfbot.html
> [2] http://www.irssi.org/
> [3] https://freenode.net/using_the_network.shtml
>
> On Wed, Nov 26, 2014 at 10:49 AM, Joe Witt <jo...@gmail.com> wrote:
>
>> Hello
>>
>> So this dev mailing list is a great start and probably sufficient right
>> now.  But wanted to start thinking about the forms of communication we
>> should also support as we progress.
>>
>> IRC appears to be a must if not for any other reason than Tony seems to
>> live in IRC.
>>
>> What about something like HipChat?  That seems to  be gaining favor.
>> Perhaps we can do both.  It is really just a matter of where folks can have
>> some sort of presence.
>>
>> I've noticed some projects also do things like keep an eye on Stackoverflow
>> and the like.
>>
>> Not entirely sure of what is acceptable from an Apache perspective.  I know
>> there are a lot of considerations to ensuring that all communications are
>> public to the greatest extent possible and that they're memorialized.
>>
>> Other thoughts?
>>
>> Thanks
>> Joe
>>

Re: Points of contact to the team

[Tony Kurc <tr...@gmail.com>]

I plan to man #nifi on freenode. I like irc, because to some extent it is
'traditional', many OSS projects have official irc channels that have been
active for over a decade. There are clients of many varieties, web clients,
graphical clients and command line clients (i use irssi [2], which is a
command line tool). There is an ASFBot [1] which can hop in the room and
record meetings for memorializing. freenode has nice nickserv and chanserv
features [3].


[1] http://apache.org/dev/asfbot.html
[2] http://www.irssi.org/
[3] https://freenode.net/using_the_network.shtml

On Wed, Nov 26, 2014 at 10:49 AM, Joe Witt <jo...@gmail.com> wrote:

> Hello
>
> So this dev mailing list is a great start and probably sufficient right
> now.  But wanted to start thinking about the forms of communication we
> should also support as we progress.
>
> IRC appears to be a must if not for any other reason than Tony seems to
> live in IRC.
>
> What about something like HipChat?  That seems to  be gaining favor.
> Perhaps we can do both.  It is really just a matter of where folks can have
> some sort of presence.
>
> I've noticed some projects also do things like keep an eye on Stackoverflow
> and the like.
>
> Not entirely sure of what is acceptable from an Apache perspective.  I know
> there are a lot of considerations to ensuring that all communications are
> public to the greatest extent possible and that they're memorialized.
>
> Other thoughts?
>
> Thanks
> Joe
>