1 |
Hello, GSoC-ers. |
2 |
|
3 |
The 'PMS test suite' project is running a little ahead of schedule. |
4 |
This week, I achieved to: |
5 |
|
6 |
1) create the project homepage [1], as a subproject to the PMS project, |
7 |
2) create the initial code structure (with the distutils build system), |
8 |
3) establish a blog [2], with a category for the project [3], |
9 |
4) create a simple project design diagram [4] and describe it [5], |
10 |
5) sum up pros and cons of various possible test library formats [6] and |
11 |
create examples for each of them [7]. |
12 |
|
13 |
Right now, I'm still waiting for the following: |
14 |
1) my blog being added to the Planet [8], |
15 |
2) more feedback on the design, |
16 |
3) feedback on whether it would be appropriate to use the 2-clause BSD |
17 |
license for the project. |
18 |
|
19 |
My plan for the upcoming week is to: |
20 |
1) create the initial library-handling code (finding, loading), |
21 |
2) create the basic test case classes, |
22 |
3) establish a simple ebuild generator using the above classes, |
23 |
4) create a README for the project, minimal docs on the library format |
24 |
and describe a little more reasoning on my design choices on the blog. |
25 |
|
26 |
If no really negative feedback shows up until then, I will use |
27 |
the Python test library format. |
28 |
|
29 |
[1]:http://www.gentoo.org/proj/en/qa/pms/pms-test-suite.xml |
30 |
[2]:http://blogs.gentoo.org/mgorny/ |
31 |
[3]:http://blogs.gentoo.org/mgorny/category/gentoo/pms-test-suite/ |
32 |
[4]:http://blogs.gentoo.org/mgorny/files/2011/05/pms-test-suite-design.png |
33 |
[5]:http://blogs.gentoo.org/mgorny/2011/05/22/pms-test-suite-the-project-design/ |
34 |
[6]:http://blogs.gentoo.org/mgorny/2011/05/18/pms-test-suite-choosing-the-test-library-format/ |
35 |
[7]:http://git.overlays.gentoo.org/gitweb/?p=proj/pms-test-suite-library.git;a=tree;f=basic;h=ab7b391803 |
36 |
[8]:http://bugs.gentoo.org/show_bug.cgi?id=367803 |
37 |
|
38 |
-- |
39 |
Best regards, |
40 |
Michał Górny |