oship-dev team mailing list archive

[Diego Manhães Pinheiro <dmpinheiro@xxxxxxxxx>]

2010/7/13 Tim Cook <timothywayne.cook@xxxxxxxxx>

> On Tue, 2010-07-13 at 16:45 +0200, Roger Erens wrote:
> > On Sat, Jul 3, 2010 at 23:54, Tim Cook <timothywayne.cook@xxxxxxxxx>
> wrote:
> > > Hello OSHIPers,
> > >
> > > Before I get into the actual outcomes of the wonderful workshop we had
> > > in Petroplis. I want to thank each of you for your work on OSHIP.  In
> no
> > > way can any one person do this.  This project and the ideas for future
> > > direction that we have and will evolve depend on us and all that will
> > > come.
> >
> > ...
> > >
> > > Tools for us to use on our artifacts, excluding software development,
>
Sorry, I don't follow. You mean documents for all , such as guides for oship
application development? Which is exactly not related with software
development ?

> > > have been chosen using the following guides.  They must be open source.
> > > They must be cross platform.  They must produce an artifact in a file
> > > format that does not prevent us from switching to another tool if
> > > necessary.
> > >
> > > They are:
> > >
> > > For documents of any kind: The Lyx Document Processor:
> > > http://www.lyx.org
> >
> > Maybe sphinx should be considered in addition?
>
> Sphinx is a excelent tool to provide project documentation, including
projects decisions and implementation details and all stuffs related to the
project implementation or information that developers need to know. Sphinx
is not a general purpose document editor. To this kind of task, we have
OpenOffice, Lyx, etc.

> Sure you can build rst for the web and latex for documentation.
>
Just to remind: Sphinx can generate latex files too.

>
> > I think it's not Python specific anymore.
>
> Seems to still be as far as extracting from source.  ???
>
> > Does Lyx have syntax colouring?
>
> Yes. http://wiki.lyx.org/LyX/NewInLyX15#toc11
>
> > And how about version control?
> Do you mean change tracking?Yes
> http://wiki.lyx.org/LyX/NewInLyX15#toc15
>
> But we use BZR for actual version control. Including documents.
>
> > Diego may have something to add to this as well...
>
> One important think to have in mind is when you have different documents
with user goals is don't mix these documents with in the same place( or
repository). A wrong directory organization can be confused to the all types
of users find out which documents is to their own roles.

> I hope so.
>
> (I know he has been struggling with headaches lately.  I hope he is
> feeling better.)
>
I'm taking medications. At the moment, I'm feeling better. :)

>
> LyX gives you a nice editor with all the power of LaTex.
>
> Cheers,
> Tim
>
>
> --
> ***************************************************************
> Timothy Cook, MSc
> Project Lead - Multi-Level Healthcare Information Modeling
> http://www.mlhim.org
>
> LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
> Skype ID == timothy.cook
> Academic.Edu Profile: http://uff.academia.edu/TimothyCook
>
> You may get my Public GPG key from  popular keyservers or
> from this link http://timothywayne.cook.googlepages.com/home
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~oship-dev
> Post to     : oship-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~oship-dev
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
http://dmpinheiro.net
-----------------------------------
Diego Manhães Pinheiro