Menu
▾
▴
plone-docs — Discussion about the Plone documentation
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(83) |
Nov
(55) |
Dec
(29) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(29) |
Feb
(31) |
Mar
(37) |
Apr
(6) |
May
(25) |
Jun
(36) |
Jul
(19) |
Aug
(7) |
Sep
(17) |
Oct
(40) |
Nov
(33) |
Dec
(44) |
| 2004 |
Jan
(20) |
Feb
(15) |
Mar
(22) |
Apr
(17) |
May
(24) |
Jun
(19) |
Jul
(15) |
Aug
(25) |
Sep
(79) |
Oct
(35) |
Nov
(112) |
Dec
(31) |
| 2005 |
Jan
(110) |
Feb
(40) |
Mar
(35) |
Apr
(37) |
May
(24) |
Jun
(10) |
Jul
(8) |
Aug
(54) |
Sep
(23) |
Oct
(17) |
Nov
(35) |
Dec
(41) |
| 2006 |
Jan
(72) |
Feb
(184) |
Mar
(57) |
Apr
(83) |
May
(38) |
Jun
(44) |
Jul
(11) |
Aug
(60) |
Sep
(33) |
Oct
(75) |
Nov
(227) |
Dec
(89) |
| 2007 |
Jan
(46) |
Feb
(27) |
Mar
(28) |
Apr
(33) |
May
(94) |
Jun
(33) |
Jul
(48) |
Aug
(24) |
Sep
(57) |
Oct
(32) |
Nov
(32) |
Dec
(23) |
| 2008 |
Jan
(65) |
Feb
(51) |
Mar
(30) |
Apr
(111) |
May
(19) |
Jun
(31) |
Jul
(114) |
Aug
(57) |
Sep
(26) |
Oct
(72) |
Nov
(252) |
Dec
(98) |
| 2009 |
Jan
(100) |
Feb
(37) |
Mar
(89) |
Apr
(57) |
May
(81) |
Jun
(27) |
Jul
(27) |
Aug
(42) |
Sep
(25) |
Oct
(45) |
Nov
(21) |
Dec
(72) |
| 2010 |
Jan
(74) |
Feb
(23) |
Mar
(6) |
Apr
(47) |
May
(64) |
Jun
(7) |
Jul
(19) |
Aug
(3) |
Sep
(26) |
Oct
(6) |
Nov
(15) |
Dec
(28) |
| 2011 |
Jan
|
Feb
(9) |
Mar
(7) |
Apr
(8) |
May
(13) |
Jun
(1) |
Jul
(35) |
Aug
(21) |
Sep
(9) |
Oct
(16) |
Nov
(6) |
Dec
(3) |
| 2012 |
Jan
(10) |
Feb
(6) |
Mar
(7) |
Apr
(26) |
May
(2) |
Jun
(7) |
Jul
(2) |
Aug
(6) |
Sep
(6) |
Oct
(15) |
Nov
(2) |
Dec
(2) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(11) |
Aug
(2) |
Sep
(3) |
Oct
(6) |
Nov
(1) |
Dec
(3) |
| 2014 |
Jan
|
Feb
|
Mar
(2) |
Apr
(9) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(4) |
|
From: Alex C. <ac...@ac...> - 2011-08-28 20:35:20
|
Hi, On 8/27/11 4:31 PM, Martin Aspeli wrote: > Hi, > > If possible, I'd like to replace the link to Professional Plone > Development on http://plone.org/documentation and > http://plone.org/documentation/books with one pointing to the new > edition at http://www.packtpub.com/professional-plone-4-development/book Congratulations, Martin! > > Is anyone able to help me do that? And could you reply to the list when you do, so others don't login and try to do it twice? :-) Thanks </nit> Alex > > Thanks! > Martin > > > ------------------------------------------------------------------------------ > EMC VNX: the world's simplest storage, starting under $10K > The only unified storage solution that offers unified management > Up to 160% more powerful than alternatives and 25% more efficient. > Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev > > > > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs -- Alex Clark · http://aclark.net |
|
From: Martin A. <opt...@gm...> - 2011-08-27 20:31:32
|
Hi, If possible, I'd like to replace the link to Professional Plone Development on http://plone.org/documentation and http://plone.org/documentation/bookswith one pointing to the new edition at http://www.packtpub.com/professional-plone-4-development/book Is anyone able to help me do that? Thanks! Martin |
|
From: Leonardo C. <leo...@gm...> - 2011-08-18 22:05:32
|
2011/8/19 Jeff Pittman <ge...@me...>: > Hi Leonardo, > I found the files you need, from the Summer of 2007. I sent them to SteveM > who graciously put them into the collective, where they should have been all > along: > http://svn.plone.org/svn/collective/plone_manual_resources/ai_files/ Hey Jeff thanks very much > These are Adobe Illustrator files, but I was able to open one in Inkscape > and ungroup the items, so you should be able to use Inkscape, if you don't > have AI, to edit the text and re-export to png. I will use Inkscape for the task > It would be a good idea for you to add your files into the collective too. > Thanks and good luck on the translation, and I hope share with plone community this work ;) > Jeff Thanks you!!! > On Aug 18, 2011, at 7:20 AM, Alex Clark wrote: > > On 8/17/11 6:56 PM, Leonardo Caballero wrote: > > Alex for example this kind of illustrations > > http://plone.org/documentation/manual/plone-3-user-manual/introduction/content_types_into_plone.png > > > I see, I suspect you'd need to contact the individual authors. > > > > 2011/8/18 Alex Clark<ac...@ac...>: > > On 8/17/11 12:55 PM, Leonardo Caballero wrote: > > Hi plonistas > > My name is Leonardo J. Caballero G., my IRC nickname is macagua this > > is my first email of Documentation team, and I write this email to > > this team because on Plone Conosur's community have been working > > (since 2008) in a initiative to translate to Spanish many Plone > > documentations useful for community of language Spanish. > > Then, we have ready the text translation for Plone 3 and Plone 4 User > > Manual to Spanish, but some Illustrations of these manual are explains > > in English, and some guys would like access the source of these > > Illustrations and generate a new version translated in Spanish. > > Then my question is: > > Is possible access of these sources? > > And with Who and Where I can found the source of illustrations for > > Plone User Manual ? > > > What are you looking for specifically? As far as I know, everything we > > have is in PHC (i.e. plone.org/documentation)[1]. > > > [1] With the exception of the Plone Community-Managed Developer Manual > > which lives here: https://github.com/collective/collective.developermanual. > > > > > > -- > > Alex Clark · http://aclark.net > > > ------------------------------------------------------------------------------ > > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > > user administration capabilities and model configuration. Take > > the hassle out of deploying and managing Subversion and the > > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > > _______________________________________________ > > Plone-docs mailing list > > Plo...@li... > > https://lists.sourceforge.net/lists/listinfo/plone-docs > > > > > > > -- > Alex Clark · http://aclark.net > > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs > > Jeff Pittman > ge...@me... > > > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs > > -- Atentamente T.S.U. Leonardo Caballero Linux Counter ID = http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=369081 Key fingerprint = 9FD2 DC71 38E7 A1D1 57F5 1D29 04DE 43BC 8A27 424A /me Corriendo Debian Squeeze 6.0 y Canaina GNU/Linux 2.1 /me Cree "El Conocimiento Humano le Pertenece al Mundo" |
|
From: Jeff P. <ge...@me...> - 2011-08-18 16:43:08
|
Hi Leonardo, I found the files you need, from the Summer of 2007. I sent them to SteveM who graciously put them into the collective, where they should have been all along: http://svn.plone.org/svn/collective/plone_manual_resources/ai_files/ These are Adobe Illustrator files, but I was able to open one in Inkscape and ungroup the items, so you should be able to use Inkscape, if you don't have AI, to edit the text and re-export to png. It would be a good idea for you to add your files into the collective too. Thanks and good luck on the translation, Jeff On Aug 18, 2011, at 7:20 AM, Alex Clark wrote: > On 8/17/11 6:56 PM, Leonardo Caballero wrote: >> Alex for example this kind of illustrations >> >> http://plone.org/documentation/manual/plone-3-user-manual/introduction/content_types_into_plone.png > > > I see, I suspect you'd need to contact the individual authors. > > >> >> 2011/8/18 Alex Clark<ac...@ac...>: >>> On 8/17/11 12:55 PM, Leonardo Caballero wrote: >>>> Hi plonistas >>>> >>>> My name is Leonardo J. Caballero G., my IRC nickname is macagua this >>>> is my first email of Documentation team, and I write this email to >>>> this team because on Plone Conosur's community have been working >>>> (since 2008) in a initiative to translate to Spanish many Plone >>>> documentations useful for community of language Spanish. >>>> >>>> Then, we have ready the text translation for Plone 3 and Plone 4 User >>>> Manual to Spanish, but some Illustrations of these manual are explains >>>> in English, and some guys would like access the source of these >>>> Illustrations and generate a new version translated in Spanish. >>>> >>>> Then my question is: >>>> >>>> Is possible access of these sources? >>>> >>>> And with Who and Where I can found the source of illustrations for >>>> Plone User Manual ? >>> >>> >>> What are you looking for specifically? As far as I know, everything we >>> have is in PHC (i.e. plone.org/documentation)[1]. >>> >>> >>> [1] With the exception of the Plone Community-Managed Developer Manual >>> which lives here: https://github.com/collective/collective.developermanual. >>> >>> >>>> >>> >>> >>> -- >>> Alex Clark · http://aclark.net >>> >>> >>> ------------------------------------------------------------------------------ >>> Get a FREE DOWNLOAD! and learn more about uberSVN rich system, >>> user administration capabilities and model configuration. Take >>> the hassle out of deploying and managing Subversion and the >>> tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 >>> _______________________________________________ >>> Plone-docs mailing list >>> Plo...@li... >>> https://lists.sourceforge.net/lists/listinfo/plone-docs >>> >> >> >> > > > -- > Alex Clark · http://aclark.net > > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs Jeff Pittman ge...@me... |
|
From: Alex C. <ac...@ac...> - 2011-08-18 12:21:15
|
On 8/17/11 6:56 PM, Leonardo Caballero wrote: > Alex for example this kind of illustrations > > http://plone.org/documentation/manual/plone-3-user-manual/introduction/content_types_into_plone.png I see, I suspect you'd need to contact the individual authors. > > 2011/8/18 Alex Clark<ac...@ac...>: >> On 8/17/11 12:55 PM, Leonardo Caballero wrote: >>> Hi plonistas >>> >>> My name is Leonardo J. Caballero G., my IRC nickname is macagua this >>> is my first email of Documentation team, and I write this email to >>> this team because on Plone Conosur's community have been working >>> (since 2008) in a initiative to translate to Spanish many Plone >>> documentations useful for community of language Spanish. >>> >>> Then, we have ready the text translation for Plone 3 and Plone 4 User >>> Manual to Spanish, but some Illustrations of these manual are explains >>> in English, and some guys would like access the source of these >>> Illustrations and generate a new version translated in Spanish. >>> >>> Then my question is: >>> >>> Is possible access of these sources? >>> >>> And with Who and Where I can found the source of illustrations for >>> Plone User Manual ? >> >> >> What are you looking for specifically? As far as I know, everything we >> have is in PHC (i.e. plone.org/documentation)[1]. >> >> >> [1] With the exception of the Plone Community-Managed Developer Manual >> which lives here: https://github.com/collective/collective.developermanual. >> >> >>> >> >> >> -- >> Alex Clark · http://aclark.net >> >> >> ------------------------------------------------------------------------------ >> Get a FREE DOWNLOAD! and learn more about uberSVN rich system, >> user administration capabilities and model configuration. Take >> the hassle out of deploying and managing Subversion and the >> tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 >> _______________________________________________ >> Plone-docs mailing list >> Plo...@li... >> https://lists.sourceforge.net/lists/listinfo/plone-docs >> > > > -- Alex Clark · http://aclark.net |
|
From: Leonardo C. <leo...@gm...> - 2011-08-17 22:56:15
|
Alex for example this kind of illustrations http://plone.org/documentation/manual/plone-3-user-manual/introduction/content_types_into_plone.png 2011/8/18 Alex Clark <ac...@ac...>: > On 8/17/11 12:55 PM, Leonardo Caballero wrote: >> Hi plonistas >> >> My name is Leonardo J. Caballero G., my IRC nickname is macagua this >> is my first email of Documentation team, and I write this email to >> this team because on Plone Conosur's community have been working >> (since 2008) in a initiative to translate to Spanish many Plone >> documentations useful for community of language Spanish. >> >> Then, we have ready the text translation for Plone 3 and Plone 4 User >> Manual to Spanish, but some Illustrations of these manual are explains >> in English, and some guys would like access the source of these >> Illustrations and generate a new version translated in Spanish. >> >> Then my question is: >> >> Is possible access of these sources? >> >> And with Who and Where I can found the source of illustrations for >> Plone User Manual ? > > > What are you looking for specifically? As far as I know, everything we > have is in PHC (i.e. plone.org/documentation)[1]. > > > [1] With the exception of the Plone Community-Managed Developer Manual > which lives here: https://github.com/collective/collective.developermanual. > > >> > > > -- > Alex Clark · http://aclark.net > > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs > -- Atentamente T.S.U. Leonardo Caballero Linux Counter ID = http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=369081 Key fingerprint = 9FD2 DC71 38E7 A1D1 57F5 1D29 04DE 43BC 8A27 424A /me Corriendo Debian Squeeze 6.0 y Canaina GNU/Linux 2.1 /me Cree "El Conocimiento Humano le Pertenece al Mundo" |
|
From: Alex C. <ac...@ac...> - 2011-08-17 21:50:18
|
On 8/17/11 12:55 PM, Leonardo Caballero wrote: > Hi plonistas > > My name is Leonardo J. Caballero G., my IRC nickname is macagua this > is my first email of Documentation team, and I write this email to > this team because on Plone Conosur's community have been working > (since 2008) in a initiative to translate to Spanish many Plone > documentations useful for community of language Spanish. > > Then, we have ready the text translation for Plone 3 and Plone 4 User > Manual to Spanish, but some Illustrations of these manual are explains > in English, and some guys would like access the source of these > Illustrations and generate a new version translated in Spanish. > > Then my question is: > > Is possible access of these sources? > > And with Who and Where I can found the source of illustrations for > Plone User Manual ? What are you looking for specifically? As far as I know, everything we have is in PHC (i.e. plone.org/documentation)[1]. [1] With the exception of the Plone Community-Managed Developer Manual which lives here: https://github.com/collective/collective.developermanual. > -- Alex Clark · http://aclark.net |
|
From: Leonardo C. <leo...@gm...> - 2011-08-17 16:55:36
|
Hi plonistas My name is Leonardo J. Caballero G., my IRC nickname is macagua this is my first email of Documentation team, and I write this email to this team because on Plone Conosur's community have been working (since 2008) in a initiative to translate to Spanish many Plone documentations useful for community of language Spanish. Then, we have ready the text translation for Plone 3 and Plone 4 User Manual to Spanish, but some Illustrations of these manual are explains in English, and some guys would like access the source of these Illustrations and generate a new version translated in Spanish. Then my question is: Is possible access of these sources? And with Who and Where I can found the source of illustrations for Plone User Manual ? -- Atentamente T.S.U. Leonardo Caballero Linux Counter ID = http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=369081 Key fingerprint = 9FD2 DC71 38E7 A1D1 57F5 1D29 04DE 43BC 8A27 424A /me Corriendo Debian Squeeze 6.0 y Canaina GNU/Linux 2.1 /me Cree "El Conocimiento Humano le Pertenece al Mundo" |
|
From: Weisglass O. <wei...@gm...> - 2011-08-04 17:59:39
|
long time ago there was how much was translated from each of the langugue it was very usfull to see also pleaes note that there are many people who can translate but not technical people at all and hard for them to understand this words like svn the very old page on plone.org was with teams by the specific langugue and it was very usfull also in caes need help in one lanagugue for example after I saw on the page that the arabic translation file was only 30present ready I did effort hire a payed students from manchester and after that contineu the work with a company from italy as donation and than the file was all translated also in some locations there are local events and the local people can sit toghter and work on the translation and like the hebrew and arabic right to left work is not only the translation of the file it is also the pages and the bugs for the right to left translation On Wed, Aug 3, 2011 at 8:43 PM, Alex Clark <ac...@ac...> wrote: > On 8/2/11 3:22 AM, Vincent Fretin wrote: > > On Tue, Aug 2, 2011 at 1:47 AM, Alex Clark > > <ac...@ac... > > <mailto:ac...@ac...>> wrote: > > > > On 8/1/11 4:18 AM, Vincent Fretin wrote: > > > Hi, > > > > > > Can anyone please remove the out of date i18nTeam page at > > > http://plone.org/team/i18nTeam > > > and if possible do a redirection to > > > > > > http://svn.plone.org/svn/collective/PloneTranslations/trunk/TRANSLATORS.html > > > where we have the most up to date contact information. > > > The old i18nTeam was referenced only from the bug tracker and I > > removed > > > this reference. > > > The wiki point to the TRANSLATORS.html file. > > > > > > Why not just keep it up to date? It uses LDAP groups, IIRC, that are > > configurable by any plone.org <http://plone.org> website admin. If > > you open a ticket, I can > > take a look. > > > > > > Here it is: > > https://dev.plone.org/plone/ticket/12082 > > > > If we keep this page, we should really include the language the person > > is responsible of. > > At the moment, the page is not very useful, that is why the page is not > > linked anywhere. > > Is it possible to show the Language member property? > > How this page is created, is it a document, a template, a view? > > > > https://svn.plone.org/svn/plone/plone.org/Products.PloneOrg/trunk/src/Products/PloneOrg/skins/ploneorg/team.pt > > > > > > > Vincent > > > > > > > ------------------------------------------------------------------------------ > > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > > The must-attend event for mobile developers. Connect with experts. > > Get tools for creating Super Apps. See the latest technologies. > > Sessions, hands-on labs, demos& much more. Register early& save! > > http://p.sf.net/sfu/rim-blackberry-1 > > > > > > > > _______________________________________________ > > Plone-docs mailing list > > Plo...@li... > > https://lists.sourceforge.net/lists/listinfo/plone-docs > > > -- > Alex Clark · http://aclark.net > > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs > |
|
From: Alex C. <ac...@ac...> - 2011-08-04 01:43:43
|
On 8/2/11 3:22 AM, Vincent Fretin wrote: > On Tue, Aug 2, 2011 at 1:47 AM, Alex Clark > <ac...@ac... > <mailto:ac...@ac...>> wrote: > > On 8/1/11 4:18 AM, Vincent Fretin wrote: > > Hi, > > > > Can anyone please remove the out of date i18nTeam page at > > http://plone.org/team/i18nTeam > > and if possible do a redirection to > > > http://svn.plone.org/svn/collective/PloneTranslations/trunk/TRANSLATORS.html > > where we have the most up to date contact information. > > The old i18nTeam was referenced only from the bug tracker and I > removed > > this reference. > > The wiki point to the TRANSLATORS.html file. > > > Why not just keep it up to date? It uses LDAP groups, IIRC, that are > configurable by any plone.org <http://plone.org> website admin. If > you open a ticket, I can > take a look. > > > Here it is: > https://dev.plone.org/plone/ticket/12082 > > If we keep this page, we should really include the language the person > is responsible of. > At the moment, the page is not very useful, that is why the page is not > linked anywhere. > Is it possible to show the Language member property? > How this page is created, is it a document, a template, a view? https://svn.plone.org/svn/plone/plone.org/Products.PloneOrg/trunk/src/Products/PloneOrg/skins/ploneorg/team.pt > > Vincent > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos& much more. Register early& save! > http://p.sf.net/sfu/rim-blackberry-1 > > > > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs -- Alex Clark · http://aclark.net |
|
From: Vincent F. <vin...@gm...> - 2011-08-02 07:23:10
|
On Tue, Aug 2, 2011 at 1:47 AM, Alex Clark <ac...@ac...> wrote: > On 8/1/11 4:18 AM, Vincent Fretin wrote: > > Hi, > > > > Can anyone please remove the out of date i18nTeam page at > > http://plone.org/team/i18nTeam > > and if possible do a redirection to > > > http://svn.plone.org/svn/collective/PloneTranslations/trunk/TRANSLATORS.html > > where we have the most up to date contact information. > > The old i18nTeam was referenced only from the bug tracker and I removed > > this reference. > > The wiki point to the TRANSLATORS.html file. > > > Why not just keep it up to date? It uses LDAP groups, IIRC, that are > configurable by any plone.org website admin. If you open a ticket, I can > take a look. > Here it is: https://dev.plone.org/plone/ticket/12082 If we keep this page, we should really include the language the person is responsible of. At the moment, the page is not very useful, that is why the page is not linked anywhere. Is it possible to show the Language member property? How this page is created, is it a document, a template, a view? Vincent |
|
From: Alex C. <ac...@ac...> - 2011-08-01 23:47:33
|
On 8/1/11 4:18 AM, Vincent Fretin wrote: > Hi, > > Can anyone please remove the out of date i18nTeam page at > http://plone.org/team/i18nTeam > and if possible do a redirection to > http://svn.plone.org/svn/collective/PloneTranslations/trunk/TRANSLATORS.html > where we have the most up to date contact information. > The old i18nTeam was referenced only from the bug tracker and I removed > this reference. > The wiki point to the TRANSLATORS.html file. Why not just keep it up to date? It uses LDAP groups, IIRC, that are configurable by any plone.org website admin. If you open a ticket, I can take a look. Alex > > Thanks > > Vincent Fretin > Plone i18n team leader > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > > > > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs -- Alex Clark · http://aclark.net |
|
From: Vincent F. <vin...@gm...> - 2011-08-01 08:18:46
|
Hi, Can anyone please remove the out of date i18nTeam page at http://plone.org/team/i18nTeam and if possible do a redirection to http://svn.plone.org/svn/collective/PloneTranslations/trunk/TRANSLATORS.html where we have the most up to date contact information. The old i18nTeam was referenced only from the bug tracker and I removed this reference. The wiki point to the TRANSLATORS.html file. Thanks Vincent Fretin Plone i18n team leader |
|
From: Encolpe D. <enc...@fr...> - 2011-07-29 14:33:06
|
I tried to start such a job with the zopeskel.unis project You can find deployement explaination here: - https://github.com/collective/zopeskel.unis/tree/master/docs And sample for configuration here: - https://github.com/collective/zopeskel.unis/tree/master/zopeskel/unis/templates/unis_plone4_buildout/profiles/etc - https://github.com/collective/zopeskel.unis/tree/master/zopeskel/unis/templates/unis_plone4_buildout/profiles/modules It's done in ReST to be displayed in github, but it can be done in other markdown system: https://github.com/collective/zopeskel.unis/wiki/Debian-Squeeze Regards Le 27/07/2011 06:22, T. Kim Nguyen a écrit : > Hello again - apologies if it seems I am barraging the list. > > As part of the monthly PloneEdu calls we've been coming up with ideas on how to build resources for (primarily) educational institutions using Plone. One of those ideas is to create documentation relating to how educational institutions have deployed Plone: the server environment, cacheing, authentication, load balancing, and so on. > > (While PloneEdu's mission is specifically education related, a lot of what we do is of general use to any organization using Plone). > > In my completely unscientific method of looking around for "plone deployment manual", "plone deployment guide", "how to deploy Plone", I have found some resources here and there, but nothing pulling it all together in one place, presumably on plone.org/documentation. > > Content that would be useful in such a manual: > > - the above bits and pieces of a production stack > > - sample configurations (buildouts, squid.cfg, pound.cfg, httpd.conf, ssl.conf, etc.) > > - case studies of deployments (by "deployment" I refer specifically to the server setup) > > - forms for accepting new deployment case studies submitted > > Has this already been done? If not, does this seem like a good idea, and if so, how to proceed? > > Kim > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey -- Encolpe DEGOUTE http://encolpe.degoute.free.fr/ Logiciels libres, hockey sur glace et autres activités cérébrales |
|
From: Dylan J. <dy...@dy...> - 2011-07-29 02:13:36
|
On 29/07/2011, at 9:32 AM, T. Kim Nguyen wrote:
> I seem to have stepped into a minefield. :)
>
> I come in peace! I was just sharing my reaction to how I would have
> to install a bunch of software on a computer, and learn a bunch of
> new things ("new" meaning "not Plone"), and, yes, I'm a techie but I
> still want to do as little extra work as possible. Dylan, it's not
> that I or other technical contributors CAN'T learn restructured
> text, but that we'd have to use git or svn or Sphinx, and those
> tools are not as easy to use as Plone or cnx.org.
>
> Ideally, contributors would have as low a barrier as possible, to
> avoid discouraging them from contributing. When I contribute a "how
> to" to my own site (uwosh.edu/ploneprojects) I don't even want to
> have to THINK, so I have a link on the site that takes me to the how
> to folder's createObject call. That's what I mean by making it
> super super easy... frictionless, superconducting, K-Y for process. :)
yes I understand your reaction. I'd say however that encouraging
people to contribute is not our biggest problem. Already anyone can
submit a KB article using plone. And many have done so. So already
this problem is solved.
Our biggest problem IMO is of consolidation, ie letting someone
contribute documentation to the right place so there aren't multiple
different out of date versions of the same advice in different places.
So we want people to THINK because not thinking of how they can
combine or improve others efforts has got us to the current state of
documentation we are in today.
Admittedly the c.docs is heading in the same way of having multiple
places talking about the same topics but we'll clean that up soon
enough :)
The goal is one developer manual which you can read end to end and it
makes sense and doesn't contradict itself or repeat itself. And yet is
still reasonably easy to contribute to.
The other aspect is we want core developers to document their own
apis. Core developers are already using git/svn. Sphinx makes is
incredibly easy to include docs from code into our manual. I've
already done this for several of the GS module level docs (which I had
to add). The easier we make this for them the better. The system is
broken if we expect non-developers to document developers code because
they won't.
>
> Alex, yes I could just forge ahead but I know the only efforts that
> work long term are those that gain wide acceptance. It would be
> self defeating for the Plone community to have competing
> documentation processes and venues.
>
> How about this: I will take a portion of the Plone user manual and
> get it into cnx.org, then show y'all what I think are the cool
> things one can do with it there.
sure, can't do any hard with regard to the users manual but you might
want to talk to the people who maintain the users manual. I've lost
track of who that is.
>
> About hosting documentation (which, to quibble, doesn't have quite
> the same meaning to me as "deployment") I was also
I was suggesting renaming hosting to deployment.
> thinking about a repo for configuration files. Is there such a
> thing already? I think it should be outside the documentation,
> since documentation such as manuals/guides are linear.
yes there is zopeskel. Also those at the sauna sprint are working on
improving these aspects of zopeskel now I believe.
>
> Kim
>
> On Jul 28, 2011, at 9:59 AM, Alex Clark wrote:
>
>> Hi,
>>
>> On 7/28/11 10:15 AM, T. Kim Nguyen wrote:
>>> Thanks Dylan.
>>>
>>> I'm afraid that contributors (including me) will be scared off by
>>> the fairly complex learning and setup required to add to this
>>> documentation (Sphinx, collective commit rights, svn, restructured
>>> text) as opposed to editing a Plone page (or equivalent).
>>>
>>> Is the http://collective-docs.readthedocs.org/en/latest/hosting/index.html
>>> documentation updated the same way?
>>
>>
>> Yup, and this is exactly why we've been stalled on documentation for
>> years now. We have two competing camps who have very strong
>> preferences
>> about how they contribute/edit documentation[1]. The c-docs are the
>> only
>> "excitement" we've seen lately IMHO.
>>
>> The good news though, is that GitHub actually supports TTW editing.
>> So
>> in the case of the hosting docs Dylan just mentioned, one could edit
>> them TTW by going here:
>>
>>
>> *
>> https://github.com/collective/collective.developermanual/blob/master/source/hosting/apache.txt
>>
>>
>> Of course, you'd have to be familiar with restructured text, but
>> that is
>> a fair compromise IMHO (I.e. you don't have to understand Sphinx or
>> collective commit rights at least.)
>>
>> Anyway, if we want to encourage folks to contribute docs on
>> plone.org by
>> using Plone, then we should be doing a much better job at managing
>> plone.org. Maybe the connexions thing could solve or address this
>> somehow (by lightening the plone.org/PHC load.) *shrug*
>>
>>
>>
>> Alex
>>
>>
>>
>>
>> [1] I feel pretty strongly that the FWT should grab some sane set of
>> documentation from the various offerings and ship it, versioned, with
>> each major release of Plone. But I've not gotten enough buy in to
>> consider an actual PLIP (where I'd happily do the work.)
>>
>>
>>
>>>
>>> Kim
>>
>>
>>
>>>
>>> On Jul 27, 2011, at 12:11 AM, Dylan Jay wrote:
>>>
>>>> My opinion (and keep in mind it is just my opinion) is that the
>>>> place for this and all future development manual work should be
>>>>
>>>> http://plone.org/documentation/manual/plone-community-developer-documentation
>>>>
>>>> which is edited via reST and sphinx and github as per these
>>>> instructionshttp://plone.org/documentation/manual/plone-community-developer-documentation/introduction/writing
>>>>
>>>> NOTE: at the time of writing this that document is out of date
>>>> and the secondary copy at readthedocs is now more up to date.
>>>> http://collective-docs.readthedocs.org/en/latest/introduction/writing.html
>>>> . We're working on fixing this so the plone.org version would be
>>>> updated nightly.
>>>>
>>>> My suggestion is we deprecate all other developer manuals and KB
>>>> articles which overlap with the collective developer manual and
>>>> concentrate on cleaning up and making this manual both clean,
>>>> easy to understand and comprehensive.
>>>>
>>>> With regard to deployment I'd suggest we enhance the "hosting"
>>>> section of this manual
>>>>
>>>> http://collective-docs.readthedocs.org/en/latest/hosting/index.html
>>>>
>>>>
>>>> Note: these comments don't apply to the users manual or other
>>>> kinds of documentation.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Got Input? Slashdot Needs You.
>>> Take our quick survey online. Come on, we don't ask for help often.
>>> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
>>> http://p.sf.net/sfu/slashdot-survey
>>
>>
>> --
>> Alex Clark · http://aclark.net
>>
>>
>> ------------------------------------------------------------------------------
>> Got Input? Slashdot Needs You.
>> Take our quick survey online. Come on, we don't ask for help often.
>> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
>> http://p.sf.net/sfu/slashdot-survey
>> _______________________________________________
>> Plone-docs mailing list
>> Plo...@li...
>> https://lists.sourceforge.net/lists/listinfo/plone-docs
>
>
> ------------------------------------------------------------------------------
> Got Input? Slashdot Needs You.
> Take our quick survey online. Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs
|
|
From: T. K. N. <ng...@uw...> - 2011-07-28 23:32:55
|
I seem to have stepped into a minefield. :)
I come in peace! I was just sharing my reaction to how I would have to install a bunch of software on a computer, and learn a bunch of new things ("new" meaning "not Plone"), and, yes, I'm a techie but I still want to do as little extra work as possible. Dylan, it's not that I or other technical contributors CAN'T learn restructured text, but that we'd have to use git or svn or Sphinx, and those tools are not as easy to use as Plone or cnx.org.
Ideally, contributors would have as low a barrier as possible, to avoid discouraging them from contributing. When I contribute a "how to" to my own site (uwosh.edu/ploneprojects) I don't even want to have to THINK, so I have a link on the site that takes me to the how to folder's createObject call. That's what I mean by making it super super easy... frictionless, superconducting, K-Y for process. :)
Alex, yes I could just forge ahead but I know the only efforts that work long term are those that gain wide acceptance. It would be self defeating for the Plone community to have competing documentation processes and venues.
How about this: I will take a portion of the Plone user manual and get it into cnx.org, then show y'all what I think are the cool things one can do with it there.
About hosting documentation (which, to quibble, doesn't have quite the same meaning to me as "deployment") I was also thinking about a repo for configuration files. Is there such a thing already? I think it should be outside the documentation, since documentation such as manuals/guides are linear.
Kim
On Jul 28, 2011, at 9:59 AM, Alex Clark wrote:
> Hi,
>
> On 7/28/11 10:15 AM, T. Kim Nguyen wrote:
>> Thanks Dylan.
>>
>> I'm afraid that contributors (including me) will be scared off by the fairly complex learning and setup required to add to this documentation (Sphinx, collective commit rights, svn, restructured text) as opposed to editing a Plone page (or equivalent).
>>
>> Is the http://collective-docs.readthedocs.org/en/latest/hosting/index.html documentation updated the same way?
>
>
> Yup, and this is exactly why we've been stalled on documentation for
> years now. We have two competing camps who have very strong preferences
> about how they contribute/edit documentation[1]. The c-docs are the only
> "excitement" we've seen lately IMHO.
>
> The good news though, is that GitHub actually supports TTW editing. So
> in the case of the hosting docs Dylan just mentioned, one could edit
> them TTW by going here:
>
>
> *
> https://github.com/collective/collective.developermanual/blob/master/source/hosting/apache.txt
>
>
> Of course, you'd have to be familiar with restructured text, but that is
> a fair compromise IMHO (I.e. you don't have to understand Sphinx or
> collective commit rights at least.)
>
> Anyway, if we want to encourage folks to contribute docs on plone.org by
> using Plone, then we should be doing a much better job at managing
> plone.org. Maybe the connexions thing could solve or address this
> somehow (by lightening the plone.org/PHC load.) *shrug*
>
>
>
> Alex
>
>
>
>
> [1] I feel pretty strongly that the FWT should grab some sane set of
> documentation from the various offerings and ship it, versioned, with
> each major release of Plone. But I've not gotten enough buy in to
> consider an actual PLIP (where I'd happily do the work.)
>
>
>
>>
>> Kim
>
>
>
>>
>> On Jul 27, 2011, at 12:11 AM, Dylan Jay wrote:
>>
>>> My opinion (and keep in mind it is just my opinion) is that the place for this and all future development manual work should be
>>>
>>> http://plone.org/documentation/manual/plone-community-developer-documentation
>>>
>>> which is edited via reST and sphinx and github as per these instructionshttp://plone.org/documentation/manual/plone-community-developer-documentation/introduction/writing
>>>
>>> NOTE: at the time of writing this that document is out of date and the secondary copy at readthedocs is now more up to date.
>>> http://collective-docs.readthedocs.org/en/latest/introduction/writing.html. We're working on fixing this so the plone.org version would be updated nightly.
>>>
>>> My suggestion is we deprecate all other developer manuals and KB articles which overlap with the collective developer manual and concentrate on cleaning up and making this manual both clean, easy to understand and comprehensive.
>>>
>>> With regard to deployment I'd suggest we enhance the "hosting" section of this manual
>>>
>>> http://collective-docs.readthedocs.org/en/latest/hosting/index.html
>>>
>>>
>>> Note: these comments don't apply to the users manual or other kinds of documentation.
>>
>>
>> ------------------------------------------------------------------------------
>> Got Input? Slashdot Needs You.
>> Take our quick survey online. Come on, we don't ask for help often.
>> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
>> http://p.sf.net/sfu/slashdot-survey
>
>
> --
> Alex Clark · http://aclark.net
>
>
> ------------------------------------------------------------------------------
> Got Input? Slashdot Needs You.
> Take our quick survey online. Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs
|
|
From: Alex C. <ac...@ac...> - 2011-07-28 15:24:55
|
Hi, On 7/28/11 11:12 AM, T. Kim Nguyen wrote: > The example the Connexions people gave is that they got funding to hire someone to write a statistics textbook for five community colleges. The cost of printing on cnx.org varies from $5 for spiral bound to $20 for hardcover with binding. It meant that the participating colleges saved a lot of money for their students, and since everything on cnx.org uses the CC license, anyone can use the textbook and print it if they wish. > > In addition, the example given was that if someone at say UW Oshkosh likes the textbook but doesn't agree with one particular section of it, he/she can rewrite that one section and thread it in with the rest of the textbook and make his/her own variation. > > So in the case of a Plone user manual, if we got the "official" one hosted on cnx.org, anyone could print it easily at low cost, and anyone who wanted to modify a portion of it for their own use or own organization could do so. That would have been of immediate practical use to us at UW Oshkosh, since we wouldn't have had to write our own manual (by cutting and pasting into some document editor); we could have picked and chosen the portions of the official manual we wanted, and made our own out of those portions plus any we wanted to write that were specific to our users. And we would have been able to do it on the cnx.org platform. > > The cnx.org people have made the basis for their service available for free use; it's called Rhaptos. > > The other big selling point for us is that Rhaptos and cnx.org are built with Plone, so the UI will be in large part familiar to any Plone user. > > Does that help? Ah! Well it explains connexions a bit more at least. But I'm afraid I have no idea how to make this work within the Plone community. The usual approach is to just mail the list (which you have done) and then if no one complains vehemently (which they have not, yet) then just go do it (and wait for more complaints, which hopefully will not come). I don't know for sure, but I suspect that the plone.org/documentation is effectively licensed (if not overtly or inherently so) under some sort of GPL or CC license; which means you may already have permission to do this. When in doubt, just email: bo...@pl... and ask. HTH, Alex > > Kim > > On Jul 28, 2011, at 9:43 AM, Alex Clark wrote: > >> Hi, >> >> On 7/27/11 12:08 AM, T. Kim Nguyen wrote: >>> At the Plone Symposium 2011 at Penn State the keynote was by Connexions (http://cnx.org). Their service allows content creators to reuse and remix anyone else's content hosted on their site, whether that's books or technical manuals, by taking the parts of a document they like, changing some of it, or adding/removing other parts, and making a new version of a document. >>> >>> I thought about how University of Wisconsin Oshkosh has created its own Plone user manuals (http://www.uwosh.edu/training/training-manuals/) for Plone and Plone forms, and how we had to create them by cutting and pasting portions of the Plone user manual on plone.org, adding our own screen shots, and our own text. >>> >>> Ideally, if the Plone user manual and other documentation currently on plone.org were to be hosted on cnx.org, any organization or integrator or client could take one of any number of variants of the cnx.org Plone manuals, modify it slightly and make it their own very easily. >>> >>> I'd like to know what you think of this idea. Is this something we could try pursuing with one of the shorter Plone manuals? >> >> >> I don't understand (probably because I am not familiar with the >> Connexions service). Can you give a more practical example? >> >> In general, it sounds fine but I think a "real life example" might >> facilitate a better discussion about what exactly is being offered here. >> And what may be involved in achieving it. >> >> >> Alex >> >> >> >>> >>> Kim >>> >>> >>> ------------------------------------------------------------------------------ >>> Got Input? Slashdot Needs You. >>> Take our quick survey online. Come on, we don't ask for help often. >>> Plus, you'll get a chance to win $100 to spend on ThinkGeek. >>> http://p.sf.net/sfu/slashdot-survey >> >> >> -- >> Alex Clark · http://aclark.net >> >> >> ------------------------------------------------------------------------------ >> Got Input? Slashdot Needs You. >> Take our quick survey online. Come on, we don't ask for help often. >> Plus, you'll get a chance to win $100 to spend on ThinkGeek. >> http://p.sf.net/sfu/slashdot-survey >> _______________________________________________ >> Plone-docs mailing list >> Plo...@li... >> https://lists.sourceforge.net/lists/listinfo/plone-docs > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey -- Alex Clark · http://aclark.net |
|
From: T. K. N. <ng...@uw...> - 2011-07-28 15:13:06
|
The example the Connexions people gave is that they got funding to hire someone to write a statistics textbook for five community colleges. The cost of printing on cnx.org varies from $5 for spiral bound to $20 for hardcover with binding. It meant that the participating colleges saved a lot of money for their students, and since everything on cnx.org uses the CC license, anyone can use the textbook and print it if they wish. In addition, the example given was that if someone at say UW Oshkosh likes the textbook but doesn't agree with one particular section of it, he/she can rewrite that one section and thread it in with the rest of the textbook and make his/her own variation. So in the case of a Plone user manual, if we got the "official" one hosted on cnx.org, anyone could print it easily at low cost, and anyone who wanted to modify a portion of it for their own use or own organization could do so. That would have been of immediate practical use to us at UW Oshkosh, since we wouldn't have had to write our own manual (by cutting and pasting into some document editor); we could have picked and chosen the portions of the official manual we wanted, and made our own out of those portions plus any we wanted to write that were specific to our users. And we would have been able to do it on the cnx.org platform. The cnx.org people have made the basis for their service available for free use; it's called Rhaptos. The other big selling point for us is that Rhaptos and cnx.org are built with Plone, so the UI will be in large part familiar to any Plone user. Does that help? Kim On Jul 28, 2011, at 9:43 AM, Alex Clark wrote: > Hi, > > On 7/27/11 12:08 AM, T. Kim Nguyen wrote: >> At the Plone Symposium 2011 at Penn State the keynote was by Connexions (http://cnx.org). Their service allows content creators to reuse and remix anyone else's content hosted on their site, whether that's books or technical manuals, by taking the parts of a document they like, changing some of it, or adding/removing other parts, and making a new version of a document. >> >> I thought about how University of Wisconsin Oshkosh has created its own Plone user manuals (http://www.uwosh.edu/training/training-manuals/) for Plone and Plone forms, and how we had to create them by cutting and pasting portions of the Plone user manual on plone.org, adding our own screen shots, and our own text. >> >> Ideally, if the Plone user manual and other documentation currently on plone.org were to be hosted on cnx.org, any organization or integrator or client could take one of any number of variants of the cnx.org Plone manuals, modify it slightly and make it their own very easily. >> >> I'd like to know what you think of this idea. Is this something we could try pursuing with one of the shorter Plone manuals? > > > I don't understand (probably because I am not familiar with the > Connexions service). Can you give a more practical example? > > In general, it sounds fine but I think a "real life example" might > facilitate a better discussion about what exactly is being offered here. > And what may be involved in achieving it. > > > Alex > > > >> >> Kim >> >> >> ------------------------------------------------------------------------------ >> Got Input? Slashdot Needs You. >> Take our quick survey online. Come on, we don't ask for help often. >> Plus, you'll get a chance to win $100 to spend on ThinkGeek. >> http://p.sf.net/sfu/slashdot-survey > > > -- > Alex Clark · http://aclark.net > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs |
|
From: Alex C. <ac...@ac...> - 2011-07-28 14:59:42
|
Hi, On 7/28/11 10:15 AM, T. Kim Nguyen wrote: > Thanks Dylan. > > I'm afraid that contributors (including me) will be scared off by the fairly complex learning and setup required to add to this documentation (Sphinx, collective commit rights, svn, restructured text) as opposed to editing a Plone page (or equivalent). > > Is the http://collective-docs.readthedocs.org/en/latest/hosting/index.html documentation updated the same way? Yup, and this is exactly why we've been stalled on documentation for years now. We have two competing camps who have very strong preferences about how they contribute/edit documentation[1]. The c-docs are the only "excitement" we've seen lately IMHO. The good news though, is that GitHub actually supports TTW editing. So in the case of the hosting docs Dylan just mentioned, one could edit them TTW by going here: * https://github.com/collective/collective.developermanual/blob/master/source/hosting/apache.txt Of course, you'd have to be familiar with restructured text, but that is a fair compromise IMHO (I.e. you don't have to understand Sphinx or collective commit rights at least.) Anyway, if we want to encourage folks to contribute docs on plone.org by using Plone, then we should be doing a much better job at managing plone.org. Maybe the connexions thing could solve or address this somehow (by lightening the plone.org/PHC load.) *shrug* Alex [1] I feel pretty strongly that the FWT should grab some sane set of documentation from the various offerings and ship it, versioned, with each major release of Plone. But I've not gotten enough buy in to consider an actual PLIP (where I'd happily do the work.) > > Kim > > On Jul 27, 2011, at 12:11 AM, Dylan Jay wrote: > >> My opinion (and keep in mind it is just my opinion) is that the place for this and all future development manual work should be >> >> http://plone.org/documentation/manual/plone-community-developer-documentation >> >> which is edited via reST and sphinx and github as per these instructionshttp://plone.org/documentation/manual/plone-community-developer-documentation/introduction/writing >> >> NOTE: at the time of writing this that document is out of date and the secondary copy at readthedocs is now more up to date. >> http://collective-docs.readthedocs.org/en/latest/introduction/writing.html. We're working on fixing this so the plone.org version would be updated nightly. >> >> My suggestion is we deprecate all other developer manuals and KB articles which overlap with the collective developer manual and concentrate on cleaning up and making this manual both clean, easy to understand and comprehensive. >> >> With regard to deployment I'd suggest we enhance the "hosting" section of this manual >> >> http://collective-docs.readthedocs.org/en/latest/hosting/index.html >> >> >> Note: these comments don't apply to the users manual or other kinds of documentation. > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey -- Alex Clark · http://aclark.net |
|
From: Alex C. <ac...@ac...> - 2011-07-28 14:43:53
|
Hi, On 7/27/11 12:08 AM, T. Kim Nguyen wrote: > At the Plone Symposium 2011 at Penn State the keynote was by Connexions (http://cnx.org). Their service allows content creators to reuse and remix anyone else's content hosted on their site, whether that's books or technical manuals, by taking the parts of a document they like, changing some of it, or adding/removing other parts, and making a new version of a document. > > I thought about how University of Wisconsin Oshkosh has created its own Plone user manuals (http://www.uwosh.edu/training/training-manuals/) for Plone and Plone forms, and how we had to create them by cutting and pasting portions of the Plone user manual on plone.org, adding our own screen shots, and our own text. > > Ideally, if the Plone user manual and other documentation currently on plone.org were to be hosted on cnx.org, any organization or integrator or client could take one of any number of variants of the cnx.org Plone manuals, modify it slightly and make it their own very easily. > > I'd like to know what you think of this idea. Is this something we could try pursuing with one of the shorter Plone manuals? I don't understand (probably because I am not familiar with the Connexions service). Can you give a more practical example? In general, it sounds fine but I think a "real life example" might facilitate a better discussion about what exactly is being offered here. And what may be involved in achieving it. Alex > > Kim > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey -- Alex Clark · http://aclark.net |
|
From: T. K. N. <ng...@uw...> - 2011-07-28 14:16:04
|
Thanks Dylan. I'm afraid that contributors (including me) will be scared off by the fairly complex learning and setup required to add to this documentation (Sphinx, collective commit rights, svn, restructured text) as opposed to editing a Plone page (or equivalent). Is the http://collective-docs.readthedocs.org/en/latest/hosting/index.html documentation updated the same way? Kim On Jul 27, 2011, at 12:11 AM, Dylan Jay wrote: > My opinion (and keep in mind it is just my opinion) is that the place for this and all future development manual work should be > > http://plone.org/documentation/manual/plone-community-developer-documentation > > which is edited via reST and sphinx and github as per these instructionshttp://plone.org/documentation/manual/plone-community-developer-documentation/introduction/writing > > NOTE: at the time of writing this that document is out of date and the secondary copy at readthedocs is now more up to date. > http://collective-docs.readthedocs.org/en/latest/introduction/writing.html. We're working on fixing this so the plone.org version would be updated nightly. > > My suggestion is we deprecate all other developer manuals and KB articles which overlap with the collective developer manual and concentrate on cleaning up and making this manual both clean, easy to understand and comprehensive. > > With regard to deployment I'd suggest we enhance the "hosting" section of this manual > > http://collective-docs.readthedocs.org/en/latest/hosting/index.html > > > Note: these comments don't apply to the users manual or other kinds of documentation. |
|
From: Dylan J. <dy...@dy...> - 2011-07-27 05:11:30
|
On 27/07/2011, at 2:22 PM, T. Kim Nguyen wrote: > Hello again - apologies if it seems I am barraging the list. > > As part of the monthly PloneEdu calls we've been coming up with > ideas on how to build resources for (primarily) educational > institutions using Plone. One of those ideas is to create > documentation relating to how educational institutions have deployed > Plone: the server environment, cacheing, authentication, load > balancing, and so on. > > (While PloneEdu's mission is specifically education related, a lot > of what we do is of general use to any organization using Plone). > > In my completely unscientific method of looking around for "plone > deployment manual", "plone deployment guide", "how to deploy Plone", > I have found some resources here and there, but nothing pulling it > all together in one place, presumably on plone.org/documentation. > > Content that would be useful in such a manual: > > - the above bits and pieces of a production stack > > - sample configurations (buildouts, squid.cfg, pound.cfg, > httpd.conf, ssl.conf, etc.) > > - case studies of deployments (by "deployment" I refer specifically > to the server setup) > > - forms for accepting new deployment case studies submitted > > Has this already been done? If not, does this seem like a good > idea, and if so, how to proceed? My opinion (and keep in mind it is just my opinion) is that the place for this and all future development manual work should be http://plone.org/documentation/manual/plone-community-developer-documentation which is edited via reST and sphinx and github as per these instructions http://plone.org/documentation/manual/plone-community-developer-documentation/introduction/writing NOTE: at the time of writing this that document is out of date and the secondary copy at readthedocs is now more up to date. http://collective-docs.readthedocs.org/en/latest/introduction/writing.html . We're working on fixing this so the plone.org version would be updated nightly. My suggestion is we deprecate all other developer manuals and KB articles which overlap with the collective developer manual and concentrate on cleaning up and making this manual both clean, easy to understand and comprehensive. With regard to deployment I'd suggest we enhance the "hosting" section of this manual http://collective-docs.readthedocs.org/en/latest/hosting/index.html Note: these comments don't apply to the users manual or other kinds of documentation. > > Kim > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs |
|
From: T. K. N. <ng...@uw...> - 2011-07-27 04:22:35
|
Hello again - apologies if it seems I am barraging the list. As part of the monthly PloneEdu calls we've been coming up with ideas on how to build resources for (primarily) educational institutions using Plone. One of those ideas is to create documentation relating to how educational institutions have deployed Plone: the server environment, cacheing, authentication, load balancing, and so on. (While PloneEdu's mission is specifically education related, a lot of what we do is of general use to any organization using Plone). In my completely unscientific method of looking around for "plone deployment manual", "plone deployment guide", "how to deploy Plone", I have found some resources here and there, but nothing pulling it all together in one place, presumably on plone.org/documentation. Content that would be useful in such a manual: - the above bits and pieces of a production stack - sample configurations (buildouts, squid.cfg, pound.cfg, httpd.conf, ssl.conf, etc.) - case studies of deployments (by "deployment" I refer specifically to the server setup) - forms for accepting new deployment case studies submitted Has this already been done? If not, does this seem like a good idea, and if so, how to proceed? Kim |
|
From: T. K. N. <ng...@uw...> - 2011-07-27 04:08:42
|
At the Plone Symposium 2011 at Penn State the keynote was by Connexions (http://cnx.org). Their service allows content creators to reuse and remix anyone else's content hosted on their site, whether that's books or technical manuals, by taking the parts of a document they like, changing some of it, or adding/removing other parts, and making a new version of a document. I thought about how University of Wisconsin Oshkosh has created its own Plone user manuals (http://www.uwosh.edu/training/training-manuals/) for Plone and Plone forms, and how we had to create them by cutting and pasting portions of the Plone user manual on plone.org, adding our own screen shots, and our own text. Ideally, if the Plone user manual and other documentation currently on plone.org were to be hosted on cnx.org, any organization or integrator or client could take one of any number of variants of the cnx.org Plone manuals, modify it slightly and make it their own very easily. I'd like to know what you think of this idea. Is this something we could try pursuing with one of the shorter Plone manuals? Kim |
|
From: Alex C. <ac...@ac...> - 2011-07-09 14:35:38
|
On 7/9/11 5:16 AM, Martin Aspeli wrote: > > > On 9 Jul 2011, at 02:14, Alex Clark<ac...@ac...> wrote: > >> On 7/8/11 6:50 PM, Dylan Jay wrote: >>> On 09/07/2011, at 12:25 AM, Alex Clark<ac...@ac...> wrote: >>> >>>> On 7/8/11 4:21 AM, Martin Aspeli wrote: >>>>> >>>>> >>>>> On 8 Jul 2011, at 08:24, Dylan Jay<dy...@dy...> wrote: >>>>> >>>>>> On 08/07/2011, at 5:15 PM, Martin Aspeli wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On 8 Jul 2011, at 02:02, Dylan Jay<dy...@dy...> wrote: >>>>>>> >>>>>>>> >>>>>>>> On 07/07/2011, at 11:39 AM, Alex Clark wrote: >>>>>>>> >>>>>>>>> Hi. >>>>>>>>> >>>>>>>>> On 6/19/11 7:36 AM, Dylan Jay wrote: >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> There's lots of links in the collective developers manual to KB >>>>>>>>>> articles. Is there any reason not to just import those documents >>>>>>>>>> directly into the manual and remove the KB article? >>>>>>>>> >>>>>>>>> Yes. >>>>>>>>> >>>>>>>>> I'll state the obvious: because it may offend the KB article author. I >>>>>>>>> suspect you'd need to contact the author directly and ask where they'd >>>>>>>>> prefer their article to live. >>>>>>>> >>>>>>>> seems a shame as where we really want to go is non-repeated >>>>>>>> documentation. >>>>>>>> but I guess you're right, not worth coming up with a process until we >>>>>>>> get manual publishing working. >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> Note: we've still got a "mess" on our hands wrt to collective docs. >>>>>>>>> I am >>>>>>>>> hoping to clean up and automate the inclusion of c-docs in plone.org >>>>>>>>> as >>>>>>>>> soon as someone from the board replies to this ticket: >>>>>>>>> >>>>>>>>> * https://dev.plone.org/plone/ticket/11771 >>>>>>>>> >>>>>>>>> >>>>>>>>> Right now we have: >>>>>>>>> >>>>>>>>> * Out of date c-docs on plone.org/documentation (because no one >>>>>>>>> understands the upload process[1]). I'm now OK with fixing this >>>>>>>>> (i.e. I >>>>>>>>> know how to do it). >>>>>>>> >>>>>>>> I'm happy to fix any coding issues with the funnelweb import. Last >>>>>>>> time I tried it was working. >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> * Out of date c-docs on collective-docs.plone.org because your recent >>>>>>>>> changes added a Sphinx module that does not exist on deus (includedocs >>>>>>>>> IIRC). >>>>>>>> >>>>>>>> :) sorry about that. But will be worth it if all goes to plan and we >>>>>>>> can kick start core devs into documenting their own work. >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> As I am not terribly interested in fixing deus[2], I've recently >>>>>>>>> considered moving c-docs to github and publishing them to >>>>>>>>> readthedocs.org (which moo has +1'd). But I still need to test. >>>>>>>> >>>>>>>> So replace collective-docs.plone.org with readthedocs? I think that's >>>>>>>> a good idea. >>>>>>> >>>>>>> +1, though we should link back to plone.org/documentation for more docs. >>>>>> >>>>>> +1 on linking back to plone.org/documentation. >>>>>> >>>>>> BTW, Alex wasn't suggesting removing the manual from plone.org/documentation. Just that he prefers not to read it there. >>>>> >>>>> I know. But having it on another plone.org subdomain is really confusing and sends the wrong message. Syndicating to readthedocs is a nice idea, and does not send such a mixed message. >>>> >>>> >>>> +1. So to clarify collective-docs.plone.org should redir to >>>> plone.org/documentation… or leave it the way it is redir'ing to >>>> readthedocs.org. >>> >>> Redir to readthedocs since people expect a sphinx layout. >> >> Done. >> >> >>> >>> But I would like to fix the issue of many many names for that manual. >>> Can we just merge the two plone developers manuals and call it that? >> >> >> This is what I was hoping Martin or someone would provide feedback for >> here. "Collective docs" sounds right to me. And the URL is reasonable. >> If we're going to make a change, I'm not sure what that change should be >> (amongst all the options I listed yesterday). > > Collective Docs is not a good name. It's meaningless to anyone not a seasoned Plone developer. > > Plone Developer Manual is fine if we merge. If not, Plone Community-Contributed Development Documentation or similar may be fine. How about a compromise (for now). I've changed the title (see attached) but there is no easy way to delete projects on readthedocs (that I can see), so I don't want to create a 2nd project with a new url just yet (which may cause more confusion). If I can figure out how to change the URL, I don't mind doing that either. Alex > > Martin > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs -- Alex Clark · http://aclark.net |
173 messages has been excluded from this view by a project administrator.
