On Sep 23, 2013, at 2:41 PM, kilon <[email protected]> wrote: > No no no I am not discouraged far from it, just not familiar with the > process. For example I had no clue that multiple slices were encouraged, > even ones that are WIP. That definetly changes everything. > > I would love to hear you workflow on this one, for example do you also > commit your own changes to smalltalkhub for backup ?
a slice is just a bunch of packages but this is important for us to know which packages work with which other ones. > Also whats the diffirence between a slice and a regular commit ? Why you > advise people not > to save the image with their changes (I assume its for testing the slice ) ? > > I would love to contribute to pharo , I really like this community cause has > been more than friendly to me and I love pharo of course since you seem to > have very similar goal to what I want to achieve with coding. I started a > project on visual live coding in python to find out that pharo was doing > already more than I was dreaming of and I left python to code for pharo . > Now my project is just to enhance pharo here and there, clean up morphic, > create a cool gui that will be easy to use, a nice help system (with > documentation of course) and an app/ library store similarly to the Apple > app store (but of course free). If some of those ideas can be integrated > inside pharo and the community wants them so much the better for me. I also > don't mind fixing the occasional bug (not my bugs, I never make bugs only > "weird" features :D ). > > Also if I can submit my slices , continue to work and resubmit any future > slices thats great for me. The problem was never waiting for a review and > integration :) I just did not want to be stopped from working because I was > waiting for a review. If I can submit multiple slices then no problemo. yes > > > EstebanLM wrote >> please, do not take it as a disincentive to collaborate, this should be >> quite the opposite :) >> >> I was trying to ask for some patience because when you join into a >> collaborative community, obviously the times spent on "the process" will >> be different than if you work alone. The gain is obvious, but we often >> lose from mind the price to pay (you do not control all the stages of the >> process). >> >> So, if you submit something, it will be some time to get the feedback >> (time to people to notice your change, to see it, etc.). Also, I was not >> talking about Marcus, Stef or me... since we are not the reviewers (that's >> also a responsibility of everybody in the community): we are just the >> integrators. >> >> So please, continue committing changes to the process... the review will >> come :) >> >> btw... one thing that I usually do when working: I commit slices even if >> they are not ready. Then I continue submitting slices until work is >> done... then I move the fix to "review needed". That way you can work in >> big changes and also be preparing a SLICE for the right moment. >> >> cheers, >> Esteban >> >> >> On Sep 23, 2013, at 11:19 AM, kilon < > >> [email protected] > >> > wrote: >> >>> EstebanLM wrote >>>> also, putting your code in "review needed" would help to reviewers to >>>> notice that you submitted something :) >>>> >>>> On Sep 23, 2013, at 11:07 AM, Esteban Lorenzano < >>> >>>> estebanlm@ >>> >>>> > wrote: >>>> >>>>> you submitted yesterday... a sunday... and we have a not so big >>>>> community, and all of us has a lot of tasks and things to do. >>>>> you should be a bit more patient :) >>>>> >>>>> Esteban >>>>> >>>>> On Sep 23, 2013, at 10:56 AM, kilon < >>> >>>> [email protected] >>> >>>> > wrote: >>>>> >>>>>> I take it from the silence , there is no interest in my code :D >>>>>> >>>>>> That's fine I will create my own HelpTopic class and keep it >>>>>> independent >>>>>> from pharo internal libs so I dont have to bother people with slices >>>>>> they >>>>>> don't deem important :) Makes my life easier too ;) >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://forum.world.st/Extending-HelpTopic-tp4709645p4709730.html >>>>>> Sent from the Pharo Smalltalk Developers mailing list archive at >>>>>> Nabble.com. >>>>>> >>>>> >>> >>> No problemo this is why I submitted this slice to see how the overall >>> process work and gain some experience so when the time comes to fix a >>> pharo >>> bug I can do it properly. >>> >>> yeah this is why I decided to keep code bases separate. I don't see a >>> need >>> for me to wait so long for a review to my code cause I will want to move >>> on >>> eventually. And plus I create more work for you and as you said there too >>> few of you and you already very busy. And I totally understand that and I >>> am >>> here to make your life easier and not harder ;) >>> >>> So its no problem I will continue the effort alone, and ping this list >>> back >>> when I have something substantial to show. >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://forum.world.st/Extending-HelpTopic-tp4709645p4709735.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> > > > > > > -- > View this message in context: > http://forum.world.st/Extending-HelpTopic-tp4709645p4709763.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >
