var test = (dev list == a place where developers write and answer to u)
// test -> true
;)
Andrea Dessì
On Sat, Sep 18, 2010 at 01:45, Ryan Florence wrote:
> Welcome to the dev list.
>
> On Sep 17, 2010, at 5:13 PM, Aaron Newton wrote:
>
> sometimes I am unwillingly insulting Aaron because I
Welcome to the dev list.
On Sep 17, 2010, at 5:13 PM, Aaron Newton wrote:
> sometimes I am unwillingly insulting Aaron because I use the
> wrong words - but in the end, language is the least of our problems.
>
> Christoph, for the last time, calling me a "troglodytic bastard" is not
> exactly a
>
> sometimes I am unwillingly insulting Aaron because I use the
> wrong words - but in the end, language is the least of our problems.
>
Christoph, for the last time, calling me a "troglodytic bastard" is not
exactly a case of poor translation...
/kidding
Haha, good one Aaron, I should add that to my invites too.
Aaron's list is a pretty good summary what you can do to get involved.
We want users to start getting active themselves. This is the only way
open source can work. If someone starts to contribute to MooTools, it
won't take long until we re
Keep in mind that the devs are the most active people on the user list.
Anyone looking for us doesn't have to try too hard.
> It's though possible that my assumptions about dev list content are
> incorrect and all that I say here doesn't make sense (is it really as
> "... difficult"? ;)
>
Here's
First, thanks to all for patience ;)
On 17 сен, 17:27, Slik Jay wrote:
> This is not developers problem, this is user's problem.
> If user interested in mootools development, he can join #mootools IRC
> chanel on irc.freenode.net, he can follow mootools developers on
> github (user doesn't know m
To my knowledge we never have asked anyone to leave. I realize you were
joking, but it might not have come across that way as sarcasm often fails to
in text...
On Fri, Sep 17, 2010 at 10:10 AM, Rajeev J Sebastian <
rajeev.sebast...@gmail.com> wrote:
> On Fri, Sep 17, 2010 at 9:52 PM, Aaron Newton
On Fri, Sep 17, 2010 at 9:52 PM, Aaron Newton wrote:
>> Also note that, unlike -users list, dev list and IRC channel can be a
>> bit ... difficult.
>
> Hah. an understatement!
> We're pretty quick to invite people to the dev list. The barrier to getting
> that invite is generally the following:
>
To clarify: the list below is an OR list not an AND list. You just have to
do one of those things, not all of them.
> We're pretty quick to invite people to the dev list. The barrier to getting
> that invite is generally the following:
>
>- you write a few blog posts that are about mootools
>
I'd like to say my opinion.
We have to admit what Aaron is saying is understandable,
and we all can accept it.
:)
I agree.
Andrea
On Fri, Sep 17, 2010 at 18:22, Aaron Newton wrote:
> Also note that, unlike -users list, dev list and IRC channel can be a
>> bit ... difficult.
>>
>
> Hah. an un
>
> Also note that, unlike -users list, dev list and IRC channel can be a
> bit ... difficult.
>
Hah. an understatement!
We're pretty quick to invite people to the dev list. The barrier to getting
that invite is generally the following:
- you write a few blog posts that are about mootools
2010/9/17 Mikhail Korobov :
> I'm a mootools user for several years (since 1.2 release) and only now
> I realized that there is a private dev list. I wasn't able to ask an
> invite because I wasn't aware this list exists. So there is no entry
> point for average developer. What average developer wo
> I'm a mootools user for several years (since 1.2 release) and only now
> I realized that there is a private dev list. I wasn't able to ask an
> invite because I wasn't aware this list exists. So there is no entry
> point for average developer. What average developer would do if he
> want to know
I'm a mootools user for several years (since 1.2 release) and only now
I realized that there is a private dev list. I wasn't able to ask an
invite because I wasn't aware this list exists. So there is no entry
point for average developer. What average developer would do if he
want to know what is ha
The idea is to get in touch with one of the devs on IRC or GTalk.
Communication is key, it is the easiest and best way to get involved.
Feel free to add me http://cpojer.net
On Sep 17, 11:24 am, Rolf -nl wrote:
> Right... this simple question started a nice conversation ;) I think
> there's somet
Right... this simple question started a nice conversation ;) I think
there's something to be said about both views*. Though as it seems to
"work" at this moment, best would be to stay this way. Maybe the dev
list people can keep a short changelog up-to-date with decisions made
which is read only (a
Part of it is that we are gunshy from the original mootools forums. Back in
2006, when MooTools first launched, there was an open forum on MooTools.net
that was quickly populated by people who wanted to use the framework and
discuss it. These were lovely times; everyone there had open, productive
d
I'll continue my offtopic :)
Let's take 'django-developers' list for example. It is public and have
5898 (!) subscribers. This is where all discussions about how to
improve django lives. Only a small part of these thousands of
subscribers actually discuss something. Most of people just read. This
Also, this is the ticket regarding fireEvent:
https://mootools.lighthouseapp.com/projects/2706/tickets/976-resolve-fireevent-issues-with-ie9
(I wrongly said we were staying with triggerEvent :) )
On Sep 17, 1:23 am, Christoph Pojer wrote:
> So the thing was that at the hackathon I discovered tha
So the thing was that at the hackathon I discovered that IE9 doesn't
pick up fireEvent from the Element.prototype. We have tried to find a
fix but it took quite a while (the fact that my IE9 preview 4 crashed
when I opened the dev console didn't help either). I have since posted
the bug to the IE9
Mostly because the dev list is where the dev team feels free to bicker,
mostly about what to name methods (like fireEvent, no, wait, triggerEvent,
no, wait...). If it were public we'd perhaps be less frank with each other.
We aren't hiding secrets but rather ensuring that we behave, in public, with
Aaron, I read this topic by accident and your answer amazes me. Why is
dev list private? This is ridiculous for popular open source project.
On 17 сен, 03:01, Aaron Newton wrote:
> This discussion is on the dev list, which is a private list.
>
>
>
> On Thu, Sep 16, 2010 at 1:49 PM, Rolf -nl wrot
22 matches
Mail list logo
