GitHub and GLASS

Today I spent some time "moving" ConfigurationOfGsCore and ConfigurationOfGsMisc to github[1].

The plan is that when folks need to extend the Squeak package that they wil be able to fork the glass repository add their change, issue a pull request (which tests the changes agains GemStone2.4.x and GemStone3.x) that can be merged (by me or any other developer with commit rights to the glass repo) into the official repo with a button press in a web browser ...

So extension methods like the ones needed by Johan[2] can be added in the correct spot as part of the porting process instead of taking a separate path ...

The next step will be to address Johans extension methods and update the Zinc repository to depend upon the glass repository ... If things look good, I will continue converting the Gs* configurations in ConfigurationOfGLASS to be managed in the glss repo ...

Before taking the step I want to take a breath and give the folks that are using or plan on using Zinc to weigh in on my plans ...

Also, there are some Metacello Scripting "tricks" that you will need to use to make it easier to manage github-based projects. I will write posts over the next few days covering some of these "tricks" (depending upon how busy I get with the move of ss3 and gemsource:)...

I think that moving most if not all of the gemstone-specific projects to github will make us much more efficient and responsive since the tools on github are just so good ...

With all of that said, I know that it is in't easy to switch repositories, so I don't want to move too fast...

Dale

[1] https://github.com/glassdb/glass
[2] https://github.com/glassdb/zinc/issues/43

Dale, I truly welcome the speed. :-)

On Sun, Jun 23, 2013 at 8:03 PM, Dale K. Henrichs <[hidden email]> wrote:

Today I spent some time "moving" ConfigurationOfGsCore and ConfigurationOfGsMisc to github[1].

The plan is that when folks need to extend the Squeak package that they wil be able to fork the glass repository add their change, issue a pull request (which tests the changes agains GemStone2.4.x and GemStone3.x) that can be merged (by me or any other developer with commit rights to the glass repo) into the official repo with a button press in a web browser ...

So extension methods like the ones needed by Johan[2] can be added in the correct spot as part of the porting process instead of taking a separate path ...

The next step will be to address Johans extension methods and update the Zinc repository to depend upon the glass repository ... If things look good, I will continue converting the Gs* configurations in ConfigurationOfGLASS to be managed in the glss repo ...

Before taking the step I want to take a breath and give the folks that are using or plan on using Zinc to weigh in on my plans ...

Also, there are some Metacello Scripting "tricks" that you will need to use to make it easier to manage github-based projects. I will write posts over the next few days covering some of these "tricks" (depending upon how busy I get with the move of ss3 and gemsource:)...

I think that moving most if not all of the gemstone-specific projects to github will make us much more efficient and responsive since the tools on github are just so good ...

With all of that said, I know that it is in't easy to switch repositories, so I don't want to move too fast...

Dale

[1] https://github.com/glassdb/glass
[2] https://github.com/glassdb/zinc/issues/43

--

Think different and code well,

-Conrad

But in the meantime some GLASS projects did pick up the use of github, metacello and travis ci ;-)

Johan

On 21 Apr 2014, at 19:19, Dale Henrichs <[hidden email]> wrote:

> Haha,
>
> This has been one wacky year and a half:) I started work on GemStone3.2 roughly a year ago January (maybe even earlier) and just finished my last bits of work last week ... It looks like I'm finally out of the woods...
>
> In the end tho':
>
>   ...there are some Metacello Scripting "tricks" that you will need to use to
>   make it easier to manage github-based projects...
>
> has morphed into tODE support for managing github-based projects and tODE itself has morphed several times in the last 1.5 years ...
>
> The fundamentals of tODE have finally settled and are solid, but there is a bit more work to be done before it is ready ... a common refrain, I know, but I am only single-threaded:(
>
> Dale
>
>
> On Sun, Apr 20, 2014 at 11:31 PM, Conrad Taylor <[hidden email]> wrote:
> Dale, I truly welcome the speed. :-)
>
>
> On Sun, Jun 23, 2013 at 8:03 PM, Dale K. Henrichs <[hidden email]> wrote:
> Today I spent some time "moving" ConfigurationOfGsCore and ConfigurationOfGsMisc to github[1].
>
> The plan is that when folks need to extend the Squeak package that they wil be able to fork the glass repository add their change, issue a pull request (which tests the changes agains GemStone2.4.x and GemStone3.x) that can be merged (by me or any other developer with commit rights to the glass repo) into the official repo with a button press in a web browser ...
>
> So extension methods like the ones needed by Johan[2] can be added in the correct spot as part of the porting process instead of taking a separate path ...
>
> The next step will be to address Johans extension methods and update the Zinc repository to depend upon the glass repository ... If things look good, I will continue converting the Gs* configurations in ConfigurationOfGLASS to be managed in the glss repo ...
>
> Before taking the step I want to take a breath and give the folks that are using or plan on using Zinc to weigh in on my plans ...
>
> Also, there are some Metacello Scripting "tricks" that you will need to use to make it easier to manage github-based projects. I will write posts over the next few days covering some of these "tricks" (depending upon how busy I get with the move of ss3 and gemsource:)...
>
> I think that moving most if not all of the gemstone-specific projects to github will make us much more efficient and responsive since the tools on github are just so good ...
>
> With all of that said, I know that it is in't easy to switch repositories, so I don't want to move too fast...
>
> Dale
>
> [1] https://github.com/glassdb/glass
> [2] https://github.com/glassdb/zinc/issues/43
>
>
>
> --
>
> Think different and code well,
>
> -Conrad
>
>

Hey,

we just made a whole course use Monticello/Filetree + Metacello + Git/Github + TravisCI (with builderCI)

So you know, there are users of that, too :D

Best
        -Tobias

On 21.04.2014, at 20:46, Dale Henrichs <[hidden email]> wrote:

> ... gotta love those guys living on the bleeding edge:)
>
> Dale
>
>
> On Mon, Apr 21, 2014 at 10:26 AM, Johan Brichau <[hidden email]> wrote:
> But in the meantime some GLASS projects did pick up the use of github, metacello and travis ci ;-)
>
> Johan
>
> On 21 Apr 2014, at 19:19, Dale Henrichs <[hidden email]> wrote:
>
> > Haha,
> >
> > This has been one wacky year and a half:) I started work on GemStone3.2 roughly a year ago January (maybe even earlier) and just finished my last bits of work last week ... It looks like I'm finally out of the woods...
> >
> > In the end tho':
> >
> >   ...there are some Metacello Scripting "tricks" that you will need to use to
> >   make it easier to manage github-based projects...
> >
> > has morphed into tODE support for managing github-based projects and tODE itself has morphed several times in the last 1.5 years ...
> >
> > The fundamentals of tODE have finally settled and are solid, but there is a bit more work to be done before it is ready ... a common refrain, I know, but I am only single-threaded:(
> >
> > Dale
> >
> >
> > On Sun, Apr 20, 2014 at 11:31 PM, Conrad Taylor <[hidden email]> wrote:
> > Dale, I truly welcome the speed. :-)
> >
> >
> > On Sun, Jun 23, 2013 at 8:03 PM, Dale K. Henrichs <[hidden email]> wrote:
> > Today I spent some time "moving" ConfigurationOfGsCore and ConfigurationOfGsMisc to github[1].
> >
> > The plan is that when folks need to extend the Squeak package that they wil be able to fork the glass repository add their change, issue a pull request (which tests the changes agains GemStone2.4.x and GemStone3.x) that can be merged (by me or any other developer with commit rights to the glass repo) into the official repo with a button press in a web browser ...
> >
> > So extension methods like the ones needed by Johan[2] can be added in the correct spot as part of the porting process instead of taking a separate path ...
> >
> > The next step will be to address Johans extension methods and update the Zinc repository to depend upon the glass repository ... If things look good, I will continue converting the Gs* configurations in ConfigurationOfGLASS to be managed in the glss repo ...
> >
> > Before taking the step I want to take a breath and give the folks that are using or plan on using Zinc to weigh in on my plans ...
> >
> > Also, there are some Metacello Scripting "tricks" that you will need to use to make it easier to manage github-based projects. I will write posts over the next few days covering some of these "tricks" (depending upon how busy I get with the move of ss3 and gemsource:)...
> >
> > I think that moving most if not all of the gemstone-specific projects to github will make us much more efficient and responsive since the tools on github are just so good ...
> >
> > With all of that said, I know that it is in't easy to switch repositories, so I don't want to move too fast...
> >
> > Dale
> >
> > [1] https://github.com/glassdb/glass
> > [2] https://github.com/glassdb/zinc/issues/43
> >
> >
> >
> > --
> >
> > Think different and code well,
> >
> > -Conrad
> >
> >
>
>

On 21.04.2014, at 21:42, Dale Henrichs <[hidden email]> wrote:

> Haha, I hope there weren't too many (unintended) casualties..

We will see. Coursework starts tomorrow.
(I am actually just preparing a screencast on how to do a git/monticello merge
with filetree).

TBH I expect some screaming of all sort (we get that from time to times for
one or the other reason…), but I hope that will just help to eventually make
things better for all of us :)

Stay tuned.

On 21.04.2014, at 22:55, Dale Henrichs <[hidden email]> wrote:

> Very interested in feedback ... so encourage bug reports:)

Will do.
BTW: this was the first outcome:
        https://github.com/dalehenrich/builderCI/pull/59
And just some days ago, this the second:
        https://github.com/dalehenrich/filetree/pull/110


When problems should arise, we will probably first
tackle them at
        https://github.com/SWTI2014/builderCI
and
        https://github.com/SWTI2014/metacello-work
for the student’s convenience.
You might want to watch those. (Or not, I’m not a cop ;)

We promise pull-requests when feasible :D

Best
        -Tobias
>
>
> On Mon, Apr 21, 2014 at 1:15 PM, Tobias Pape <[hidden email]> wrote:
>
> On 21.04.2014, at 21:42, Dale Henrichs <[hidden email]> wrote:
>
> > Haha, I hope there weren't too many (unintended) casualties..
>
> We will see. Coursework starts tomorrow.
> (I am actually just preparing a screencast on how to do a git/monticello merge
> with filetree).
>
> TBH I expect some screaming of all sort (we get that from time to times for
> one or the other reason…), but I hope that will just help to eventually make
> things better for all of us :)
>
> Stay tuned.
>