Radu, It's not clear from your emails whether you're volunteering to take on the project discussed earlier in the thread, or looking for one of a different scope.
You can find a variety of small to medium Servo tasks listed at https://starters.servo.org/ and a list of more major projects at https://github.com/servo/servo/wiki/Remaining-work . When asking for help, you'll get better answers if you clarify what task you are working on, what you've done so far to attempt the task, and what kind of help you need. You can also join us in the #servo channel on Mozilla IRC, https://wiki.mozilla.org/IRC . On Mon, Feb 22, 2016 at 11:57 AM, Radu Manole <[email protected]> wrote: > Hello, can someone help me with this. I would like to start working as soon > as possible. > I am currently trying to solve small tasks for the project. > Thanks. > > > 2016-01-21 1:10 GMT+02:00 Radu Manole <[email protected]>: > > > Hello, > > > > I have talked with my professor about my bachelor degree. The complexity > > should be that of the 2001 GSoC project Tilt made by Victor Porof, > > http://blog.mozilla.com/tilt > > > > One of my professor student. I am interested in any project that could > > help servo project. And to help me advance as an software developer. > > > > Thanks. > > > > P. S. Sorry for delay. Exams. > > > > 2016-01-11 20:44 GMT+02:00 Bobby Holley <[email protected]>: > > > >> At least in Gecko, the media stack is somewhat intertwined. I know we > were > >> planning on lifting at least the media playback pieces from Gecko into > >> Servo, so it's worth considering the implications there. > >> > >> I've also heard it suggested several times that Gecko might be > interested > >> in building a WebAudio implementation in Rust. So it seems like there's > >> some collaboration potential there, but only if we think it through and > >> align resources. > >> > >> All in all, I think it's probably not suitable for a student project. > >> > >> On Sun, Jan 10, 2016 at 1:45 PM, Ms2ger <[email protected]> wrote: > >> > >> > -----BEGIN PGP SIGNED MESSAGE----- > >> > Hash: SHA1 > >> > > >> > On 01/10/2016 09:48 PM, Robert O'Callahan wrote: > >> > > On Mon, Jan 11, 2016 at 7:04 AM, Nicolas Silva > >> > > <[email protected]> wrote: > >> > > > >> > >> Anyone interested in implementing WebAudio and/or WebRTC (in > >> > >> Gecko there's some overlap in the underlying infrastructure) > >> > >> should first spend some time discussing the architecture with > >> > >> Paul Adenot (look for padenot on irc). Having a competitive or > >> > >> even just decent WebAudio implementation is more complex than it > >> > >> looks, and Gecko's implementation had to go through massive > >> > >> rewrites before it got to a satisfying place. According to Paul > >> > >> it's not the kind of architecture one gets right the first time > >> > >> without some serious experience in audio engines. That said, it > >> > >> would be great to have a WebAudio implementation in rust, and I > >> > >> am sure the rust gamedev community would be thrilled to have > >> > >> something like this! > >> > >> > >> > > > >> > > Right. > >> > > > >> > > You'd really want to study the architecture of Gecko's > >> > > implementation and understand why it is the way it is before > >> > > attempting this. You'd also want to understand the architectural > >> > > changes we're still planning to make. Paul and I can help with > >> > > this. > >> > > > >> > > In Gecko MediaStreams and WebAudio are integrated into a single > >> > > real-time media graph (well, multiple graphs, one per logical > >> > > output channel), which has advantages but means you're designing > >> > > more than just WebAudio. > >> > > > >> > > If we did have a good WebAudio implementation in Servo it's one > >> > > piece I could imagine sharing with Gecko. But it's a lot of work to > >> > > get to parity. > >> > > > >> > > >> > FWIW, the issue (<https://github.com/servo/servo/issues/6710>) > already > >> > says suggests talking to Paul and you, from the last time this was > >> > discussed. > >> > > >> > HTH > >> > Ms2ger > >> > -----BEGIN PGP SIGNATURE----- > >> > > >> > iQEcBAEBAgAGBQJWktEKAAoJEOXgvIL+s8n2cfoH/0JcslWVFJZwjvurKWKRz4sv > >> > jVWwywdFQ1TGPHIPtMTlmtbeZMkT5Y8CJ2jXY6OYv27JnQtr8JguosDe3rtQiq3x > >> > ahRaaWTcvfwa6elAvnusLeA24oowSXW94VGixjVW9W5VWqJgi4wN/B1WT4QUvpp7 > >> > vVeT2jFcYQUWLjOOVnFWmvsCeZNUggsN1B6oNwlXTIWpDzXPaippPwlFPOvZUMqc > >> > kJAU5bsD+XA7686rL2GqGLBKyALcJx4oyEQQOhyt56PubQcR1Zy7Z5t0+oWsoKjt > >> > Lcimxcx9ts1Z1jqLgaZvWTQwDnEL9zvGX+7PGyw8kgH4P/TGNOXQ31fspA3FULY= > >> > =fhYA > >> > -----END PGP SIGNATURE----- > >> > _______________________________________________ > >> > dev-servo mailing list > >> > [email protected] > >> > https://lists.mozilla.org/listinfo/dev-servo > >> > > >> _______________________________________________ > >> dev-servo mailing list > >> [email protected] > >> https://lists.mozilla.org/listinfo/dev-servo > >> > > > > > _______________________________________________ > dev-servo mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-servo > _______________________________________________ dev-servo mailing list [email protected] https://lists.mozilla.org/listinfo/dev-servo
