17 Apr
2008
17 Apr
'08
3:31 a.m.
Hello,
I have been spoken to Adam Linford and he agrees to include the Getting
Started guide he started in the openser svn and open it for all
contributions. I am going to review a bit and then I will commit it in
the trunk.
http://openser.oralnet.co.uk/
As Ramona is going to commit soon the devel guide, I think the best
place to have them to are under doc directory:
doc/devel-guide/
doc/getting-started/
Other opinions?
Cheers,
Daniel
--
http://www.asipto.com
17 Apr
17 Apr
5:28 a.m.
On Thursday 17 April 2008, Daniel-Constantin Mierla wrote:
I have been spoken to Adam Linford and he agrees to
include the Getting
Started guide he started in the openser svn and open it for all
contributions. I am going to review a bit and then I will commit it in
the trunk.
http://openser.oralnet.co.uk/
Hi Daniel,
good news. :-)
As Ramona is going to commit soon the devel guide, I
think the best
place to have them to are under doc directory:
doc/devel-guide/
doc/getting-started/
For me its ok for now. But if this content gets bigger (e.g. more diagrams or
screenshots are added) then this will increase the size of the tar.gz we use
for distribution, and also the svn checkouts. Perhaps it make sense to add a
new 'doc' directory on the same level as the 'trunk' and 'tags' to
hold this
content.
What do you think?
Henning
8:51 a.m.
Hello Henning,
On 04/17/08 12:28, Henning Westerholt wrote:
On Thursday 17 April 2008, Daniel-Constantin Mierla
wrote:
maybe is better to do it this way from beginning. I have to check how
can be created a top level directory in sourceforge SVN -- perhaps with
the svn client.
How to name it?
- tutorials
- documentation
- docs
Cheers,
Daniel
I have been spoken to Adam Linford and he agrees
to include the Getting
Started guide he started in the openser svn and open it for all
contributions. I am going to review a bit and then I will commit it in
the trunk.
http://openser.oralnet.co.uk/
Hi Daniel,
good news. :-)
As Ramona is going to commit soon the devel
guide, I think the best
place to have them to are under doc directory:
doc/devel-guide/
doc/getting-started/
For me its ok for now. But if this content gets bigger (e.g. more diagrams or
screenshots are added) then this will increase the size of the tar.gz we use
for distribution, and also the svn checkouts. Perhaps it make sense to add a
new 'doc' directory on the same level as the 'trunk' and 'tags'
to hold this
content.
What do you think?
Henning
--
http://www.asipto.com
9 a.m.
On Thursday 17 April 2008, Daniel-Constantin Mierla wrote:
maybe is better to do it this way from beginning. I
have to check how
can be created a top level directory in sourceforge SVN -- perhaps with
the svn client.
Hello Daniel,
should be possible with 'svn mkdir'.
How to name it?
- tutorials
- documentation
- docs
I like 'docs':
/docs/devel-guide/
/docs/getting-started/
This name matches the name of this list, and also it separates (a little bit)
from the '/trunk/doc' directory.
Cheers,
Henning
6101
days inactive
6101
days old
3 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Henning Westerholt