Bug: SoundService default is not a class

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Bug: SoundService default is not a class

David T. Lewis
On Wed, Jul 18, 2018 at 09:25:48PM -0500, Sean P. DeNigris wrote:

> Nicolas Cellier wrote
> > github is the key. It's the social thing.
>
> +1. Things like issue/commit linking, and the ability to discuss changes
> inline in the diff are powerful (and fun). For me the game changer was
> one-click forking???
>
> Old workflow: find an awesome - but abandoned - library. Have a small fix
> that makes it work again. But no access to mcz repo :/ Start a
> days?weeks?months?-long hunt for the maintainer. Ultimately realize that
> they have left the community and???
>
> New workflow: Click "Fork" and happily continue coding. Bonus points for
> clicking "New Pull Request" so the original project can merge if interested.
>

Thanks Sean, that is a very good explanation :-)

Dave


Reply | Threaded
Open this post in threaded view
|

Re: Bug: SoundService default is not a class

Ben Coman
In reply to this post by Sean P. DeNigris
On 19 July 2018 at 10:25, Sean P. DeNigris <[hidden email]> wrote:

> Nicolas Cellier wrote
>> github is the key. It's the social thing.
>
> +1. Things like issue/commit linking, and the ability to discuss changes
> inline in the diff are powerful (and fun). For me the game changer was
> one-click forking…
>
> Old workflow: find an awesome - but abandoned - library. Have a small fix
> that makes it work again. But no access to mcz repo :/ Start a
> days?weeks?months?-long hunt for the maintainer. Ultimately realize that
> they have left the community and…
>
> New workflow: Click "Fork" and happily continue coding. Bonus points for
> clicking "New Pull Request" so the original project can merge if interested.

And more importantly, you don't have to feel guilty about forking
since its the normal workflow to contribute to a project.
In old days it can be hard (I've heard) to track changes between forks.
So here is my favourite git/github view...
    https://github.com/OpenSmalltalk/opensmalltalk-vm/network
which tracks all changes in all forks.  That doesn't work so well
between git-providers, but maybe one day changes might be federated
between providers.

cheers -ben

12