Opened 10 years ago

Last modified 10 years ago

#2936 new defect

IRC 10 should not default to #sugar-es but to #sugar

Reported by: satellit Owned by: fran
Priority: High Milestone: Unspecified
Component: Irc Version: Unspecified
Severity: Unspecified Keywords: IRC, default channel
Cc: Distribution/OS: Unspecified
Bug Status: Unconfirmed

Description

IRC-10.xo should default to #sugar not #sugar-es. When new users log on to IRC and see almost no one on #sugar-es. Thus they think no one is available on line. They can switch to the #sugar-es if they need translation to occur.

Change History (4)

comment:1 Changed 10 years ago by RafaelOrtiz

My though here is that by default should be #sugar-es as the majority of sugar users are located in LA, the desired behavior is that irc, enters as per default in #sugar-lang channel.

Anyway, I think you are right and we must change it to enter #sugar and not #sugar-es
per default.

comment:2 follow-up: Changed 10 years ago by walter

I thought we had decided long ago that we grab $LANG and append the suffix based on that. BTW, If you end up in sugar-es, you should be seeing a google-translation of all of the #sugar chat and the Topic for the channel explains this and offers up a link directly to #sugar. Is that not sufficient?

comment:3 in reply to: ↑ 2 Changed 10 years ago by satellit

Replying to walter:

I thought we had decided long ago that we grab $LANG and append the suffix based on that. BTW, If you end up in sugar-es, you should be seeing a google-translation of all of the #sugar chat and the Topic for the channel explains this and offers up a link directly to #sugar. Is that not sufficient?

The main problem is that the list of users displayed in #sugar-es is very small and it appears that no one is available to communicate with on IRC.

I agree it would be a much better solution to access $LANG and connect to the appropriate meeting translate channel. Including connecting to #sugar for english.

comment:4 Changed 10 years ago by RafaelOrtiz

This feature should be in next version (not yet coded), can we close this one as it only refers to v10 ?,
and fill a new one describing the desired behavior of per-lang channels.

Note: See TracTickets for help on using tickets.