zope3docs -> zopeframework?
Hi there, We have an area called 'zope3docs': http://svn.zope.org/zope3docs/ which contains many documents that are actually more about the Zope Framework than the Zope 3 app server. In fact I suspect all of these documents are more about the framework than anything else, so we should move them all over. http://svn.zope.org/zopeframework/trunk/ Opinions? Regards, Martijn
2009/3/4 Martijn Faassen <faassen@startifact.com>:
Hi there,
We have an area called 'zope3docs':
http://svn.zope.org/zope3docs/
which contains many documents that are actually more about the Zope Framework than the Zope 3 app server. In fact I suspect all of these documents are more about the framework than anything else, so we should move them all over.
http://svn.zope.org/zopeframework/trunk/
Opinions?
Well, that docs are currently not necessarily about the "zope framework" (as far as I understood what's "zope framework" now), but more about general development guidelines applied to any package in zope svn (except the "migration" section, maybe), but I personally don't have any objections, as it's still easy to find those docs and that's the most important. :-) -- WBR, Dan Korostelev
Hi there, On Wed, Mar 4, 2009 at 8:05 PM, Dan Korostelev <nadako@gmail.com> wrote: [snip
Well, that docs are currently not necessarily about the "zope framework" (as far as I understood what's "zope framework" now), but more about general development guidelines applied to any package in zope svn (except the "migration" section, maybe), but I personally don't have any objections, as it's still easy to find those docs and that's the most important. :-)
I think following the Zope Framework model we should make these documents just apply to the source files in the Zope Framework, and let them serve as an example for other files. There's nobody who can *enforce* compliance though. Besides, lots of those guidelines won't apply to Zope 2 code anyway as far as I know. Well, there is a group that could force compliance for the entire repository, and that's the Zope Foundation (soon), but they care only about a few basic things. Regards, Martijn
On Wed, 2009-03-04 at 20:50 +0100, Martijn Faassen wrote:
Hi there,
On Wed, Mar 4, 2009 at 8:05 PM, Dan Korostelev <nadako@gmail.com> wrote: [snip
Well, that docs are currently not necessarily about the "zope framework" (as far as I understood what's "zope framework" now), but more about general development guidelines applied to any package in zope svn (except the "migration" section, maybe), but I personally don't have any objections, as it's still easy to find those docs and that's the most important. :-)
I think following the Zope Framework model we should make these documents just apply to the source files in the Zope Framework, and let them serve as an example for other files. There's nobody who can *enforce* compliance though. Besides, lots of those guidelines won't apply to Zope 2 code anyway as far as I know.
Well, there is a group that could force compliance for the entire repository, and that's the Zope Foundation (soon), but they care only about a few basic things.
When I started putting in those documents I named it zope3docs initially although I suspected that they would apply to what now became the Zope Framework. The migration document would ne a slight revamp though, as we don't have Zope Framework releases, yet. As Dan pointed out, some of those documents are a bit more general than Zope Framework, but, then again, they're also more general than Zope 3. So even for that its better to have them in the Zope Framework area than Zope 3. Christian -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mar 5, 2009, at 08:24 , Christian Theune wrote:
As Dan pointed out, some of those documents are a bit more general than Zope Framework, but, then again, they're also more general than Zope 3. So even for that its better to have them in the Zope Framework area than Zope 3.
Before anything is moved around please be aware that the zope3docs repository folder is used to rebuild http://docs.zope.org/zope3docs/ on a daily basis. So make sure you don't completely break it since the URL is now known, indexed and used. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkmvg4wACgkQRAx5nvEhZLK0sgCeKvPJRd6OSzBpGY7SV1470yFq cF8AnR1ZFLTQdMdJpB36RJK+qgcL5hMG =dDsp -----END PGP SIGNATURE-----
Jens Vagelpohl wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mar 5, 2009, at 08:24 , Christian Theune wrote:
As Dan pointed out, some of those documents are a bit more general than Zope Framework, but, then again, they're also more general than Zope 3. So even for that its better to have them in the Zope Framework area than Zope 3.
Before anything is moved around please be aware that the zope3docs repository folder is used to rebuild http://docs.zope.org/zope3docs/ on a daily basis. So make sure you don't completely break it since the URL is now known, indexed and used.
Thanks for pointing that out. If we moved it could you put a redirect in place that just pointed .../zope3docs to .../zopeframework? I think to get started on the move we could copy the information using svn copy instead of svn move it, so that we don't break the URL until we're ready updating the texts. Regards, Martijn
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mar 5, 2009, at 16:32 , Martijn Faassen wrote:
Thanks for pointing that out. If we moved it could you put a redirect in place that just pointed .../zope3docs to .../zopeframework?
I think to get started on the move we could copy the information using svn copy instead of svn move it, so that we don't break the URL until we're ready updating the texts.
Let's do this: - svn copy zope3docs to zopeframework - once you think zopeframework is ready for public viewing, let me know and I'll set up a self-updating sandbox and a redirect - after all that you can safely delete zope3docs in SVN. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkmwCswACgkQRAx5nvEhZLIw7wCfYdIyMeo1Bdr0Z96oxzKutrh8 DM0An0bVZyVT0T7C7aXwcD71AQOx0/kv =1wTg -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mar 5, 2009, at 18:24 , Jens Vagelpohl wrote:
Let's do this:
- svn copy zope3docs to zopeframework
- once you think zopeframework is ready for public viewing, let me know and I'll set up a self-updating sandbox and a redirect
- after all that you can safely delete zope3docs in SVN.
Just saw your other message, I'll set everything up and answer the other thread then. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkmwC3sACgkQRAx5nvEhZLKVqwCeIRgkDTOTAKJVbNTuA/25e9gx pnUAn3WMB/jp0pa06UqwYfAHwxZxznKs =mzhb -----END PGP SIGNATURE-----
participants (4)
-
Christian Theune -
Dan Korostelev -
Jens Vagelpohl -
Martijn Faassen