Hi! Firstly, we would like to apologize for time delay. One of us was abroad and had problems with Internet access.
We really like the first and third proposition and we would like to work on them. If we still have some time after we finish these tasks, then we might contribute more. Can you also give us more details about the fourth proposition and time estimates for all of them? We have also some questions about the workflow. Will our changes be thematically squashed into big commits or do you prefer small ones? Should each such a commit be a single pull request? How long does it usually take for a single pull request to be reviewed by some servo developer? Will we have an assigned reviewer to our changes? We are concerned that code review could block our work in a case we want to create a new commit, but the previous one is still in review. Then rebasing newer commits could be painful. In worst case, due to Bachelor's thesis deadline, we may work on our fork and then be submitting slowly, but successively new pull requests, one after one. We would really like to avoid it since it unnecessarily makes contributing more difficult and less productive. And we would like our code to change the world! :) -- Regards, Artur "Mrowqa" Jamro www.mrowqa.pl <http://mrowqa.pl> 2017-06-17 0:09 GMT+02:00 Josh Matthews <j...@joshmatthews.net>: > Hi! Sorry for the long wait; I finally found the time to think about some > projects that could fit your requirements. Here are high-level descriptions > of what I have come up with: > > * Fill in missing pieces of the WebGL APIs - both methods that aren't > implemented yet (comments in https://dxr.mozilla.org/servo/ > source/components/script/dom/webidls/WebGLRenderingContext.webidl) and > parts of the specification that do not match the existing implementation. > Focus on addressing automated tests that do not yet pass, and look for > pretty demos that don't work correctly. > > * Make it easier to evaluate the performance of the network stack - > integrate rust-har into the network implementation and document loader, > making it possible to export HAR timing information about all of the > resources for a particular document. Additionally, create a workflow for > recording HTTP traffic using a proxy and replaying it later, making it > possible to compare before/after performance when modifying the network > stack. > > * Finish the MutationObserver API - only attribute and child mutations > have been implemented so far; add support for all remaining mutations, as > well as subtree notifications, and get all the tests passing. > > * Add more introspection to Servo's event loop - build an event loop > abstraction that can select from many different input sources, report how > many events are queued, and prioritize some queues over others. This should > be used to replace the existing event loop in the script thread. > Additionally, add markers when queuing user input that can report how long > it took for that input to actually be processed. > > How do those sound? > > Cheers, > Josh > > > On 6/6/17 3:29 PM, Artur Jamro wrote: > >> Hi! >> >> We would like to share some updates with you. >> >> We talked with the University of Warsaw IT team and they agreed to be the >> formal project owner and handle all the formal stuff, including the >> presentation. We added their representative to CC. >> >> Now, all we need are project proposals. We ask you for multiple >> suggestions, both small and bigger ones. This is for two reasons: firstly, >> we would like to choose the ones we find most interesting, secondly - the >> Bachelor's thesis has some constraints and we will need to consult them >> with our future thesis supervisor for acceptance. >> >> We are eagerly awaiting project proposals :) >> >> > _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
