A Git-based VM sources repositories for you

>
> Hi:
>
> On 14 Dec 2010, at 22:23, Igor Stasenko wrote:
>
>> http://gitorious.org/squeak-vm/blessed
> Nice, does any of the git gurus have an idea how I could use that to downstream updates to relevant plugins into the RoarVM repo?
>
> I have no idea whether it is possible in a tool supported way, since the directory structure has changed and we needed to patch at least some of the plugins for our purpose...
>
> But since it is now also in a git repo, perhaps there is some magic?
>
> Thanks
> Stefan
>
>
>
> --
> Stefan Marr
> Software Languages Lab
> Vrije Universiteit Brussel
> Pleinlaan 2 / B-1050 Brussels / Belgium
> http://soft.vub.ac.be/~smarr
> Phone: +32 2 629 2974
> Fax:   +32 2 629 3525
>

>
> Hello, community
>
> (preface) there was a discussion about using git for VM sources and
> recently in pharo team, we are also discussed that, and decided to go
> on.
> So i started to look for an options and found that Gitorious is best
> solution for us all.
> In contrast to github, it doesn't charging users when their repository
> grow beyond 300Mb in size.
> And its totally free for open-source projects.
>
> To be sure, that i understood thing well, i even sent mail to support
> to clarify some aspects of their policy and got following in answer:
>
> <<<<  quote start
>
> I can't even begin to tell you how happy I am about this! Smalltalk is
> the coolest thing I know about computers, and I love what you have
> done with Squeak, thanks!
>
> <... skip technical details ...>
>
> The short version: go ahead! I'm really pleased you want to use
> Gitorious and I hope you'll be satisfied!
>
> Cheers,
> - Marius
>
>>>>>>> quote end.
>
>
> So, after such warm welcome, the choice was obvious :)
> I made a mirrors of SVN repositories for Squeak VM and Cog VM
> on gitorious.org.
>
> i created a group named:  squeak-vm-developers
>      http://gitorious.org/+squeak-vm-developers
>
> this group owns two projects:
>     Squeak VM  (http://gitorious.org/squeak-vm)
>     and Cog VM (http://gitorious.org/cogvm)
>
> Any member(s) of group having an admin access to these projects , and
> commit rights to projects 'blessed' repositories:
>
> http://gitorious.org/cogvm/blessed
> http://gitorious.org/squeak-vm/blessed
>
> (yes, a single project could have multiple repositories, but for start
> we will use just one - a blessed ;)
>
> Now what any people from street can do:
>   - register @ gitorious.org
>   - go to /cogvm/blessed or /squeak-vm/blessed
>   - click magic 'clone repository' button
>   and from now you will have a fresh copy of 'official' repository,
> ready for hacking in your own corner,
> where you are the all powerful deity and can do anything you want
> without asking anyone.
>
> That's the main reason for migrating to git-based hosting:
>   - easy for getting in
>   - no additional administration costs
>   - people can easily exchange the results of their own experiments
> without putting an 'official' repository in danger.
>
> @(John, Elior, Ian&  other currently active SVN users) note: There is
> no pressure for migrating to git-based source code management.
>
> if you keep using SVN, no problem. I will take care with refreshing a
> blessed repo(s) with SVN commits.
>
> But if you want to migrate, ask me, and i will add you to
> 'squeak-vm-developers' group. Note that this group serves only for
> managing
> and official 'blessed' repos, and if you don't want participate, you
> can just live in own corner as anyone else can. This doesn't make much
> difference anyways :)
>
> I just wanna tell, that from now i will use own clone(s) of 'blessed'
> repos for experiments and of course i encouraging everyone,
> who wants to start hacking VM(s) to do the same.
>
>

>
> El 14/12/2010, a las 7:31p.m., Stefan Marr escribió:
>
>>
>> Hi:
>>
>> On 14 Dec 2010, at 22:23, Igor Stasenko wrote:
>>
>>> http://gitorious.org/squeak-vm/blessed
>> Nice, does any of the git gurus have an idea how I could use that to downstream updates to relevant plugins into the RoarVM repo?
>>
>> I have no idea whether it is possible in a tool supported way, since the directory structure has changed and we needed to patch at least some of the plugins for our purpose...
>>
>> But since it is now also in a git repo, perhaps there is some magic?
>>
>> Thanks
>> Stefan
>>
>>
>>
>> --
>> Stefan Marr
>> Software Languages Lab
>> Vrije Universiteit Brussel
>> Pleinlaan 2 / B-1050 Brussels / Belgium
>> http://soft.vub.ac.be/~smarr
>> Phone: +32 2 629 2974
>> Fax:   +32 2 629 3525
>>
>
>

> Cheers,
>  - Andreas
>
> On 12/14/2010 1:23 PM, Igor Stasenko wrote:
>>
>> Hello, community
>>
>> (preface) there was a discussion about using git for VM sources and
>> recently in pharo team, we are also discussed that, and decided to go
>> on.
>> So i started to look for an options and found that Gitorious is best
>> solution for us all.
>> In contrast to github, it doesn't charging users when their repository
>> grow beyond 300Mb in size.
>> And its totally free for open-source projects.
>>
>> To be sure, that i understood thing well, i even sent mail to support
>> to clarify some aspects of their policy and got following in answer:
>>
>> <<<<  quote start
>>
>> I can't even begin to tell you how happy I am about this! Smalltalk is
>> the coolest thing I know about computers, and I love what you have
>> done with Squeak, thanks!
>>
>> <... skip technical details ...>
>>
>> The short version: go ahead! I'm really pleased you want to use
>> Gitorious and I hope you'll be satisfied!
>>
>> Cheers,
>> - Marius
>>
>>>>>>>> quote end.
>>
>>
>> So, after such warm welcome, the choice was obvious :)
>> I made a mirrors of SVN repositories for Squeak VM and Cog VM
>> on gitorious.org.
>>
>> i created a group named:  squeak-vm-developers
>>     http://gitorious.org/+squeak-vm-developers
>>
>> this group owns two projects:
>>    Squeak VM  (http://gitorious.org/squeak-vm)
>>    and Cog VM (http://gitorious.org/cogvm)
>>
>> Any member(s) of group having an admin access to these projects , and
>> commit rights to projects 'blessed' repositories:
>>
>> http://gitorious.org/cogvm/blessed
>> http://gitorious.org/squeak-vm/blessed
>>
>> (yes, a single project could have multiple repositories, but for start
>> we will use just one - a blessed ;)
>>
>> Now what any people from street can do:
>>  - register @ gitorious.org
>>  - go to /cogvm/blessed or /squeak-vm/blessed
>>  - click magic 'clone repository' button
>>  and from now you will have a fresh copy of 'official' repository,
>> ready for hacking in your own corner,
>> where you are the all powerful deity and can do anything you want
>> without asking anyone.
>>
>> That's the main reason for migrating to git-based hosting:
>>  - easy for getting in
>>  - no additional administration costs
>>  - people can easily exchange the results of their own experiments
>> without putting an 'official' repository in danger.
>>
>> @(John, Elior, Ian&  other currently active SVN users) note: There is
>> no pressure for migrating to git-based source code management.
>>
>> if you keep using SVN, no problem. I will take care with refreshing a
>> blessed repo(s) with SVN commits.
>>
>> But if you want to migrate, ask me, and i will add you to
>> 'squeak-vm-developers' group. Note that this group serves only for
>> managing
>> and official 'blessed' repos, and if you don't want participate, you
>> can just live in own corner as anyone else can. This doesn't make much
>> difference anyways :)
>>
>> I just wanna tell, that from now i will use own clone(s) of 'blessed'
>> repos for experiments and of course i encouraging everyone,
>> who wants to start hacking VM(s) to do the same.
>>
>>
>

>
> On 14 December 2010 23:41, Andreas Raab <[hidden email]> wrote:
>>
>> I thought we had sort of agreed on using http://squeakvm.googlecode.com?
>>
>
> Oh. Seems like i missed that part.
>
>> Besides using git (which is a downside from my perspective; I'm much more in
>> favor of Mercurial) how does gitorious stack up compared to Google code?
>>
>
> I plan to use it mainly for storing a code there.
> What else we need? Issue tracker? Wiki? mailing list(s)? We got that already.

>
>
> On 14.12.2010, at 14:50, Igor Stasenko wrote:
>
>>
>> On 14 December 2010 23:41, Andreas Raab <[hidden email]> wrote:
>>>
>>> I thought we had sort of agreed on using http://squeakvm.googlecode.com?
>>>
>>
>> Oh. Seems like i missed that part.
>>
>>> Besides using git (which is a downside from my perspective; I'm much more in
>>> favor of Mercurial) how does gitorious stack up compared to Google code?
>>>
>>
>> I plan to use it mainly for storing a code there.
>> What else we need? Issue tracker? Wiki? mailing list(s)? We got that already.
>
> Download hosting, bug tracker that is linked into the SCM, wiki only to describe downloads and instructions ( a homepage (supposed to replace squeakvm.org).

>  
> Hello, community
>
> (preface) there was a discussion about using git for VM sources and
> recently in pharo team, we are also discussed that, and decided to go
> on.
> So i started to look for an options and found that Gitorious is best
> solution for us all.
> In contrast to github, it doesn't charging users when their repository
> grow beyond 300Mb in size.
> And its totally free for open-source projects.

>
> Hello, community
>
> (preface) there was a discussion about using git for VM sources and
> recently in pharo team, we are also discussed that, and decided to go
> on.
> So i started to look for an options and found that Gitorious is best
> solution for us all.
> In contrast to github, it doesn't charging users when their repository
> grow beyond 300Mb in size.
> And its totally free for open-source projects.
>
> To be sure, that i understood thing well, i even sent mail to support
> to clarify some aspects of their policy and got following in answer:
>
> <<<< quote start
>
> I can't even begin to tell you how happy I am about this! Smalltalk is
> the coolest thing I know about computers, and I love what you have
> done with Squeak, thanks!
>
> <... skip technical details ...>
>
> The short version: go ahead! I'm really pleased you want to use
> Gitorious and I hope you'll be satisfied!
>
> Cheers,
> - Marius
>
>>>>>>> quote end.
>
>
> So, after such warm welcome, the choice was obvious :)
> I made a mirrors of SVN repositories for Squeak VM and Cog VM
> on gitorious.org.
>
> i created a group named:  squeak-vm-developers
>    http://gitorious.org/+squeak-vm-developers
>
> this group owns two projects:
>   Squeak VM  (http://gitorious.org/squeak-vm)
>   and Cog VM (http://gitorious.org/cogvm)
>
> Any member(s) of group having an admin access to these projects , and
> commit rights to projects 'blessed' repositories:
>
> http://gitorious.org/cogvm/blessed
> http://gitorious.org/squeak-vm/blessed
>
> (yes, a single project could have multiple repositories, but for start
> we will use just one - a blessed ;)
>
> Now what any people from street can do:
> - register @ gitorious.org
> - go to /cogvm/blessed or /squeak-vm/blessed
> - click magic 'clone repository' button
> and from now you will have a fresh copy of 'official' repository,
> ready for hacking in your own corner,
> where you are the all powerful deity and can do anything you want
> without asking anyone.
>
> That's the main reason for migrating to git-based hosting:
> - easy for getting in
> - no additional administration costs
> - people can easily exchange the results of their own experiments
> without putting an 'official' repository in danger.
>
> @(John, Elior, Ian & other currently active SVN users) note: There is
> no pressure for migrating to git-based source code management.
>
> if you keep using SVN, no problem. I will take care with refreshing a
> blessed repo(s) with SVN commits.
>
> But if you want to migrate, ask me, and i will add you to
> 'squeak-vm-developers' group. Note that this group serves only for
> managing
> and official 'blessed' repos, and if you don't want participate, you
> can just live in own corner as anyone else can. This doesn't make much
> difference anyways :)
>
> I just wanna tell, that from now i will use own clone(s) of 'blessed'
> repos for experiments and of course i encouraging everyone,
> who wants to start hacking VM(s) to do the same.
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.

>>
>
> Igor,
>
> Thanks for your initiative, and I expect a lively discussion moving forward ;)
>
> To the community at large,
>
> We have a wonderful mix of people participating in Squeak/Etoys/Phoro/Cuis
> and other projects, some of whom have be participating for many years, as well
> as many newer contributors. Regardless of how the VM(s) are managed in the
> future, I would ask that everyone with an interest in this please be respectful
> of the people who created the original work for our benefit. In particular,
> Andreas, Ian, John, and Eliot have contributed major VM development that
> they have made available to us with open source licenses, and Dan Ingalls'
> original portable VM is a remarkable piece of work from which we all are
> benefiting every day.
>
> So the meta-comment is: Let's all be respectful of the wishes of the original
> authors of these works.

> For those doing VM platform work, I would ask also that you take the time
> to read the various README and documention files to be found in the platforms
> sources, as these often contain guidance as to how the code should be managed,
> how contributions can most effectively be made to the original authors, and
> of course how to build the VM for each respective platform.
>
> Thanks everybody!
>
> Dave
>

>
> On Tue, Dec 14, 2010 at 10:23:25PM +0100, Igor Stasenko wrote:
>>
>> Hello, community
>>
>> (preface) there was a discussion about using git for VM sources and
>> recently in pharo team, we are also discussed that, and decided to go
>> on.
>> So i started to look for an options and found that Gitorious is best
>> solution for us all.
>> In contrast to github, it doesn't charging users when their repository
>> grow beyond 300Mb in size.
>> And its totally free for open-source projects.
>
> Igor,
>
> Thanks for your initiative, and I expect a lively discussion moving forward ;)
>
> To the community at large,
>
> We have a wonderful mix of people participating in Squeak/Etoys/Phoro/Cuis
> and other projects, some of whom have be participating for many years, as well
> as many newer contributors. Regardless of how the VM(s) are managed in the
> future, I would ask that everyone with an interest in this please be respectful
> of the people who created the original work for our benefit. In particular,
> Andreas, Ian, John, and Eliot have contributed major VM development that
> they have made available to us with open source licenses, and Dan Ingalls'
> original portable VM is a remarkable piece of work from which we all are
> benefiting every day.
>
> So the meta-comment is: Let's all be respectful of the wishes of the original
> authors of these works.
>

> For those doing VM platform work, I would ask also that you take the time
> to read the various README and documention files to be found in the platforms
> sources, as these often contain guidance as to how the code should be managed,
> how contributions can most effectively be made to the original authors, and
> of course how to build the VM for each respective platform.
>
> Thanks everybody!
>
> Dave
>

>
> igor
>
> It would be good to have a structure so that people can have their own branches and do not pollute by accident the blessed one. What is the process then?
> I would like to have
>        - mariano experiments
>        - JB handle vm
>        - ...
> that can be checkedout and compiled but not polluting the normal VM.
>

>> It would be good to have a structure so that people can have their own branches and do not pollute by accident the blessed one. What is the process then?
>> I would like to have
>>        - mariano experiments
>>        - JB handle vm
>>        - ...
>> that can be checkedout and compiled but not polluting the normal VM.
>>
>
> Sure, that's possible without any extra effort.
> Any user can create own, private (in terms that only he can make
> modifications, but everyone can read the results) repository.
>
> The blessed repository obviously made for the branch people could use
> for compiling an 'official' VM, which is stable and
> bug free :) Only selected people will have a write access to it.
> You can, consider that 'blessed' one is the same as current SVN
> repository. But we extending the model with possibility that everyone
> outside can do own clone of it, and make own work publicly available.
> And of course portions of code can flow between private and 'blessed'
> branches after review.
>
>
>> Stef
>>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>

>
> On 15 December 2010 03:35, David T. Lewis <[hidden email]> wrote:
>>
>> On Tue, Dec 14, 2010 at 10:23:25PM +0100, Igor Stasenko wrote:
>>>
>>> Hello, community
>>>
>>> (preface) there was a discussion about using git for VM sources and
>>> recently in pharo team, we are also discussed that, and decided to go
>>> on.
>>> So i started to look for an options and found that Gitorious is best
>>> solution for us all.
>>> In contrast to github, it doesn't charging users when their repository
>>> grow beyond 300Mb in size.
>>> And its totally free for open-source projects.
>>
>> Igor,
>>
>> Thanks for your initiative, and I expect a lively discussion moving forward ;)
>>
>> To the community at large,
>>
>> We have a wonderful mix of people participating in Squeak/Etoys/Phoro/Cuis
>> and other projects, some of whom have be participating for many years, as well
>> as many newer contributors. Regardless of how the VM(s) are managed in the
>> future, I would ask that everyone with an interest in this please be respectful
>> of the people who created the original work for our benefit. In particular,
>> Andreas, Ian, John, and Eliot have contributed major VM development that
>> they have made available to us with open source licenses, and Dan Ingalls'
>> original portable VM is a remarkable piece of work from which we all are
>> benefiting every day.
>>
>> So the meta-comment is: Let's all be respectful of the wishes of the original
>> authors of these works.
>>
>
> I am always acting with best intents for all of us. If creating a
> separate code repository
> goes against somebody's wishes, please speak.
> I didn't want to cause any harm.
> My intent is to make VM development process more open and flexible.
>