Josh/Till this is a good start, good documentation is painful, but necessary.

David thank you, I think these are great question that we should
present with some easy answers. We should probably start collecting
some of this stuff into one central place. But somebody said on IRC
recently that on big pile of information usually doesn't help either.

>>Tom wrote:
>>- Events/Conferecens
>Not sure yet.
>I have the feeling that I don't see enough talks on SpiderMonkey. For sure, 
>recently, I see less talks on SpiderMonkey >than on V8 and I'm convinced there 
>is no less to say.
>Maybe I'm wrong and look at the wrong place, but SpiderMonkey seems less 
>visible from the outside world. Make it >visible, show your work!

Ha spot on, I think this was my feeling when writing that, too. We
should encourage people besides Dave & David to talk about the stuff
we do. Even maybe at smaller conferences/meetups (I did that recently,
will blog about that soon).

Nicolas:
>Feel free to ask me for any IonMonkey details.  I spent a few hours explaining 
>the same thing to people inside the MV >office, I just need to allocate time 
>to spend on the documentation.  Do we have a structure that we can follow or 
>point >of interest that needs to be documented?
This isn't really about me ;)
What would be really awesome if we could do some short introductory
video (like the old v8 one) and then link to a page that explains
different concepts. I also started collecting some technical papers
that are relevant to the stuff we implement. (Like SSA, Ropes etc.,
feel free to extend
https://wiki.mozilla.org/JavaScript:Compiler_References)


> "Monkey Island" works too :)
Hehe

>I think a part of the JS Team is not used to work much with remotes, including 
>my-self.  We are doing our best, but it is >not as easy to explain when there 
>is no black board.
That isn't really the feeling I have, from purely IRC, maybe we don't
yet think about working with remote people in the right way?

>I noticed that we have fewer work weeks than other team,  Inviting 
>contributors to our work weeks should also remind us
>that we are not alone and that we are working with/for the community.  This 
>not only for discussing the project but mainly
>to bound people together such as the term "JS Team" can have boundaries 
>out-side employees circle.
Exactly what I was thinking :)



What I am really hoping for at the moment that David or so, could
weight in, so we could make the Meeting and weekly notes part working.
For me this is easily the most important part.
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals

Reply via email to