SVN Server for tutorial code

[Ralf Eggert]

Hi,

I am not quite sure if this is the correct list to post my message, but
I guess you might point me to the right direction if I am totally wrong.

A couple of month ago I started a German Zend Framework tutorial in my
private blog, which is not yet finished. The plan was to build a
step-by-step guide to create a real life example software and use as
many ZF components as possible and reasonable. The ZF based software is
a weblog and the tutorial can be found here:

http://www.ralfeggert.de/zend-framework-tutorial/

My problem is that it is quite a lot of work to keep this extensive
tutorial in sync with new ZF releases. Due to the lack of time I did not
even finish the rework of the tutorial to fit with ZF release 0.6.0.

Now I had the idea to pass the tutorial to the German ZF community to
get some helping hands for maintaining both the tutorial pages and the
weblog code. We are currently discussing how to realize this, so it came
to my mind to use the available infrastructure of the ZF SVN server to
manage the code.

Is it possible to get a special directory on the SVN server for this
project with several people to get write access? Since every part of the
tutorial builds on a preceding part we will need a lot of subdirectories
to hold the code for part 1, part 2, part 3, ... part 20, etc., which
should be maintainable independently.

For the tutorial pages we are not sure yet if we should use the ZF wiki
or set up a kind of separate incubator wiki for building the tutorial
and move a usable version to another place after updating. Does
Confluence allow it to set to up a special area for this wiki with a
maintainable version with write access for just a few users and a
readable version for everyone?

Thanks for your kind help.

Best Regards,

Ralf

[GavinZend]

Hi Ralf,

I think this topic fits with fw-docs list, so I'm switching the
discussion over there.

I am strongly in favor of supporting tutorials like this.
Surely we can allocate SVN space in our ZF Lab SVN repository.

Also, I can easily create a wiki space, separate from the other ones, as
you suggest below :)

What does everyone else think about these ideas?

Cheers,
Gavin

Ralf Eggert wrote:

> Hi,
>
> I am not quite sure if this is the correct list to post my message, but
> I guess you might point me to the right direction if I am totally wrong.
>
> A couple of month ago I started a German Zend Framework tutorial in my
> private blog, which is not yet finished. The plan was to build a
> step-by-step guide to create a real life example software and use as
> many ZF components as possible and reasonable. The ZF based software is
> a weblog and the tutorial can be found here:
>
> http://www.ralfeggert.de/zend-framework-tutorial/
>
> My problem is that it is quite a lot of work to keep this extensive
> tutorial in sync with new ZF releases. Due to the lack of time I did not
> even finish the rework of the tutorial to fit with ZF release 0.6.0.
>
> Now I had the idea to pass the tutorial to the German ZF community to
> get some helping hands for maintaining both the tutorial pages and the
> weblog code. We are currently discussing how to realize this, so it came
> to my mind to use the available infrastructure of the ZF SVN server to
> manage the code.
>
> Is it possible to get a special directory on the SVN server for this
> project with several people to get write access? Since every part of the
> tutorial builds on a preceding part we will need a lot of subdirectories
> to hold the code for part 1, part 2, part 3, ... part 20, etc., which
> should be maintainable independently.
>
> For the tutorial pages we are not sure yet if we should use the ZF wiki
> or set up a kind of separate incubator wiki for building the tutorial
> and move a usable version to another place after updating. Does
> Confluence allow it to set to up a special area for this wiki with a
> maintainable version with write access for just a few users and a
> readable version for everyone?
>
> Thanks for your kind help.
>
> Best Regards,
>
> Ralf