Re: [Openstil-devel] I want to join your team

[J. W. <joe...@ya...>]

Luo,=0A=0AI am moving the last part of this thread to developers mailing li=
st.=0A=0AIt looks as though your browser may need a 'reload'- it appears th=
at it is trying to access an old path to the data. Try going to the homepag=
e ( http://openstil.sourceforge.net/ ) and reload that page in your browser=
, and try again. =0A=0AIf that does not work, the full path to the URL docs=
 is=0Ahttp://openstil.sourceforge.net/docs/gen/dox/html/index.html=0A =0AJo=
el Wheeler=0A=0A----- Original Message ----=0AFrom: "xkl...@ya..."=
 <xkl...@ya...>=0ATo: J. W. <joe...@ya...>=0ACc: Doug Spr=
ague <dsp...@gm...>=0ASent: Wednesday, January 10, 2007 6:44:00 AM=0A=
Subject: Re: I want to join your team=0A=0AHello Joel,=0A   =0A  Thank you =
for the advice.=0A   =0A  However I failed to get the API documentation bec=
ause of the following error:=0A   =0A  1. Server: openstil.sourceforge.net=
=0A=0A2. URL path: /dox/gen/html/index.html=0A=0A3. Error notes: File does =
not exist: /home/groups/o/op/openstil/htdocs/dox/gen/html/index.html=0A=0A4=
. Error type: 404=0A=0A5. Request method: GET=0A=0A6. Request query string:=
 =0A=0A7. Time: 2007-01-10 03:30:38 PST (1168428638)=0A   =0A  Would you pl=
ease have a check on it?=0A   =0A  I agree with you on moving our discussio=
n to the mail list. I think the discussion may be useful to those who have =
interest in our project.=0A =0A  =0A  Best regards,=0A  Luo=0A   =0A   =0A =
 =0A=0A"J. W." <joe...@ya...> wrote:=0A        Luo,=0A=0A=0A=0A>>1=
. Making the development environment.=0A=0A=0A=0AFirst, you will need to ha=
ve the SubVersion ("svn") application installed on your system to get the l=
atest source code. We use SourceForge's subversion system as our revision c=
ontrol system. If you are not familiar with subversion, it is basically sim=
ilar to CVS in it's functionality and commands.=0A You should be able to fi=
nd more information online. =0A=0A=0A=0AAs Doug suggests, you can get the l=
atest source by running=0A=0A=0A=0Asvn co https://openstil.svn.sourceforge.=
net/svnroot/openstil openstil=0A=0A=0A=0AThis will give you the entire sour=
ce code package, including all revisions. You will want to work in the 'tru=
nk' directory of the tree. Or, if you do not want all revisions of the sour=
ce, and just want the latest, you can run:=0A=0A=0A=0Asvn co https://openst=
il.svn.sourceforge.net/svnroot/openstil/trunk openstil=0A=0A=0A=0AOnce you =
get the source, the environment is pretty simple. Read the 'INSTALL' file f=
or info on how to run the build process. It is basically just a matter of g=
oing to the 'src' dir and executing a 'gmake'.=0A=0A=0A=0A>> 2. Knowing the=
 architecture of the code.=0A=0A=0A=0AThe API and it's contents are documen=
ted on the OpenSTIL homepage, at=0A=0A=0A=0Ahttp://openstil.sourceforge.net=
/=0A=0A=0A=0AProbably the link to 'API documentation' is the best place to =
start.=0A=0A=0A=0AI would also suggest reviewing some of the existing sourc=
e code to get a feel for the programming style and structure of the API.=0A=
=0A=0A=0A  >> 3. Adding support for 1450.1 "PatternFailReport".=0A=0A=0A=0A=
While reviewing the API and the existing source code you should get a good =
feel for how the current API is structured and implemented. You should also=
 check out the docs/Programmers.Guidelines file (in the downloaded source p=
ackage) for more info on how to add comments that can be=0A picked up by th=
e documentation tool, how to format variable names, etc, so that we can mai=
ntain a fairly consistent approach to implementing the code.=0A=0A=0A=0A=0A=
  >> 4. Adding API support for these fail data blocks.=0A=0A=0A=0AFirst, yo=
u'll need to add this new block into the parser, made up of the lexer (stil=
tok.l) and the grammar (stilgmr.y). Then you'll need to create the data str=
uctures to hold the parsed data. Once you've started examining the source c=
ode we can discuss this in more=0A detail.=0A=0A=0A=0A=0A  >> 5. Doing more=
...=0A  >> =0A  >>In doing 1 and 2, I will try to find as much information =
as I can from sourceforge. I have not got enough time to read >>through all=
 the mail list and the documents. If possible, I would like some=0A advice =
on how to read them. I mean the priority.=0A=0A=0A=0AIt would be beneficial=
 to read through that information as you have time, just to get some perspe=
ctive on the history of the project and what has been done so far. But I wo=
uldn't make this your top priority.=0A=0A=0A   =0A>> Besides, is there any =
difference in being a registered member of OpenSTIL or not? I mean is there=
 any information that can >> only be seen by registered members?=0A=0A=0A=
=0AIt would be a good idea for you to get registered if you do become an ac=
tive contributor. Without being registered, we cannot give you any admin ac=
cess to the project, or the access to commit any changes to the source code=
.=0A=0A=0A=0AAlso- I would like to move this discussion to the developer ma=
iling list if that is OK with you. Then the discussion can be documented an=
d others will know that you may potentially be doing some 1450.1 work. I wo=
uld only post this reposnse, and the questions from your last reply.=0A=0A =
  =0AJoel Wheeler  =0A=0A=0A=0A  ----- Original Message ----=0A=0AFrom: "xk=
lu...@ya..." <xkl...@ya...>=0A=0ATo: J. W. <joel1234567@ya=
hoo.com>; Doug Sprague <dsp...@gm...>=0A=0ASent: Tuesday, January 9, =
2007 7:30:00 AM=0A=0ASubject: Re: I want to join your team=0A=0A=0A=0A  Hel=
lo Joel,=0A   =0A  Glad to hear from you.=0A  That sounds good. I think it =
will be a good start for me in OpenSTIL.=0A   =0A  From now I am going to d=
o:=0A  1. Making the development environment.=0A  2. Knowing the=0A archite=
cture of the code.=0A  3. Adding support for 1450.1 "PatternFailReport".=0A=
  4. Adding API support for these fail data blocks.=0A  5. Doing more...=0A=
   =0A  In doing 1 and 2, I will try to find as much information as I can f=
rom=0A sourceforge. I have not got enough time to read through all the mail=
 list and the documents. If possible, I would like some advice on how to re=
ad them. I mean the priority.=0A   =0A  Besides, is there any difference in=
 being a registered member of OpenSTIL or not? I mean=0A is there any infor=
mation that can only be seen by registered members?=0A=0A=0A  I will have t=
o bother you and Doug a lot for some help from now on. I am glad that I can=
 do something for OpenSTIL.=0A   =0A  Best regards,=0A  Luo=0A   =0A  =0A=
=0A"J. W." <joe...@ya...> wrote:=0A    Hello Luo,=0A=0A=0A=0AGlad =
to hear of your interest in the OpenSTIL project!=0A=0A=0A=0AFor things tha=
t people are working on, I do agree with Doug that we should probably get t=
he "Tasks" section of our SourceForge site up and running, and list some pr=
ojects that developers are working on and the status of those. It would be =
good for us- and anyone viewing the project that is not on=0A a mailing lis=
t- to keep up with what is happening in development. Most of the work is un=
scheduled, as we work on it in our spare time, and there are not currently =
major projects driving a schedule.=0A=0A=0A=0AI had been thinking about put=
ting together an application to do some fail data analysis. It would proces=
s a STIL Pattern block, and a STIL PatternFailReport, and then from that da=
ta it could identify the specific failing STIL vectors. This would require =
the addition of  support for the 1450.1=0A "PatternFailReport" block in the=
 OpenSTIL API. Adding API support for these fail data blocks might be a goo=
d starting point for you to do some programming and familiarize yourself wi=
th the project if you are interested.=0A=0A=0A=0A   =0AJoel Wheeler=0A=0A=
=0A=0A=0A=0A=0A=0A=0A=0A =0A_______________________________________________=
_____________________________________=0AAny questions? Get answers on any t=
opic at www.Answers.yahoo.com.  Try it now.