Hi I am interested in contributing mozilla.especially to know more about RUST.I tried installing it on my Ubuntu.after make && make install I am getting an error.please report the issue https://gist.github.com/Tessie/7470406 Regards Tessy
On Thu, Nov 14, 2013 at 11:35 AM, <[email protected]> wrote: > Send Rust-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.mozilla.org/listinfo/rust-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Rust-dev digest..." > > > Today's Topics: > > 1. Rust docs (Daniel Glazman) > 2. Re: Rust docs (Corey Richardson) > 3. Re: Rust docs (Philip Herron) > 4. Re: Rust docs (Thad Guidry) > 5. Call for speakers at the next Bay Area meetup (Erick Tryzelaar) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 14 Nov 2013 16:03:36 +0100 > From: Daniel Glazman <[email protected]> > To: [email protected] > Subject: [rust-dev] Rust docs > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello rust-dev, > > I would like to make a comment I feel is important about both the Rust > tutorial and manual. Please don't misunderstand me, no flame here, I > am sending this message to help. I think good docs are extremely > important to increase the size of a community, and in particular make > more people contribute to Servo (the reason why I'm here). > > If the Reference Manual for Rust tries to be complete and does not try > to avoid language complexity, it can be from time to time hard to read > because of one thing: examples are not well or often enough explained > and are often too complex given the section they belong too. It's for > instance difficult for the reader to understand an example of section > n that uses notions explained only in section n+4. > > The Tutorial is the entry point for all people willing to investigate > Rust and/or contribute to Servo. I think that document is super > precious, super-important. Unfortunately, I don't think it is really a > tutorial but only a lighter manual. Examples are here even more > important than in the case of the Manual above. A good Tutorial is > often built around one single programming task that becomes more and > more complex as more features of the language are read and > known. Furthermore, the Tutorial has clearly adopted the language > complexity of the reference manual, something that I think should be > in general avoided. I also think all examples should be buildable > and produce a readable result on the console even if that result is a > build or execution error. That would drastically help the reader. > > All in all, I think the Tutorial needs some love and probably a > technical writer who is not working on the guts of Rust, someone who > could vulgarize the notions of the Manual into an easy-to-read, > simple-to-experiment, step-by-step tutorial and avoiding in general > vocabulary inherited from programming language science. > > Best regards, > > </Daniel> > > > ------------------------------ > > Message: 2 > Date: Thu, 14 Nov 2013 10:38:53 -0500 > From: Corey Richardson <[email protected]> > To: Daniel Glazman <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: [rust-dev] Rust docs > Message-ID: > < > ca++bo6rk41vs-gtlw8wbuge7pbd3_egxzmdj9nhoqskyl24...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Thu, Nov 14, 2013 at 10:03 AM, Daniel Glazman > <[email protected]> wrote: > > The Tutorial is the entry point for all people willing to investigate > > Rust and/or contribute to Servo. I think that document is super > > precious, super-important. Unfortunately, I don't think it is really a > > tutorial but only a lighter manual. Examples are here even more > > important than in the case of the Manual above. A good Tutorial is > > often built around one single programming task that becomes more and > > more complex as more features of the language are read and > > known. Furthermore, the Tutorial has clearly adopted the language > > complexity of the reference manual, something that I think should be > > in general avoided. I also think all examples should be buildable > > and produce a readable result on the console even if that result is a > > build or execution error. That would drastically help the reader. > > > > All in all, I think the Tutorial needs some love and probably a > > technical writer who is not working on the guts of Rust, someone who > > could vulgarize the notions of the Manual into an easy-to-read, > > simple-to-experiment, step-by-step tutorial and avoiding in general > > vocabulary inherited from programming language science. > > > > I agree, partially. I think "Rust for Rubyists" fills this role quite > well for now. Generally I think the language tutorial should not try > to hide complexity or paper over things, at the very least so it can > be complete and correct. I think the Python tutorial is a good > benchmark. We might even be able to rip off the Python tutorial's > structure wholesale. > > The "on-boarding" process is still very rough. Maybe some sort of > live-comment system would work well for finding pain points, where one > can add comments/feedback while reading the tutorial. > > > ------------------------------ > > Message: 3 > Date: Thu, 14 Nov 2013 15:51:23 +0000 > From: Philip Herron <[email protected]> > To: Corey Richardson <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: [rust-dev] Rust docs > Message-ID: > < > caevrbeqnf+znf-n-jwmie5axmtmjg2fmaye_rhjdbuijyez...@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > I would defineltly like to see a clone of the python tutorial because it > really does it so well going inch by inch building up what way things work > i am not a web developer but would love to write content i wonder is it > possible to start a github project for this using sphinx i think it uses > isn't it? > > > On 14 November 2013 15:38, Corey Richardson <[email protected]> wrote: > > > On Thu, Nov 14, 2013 at 10:03 AM, Daniel Glazman > > <[email protected]> wrote: > > > The Tutorial is the entry point for all people willing to investigate > > > Rust and/or contribute to Servo. I think that document is super > > > precious, super-important. Unfortunately, I don't think it is really a > > > tutorial but only a lighter manual. Examples are here even more > > > important than in the case of the Manual above. A good Tutorial is > > > often built around one single programming task that becomes more and > > > more complex as more features of the language are read and > > > known. Furthermore, the Tutorial has clearly adopted the language > > > complexity of the reference manual, something that I think should be > > > in general avoided. I also think all examples should be buildable > > > and produce a readable result on the console even if that result is a > > > build or execution error. That would drastically help the reader. > > > > > > All in all, I think the Tutorial needs some love and probably a > > > technical writer who is not working on the guts of Rust, someone who > > > could vulgarize the notions of the Manual into an easy-to-read, > > > simple-to-experiment, step-by-step tutorial and avoiding in general > > > vocabulary inherited from programming language science. > > > > > > > I agree, partially. I think "Rust for Rubyists" fills this role quite > > well for now. Generally I think the language tutorial should not try > > to hide complexity or paper over things, at the very least so it can > > be complete and correct. I think the Python tutorial is a good > > benchmark. We might even be able to rip off the Python tutorial's > > structure wholesale. > > > > The "on-boarding" process is still very rough. Maybe some sort of > > live-comment system would work well for finding pain points, where one > > can add comments/feedback while reading the tutorial. > > _______________________________________________ > > Rust-dev mailing list > > [email protected] > > https://mail.mozilla.org/listinfo/rust-dev > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mail.mozilla.org/pipermail/rust-dev/attachments/20131114/7361ce13/attachment-0001.html > > > > ------------------------------ > > Message: 4 > Date: Thu, 14 Nov 2013 10:21:46 -0600 > From: Thad Guidry <[email protected]> > To: Corey Richardson <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: [rust-dev] Rust docs > Message-ID: > <CAChbWaOxs-1= > [email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Corey, > > Could we get that comments/feedback ability into the tutorial easily ? I > agree that would be a good start in improving things. > > > On Thu, Nov 14, 2013 at 9:38 AM, Corey Richardson <[email protected]> > wrote: > > > On Thu, Nov 14, 2013 at 10:03 AM, Daniel Glazman > > <[email protected]> wrote: > > > The Tutorial is the entry point for all people willing to investigate > > > Rust and/or contribute to Servo. I think that document is super > > > precious, super-important. Unfortunately, I don't think it is really a > > > tutorial but only a lighter manual. Examples are here even more > > > important than in the case of the Manual above. A good Tutorial is > > > often built around one single programming task that becomes more and > > > more complex as more features of the language are read and > > > known. Furthermore, the Tutorial has clearly adopted the language > > > complexity of the reference manual, something that I think should be > > > in general avoided. I also think all examples should be buildable > > > and produce a readable result on the console even if that result is a > > > build or execution error. That would drastically help the reader. > > > > > > All in all, I think the Tutorial needs some love and probably a > > > technical writer who is not working on the guts of Rust, someone who > > > could vulgarize the notions of the Manual into an easy-to-read, > > > simple-to-experiment, step-by-step tutorial and avoiding in general > > > vocabulary inherited from programming language science. > > > > > > > I agree, partially. I think "Rust for Rubyists" fills this role quite > > well for now. Generally I think the language tutorial should not try > > to hide complexity or paper over things, at the very least so it can > > be complete and correct. I think the Python tutorial is a good > > benchmark. We might even be able to rip off the Python tutorial's > > structure wholesale. > > > > The "on-boarding" process is still very rough. Maybe some sort of > > live-comment system would work well for finding pain points, where one > > can add comments/feedback while reading the tutorial. > > _______________________________________________ > > Rust-dev mailing list > > [email protected] > > https://mail.mozilla.org/listinfo/rust-dev > > > > > > -- > -Thad > +ThadGuidry <https://www.google.com/+ThadGuidry> > Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mail.mozilla.org/pipermail/rust-dev/attachments/20131114/56237d25/attachment-0001.html > > > > ------------------------------ > > Message: 5 > Date: Thu, 14 Nov 2013 08:35:05 -0800 > From: Erick Tryzelaar <[email protected]> > To: "[email protected]" <[email protected]> > Subject: [rust-dev] Call for speakers at the next Bay Area meetup > Message-ID: > < > caldfqqlpyyhv8ddxnjr4hvq3k8nzyp+mldqp6s+joqecbzz...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Good morning Rustics, > > The second Bay Area meetup is happening in 6 days: > > http://www.meetup.com/Rust-Bay-Area/events/143439552/ > > Patrick will be giving a presentation about Sprocketnes along with a few > others giving some lightning talks. I'd like to start planning for the next > one in December/January. Would anyone like to give a 30 minute - 1 hour > presentation? If so, please let me know the subject and when you'd be > available to speak. > > Thanks! > -Erick > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mail.mozilla.org/pipermail/rust-dev/attachments/20131114/4df883a3/attachment.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev > > > ------------------------------ > > End of Rust-dev Digest, Vol 41, Issue 76 > **************************************** >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
