GSOC 2014~

Philippe Ombredanne pombredanne at nexb.com
Sun Mar 2 11:51:54 UTC 2014


On Sun, Mar 2, 2014 at 12:43 PM, ChenQin <warptencq at gmail.com> wrote:
> HERE IS MY REQUEST FOR GSOC 2014~
> Name:ChenQin
> Title:Downstream patches roundup and ushering
>
> Abstract : The goal of this project would to review available patches and
> bugs from the key downstream maintainers and either contribute these as
> patches to strace when relevant or work with the downstream maintainers to
> contribute their patches back to strace. Ideally mini tools should be
> created to collect these bugs and patches automatically on a regular basis
> to inform the strace community of bugs and conversation happening elsewhere
> than on the strace mailing list.
>
> Idea:
> So my idea is to build a mini tool,collect these bugs and patches,and i will
> check if these patches are right,and test it automatically.And separate the
> bug by type etc.At last build a regular output to post some where like
> community.
>
> For solved problems,i just grab the patches.
> For automatic solve unsolved issues,i will down both version before and
> after that branch,and run all test and test cases,
> if they all pass,i will assume that patch is correct and the corresponding
> issue is solved.
[...]
> for unix and linux distros,
> https://github.com/torvalds/linux/graphs/commit-activity
> according this url,they have 600 commits per week average.
> And they have 599 such patched(described in that paper)for 3 years for
> linux_kernel.

So I guess you would consider also improving the test coverage with
new tests and setting up some test infratrsucture?
How would you go about this?


-- 
Philippe Ombredanne




More information about the Strace-devel mailing list