oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Unless there are objections raised on the mailing list.  I will merge
the adl2py branch with the trunk on Monday May 25, 2009.  

While it doesn't have a full working tutorial yet it does have an
application developers guide and a good start on an example application.
I plan to have it near completion before the merge.

My reason for making this move on Monday has many aspects.  Grok 1.0a4
was just released.  It solved some installation issues.  The guide will
not only help app developers but OSHIP developers as well, see where my
thoughts are on where OSHIP should go.  On June 1, there is a conference
call with the Teaching Open Source group
( http://teachingopensource.org/index.php/Category:Projects ) and this
is our best connection to educators worldwide.  I want us to have
something to show them.  

Bug reports and blueprints help show that we are an active project and
have a clue where we are going. 

PLEASE!!!!! File some bug reports.  https://bugs.launchpad.net/oship I
know that there are many.  The ones that YOU notice are the ones that
everyone will notice.  I'm too close, I have a methodology, I'll never
see them.  

Do like Wagner did and install OSHIP on a system and wonder; hey what
the heck.  Why do I get this failure.  Actually if Wagner had filed a
bug report instead of just sending a question to the email list it would
have shown outsiders that we are organized and attentive to users needs.
People from the outside almost never read mailing list archives.

Thanks for your help!

Tim

PS. Any progress on the Windows or Mac installations?  If not File a bug
report!  :-)









-- 
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook 
**************************************************************
*You may get my Public GPG key from  popular keyservers or   *
*from this link http://timothywayne.cook.googlepages.com/home*
**************************************************************

Attachment: signature.asc
Description: This is a digitally signed message part