Re: [Elementary-dev-community] Question regarding Slack Access and IRC

2015-04-14 Thread Cameron Norman
On Sun, Apr 12, 2015 at 6:34 PM, Nopey Nope  wrote:
> There are solutions that bridge a single channel in slack to an IRC channel:
> https://github.com/jimmyhillis/slack-irc-plugin
>
> I think this would be an ideal solution.  That way, slack members aren't
> completely cut-off from IRC, but the division of the specific channel helps
> prevent the "virtual office" from being disruptive.  Ignore the channel if
> you want, or stop on in if you feel like it.

We actually already have this, but it is read only so it amounts to
very little unfortunately... not a fluid design at all.

> I just don't think it's healthy to move the experienced individuals away to
> a "walled garden" where you will have no indication of a serious problem.

Indeed, and for now just try to contribute to bugs that seem
simple/easy. We use the bitesize tag for easy bugs, see a list here:

https://bugs.launchpad.net/elementary/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=bitesize&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on

If you have any questions, feel free to get in touch.

Cheers,
--
Cameron Norman

-- 
Mailing list: https://launchpad.net/~elementary-dev-community
Post to : [email protected]
Unsubscribe : https://launchpad.net/~elementary-dev-community
More help   : https://help.launchpad.net/ListHelp


Re: [Elementary-dev-community] Question regarding Slack Access and IRC

2015-04-12 Thread Nopey Nope
There are solutions that bridge a single channel in slack to an IRC
channel: https://github.com/jimmyhillis/slack-irc-plugin

I think this would be an ideal solution.  That way, slack members aren't
completely cut-off from IRC, but the division of the specific channel helps
prevent the "virtual office" from being disruptive.  Ignore the channel if
you want, or stop on in if you feel like it.

I just don't think it's healthy to move the experienced individuals away to
a "walled garden" where you will have no indication of a serious problem.

On Sun, Apr 12, 2015 at 8:46 PM, Daniel Foré 
wrote:

> Hey there,
>
> I definitely understand your concerns and we've talked about trying to set
> up a public channel but Slack just isn't built to do that. So there are
> technical challenges.
>
> But I think one thing that should be made clear is that developers are not
> support staff. Some developers have made themselves available to provide
> support and that's awesome, but that is their choice. Slack is not a
> Support channel. It's our "virtual office". It's our work place. Not a call
> center.
>
> That said, we definitely understand that providing better information and
> support is something very important and it is one of the goals of the new
> website. I think you'll find that the new "get involved" page has way more
> information than the old one and we intend to continue to iterate to make
> it better.
>
> Cheers,
>
> Daniel Foré
> elementaryos.org
>
>
> On Sun, Apr 12, 2015 at 8:34 AM, Nopey Nope 
> wrote:
>
>> Hi!  I'm a little new here.
>>
>> I'm primarily a C and Java dev, with a comfortable level of Linux
>> experience.  I'm by NO MEANS an expert, but I truly enjoy helping other
>> people solve issues if I'm able to help.
>>
>> I maintain an IRC presence for a couple projects, and I fell in love with
>> Elementary the moment I saw it.  I don't mind answering some of the easier
>> questions, or topics in our channel (#Elementary at irc.freenode.net),
>> but the dev's perspective has... put me off a little bit.
>>
>> From an IRC-perspective, the Dev's have basically created a walled garden
>> with how they treat the slack servers.  I personally understand WHY they
>> have done so.  And... *that's completely fine.* Creating a space where
>> developers can go and talk to other developers on an invite-only basis is
>> incredibly healthy, and encourages a lot of growth for that community.  I
>> don't want that to stop.
>>
>> The issues arise when we're stuck in the IRC channel alone.  I'm
>> comfortable with bash scripts, some basic package-managing, and I've helped
>> with a couple of other odd issues, so I feel comfortable/qualified to at
>> least try and help, but what happens when I run into another issue that
>> needs a more experienced perspective?
>>
>> There are a couple of other individuals in the channel who can also help,
>> but that isn't always enough.  We run into questions that require some more
>> insight, and because the knowledgeable talent is behind slack, it's largely
>> inaccessible.
>>
>> I've had to redirect a number of individuals to the sub-reddit, but
>> that's not a great solution if Eos' IRC just points people Reddit all the
>> time...  (Also, I'm disregarding SO atm)
>>
>> Has the dev-community considered adding an IRC-bridge channel?  If not,
>> would it be possible to allow members interested in support to join the
>> Slack server?  I feel like there needs to be SOME level of access, but I
>> understand why the devs would want to limit it, or have it go though some
>> level of filtering before the devs are constantly barraged with a stream of
>> "it doesn't work"
>>
>> Thoughts?
>> -CptSpaceToaster-
>>
>
>
-- 
Mailing list: https://launchpad.net/~elementary-dev-community
Post to : [email protected]
Unsubscribe : https://launchpad.net/~elementary-dev-community
More help   : https://help.launchpad.net/ListHelp


Re: [Elementary-dev-community] Question regarding Slack Access and IRC

2015-04-12 Thread Luis Alonso Calle Núñez
Totally agreed with Nopey Nope. We need a better support for newbie 
developers.


On dom, abr 12, 2015 at 10:34 AM, Nopey Nope 
 wrote:

Hi!  I'm a little new here.

I'm primarily a C and Java dev, with a comfortable level of Linux 
experience.  I'm by NO MEANS an expert, but I truly enjoy helping 
other people solve issues if I'm able to help.


I maintain an IRC presence for a couple projects, and I fell in love 
with Elementary the moment I saw it.  I don't mind answering some of 
the easier questions, or topics in our channel (#Elementary at 
irc.freenode.net), but the dev's perspective has... put me off a 
little bit.


From an IRC-perspective, the Dev's have basically created a walled 
garden with how they treat the slack servers.  I personally 
understand WHY they have done so.  And... that's completely fine. 
Creating a space where developers can go and talk to other developers 
on an invite-only basis is incredibly healthy, and encourages a lot 
of growth for that community.  I don't want that to stop.


The issues arise when we're stuck in the IRC channel alone.  I'm 
comfortable with bash scripts, some basic package-managing, and I've 
helped with a couple of other odd issues, so I feel 
comfortable/qualified to at least try and help, but what happens when 
I run into another issue that needs a more experienced perspective?


There are a couple of other individuals in the channel who can also 
help, but that isn't always enough.  We run into questions that 
require some more insight, and because the knowledgeable talent is 
behind slack, it's largely inaccessible.


I've had to redirect a number of individuals to the sub-reddit, but 
that's not a great solution if Eos' IRC just points people Reddit all 
the time...  (Also, I'm disregarding SO atm)


Has the dev-community considered adding an IRC-bridge channel?  If 
not, would it be possible to allow members interested in support to 
join the Slack server?  I feel like there needs to be SOME level of 
access, but I understand why the devs would want to limit it, or have 
it go though some level of filtering before the devs are constantly 
barraged with a stream of "it doesn't work"


Thoughts?
-CptSpaceToaster-
-- 
Mailing list: https://launchpad.net/~elementary-dev-community
Post to : [email protected]
Unsubscribe : https://launchpad.net/~elementary-dev-community
More help   : https://help.launchpad.net/ListHelp