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: Mikko O. <mik...@re...> - 2012-06-29 15:02:13
|
On Fri, Jun 29, 2012 at 3:26 PM, kimanibob <kim...@ho...> wrote: > Thanks guys, think I found a solution. I copied the buildout.cfg to the bin > folder and all seem to be fine. > You are doing it wrong. Please do as in the instructions to avoid further problems. We did not wrote those instructions for nothing :( -Mikko > > -- > View this message in context: > http://plone.293351.n2.nabble.com/buildout-on-windows-tp7556557p7556562.html > Sent from the Documentation Team mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs > > -- > Mikko Ohtamaa > <https://lists.sourceforge.net/lists/listinfo/plone-docs> > http://opensourcehacker.com > http://twitter.com/moo9000 > > > > |
|
From: kimanibob <kim...@ho...> - 2012-06-29 12:26:21
|
Thanks guys, think I found a solution. I copied the buildout.cfg to the bin folder and all seem to be fine. Sorry for being the wrong forum -- View this message in context: http://plone.293351.n2.nabble.com/buildout-on-windows-tp7556557p7556562.html Sent from the Documentation Team mailing list archive at Nabble.com. |
|
From: Mikko O. <mik...@re...> - 2012-06-29 12:16:52
|
On Fri, Jun 29, 2012 at 2:43 PM, Clayton Parker <cl...@si...>wrote: > Also, I should mention that this list is for discussing things related to > documentation. If you need further assistance for issues like this you > should use plone-users or stack overflow. > To make it related, one relevant doc is here (looks to be correct): http://plone.org/documentation/kb/installing-add-ons-quick-how-to/ Then in-depth: http://plone.org/documentation/kb/using-buildout-on-windows/ If you find any invalid documentation please point it to us and we'll do some book burning. -M > > Clayton > -- > Six Feet Up, Inc. | Where sophisticated web projects thrive > Direct Line: +1 (317) 861-5948 x603 > Email: cl...@si... > Try Plone 4 Today at: http://plone4demo.com > > > > > > On Jun 29, 2012, at 7:40 AM, Clayton Parker wrote: > > > On Jun 29, 2012, at 7:22 AM, kimanibob wrote: > > > >> I have installed Plone 4.1.5, which was successful. however I want to > enable > >> services using Buildout and experience the error below. > >> Am run plone out on windows 7 sp1. How do i go about sort the error > below. > >> Note: am new to plone. > >> > >> /C:\Plone41\bin>buildout.exe > >> While: Initializing. > >> Error: Couldn't open C:\Plone41\bin\buildout.cfg > >> C:\Plone41\bin>/ > > > > You have to run buildout from the level above. > > > > C:\Plone41\bin> cd .. > > C:\Plone41> bin\buildout.exe > > > > Then it should work. When the buildout command is run, it looks for the > buildout.cfg in the same working directory. > > > > Clayton > > -- > > Six Feet Up, Inc. | Where sophisticated web projects thrive > > Direct Line: +1 (317) 861-5948 x603 > > Email: cl...@si... > > Try Plone 4 Today at: http://plone4demo.com > > > > > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > Plone-docs mailing list > > Plo...@li... > > https://lists.sourceforge.net/lists/listinfo/plone-docs > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs > > -- > Mikko Ohtamaa > <https://lists.sourceforge.net/lists/listinfo/plone-docs> > http://opensourcehacker.com > http://twitter.com/moo9000 > > > > > > |
|
From: Clayton P. <cl...@si...> - 2012-06-29 11:43:13
|
Also, I should mention that this list is for discussing things related to documentation. If you need further assistance for issues like this you should use plone-users or stack overflow. Clayton -- Six Feet Up, Inc. | Where sophisticated web projects thrive Direct Line: +1 (317) 861-5948 x603 Email: cl...@si... Try Plone 4 Today at: http://plone4demo.com On Jun 29, 2012, at 7:40 AM, Clayton Parker wrote: > On Jun 29, 2012, at 7:22 AM, kimanibob wrote: > >> I have installed Plone 4.1.5, which was successful. however I want to enable >> services using Buildout and experience the error below. >> Am run plone out on windows 7 sp1. How do i go about sort the error below. >> Note: am new to plone. >> >> /C:\Plone41\bin>buildout.exe >> While: Initializing. >> Error: Couldn't open C:\Plone41\bin\buildout.cfg >> C:\Plone41\bin>/ > > You have to run buildout from the level above. > > C:\Plone41\bin> cd .. > C:\Plone41> bin\buildout.exe > > Then it should work. When the buildout command is run, it looks for the buildout.cfg in the same working directory. > > Clayton > -- > Six Feet Up, Inc. | Where sophisticated web projects thrive > Direct Line: +1 (317) 861-5948 x603 > Email: cl...@si... > Try Plone 4 Today at: http://plone4demo.com > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs |
|
From: Clayton P. <cl...@si...> - 2012-06-29 11:40:35
|
On Jun 29, 2012, at 7:22 AM, kimanibob wrote: > I have installed Plone 4.1.5, which was successful. however I want to enable > services using Buildout and experience the error below. > Am run plone out on windows 7 sp1. How do i go about sort the error below. > Note: am new to plone. > > /C:\Plone41\bin>buildout.exe > While: Initializing. > Error: Couldn't open C:\Plone41\bin\buildout.cfg > C:\Plone41\bin>/ You have to run buildout from the level above. C:\Plone41\bin> cd .. C:\Plone41> bin\buildout.exe Then it should work. When the buildout command is run, it looks for the buildout.cfg in the same working directory. Clayton -- Six Feet Up, Inc. | Where sophisticated web projects thrive Direct Line: +1 (317) 861-5948 x603 Email: cl...@si... Try Plone 4 Today at: http://plone4demo.com |
|
From: kimanibob <kim...@ho...> - 2012-06-29 11:23:09
|
I have installed Plone 4.1.5, which was successful. however I want to enable
services using Buildout and experience the error below.
Am run plone out on windows 7 sp1. How do i go about sort the error below.
Note: am new to plone.
/C:\Plone41\bin>buildout.exe
While: Initializing.
Error: Couldn't open C:\Plone41\bin\buildout.cfg
C:\Plone41\bin>/
--
View this message in context: http://plone.293351.n2.nabble.com/buildout-on-windows-tp7556557.html
Sent from the Documentation Team mailing list archive at Nabble.com.
|
|
From: Jon S. <jon...@gm...> - 2012-06-25 20:18:56
|
Spotted this on HN this morning: http://developmentseed.org/blog/2012/june/25/prose-a-content-editor-for-github/ I'm not sure I understand all the infrastructure/architecture particulars, but it looks like this could be a really nice way to let folks edit our github-hosted docs/manuals. :jon --- Jon Stahl http://jstahl.org 206.226.0818 |
|
From: Mikko O. <mik...@re...> - 2012-05-25 12:55:20
|
Fixed On Fri, May 25, 2012 at 3:29 PM, Roy Mathew <rma...@gm...> wrote: > >> http://plone.org/documentation/manual/plone-4-user-manual/adding-content/adding-new-content has >> a line that reads: >> New content items are adding via the *Add New . . .* drop-down menu: >> and should read: >> New content items are added via the *Add New . . .* drop-down menu: >> > > -- > Roy. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs > > -- > Mikko Ohtamaa > <https://lists.sourceforge.net/lists/listinfo/plone-docs> > http://opensourcehacker.com > http://twitter.com/moo9000 > > > > |
|
From: Roy M. <rma...@gm...> - 2012-05-25 12:29:57
|
> > > http://plone.org/documentation/manual/plone-4-user-manual/adding-content/adding-new-content has > a line that reads: > New content items are adding via the *Add New . . .* drop-down menu: > and should read: > New content items are added via the *Add New . . .* drop-down menu: > -- Roy. |
|
From: Jon S. <jon...@gm...> - 2012-04-26 19:19:27
|
Done, and ticket closed, thanks! :jon On Thu, Apr 26, 2012 at 11:45 AM, Gerardo Lisboa (INFO-CARE) <ger...@in...> wrote: > Hello, > > According to https://dev.plone.org/ticket/9326 > http://plone.org/documentation/manual/installing-plone/installing-on-linux-unix-bsd/debian-libraries should > be changed to > > > sudo apt-get install build-essential > sudo apt-get install libssl-dev > sudo apt-get install libxml2-dev > sudo apt-get install libxslt1-dev > sudo apt-get install libbz2-dev > > Also, the libreadline package has been renamed: > > > sudo apt-get install libjpeg62-dev > sudo apt-get install libreadline-gplv2-dev > > Tested on Ubuntu 11.10 x64 > > Best Regards, > Gerardo V. Lisboa > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs > |
|
From: Gerardo L. (INFO-CARE) <ger...@in...> - 2012-04-26 18:53:41
|
Hello, According to https://dev.plone.org/ticket/9326 http://plone.org/documentation/manual/installing-plone/installing-on-linux-unix-bsd/debian-libraries should be changed to sudo apt-get install build-essential sudo apt-get install libssl-dev sudo apt-get install libxml2-devsudo apt-get install libxslt1-devsudo apt-get install libbz2-dev Also, the libreadline package has been renamed: sudo apt-get install libjpeg62-dev sudo apt-get install libreadline-gplv2-dev Tested on Ubuntu 11.10 x64 Best Regards, Gerardo V. Lisboa |
|
From: Dylan J. <dy...@dy...> - 2012-04-26 13:43:49
|
On 26/04/2012, at 5:13 AM, Mikko Ohtamaa wrote: > > Pull when ready and let's get this sorted out. done https://github.com/collective/collective.developermanual/pull/35 > > > Dylan Jay-4 wrote >> >> Hi, >> >> As previously discussed I've created a branch to remove the tutorials >> section and redistribute the content to new or existing sections. >> >> I haven't created a pull request yet as I have to go fix a bunch of >> broken links and also move some content that has recently been added >> to the tutorials section. >> >> You can see the diffs here. >> >> https://github.com/collective/collective.developermanual/compare/master...djay >> >> >> >> >> >> ------------------------------------------------------------------------------ >> For Developers, A Lot Can Happen In A Second. >> Boundary is the first to Know...and Tell You. >> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! >> http://p.sf.net/sfu/Boundary-d2dvs2 >> _______________________________________________ >> Plone-docs mailing list >> Plone-docs@.sourceforge >> https://lists.sourceforge.net/lists/listinfo/plone-docs >> > > > ----- > > Follow me in Twitter > > > > Read my blog > > > > > > -- > View this message in context: http://plone.293351.n2.nabble.com/cleaning-up-tutorials-section-tp7469338p7500532.html > Sent from the Documentation Team mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs |
|
From: Jean J. <jea...@gm...> - 2012-04-26 06:19:42
|
On Wed, Apr 25, 2012 at 10:26 PM, Dylan Jay <dy...@dy...> wrote: > Hi, > > I released funnelweb 1.1 and added the example of converting the rtd > manual to PHC. > > https://github.com/collective/funnelweb#read-the-docs > > I'll fork the plone.org buildout and add this as a nightly task. Very cool, thanks Dylan. -- jean . .. .... //\\\oo///\\ |
|
From: sven <sv...@so...> - 2012-04-25 20:15:34
|
Hi, yes, i did, but this is just a very basic howto for nano not sure if that is enough .... if we want a howto/link collection for remote editing, in my opinion, we have to cut it down to only a couple of possibilities otherwise it will be really because there are so many different solutions like: - ssh and a remote editor - vnc - sshfs - nx/neatx - ssh with x forward - a sftp/ftp client - ... cheers /sven On 04/25/2012 09:34 PM, Mikko Ohtamaa wrote: > Someone pasted in IRC: > > http://www.howtogeek.com/howto/42980/the-beginners-guide-to-nano-the-linux-command-line-text-editor/ > > ----- > > Follow me in Twitter > > > > Read my blog > > > > > > -- > View this message in context: http://plone.293351.n2.nabble.com/Tutorial-for-editing-files-on-UNIX-servers-tp7500567p7500579.html > Sent from the Documentation Team mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs |
|
From: Mikko O. <mik...@re...> - 2012-04-25 19:34:39
|
Someone pasted in IRC: http://www.howtogeek.com/howto/42980/the-beginners-guide-to-nano-the-linux-command-line-text-editor/ ----- Follow me in Twitter Read my blog -- View this message in context: http://plone.293351.n2.nabble.com/Tutorial-for-editing-files-on-UNIX-servers-tp7500567p7500579.html Sent from the Documentation Team mailing list archive at Nabble.com. |
|
From: Mikko O. <mik...@re...> - 2012-04-25 19:27:34
|
Hi all, Our dear users need guidance how to edit files on a remote (UNIX) server over SSH connections and such. buildout.cfg, to name one. Does anyone have good links, so we don't need to document this ourselves? ----- Follow me in Twitter Read my blog -- View this message in context: http://plone.293351.n2.nabble.com/Tutorial-for-editing-files-on-UNIX-servers-tp7500567p7500567.html Sent from the Documentation Team mailing list archive at Nabble.com. |
|
From: Mikko O. <mik...@re...> - 2012-04-25 19:15:00
|
Hi, I have created a Travis CI job to check collective.developermanual for Sphinx errors: http://travis-ci.org/#!/collective/collective.developermanual/builds/1174760 However Travis tells me something depressing: Executing your install (bin/buildout) took longer than 900 seconds and was terminated. Consider rewriting your stuff in AssemblyScript, we've heard it handles Web Scale™ How to make c.developermanual buildout faster....? ----- Follow me in Twitter Read my blog -- View this message in context: http://plone.293351.n2.nabble.com/Travis-CI-job-for-collective-developermanual-and-too-sloooow-buildout-tp7500539p7500539.html Sent from the Documentation Team mailing list archive at Nabble.com. |
|
From: Mikko O. <mik...@re...> - 2012-04-25 19:13:26
|
Pull when ready and let's get this sorted out. Dylan Jay-4 wrote > > Hi, > > As previously discussed I've created a branch to remove the tutorials > section and redistribute the content to new or existing sections. > > I haven't created a pull request yet as I have to go fix a bunch of > broken links and also move some content that has recently been added > to the tutorials section. > > You can see the diffs here. > > https://github.com/collective/collective.developermanual/compare/master...djay > > > > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Plone-docs mailing list > Plone-docs@.sourceforge > https://lists.sourceforge.net/lists/listinfo/plone-docs > ----- Follow me in Twitter Read my blog -- View this message in context: http://plone.293351.n2.nabble.com/cleaning-up-tutorials-section-tp7469338p7500532.html Sent from the Documentation Team mailing list archive at Nabble.com. |
|
From: Dylan J. <dy...@dy...> - 2012-04-25 15:56:22
|
Hi, I released funnelweb 1.1 and added the example of converting the rtd manual to PHC. https://github.com/collective/funnelweb#read-the-docs I'll fork the plone.org buildout and add this as a nightly task. |
|
From: Dylan J. <dy...@dy...> - 2012-04-16 06:57:47
|
Hi, As previously discussed I've created a branch to remove the tutorials section and redistribute the content to new or existing sections. I haven't created a pull request yet as I have to go fix a bunch of broken links and also move some content that has recently been added to the tutorials section. You can see the diffs here. https://github.com/collective/collective.developermanual/compare/master...djay |
|
From: Steve M. <st...@dc...> - 2012-04-16 00:59:28
|
On Thu, Jan 26, 2012 at 12:17 PM, Mikko Ohtamaa < mik...@re...> wrote: > ... > Of course this would involve some politics as I believe official developer > manual is copyrighted by the foundation, but collective docs are by > individual contributors. > ... > Unfortunately, the PF has no copyright agreement for any of the documentation space. It had been the intention to do that, but I don't think the developer agreement was ever amended to include documentation. So, copying anything from the documentation area anywhere without permission of the original authors would be problematic. I suspect the only documentation that's probably got a clear license is that included with packages contributed under the developers' agreement. Note that this is probably a very similar situation to collective docs. Since there's no contributor's agreement, everything in it probably needs to be considered the copyrighted property of the individual authors and everyone else who ever made a substantive change. Copyright law sucks. Lack of clear license unfortunately does not mean something is free for the taking. It means the opposite: it's hopelessly encumbered and can't be reused by anyone. Sorry to be a late contributor to the discussion! |
|
From: John S. <jo...@ec...> - 2012-04-14 18:42:35
|
Thanks, I did the pull request. Only thing I have missed is to fill in the *commit message* text when I originally did the *propose file change*, however I see the change has already been merged in this case. thanks, John S. On 04/14/2012 12:41 AM, Mikko Ohtamaa wrote: > > On Sat, Apr 14, 2012 at 13:26, Mikko Ohtamaa > <mik...@re... <mailto:mikko%2B...@re...>> > wrote: > > > > On Sat, Apr 14, 2012 at 04:11, John Schinnerer <jo...@ec... > <mailto:jo...@ec...>> wrote: > > Thank you, simple enough, and...done. > Is that it? > After *Propose file change* I get a page re sending a pull > request. Don't grok it...do I need to do that? > > > > Ok here are the reviewed mini instructions: > > > Edit this document > > The source code of this file is hosted on GitHub. Everyone can update > and fix errors in this document with few clicks - no downloads needed. > > 1. Go to XXX on GitHub. > 2. Press *Fork and edit this file* button. > 3. Edit file contents using GitHub's text editor in your web browserm > 4. Fill in the *Commit message* text box at the end of the page telling > /why/ you did the changes. Press *Propose file change* button next > to it when done. > 5. On /Send a pull request/ page you don't need to fill in text > anymore. Just press *Send pull request* button. > 6. Your changes are now queued for review under project's Pull requests > <https://github.com/collective/collective.developermanual/pulls> tab > on Github. > > For basic information about updating this manual and Sphinx format > please see Writing and updating the manual > <http://collective-docs.readthedocs.org/en/latest/introduction/writing.html> > guide. > > > > Yes, that must be done also. I'll clarify that in nstructions. > > Cheers, Mikko > -Mikko > > > thanks, > John S. > > > On 04/13/2012 11:46 AM, Mikko Ohtamaa wrote: > > > > On Fri, Apr 13, 2012 at 23:42, John Schinnerer > <jo...@ec... <mailto:jo...@ec...> > <mailto:jo...@ec... <mailto:jo...@ec...>>> > wrote: > > I am totally new to github...the apparently relevant > button says > "Fork and Edit this file" - not sure if that is the correct > thing to > do? Please advise how to make the edit without making a > mess... > > > Should go like this > > 1. Go to Writing and updating the documentation > <https://github.com/__collective/collective.__developermanual/edit/master/__source/introduction/writing.__rst > <https://github.com/collective/collective.developermanual/edit/master/source/introduction/writing.rst>> > on GitHub. > 2. Press *Fork and edit this file* button > 3. Edit file contents using GitHub's text editor in your > web browser > 4. Press *Propose file change* at the bottom of the page > > > > > thanks, > John S. > > > On 04/12/2012 08:56 PM, Mikko Ohtamaa wrote: > > Hi John, > > Mention early on, with link, to see the Hosting > Guide for > information > about production installations/deployments. > > > Good spot. Can you go ahead and fix it directly here? > > https://github.com/collective/____collective.developermanual/____blob/master/source/tutorials/____installation.rst > <https://github.com/collective/__collective.developermanual/__blob/master/source/tutorials/__installation.rst> > > <https://github.com/__collective/collective.__developermanual/blob/master/__source/tutorials/installation.__rst > <https://github.com/collective/collective.developermanual/blob/master/source/tutorials/installation.rst>> > > -Mikko > > For example where it now says: > > ------------------------------____---------- > > ... > Installing Plone using Unified UNIX Installer > > Note > This is the recommended installation method > > This recipe is good for > Lightweight production sites > Plone development and testing on Ubuntu / > Debian > ... > ------------------------------____------------ > > > ...add some following text like: > > "For information on using this installation with production > environments/deployments, see the [hosting guide]." > > There is a line that hints at that at the very > end of the > unified > installer section, and I think it could be > clearer and sooner. > > thanks, > John S. > > On 04/10/2012 05:04 AM, Mikko Ohtamaa wrote: > > Hi, > > > > I try to modernize / centralize existing Plone installation > instructions. > > > > Please take a look on: > > > > > http://collective-docs.__readt__hedocs.org/en/latest/____tutorials/installation.html > <http://readthedocs.org/en/latest/__tutorials/installation.html> > > <http://collective-docs.__readthedocs.org/en/latest/__tutorials/installation.html > <http://collective-docs.readthedocs.org/en/latest/tutorials/installation.html>> > > > > ...and then take a stab on the document or me. > > > > Cheers, > > Mikko > > > > ----- > > > > Follow me in Twitter > > > > > > > > Read my blog > > > > > > > > > > > > -- > > View this message in context: > http://plone.293351.n2.nabble.____com/New-installation-____instructions-____tp7453156p7453156.html > > <http://plone.293351.n2.__nabble.com/New-installation-__instructions-__tp7453156p7453156.html > <http://plone.293351.n2.nabble.com/New-installation-instructions-tp7453156p7453156.html>> > > Sent from the Documentation Team mailing list archive at > Nabble.com. > > > > > > > ------------------------------____----------------------------__--__------------------ > > > Better than sec? Nothing is better than sec when it comes to > > monitoring Big Data applications. Try Boundary one-second > > resolution app monitoring today. Free. > > http://p.sf.net/sfu/Boundary-____dev2dev > <http://p.sf.net/sfu/Boundary-__dev2dev> > <http://p.sf.net/sfu/Boundary-__dev2dev > <http://p.sf.net/sfu/Boundary-dev2dev>> > > ___________________________________________________ > > Plone-docs mailing list > > Plo...@li...urceforge.____net > <mailto:Plone-docs@lists.__sourceforge.net > <mailto:Plo...@li...>> > <mailto:Plone-docs@lists. > <mailto:Plone-docs@lists.>__sou__rceforge.net > <http://sourceforge.net> > <mailto:Plone-docs@lists.__sourceforge.net > <mailto:Plo...@li...>>> > > > > https://lists.sourceforge.net/____lists/listinfo/plone-docs > <https://lists.sourceforge.net/__lists/listinfo/plone-docs> > > <https://lists.sourceforge.__net/lists/listinfo/plone-docs > <https://lists.sourceforge.net/lists/listinfo/plone-docs>> > > -- > John Schinnerer - M.A., Whole Systems Design > ------------------------------____-------------- > > - Eco-Living - > Whole Systems Design Services > People - Place - Learning - Integration > jo...@ec... <mailto:jo...@ec...> > <mailto:jo...@ec... <mailto:jo...@ec...>> > <mailto:jo...@ec... <mailto:jo...@ec...> > <mailto:jo...@ec... <mailto:jo...@ec...>>> > > http://eco-living.net > > > > ------------------------------____----------------------------__--__------------------ > > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine > Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-____d2dvs2 > <http://p.sf.net/sfu/Boundary-__d2dvs2> > <http://p.sf.net/sfu/Boundary-__d2dvs2 > <http://p.sf.net/sfu/Boundary-d2dvs2>> > ___________________________________________________ > Plone-docs mailing list > Plo...@li...urceforge.____net > <mailto:Plone-docs@lists.__sourceforge.net > <mailto:Plo...@li...>> > <mailto:Plone-docs@lists. > <mailto:Plone-docs@lists.>__sou__rceforge.net > <http://sourceforge.net> > <mailto:Plone-docs@lists.__sourceforge.net > <mailto:Plo...@li...>>> > > https://lists.sourceforge.net/____lists/listinfo/plone-docs > <https://lists.sourceforge.net/__lists/listinfo/plone-docs> > > <https://lists.sourceforge.__net/lists/listinfo/plone-docs > <https://lists.sourceforge.net/lists/listinfo/plone-docs>> > > -- > Mikko Ohtamaa > http://opensourcehacker.com > http://twitter.com/moo9000 > > > > > -- > John Schinnerer - M.A., Whole Systems Design > ------------------------------____-------------- > > - Eco-Living - > Whole Systems Design Services > People - Place - Learning - Integration > jo...@ec... <mailto:jo...@ec...> > <mailto:jo...@ec... <mailto:jo...@ec...>> > http://eco-living.net > > -- > Mikko Ohtamaa > http://opensourcehacker.com > http://twitter.com/moo9000 > > > > > -- > John Schinnerer - M.A., Whole Systems Design > ------------------------------__-------------- > - Eco-Living - > Whole Systems Design Services > People - Place - Learning - Integration > jo...@ec... <mailto:jo...@ec...> > http://eco-living.net > > -- > Mikko Ohtamaa > http://opensourcehacker.com > http://twitter.com/moo9000 > > -- > Mikko Ohtamaa > http://opensourcehacker.com > http://twitter.com/moo9000 > > > -- John Schinnerer - M.A., Whole Systems Design -------------------------------------------- - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration jo...@ec... http://eco-living.net |
|
From: Mikko O. <mik...@re...> - 2012-04-14 10:41:31
|
On Sat, Apr 14, 2012 at 13:26, Mikko Ohtamaa <mik...@re...>wrote: > > > On Sat, Apr 14, 2012 at 04:11, John Schinnerer <jo...@ec...>wrote: > >> Thank you, simple enough, and...done. >> Is that it? >> After *Propose file change* I get a page re sending a pull request. Don't >> grok it...do I need to do that? >> > > Ok here are the reviewed mini instructions: Edit this document The source code of this file is hosted on GitHub. Everyone can update and fix errors in this document with few clicks - no downloads needed. 1. Go to XXX on GitHub. 2. Press *Fork and edit this file* button. 3. Edit file contents using GitHub's text editor in your web browserm 4. Fill in the *Commit message* text box at the end of the page telling * why* you did the changes. Press *Propose file change* button next to it when done. 5. On *Send a pull request* page you don't need to fill in text anymore. Just press *Send pull request* button. 6. Your changes are now queued for review under project's Pull requests<https://github.com/collective/collective.developermanual/pulls>tab on Github. For basic information about updating this manual and Sphinx format please see Writing and updating the manual<http://collective-docs.readthedocs.org/en/latest/introduction/writing.html>guide. > Yes, that must be done also. I'll clarify that in nstructions. > > Cheers, Mikko > -Mikko > > >> >> thanks, >> John S. >> >> >> On 04/13/2012 11:46 AM, Mikko Ohtamaa wrote: >> >>> >>> >>> On Fri, Apr 13, 2012 at 23:42, John Schinnerer <jo...@ec... >>> <mailto:jo...@ec...>> wrote: >>> >>> I am totally new to github...the apparently relevant button says >>> "Fork and Edit this file" - not sure if that is the correct thing to >>> do? Please advise how to make the edit without making a mess... >>> >>> >>> Should go like this >>> >>> 1. Go to Writing and updating the documentation >>> <https://github.com/**collective/collective.** >>> developermanual/edit/master/**source/introduction/writing.**rst<https://github.com/collective/collective.developermanual/edit/master/source/introduction/writing.rst> >>> > >>> on GitHub. >>> 2. Press *Fork and edit this file* button >>> 3. Edit file contents using GitHub's text editor in your web browser >>> 4. Press *Propose file change* at the bottom of the page >>> >>> >>> >>> >>> thanks, >>> John S. >>> >>> >>> On 04/12/2012 08:56 PM, Mikko Ohtamaa wrote: >>> >>> Hi John, >>> >>> Mention early on, with link, to see the Hosting Guide for >>> information >>> about production installations/deployments. >>> >>> >>> Good spot. Can you go ahead and fix it directly here? >>> >>> https://github.com/collective/**__collective.developermanual/_** >>> _blob/master/source/tutorials/**__installation.rst<https://github.com/collective/__collective.developermanual/__blob/master/source/tutorials/__installation.rst> >>> >>> <https://github.com/**collective/collective.** >>> developermanual/blob/master/**source/tutorials/installation.**rst<https://github.com/collective/collective.developermanual/blob/master/source/tutorials/installation.rst> >>> > >>> >>> -Mikko >>> >>> For example where it now says: >>> >>> ------------------------------**__---------- >>> >>> ... >>> Installing Plone using Unified UNIX Installer >>> >>> Note >>> This is the recommended installation method >>> >>> This recipe is good for >>> Lightweight production sites >>> Plone development and testing on Ubuntu / Debian >>> ... >>> ------------------------------**__------------ >>> >>> >>> ...add some following text like: >>> >>> "For information on using this installation with production >>> environments/deployments, see the [hosting guide]." >>> >>> There is a line that hints at that at the very end of the >>> unified >>> installer section, and I think it could be clearer and sooner. >>> >>> thanks, >>> John S. >>> >>> On 04/10/2012 05:04 AM, Mikko Ohtamaa wrote: >>> > Hi, >>> > >>> > I try to modernize / centralize existing Plone installation >>> instructions. >>> > >>> > Please take a look on: >>> > >>> > >>> http://collective-docs.__readt**hedocs.org/en/latest/__** >>> tutorials/installation.html<http://readthedocs.org/en/latest/__tutorials/installation.html> >>> >>> <http://collective-docs.**readthedocs.org/en/latest/** >>> tutorials/installation.html<http://collective-docs.readthedocs.org/en/latest/tutorials/installation.html> >>> > >>> > >>> > ...and then take a stab on the document or me. >>> > >>> > Cheers, >>> > Mikko >>> > >>> > ----- >>> > >>> > Follow me in Twitter >>> > >>> > >>> > >>> > Read my blog >>> > >>> > >>> > >>> > >>> > >>> > -- >>> > View this message in context: >>> http://plone.293351.n2.nabble.**__com/New-installation-__** >>> instructions-__**tp7453156p7453156.html >>> >>> <http://plone.293351.n2.**nabble.com/New-installation-** >>> instructions-**tp7453156p7453156.html<http://plone.293351.n2.nabble.com/New-installation-instructions-tp7453156p7453156.html> >>> > >>> > Sent from the Documentation Team mailing list archive at >>> Nabble.com. >>> > >>> > >>> >>> ------------------------------**__----------------------------* >>> *--__------------------ >>> >>> > Better than sec? Nothing is better than sec when it comes to >>> > monitoring Big Data applications. Try Boundary one-second >>> > resolution app monitoring today. Free. >>> > http://p.sf.net/sfu/Boundary-_**_dev2dev<http://p.sf.net/sfu/Boundary-__dev2dev> >>> <http://p.sf.net/sfu/Boundary-**dev2dev<http://p.sf.net/sfu/Boundary-dev2dev> >>> > >>> > ______________________________**___________________ >>> > Plone-docs mailing list >>> > Plo...@li...urceforge._**_net >>> <mailto:Plone-docs@lists.**sourceforge.net<Plo...@li...> >>> > >>> <mailto:Plone-docs@lists.__sou**rceforge.net<http://sourceforge.net> >>> <mailto:Plone-docs@lists.**sourceforge.net<Plo...@li...> >>> >> >>> >>> > https://lists.sourceforge.net/**__lists/listinfo/plone-docs<https://lists.sourceforge.net/__lists/listinfo/plone-docs> >>> >>> <https://lists.sourceforge.**net/lists/listinfo/plone-docs<https://lists.sourceforge.net/lists/listinfo/plone-docs> >>> > >>> >>> -- >>> John Schinnerer - M.A., Whole Systems Design >>> ------------------------------**__-------------- >>> >>> - Eco-Living - >>> Whole Systems Design Services >>> People - Place - Learning - Integration >>> jo...@ec... <mailto:jo...@ec...> >>> <mailto:jo...@ec... <mailto:jo...@ec...>> >>> >>> http://eco-living.net >>> >>> >>> ------------------------------**__----------------------------* >>> *--__------------------ >>> >>> For Developers, A Lot Can Happen In A Second. >>> Boundary is the first to Know...and Tell You. >>> Monitor Your Applications in Ultra-Fine Resolution. Try it >>> FREE! >>> http://p.sf.net/sfu/Boundary-_**_d2dvs2<http://p.sf.net/sfu/Boundary-__d2dvs2> >>> <http://p.sf.net/sfu/Boundary-**d2dvs2<http://p.sf.net/sfu/Boundary-d2dvs2> >>> > >>> ______________________________**___________________ >>> Plone-docs mailing list >>> Plo...@li...urceforge._**_net >>> <mailto:Plone-docs@lists.**sourceforge.net<Plo...@li...> >>> > >>> <mailto:Plone-docs@lists.__sou**rceforge.net<http://sourceforge.net> >>> <mailto:Plone-docs@lists.**sourceforge.net<Plo...@li...> >>> >> >>> >>> https://lists.sourceforge.net/**__lists/listinfo/plone-docs<https://lists.sourceforge.net/__lists/listinfo/plone-docs> >>> >>> <https://lists.sourceforge.**net/lists/listinfo/plone-docs<https://lists.sourceforge.net/lists/listinfo/plone-docs> >>> > >>> >>> -- >>> Mikko Ohtamaa >>> http://opensourcehacker.com >>> http://twitter.com/moo9000 >>> >>> >>> >>> >>> -- >>> John Schinnerer - M.A., Whole Systems Design >>> ------------------------------**__-------------- >>> >>> - Eco-Living - >>> Whole Systems Design Services >>> People - Place - Learning - Integration >>> jo...@ec... <mailto:jo...@ec...> >>> http://eco-living.net >>> >>> -- >>> Mikko Ohtamaa >>> http://opensourcehacker.com >>> http://twitter.com/moo9000 >>> >>> >>> >>> >> -- >> John Schinnerer - M.A., Whole Systems Design >> ------------------------------**-------------- >> - Eco-Living - >> Whole Systems Design Services >> People - Place - Learning - Integration >> jo...@ec... >> http://eco-living.net >> >> -- >> Mikko Ohtamaa >> <http://eco-living.net>http://opensourcehacker.com >> http://twitter.com/moo9000 >> >> -- >> Mikko Ohtamaa >> <http://twitter.com/moo9000>http://opensourcehacker.com >> http://twitter.com/moo9000 >> >> >> >> |
|
From: Mikko O. <mik...@re...> - 2012-04-14 10:26:13
|
On Sat, Apr 14, 2012 at 04:11, John Schinnerer <jo...@ec...> wrote: > Thank you, simple enough, and...done. > Is that it? > After *Propose file change* I get a page re sending a pull request. Don't > grok it...do I need to do that? > Yes, that must be done also. I'll clarify that in nstructions. Cheers, Mikko -Mikko > > thanks, > John S. > > > On 04/13/2012 11:46 AM, Mikko Ohtamaa wrote: > >> >> >> On Fri, Apr 13, 2012 at 23:42, John Schinnerer <jo...@ec... >> <mailto:jo...@ec...>> wrote: >> >> I am totally new to github...the apparently relevant button says >> "Fork and Edit this file" - not sure if that is the correct thing to >> do? Please advise how to make the edit without making a mess... >> >> >> Should go like this >> >> 1. Go to Writing and updating the documentation >> <https://github.com/**collective/collective.** >> developermanual/edit/master/**source/introduction/writing.**rst<https://github.com/collective/collective.developermanual/edit/master/source/introduction/writing.rst> >> > >> on GitHub. >> 2. Press *Fork and edit this file* button >> 3. Edit file contents using GitHub's text editor in your web browser >> 4. Press *Propose file change* at the bottom of the page >> >> >> >> >> thanks, >> John S. >> >> >> On 04/12/2012 08:56 PM, Mikko Ohtamaa wrote: >> >> Hi John, >> >> Mention early on, with link, to see the Hosting Guide for >> information >> about production installations/deployments. >> >> >> Good spot. Can you go ahead and fix it directly here? >> >> https://github.com/collective/**__collective.developermanual/_** >> _blob/master/source/tutorials/**__installation.rst<https://github.com/collective/__collective.developermanual/__blob/master/source/tutorials/__installation.rst> >> >> <https://github.com/**collective/collective.** >> developermanual/blob/master/**source/tutorials/installation.**rst<https://github.com/collective/collective.developermanual/blob/master/source/tutorials/installation.rst> >> > >> >> -Mikko >> >> For example where it now says: >> >> ------------------------------**__---------- >> >> ... >> Installing Plone using Unified UNIX Installer >> >> Note >> This is the recommended installation method >> >> This recipe is good for >> Lightweight production sites >> Plone development and testing on Ubuntu / Debian >> ... >> ------------------------------**__------------ >> >> >> ...add some following text like: >> >> "For information on using this installation with production >> environments/deployments, see the [hosting guide]." >> >> There is a line that hints at that at the very end of the >> unified >> installer section, and I think it could be clearer and sooner. >> >> thanks, >> John S. >> >> On 04/10/2012 05:04 AM, Mikko Ohtamaa wrote: >> > Hi, >> > >> > I try to modernize / centralize existing Plone installation >> instructions. >> > >> > Please take a look on: >> > >> > >> http://collective-docs.__readt**hedocs.org/en/latest/__** >> tutorials/installation.html<http://readthedocs.org/en/latest/__tutorials/installation.html> >> >> <http://collective-docs.**readthedocs.org/en/latest/** >> tutorials/installation.html<http://collective-docs.readthedocs.org/en/latest/tutorials/installation.html> >> > >> > >> > ...and then take a stab on the document or me. >> > >> > Cheers, >> > Mikko >> > >> > ----- >> > >> > Follow me in Twitter >> > >> > >> > >> > Read my blog >> > >> > >> > >> > >> > >> > -- >> > View this message in context: >> http://plone.293351.n2.nabble.**__com/New-installation-__** >> instructions-__**tp7453156p7453156.html >> >> <http://plone.293351.n2.**nabble.com/New-installation-** >> instructions-**tp7453156p7453156.html<http://plone.293351.n2.nabble.com/New-installation-instructions-tp7453156p7453156.html> >> > >> > Sent from the Documentation Team mailing list archive at >> Nabble.com. >> > >> > >> >> ------------------------------**__----------------------------** >> --__------------------ >> >> > Better than sec? Nothing is better than sec when it comes to >> > monitoring Big Data applications. Try Boundary one-second >> > resolution app monitoring today. Free. >> > http://p.sf.net/sfu/Boundary-_**_dev2dev<http://p.sf.net/sfu/Boundary-__dev2dev> >> <http://p.sf.net/sfu/Boundary-**dev2dev<http://p.sf.net/sfu/Boundary-dev2dev> >> > >> > ______________________________**___________________ >> > Plone-docs mailing list >> > Plo...@li...urceforge._**_net >> <mailto:Plone-docs@lists.**sourceforge.net<Plo...@li...> >> > >> <mailto:Plone-docs@lists.__sou**rceforge.net<http://sourceforge.net> >> <mailto:Plone-docs@lists.**sourceforge.net<Plo...@li...> >> >> >> >> > https://lists.sourceforge.net/**__lists/listinfo/plone-docs<https://lists.sourceforge.net/__lists/listinfo/plone-docs> >> >> <https://lists.sourceforge.**net/lists/listinfo/plone-docs<https://lists.sourceforge.net/lists/listinfo/plone-docs> >> > >> >> -- >> John Schinnerer - M.A., Whole Systems Design >> ------------------------------**__-------------- >> >> - Eco-Living - >> Whole Systems Design Services >> People - Place - Learning - Integration >> jo...@ec... <mailto:jo...@ec...> >> <mailto:jo...@ec... <mailto:jo...@ec...>> >> >> http://eco-living.net >> >> >> ------------------------------**__----------------------------** >> --__------------------ >> >> For Developers, A Lot Can Happen In A Second. >> Boundary is the first to Know...and Tell You. >> Monitor Your Applications in Ultra-Fine Resolution. Try it >> FREE! >> http://p.sf.net/sfu/Boundary-_**_d2dvs2<http://p.sf.net/sfu/Boundary-__d2dvs2> >> <http://p.sf.net/sfu/Boundary-**d2dvs2<http://p.sf.net/sfu/Boundary-d2dvs2> >> > >> ______________________________**___________________ >> Plone-docs mailing list >> Plo...@li...urceforge._**_net >> <mailto:Plone-docs@lists.**sourceforge.net<Plo...@li...> >> > >> <mailto:Plone-docs@lists.__sou**rceforge.net<http://sourceforge.net> >> <mailto:Plone-docs@lists.**sourceforge.net<Plo...@li...> >> >> >> >> https://lists.sourceforge.net/**__lists/listinfo/plone-docs<https://lists.sourceforge.net/__lists/listinfo/plone-docs> >> >> <https://lists.sourceforge.**net/lists/listinfo/plone-docs<https://lists.sourceforge.net/lists/listinfo/plone-docs> >> > >> >> -- >> Mikko Ohtamaa >> http://opensourcehacker.com >> http://twitter.com/moo9000 >> >> >> >> >> -- >> John Schinnerer - M.A., Whole Systems Design >> ------------------------------**__-------------- >> >> - Eco-Living - >> Whole Systems Design Services >> People - Place - Learning - Integration >> jo...@ec... <mailto:jo...@ec...> >> http://eco-living.net >> >> -- >> Mikko Ohtamaa >> http://opensourcehacker.com >> http://twitter.com/moo9000 >> >> >> >> > -- > John Schinnerer - M.A., Whole Systems Design > ------------------------------**-------------- > - Eco-Living - > Whole Systems Design Services > People - Place - Learning - Integration > jo...@ec... > http://eco-living.net > > -- > Mikko Ohtamaa > <http://eco-living.net>http://opensourcehacker.com > http://twitter.com/moo9000 > > > > |
|
From: John S. <jo...@ec...> - 2012-04-14 01:11:50
|
Thank you, simple enough, and...done. Is that it? After *Propose file change* I get a page re sending a pull request. Don't grok it...do I need to do that? thanks, John S. On 04/13/2012 11:46 AM, Mikko Ohtamaa wrote: > > > On Fri, Apr 13, 2012 at 23:42, John Schinnerer <jo...@ec... > <mailto:jo...@ec...>> wrote: > > I am totally new to github...the apparently relevant button says > "Fork and Edit this file" - not sure if that is the correct thing to > do? Please advise how to make the edit without making a mess... > > > Should go like this > > 1. Go to Writing and updating the documentation > <https://github.com/collective/collective.developermanual/edit/master/source/introduction/writing.rst> > on GitHub. > 2. Press *Fork and edit this file* button > 3. Edit file contents using GitHub's text editor in your web browser > 4. Press *Propose file change* at the bottom of the page > > > > thanks, > John S. > > > On 04/12/2012 08:56 PM, Mikko Ohtamaa wrote: > > Hi John, > > Mention early on, with link, to see the Hosting Guide for > information > about production installations/deployments. > > > Good spot. Can you go ahead and fix it directly here? > > https://github.com/collective/__collective.developermanual/__blob/master/source/tutorials/__installation.rst > <https://github.com/collective/collective.developermanual/blob/master/source/tutorials/installation.rst> > > -Mikko > > For example where it now says: > > ------------------------------__---------- > ... > Installing Plone using Unified UNIX Installer > > Note > This is the recommended installation method > > This recipe is good for > Lightweight production sites > Plone development and testing on Ubuntu / Debian > ... > ------------------------------__------------ > > ...add some following text like: > > "For information on using this installation with production > environments/deployments, see the [hosting guide]." > > There is a line that hints at that at the very end of the > unified > installer section, and I think it could be clearer and sooner. > > thanks, > John S. > > On 04/10/2012 05:04 AM, Mikko Ohtamaa wrote: > > Hi, > > > > I try to modernize / centralize existing Plone installation > instructions. > > > > Please take a look on: > > > > > http://collective-docs.__readthedocs.org/en/latest/__tutorials/installation.html > <http://collective-docs.readthedocs.org/en/latest/tutorials/installation.html> > > > > ...and then take a stab on the document or me. > > > > Cheers, > > Mikko > > > > ----- > > > > Follow me in Twitter > > > > > > > > Read my blog > > > > > > > > > > > > -- > > View this message in context: > http://plone.293351.n2.nabble.__com/New-installation-__instructions-__tp7453156p7453156.html > <http://plone.293351.n2.nabble.com/New-installation-instructions-tp7453156p7453156.html> > > Sent from the Documentation Team mailing list archive at > Nabble.com. > > > > > > ------------------------------__------------------------------__------------------ > > Better than sec? Nothing is better than sec when it comes to > > monitoring Big Data applications. Try Boundary one-second > > resolution app monitoring today. Free. > > http://p.sf.net/sfu/Boundary-__dev2dev > <http://p.sf.net/sfu/Boundary-dev2dev> > > _________________________________________________ > > Plone-docs mailing list > > Plo...@li...urceforge.__net > <mailto:Plo...@li...> > <mailto:Plone-docs@lists.__sourceforge.net > <mailto:Plo...@li...>> > > > https://lists.sourceforge.net/__lists/listinfo/plone-docs > <https://lists.sourceforge.net/lists/listinfo/plone-docs> > > -- > John Schinnerer - M.A., Whole Systems Design > ------------------------------__-------------- > - Eco-Living - > Whole Systems Design Services > People - Place - Learning - Integration > jo...@ec... <mailto:jo...@ec...> > <mailto:jo...@ec... <mailto:jo...@ec...>> > > http://eco-living.net > > > ------------------------------__------------------------------__------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-__d2dvs2 > <http://p.sf.net/sfu/Boundary-d2dvs2> > _________________________________________________ > Plone-docs mailing list > Plo...@li...urceforge.__net > <mailto:Plo...@li...> > <mailto:Plone-docs@lists.__sourceforge.net > <mailto:Plo...@li...>> > > https://lists.sourceforge.net/__lists/listinfo/plone-docs > <https://lists.sourceforge.net/lists/listinfo/plone-docs> > > -- > Mikko Ohtamaa > http://opensourcehacker.com > http://twitter.com/moo9000 > > > > > -- > John Schinnerer - M.A., Whole Systems Design > ------------------------------__-------------- > - Eco-Living - > Whole Systems Design Services > People - Place - Learning - Integration > jo...@ec... <mailto:jo...@ec...> > http://eco-living.net > > -- > Mikko Ohtamaa > http://opensourcehacker.com > http://twitter.com/moo9000 > > > -- John Schinnerer - M.A., Whole Systems Design -------------------------------------------- - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration jo...@ec... http://eco-living.net |
173 messages has been excluded from this view by a project administrator.
