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 >> >> >> >> |