On 20.09.2007, Austin Appel wrote:
It seems that we have had a big surge in annoyances in
#rockbox lately. To put it short, do people think the time has
come where we need to move to the split model? #rockbox (for
support), #rockbox-dev (for development), #rockbox-community
I never
On 9/20/07, Austin Appel [EMAIL PROTECTED] wrote:
To put it short, do people think the time has come where we need to move to
the split model? #rockbox (for support), #rockbox-dev (for development),
#rockbox-community (for offtopic and social)
While I'm in favor of cutting down the noise in
It seems that we have had a big surge in “annoyances”
in #rockbox lately. To put it short, do people think
the time has come where we need to move to the split model?
#rockbox (for support), #rockbox-dev (for development),
#rockbox-community (for offtopic and social). All channels
I would also *strongly* prefer a single channel.
I have not found the user helping aspect annoying, and it's sometimes
useful to stimulate development ideas. If people are annoying, then a
quick RTFM response is perfectly acceptable; if they continue to annoy, why
not have a few more channel
Dominik Riebeling wrote:
While I'm in favor of cutting down the noise in #rockbox let me
propose a slightly different approach: why not just keep #rockbox for
development and extended support and direct all new users to
#rockbox-community and provice basic support there? I.e. just make
cgi::irc to
On Wed, 19 Sep 2007, Austin Appel wrote:
It seems that we have had a big surge in annoyances in #rockbox lately. To
put it short, do people think the time has come where we need to move to the
split model?
In my view we're far from a situation where that is needed, and thus I am
against it.
On Thu, 20 Sep 2007, Jonas Häggqvist wrote:
also whats the user attribute?
It's a not-yet implemented feature of langv2 and I believe it's related to
allowing translation and voice for plugins.
Yes, it is meant to allow the language or voice binary to have a speal chunk
for a particular
Daniel Stenberg wrote:
Splitting users from devs (even the distinction is wierd) will just
risk that either users sit in a channel where not enough devs are so
they won't get the help they seek, or they come to the dev channel to
ask the questions since there's where the devs are etc.
And I
How do you measure infrequently ?
I don't - without logs it's not easy to. All I know is that on the
occasions I've been in there (not many, granted), I've only seen tumbleweed.
--
pondlife
I'm also strongly in favour of keeping a single channel - I'm not that
annoyed by off-topic chat (I can easily ignore it), and very much like
the fact that the Rockbox community is one where there is no strong
distinction between devs and users - every user is encouraged to help
themselves and
Maybe the rules need a little tightening first? Could we have the same
rules for support on both IRC and the forums? Enough to say that you
should RTFM before asking a question.
The rules are already pretty tight and are *supposed* to be read before
speaking, but do you have any suggestions for
The rules are already pretty tight and are *supposed* to be read before
speaking, but do you have any suggestions for changing them?
http://www.rockbox.org/wiki/IrcGuidelines
The only way to ensure the rules are read is to introduce an IRC
CAPTCHA. This would require the user to have read the
The only way to ensure the rules are read is to introduce an IRC
CAPTCHA. This would require the user to have read the rules, and then
respond to an automated question posed by a bot to them when they
first enter the channel. Only when they respond with the correct
answer (presumably
well, it could of course be used only if you're using the web client
and have not registered to freenode -- or is something like this too
hard to implement?
Otoh, I'm not sure if this is really necessary if we enforce the rules
more strictly.
It could be implemented using a bot and a voicing
On 9/20/07, Dave Chapman [EMAIL PROTECTED] wrote:
I'm also strongly in favour of keeping a single channel - I'm not that
annoyed by off-topic chat (I can easily ignore it), and very much like
the fact that the Rockbox community is one where there is no strong
distinction between devs and users
On Thu, 20 Sep 2007, Jonas Häggqvist wrote:
The current format was introduced/discussed [1] in June 2006, where Daniel
Stenberg proposed the current format in relation to the langv2 rework and a
small-scale flamewar about using an XML format erupted. In the end, I think
Daniel got tired of
Jonas Häggqvist wrote:
I still doubt translators will care much one way or the other, even if they
were to edit the file by hand. For now, I'll go ahead and have a go at
implementing genlang using this XML format.
One additional question: is the XML parser module included in standard
Perl? Or
Hi,
What does everyone think of having a wiki page for blind users which
will have the following:
How to code when your blind;
how to setup your environment;
Describes how to apply patches and how to use cygwin with a screenreader;
Maybe linux as well if someone knows about that;
also some
Linus Nielsen Feltzing wrote:
Jonas Häggqvist wrote:
I still doubt translators will care much one way or the other, even if
they
were to edit the file by hand. For now, I'll go ahead and have a go at
implementing genlang using this XML format.
One additional question: is the XML parser
Jonas Häggqvist wrote:
Linus Nielsen Feltzing wrote:
Jonas Häggqvist wrote:
I still doubt translators will care much one way or the other, even if
they
were to edit the file by hand. For now, I'll go ahead and have a go at
implementing genlang using this XML format.
One additional question:
Jerry Van Baren wrote:
Jonas Häggqvist wrote:
It seems that Cygwin does not package any non-core modules
for Perl, so we're out of luck for any XML parser.
I'm running cygwin perl for an unrelated purpose and my installation
supports Expat:
use XML::Parser
with no extra work.
In fact,
On Thu, Sep 20, 2007 at 09:52:27PM +1000, Daniel Dalton wrote:
Hi,
What does everyone think of having a wiki page for blind users which
will have the following:
How to code when your blind;
how to setup your environment;
Describes how to apply patches
All this is pretty trivial
Sorry for being so late with this response. It's been a busy week and I
really wanted to respond to Daniel's comments...
Daniel Stenberg wrote:
On Tue, 11 Sep 2007, Ray Lambert wrote:
The GPL has a specific reason for existing. It's to protect the hard work
of programmers from those people
DervishD wrote:
No, IANAL, but I read Groklaw a lot... ;)
Well, that's almost like being a lawyer without having to eat human
flesh ...
Very funny! I love it! :-)
~ray
On 21/09/2007 12:03 AM, Tapio Kelloniemi wrote:
Cygwin support might be appropriate for someone, but I strongly
recommend
that general instructions for compiling Rockbox would not be repeated there.
It was mainly going to be about useful patches for blind users for
example p6323.
On 20/09/2007 10:33 PM, RaZorbacK wrote:
sure I am. there're some valuable infos and tutorials what shoudn't be
lost. i'm thinking about one in particular by a guy named Sean which is
worth putting on the wiki. it's rally well done and it had helped me
installing my cygwin without any
Daniel Dalton wrote on 20/09/2007 23:58 :
That could go in the setting up cygwin section. It isn't the same as the
other guide since it is written for how to do it when your blind and
with a screenreader.
if he's not reading this, I will ask Sean if he agree that I pu his work
on the wiki
27 matches
Mail list logo
