Please organize your efforts with the core team if your going to do
more. This will avoid frustration on your side and lead to better
contributions to MooTools. (An example would be the documentation of
native javascript functionality which we don't want).
I'd gladly guide you or other people on how to contribute. Ping me on
IRC (JanK) or just drop me a mail for instant messanger info.
On Jan 9, 2009, at 11:03, keif wrote:
I'd be all about jumping in on editing the docs and the like, and I
currently have a demo dump for most of my stuff (it's a combination of
my scripts, scripts I've found/liked).
I'll do my best (errrr) to try and convert all the old demos and come
up with a decent presentation page for consideration to be moved to
the official demos - I'd especially *love* to have the show/hide of
the 1.11 demos put back in.
-kb
On Jan 9, 1:27 am, rpflo <[email protected]> wrote:
While the docs could use some help (I guess), I love them.
I'm a graphic designer who got involved with a software company
designing their user interfaces. I don't consider myself a developer,
and I don't know a lick of "real" javascript. I got sick of our
developers saying things were "too hard" or "impossible" and set out
to learn to program a bit to throw it back at them (if the graphic
designer can do it ... why can't the devs?!).
When mootools 1.2 and the new website came out things finally started
to click. I quit being a copy/paste moron, and have started to build
some really impressive applications interfaces (so much so that
when I
showed one of my company's real developers an interface piece I
designed and asked if we could add that to our company's web app he
said "Desktop stuff is hard to move onto the web" and I replied "this
is javascript: it is the web").
So anyway, just saying, the new docs page helped me go from idiot
to a
decent code monkey. So thank you!
(from a usability stand point it's top-notch, very well thought out)
On Jan 8, 4:14 pm, nutron <[email protected]> wrote:
Doc changes should go through github. Fork the core, make your
change, and
send a pull request.
The Event.target thing is not something that needs to be
documented as it's
part of JavaScript, and our documentation should not seek to cover
that
ground.
On Thu, Jan 8, 2009 at 3:11 PM, jiggliemon (via Nabble) <
[email protected]<ml-user
%[email protected]>
wrote:
As I learn more about the library I'd like to update the docs.
Nutron
recently helped clear up some Event.target questions I had that
would
be well suited in the docs (as they're unclear about where the
target
is referent to) and other minor issues like this.
Is there someone we could email the doc submissions to currently?
On Jan 8, 9:04 am, nutron <anut...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2130784&i=0
>>
wrote:
I think version control for the docs is just fine - I don't
think we
should
move the docs off github.
On Thu, Jan 8, 2009 at 12:14 AM, Jan Kassens (via Nabble) <
ml-user+57495-467023...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2130784&i=1
>
<ml-user%2b57495-467023...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2130784&i=2
>>
wrote:
I just wanted to chime in here and say that I'm pretty excited
about
all your enthusiasm and every contribution from the community is
highly welcome. (after all it is an open source project!).
But I also figured the infrastructure isn't perfect, especially
because git is a bit different from what most people know, but
those
who are want to learn it are free to fork mootools on github
and send
me a pull request.
I'll try to think of an easier way to contribute to the docs as
well
as the demos. Perfectly something not involving a version control
system at least for the docs.
On Jan 8, 2009, at 0:42, nutron wrote:
Before all this good will evaporates, let me reiterate that
all you
guys / gals who are saying you want to help is both much
appreciated
and quite welcome.
At issue now is mostly that of infrastructure. Specifically,
making
it so that you CAN contribute to things like the demos, which
are no
longer part of the code repository (and thus harder for you to
get
your hands on). I'm still looking for Tom and Valerio to pop
online.
Tom just moved out here (to California) for his new job like,
4 days
ago, and Valerio had some huge deadline as of a few days ago. So
I'll keep this as a to-do item on my list to get them engaged on
this topic as soon as possible. Don't get discouraged if it
takes a
few more days. It's the beginning of the year and a lot of
people
are still kinda getting their wheels rolling after taking a long
vacation.
Stay tuned.
--
Jan - MooTools comitter
twitter/blog:http://kassens.net
------------------------------
View message @
http://n2.nabble.com/General-thoughts-on-Mootools.net-tp2118117p21268
...
To start a new topic under MooTools Users, email
ml-node+660466-1583815...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2130784&i=3
>
<ml-node%2b660466-1583815...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2130784&i=4
>>
To unsubscribe from MooTools Users, click here< (link removed) >.
-----
The MooTools Tutorial: http://www.mootorial.comwww.mootorial.com
Clientcide: http://www.clientcide.comwww.clientcide.com
--
View this message in context:
http://n2.nabble.com/General-thoughts-on-Mootools.net-tp2118117p21288
...
Sent from the MooTools Users mailing list archive at Nabble.com.
------------------------------
View message @
http://n2.nabble.com/General-thoughts-on-Mootools.net-tp2118117p21307
...
To start a new topic under MooTools Users, email
[email protected]<ml-node
%[email protected]>
To unsubscribe from MooTools Users, click here< (link removed) >.
-----
The MooTools Tutorial: http://www.mootorial.comwww.mootorial.com
Clientcide: http://www.clientcide.comwww.clientcide.com
--
View this message in context:http://n2.nabble.com/General-thoughts-on-Mootools.net-tp2118117p21307
...
Sent from the MooTools Users mailing list archive at Nabble.com.
--
Jan - MooTools comitter
http://kassens.net
