Hi, On 13 Aug 2014, at 13:42, Tim Mackinnon <tim@testit.works> wrote:
> Thanks Esteban, that’s definitely (minor point: you didn’t use the same text > I gave you below, so there are some grammatical errors on the site). actually, I did not wrote anything (that was Stef :)… I just fixed the links :) the format for pharo site is pillar (same as pier). I will include your changes now. cheers, Esteban > > If you want to keep control of how things are published - maybe it makes > sense, and is much easier to set the rule: “Give me a complete page with > changes in XXXX format” (you tell me what XXX is - markdown?). And then we > can send you full pages you can paste in (and diff?) > > For now - can you also change the first paragraph, I think it makes more > sense to say that Pharo.org is the main place for information, and so its > much better to write: > > #How to propose a bug fix or enhancement > First check if your change has already been entered into > [Fogbugz](https://pharo.fogbugz.com/), and consider watching the [overview > video](https://www.youtube.com/watch?v=iFomI-7h4qQ) of the steps documented > below. > > Can you also change the Pre-reqs section to fix some minor typos (and match > the formatting of the text further down) > > ##Prerequisites > In order to propose a bug fix or enhancement for Pharo you need: > > - An account for the [Fogbugz Pharo Issue Tracker]( > https://pharo.fogbugz.com), > - An account on [SmalltalkHub](http://smalltalkhub.com) with commit rights to > the [Pharo Inbox]( http://smalltalkhub.com/#!/~Pharo/Pharo40Inbox). > _Note, in the recent version of SmalltalkHub this is a public repository. If > you encounter problems you can ask for commit rights on the [Pharo Developers > mailinglist(http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.org)._ >> > > Tim > > > > > On 12 Aug 2014, at 12:30, EstebanLM [via Smalltalk] <[hidden email]> wrote: > >> >> On 11 Aug 2014, at 18:28, Tim Mackinnon <<a >> href="x-msg://7/user/SendEmail.jtp?type=node&node=4772981&i=0" >> target="_top" rel="nofollow" link="external">[hidden email]> wrote: >> >>> Bump? The text on http://pharo.org/contribute-propose-fix is still wrong - >>> can someone include the text I fixed up below? >> >> fixed >> >> Esteban >> >>> >>> Also - do we want to make pharo.org the primary place for docs (and hence >>> change the first paragraph to: >>> >>> #How to propose a bug fix or enhancement >>> First check if your change has already been entered into Fogbugz, and >>> consider watching the [overview >>> video](https://www.youtube.com/watch?v=iFomI-7h4qQ) of the steps documented >>> below. >>> >>> If we want to move away from the Fogbugz wiki, I will also simplify some of >>> the text and point it back to pharo.org. >>> >>> Tim >>> >>> On 8 Aug 2014, at 08:40, Tim Mackinnon <<a >>> href="x-msg://7/user/SendEmail.jtp?type=node&node=4772981&i=1" >>> target="_top" rel="nofollow" link="external">[hidden email]> wrote: >>> >>>> Ok - I’ve fixed my faux-pas and propose the following text (a slight >>>> rework of what is published now). Taking a hint from Martin there is a >>>> notehub link here >>>> (http://notehub.org/2014/8/8/how-to-propose-a-bug-fix-or-enhancement) - >>>> although I’ve noticed notehub handles sub-bullets a bit strangely. We >>>> might also want to do another slight change if we agree that Fogbugz >>>> should be secondary content (if so - adjust the first paragraph to >>>> something like: Check if your change has already been entered into >>>> Fogbugz, and consider watching the overview video of the steps documented >>>> below.) >>>> >>>> —— >>> >>> >>>> #How to propose a bug fix or enhancement >>>> First check you meet the submission requirements and are familiar with the >>>> more detailed [contribution >>>> steps](https://pharo.fogbugz.com/default.asp?W68) (watch the [tutorial >>>> video](https://pharo.fogbugz.com/default.asp?pg=pgDownload&pgType=pgWikiAttachment&ixAttachment=3476&sFileName=PharoCreateIssue-small2.mp4), >>>> it's great!) >>>> >>>> ##Prerequisites >>>> In order to propose a bug fix or enhancement for Pharo you need: >>>> >>>> - An account for the [Fogbugz Pharo Issue Tracker]( >>>> https://pharo.fogbugz.com), >>>> - An account on [SmalltalkHub](http://smalltalkhub.com) with rights to the >>>> [Pharo Inbox]( http://smalltalkhub.com/#!/~Pharo/Pharo40Inbox). >>>> _Note, in the recent version of SmalltalkHub this is a public repository. >>>> If you encounter problems you can ask for commit rights on the [Pharo >>>> Developers >>>> mailinglist(http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.org)._ >>>> >>>> ##Procedure >>>> To commit a change, you will follow these steps: >>>> >>>> - Take the latest [stable or development >>>> system](http://pharo.org/download), ideally using the latest virtual >>>> machine for your OS >>>> - Ensure you have created [details of the issue in the Fogbugz issue >>>> tracker] (https://pharo.fogbugz.com) >>>> - Create a code fix (ideally with a [unit >>>> test](http://pharo.gforge.inria.fr/PBE1/PBE1ch8.html) exercising the >>>> working code) >>>> - Create a Monticello Slice (group of packages) for your changes: >>>> - Open the Monticello Browser >>>> - Open the Slice Maker by clicking the "Slice" button >>>> - In Slice Maker enter the Fogbugz issue number and "grab" the issue >>>> summary >>>> - Select all dirty packages affected by your fix >>>> - Verify your changes (click the Changes button) >>>> - Select the Pharo40 repository >>>> - Select your Slice >>>> - Press changes in the Monticello Browser and verify that your changes >>>> are correct >>>> - Publish the Slice to the inbox: >>>> - Select the whole Slice (not it's individual packages). >>>> - Select the SmalltalkHub Pharo Inbox repository. >>>> - Commit the Slice. >>>> - Verify that your fix loads: >>>> - Take a fresh image and load the Slice you just published >>>> - Update the bug entry to mention that you submitted a Slice in the inbox >>>> - Now sit back and feel good! You've helped influence a brighter future... >>>> >>>> You can also contribute to Pharo by proposing enhancements on the mailing >>>> list and/or by submitting a Fogbugz issue. Note that all code submitted to >>>> the [Pharo repositories](http://smalltalkhub.com/#!/~Pharo) is licensed >>>> under the [MIT license]http://opensource.org/licenses/MIT). Do not forget >>>> to sign the [license >>>> agreement](http://files.pharo.org/media/PharoSoftwareDistributionAgreement.pdf). >>>> >>>> >>>> On 8 Aug 2014, at 07:16, Tim Mackinnon <<a >>>> href="x-msg://7/user/SendEmail.jtp?type=node&node=4772981&i=2" >>>> target="_top" rel="nofollow" link="external">[hidden email]> wrote: >>>> >>>>> Stef - I've confused you with my suggestion. Where I wrote "use link" >>>>> after the text in [] - I meant put that hyperlink for the [text]. >>>>> >>>>> Sorry, I was writing my reply in a text editor and was doing a sort of >>>>> pseudo markdown syntax. >>>>> >>>>> Looking at where this is going - maybe we should instead make the >>>>> Pharo.org site the main source of info and not Fogbugz? We have a >>>>> duplication problem - and when things change we end up with conflicting >>>>> instructions as we forget to update the other copies. Essentially we need >>>>> to refactor the docs. >>>>> >>>>> Is Pharo.org easily editable by others (is this the Pillar bit?). If it >>>>> was then I would say let's edit the Fogbugz pages - simplify them and >>>>> point them back to the more detailed Pharo.org pages. >>>>> >>>>> For now, I will find a laptop and send some cleaned up text. >>>>> >>>>> Tim >>>>> >>>>> Sent from my iPhone >>>>> >>>>> On 7 Aug 2014, at 10:45 pm, "stepharo [via Smalltalk]" <<a href="<a >>>>> href="x-msg://28/user/SendEmail.jtp?type=node&amp;node=4772414&amp;i=0">x-msg://28/user/SendEmail.jtp?type=node&node=4772414&i=0" >>>>> target="_top" rel="nofollow" link="external">[hidden email]> wrote: >>>>> >>>>>> in fact I just did a merge with the version of Tim and it is looking >>>>>> great. >>>>>> On 7/8/14 22:32, stepharo wrote: >>>>>> >>>>>> > Thanks martin I will have a look tomorrow. >>>>>> > >>>>>> > Stef >>>>>> > >>>>>> > On 7/8/14 22:11, MartinW wrote: >>>>>> >> Could you extend http://pharo.org/contribute-propose-fix a bit? And >>>>>> >> add a >>>>>> >> screenshot of Slice Maker (I attach one). The following text would >>>>>> >> have >>>>>> >> helped me (I paste the markdown. I also posted it on NoteHub for a >>>>>> >> better >>>>>> >> reading experience >>>>>> >> http://www.notehub.org/2014/8/7/how-to-propose-a-bug-fix): >>>>>> >> >>>>>> >> #How to propose a bug fix: >>>>>> >> ##Prerequesites: >>>>>> >> In order to propose a bug fix or enhancement for Pharo you need: >>>>>> >> >>>>>> >> - an account at the [Pharo Issue Tracker on >>>>>> >> Fogbugz](https://pharo.fogbugz.com), >>>>>> >> - a [SmalltalkHub](http://smalltalkhub.com) account and >>>>>> >> - the commit right for the [Pharo Inbox on >>>>>> >> SmalltalkHub](http://smalltalkhub.com/#!/~Pharo/Pharo40Inbox) (Ask on >>>>>> >> the >>>>>> >> [Pharo Developers >>>>>> >> mailinglist](http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.org) >>>>>> >> >>>>>> >> >>>>>> >> for the commit right). >>>>>> >> >>>>>> >> ##Procedure: >>>>>> >> - Take the latest stable or latest development system, ideally using >>>>>> >> the >>>>>> >> latest virtual machine. >>>>>> >> - Do a fix for a given bug, or a new bug you entered to the issue >>>>>> >> tracker. >>>>>> >> - Create a slice (group of packages): >>>>>> >> - Open the Monticello Browser. >>>>>> >> - Open the Slice Maker by clicking the **+Slice** button. >>>>>> >> - In Slice Maker enter the Fogbugz issue number and **grab** the >>>>>> >> issue >>>>>> >> summary. >>>>>> >> - Select all dirty packages affected by your bug fix. >>>>>> >> - Publish the slice to the inbox: >>>>>> >> - Select the whole slice (not it's individual packages). >>>>>> >> - Select the SmalltalkHub Pharo Inbox repository. >>>>>> >> - Commit your slice. >>>>>> >> - Verify that your fix loads: take a fresh image and load the slice >>>>>> >> you >>>>>> >> published. >>>>>> >> - Update the bug entry to mention that you submitted a slice in the >>>>>> >> inbox. >>>>>> >> >>>>>> >> You can also contribute to Pharo by proposing enhancements following >>>>>> >> the >>>>>> >> same process. Note that all code submitted to the Pharo repositories >>>>>> >> is >>>>>> >> licensed under the MIT license. Do not forget to sign the license >>>>>> >> agreement. >>>>>> >> >>>>>> >> <http://forum.world.st/file/n4772388/SliceMaker.png> >>>>>> >> >>>>>> >> >>>>>> >> >>>>>> >> -- >>>>>> >> View this message in context: >>>>>> >> http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-right-there-tp4771765p4772388.html >>>>>> >> Sent from the Pharo Smalltalk Developers mailing list archive at >>>>>> >> Nabble.com. >>>>>> >> >>>>>> >> >>>>>> > >>>>>> > >>>>>> > >>>>>> >>>>>> If you reply to this email, your message will be added to the discussion >>>>>> below: >>>>>> http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-right-there-tp4771765p4772394.html >>>>>> To unsubscribe from About your contributions: Improve Pharo right now, >>>>>> right there., click here. >>>>>> NAML >>>>> >>>>> View this message in context: Re: About your contributions: Improve Pharo >>>>> right now, right there. >>>>> Sent from the Pharo Smalltalk Developers mailing list archive at >>>>> Nabble.com. >>>> >>> >> >> >> >> If you reply to this email, your message will be added to the discussion >> below: >> http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-right-there-tp4771765p4772981.html >> To unsubscribe from About your contributions: Improve Pharo right now, right >> there., click here. >> NAML > > > View this message in context: Re: About your contributions: Improve Pharo > right now, right there. > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
