Ludus in the current amber > compilation issue

P.S. As you have only one hour and if the cloning exercise is not
successful please just post your change requests as issues

      https://github.com/philippeback/Ludus/issues

I assume the fixes are minor.

On 4/25/14, H. Hirzel <[hidden email]> wrote:
> On 4/25/14, Bernat Romagosa <[hidden email]> wrote:
>>>
>>> In which repo did you do the change?
>>>
>>> Oh I cloned the phil's repo locally and made the changes there.
>
> You have to fork Phil's repo first (through the github web site)
>
> This gives you
>        https://github.com/bromagosa/Ludus
>
> and then clone your fork.
>
>      git clone  https://github.com/bromagosa/Ludus
>
> Then you commit locally and then do
>
>    git push https://github.com/bromagosa/Ludus
>
> Then issue a pull request through the web interface:
> In your fork click on 'Pull Request' on the right hand side of the
> screen and check if it is fine and comment if necessary and send it
> off.
>

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

If the project would be the only one in the gh organization you could also decide on a main repository and add the other accounts as collaborators.

If you plan to have multiple repos an organization might be worth the extra effort.

Best,
Manfred

Am 25.04.2014 17:28 schrieb "Bernat Romagosa" <[hidden email]>:

Cool, I submitted the issue. Let's move forward to create the Ludus gh org and I'll start reviewing everything and writing the full documentation.

2014-04-25 17:02 GMT+02:00 H. Hirzel <[hidden email]>:

P.S. As you have only one hour and if the cloning exercise is not
successful please just post your change requests as issues

      https://github.com/philippeback/Ludus/issues

I assume the fixes are minor.

On 4/25/14, H. Hirzel <[hidden email]> wrote:
> On 4/25/14, Bernat Romagosa <[hidden email]> wrote:
>>>
>>> In which repo did you do the change?
>>>
>>> Oh I cloned the phil's repo locally and made the changes there.
>
> You have to fork Phil's repo first (through the github web site)
>
> This gives you
>        https://github.com/bromagosa/Ludus
>
> and then clone your fork.
>
>      git clone  https://github.com/bromagosa/Ludus
>
> Then you commit locally and then do
>
>    git push https://github.com/bromagosa/Ludus
>
> Then issue a pull request through the web interface:
> In your fork click on 'Pull Request' on the right hand side of the
> screen and check if it is fine and comment if necessary and send it
> off.
>

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
Bernat Romagosa.

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Bernat,

So far Philipe has not answered. So I'd say as you are the original
author and put in most of the effort -- Do what you like best. The
efforts in April was porting work to Amber 0.12.4

As Github is very flexible I'd say -- easy things first and go for the
suggestion of Manfred. A single repo (e.g. 'Ludus14' , 14 for 2014 or
something else) with collaborators.

Just copy the code of Philippe's repo. As for me, I am not interested
in the history. Amber can now be loaded independently of application
code with package managers. So a repo just needs to contain the
application code and some configuration and documentation file.

People interested in the history may have a look at your old repo.

To sum up  I consider a new start with a new repo to be a good move.

--Hannes

On 4/29/14, Bernat Romagosa <[hidden email]> wrote:
> Ok, so how do we proceed? Do I create a repo in my account? Do we merge
> what's in yours with my original one? Do we create a Ludus org?
>
> Cheers!
> Bernat.
>
>
> 2014-04-25 17:32 GMT+02:00 Manfred Kröhnert <[hidden email]>:
>
>> If the project would be the only one in the gh organization you could
>> also
>> decide on a main repository and add the other accounts as collaborators.
>>
>> If you plan to have multiple repos an organization might be worth the
>> extra effort.
>>
>> Best,
>> Manfred
>>  Am 25.04.2014 17:28 schrieb "Bernat Romagosa" <
>> [hidden email]>:
>>
>>  Cool, I submitted the issue. Let's move forward to create the Ludus gh
>>> org and I'll start reviewing everything and writing the full
>>> documentation.
>>>
>>>
>>> 2014-04-25 17:02 GMT+02:00 H. Hirzel <[hidden email]>:
>>>
>>>> P.S. As you have only one hour and if the cloning exercise is not
>>>> successful please just post your change requests as issues
>>>>
>>>>       https://github.com/philippeback/Ludus/issues
>>>>
>>>> I assume the fixes are minor.
>>>>
>>>> On 4/25/14, H. Hirzel <[hidden email]> wrote:
>>>> > On 4/25/14, Bernat Romagosa <[hidden email]> wrote:
>>>> >>>
>>>> >>> In which repo did you do the change?
>>>> >>>
>>>> >>> Oh I cloned the phil's repo locally and made the changes there.
>>>> >
>>>> > You have to fork Phil's repo first (through the github web site)
>>>> >
>>>> > This gives you
>>>> >        https://github.com/bromagosa/Ludus
>>>> >
>>>> > and then clone your fork.
>>>> >
>>>> >      git clone  https://github.com/bromagosa/Ludus
>>>> >
>>>> > Then you commit locally and then do
>>>> >
>>>> >    git push https://github.com/bromagosa/Ludus
>>>> >
>>>> > Then issue a pull request through the web interface:
>>>> > In your fork click on 'Pull Request' on the right hand side of the
>>>> > screen and check if it is fine and comment if necessary and send it
>>>> > off.
>>>> >
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "amber-lang" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [hidden email].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Bernat Romagosa.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups
>>> "amber-lang" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an
>>> email to [hidden email].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "amber-lang" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [hidden email].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Bernat Romagosa.
>
> --
> You received this message because you are subscribed to the Google Groups
> "amber-lang" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [hidden email].
> For more options, visit https://groups.google.com/d/optout.
>

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Ok, so I'll go for this solution and explain where the project comes from in the readme :)

2014-04-29 19:35 GMT+02:00 H. Hirzel <[hidden email]>:

Bernat,

So far Philipe has not answered. So I'd say as you are the original
author and put in most of the effort -- Do what you like best. The
efforts in April was porting work to Amber 0.12.4

As Github is very flexible I'd say -- easy things first and go for the
suggestion of Manfred. A single repo (e.g. 'Ludus14' , 14 for 2014 or
something else) with collaborators.

Just copy the code of Philippe's repo. As for me, I am not interested
in the history. Amber can now be loaded independently of application
code with package managers. So a repo just needs to contain the
application code and some configuration and documentation file.

People interested in the history may have a look at your old repo.

To sum up  I consider a new start with a new repo to be a good move.

--Hannes

On 4/29/14, Bernat Romagosa <[hidden email]> wrote:
> Ok, so how do we proceed? Do I create a repo in my account? Do we merge
> what's in yours with my original one? Do we create a Ludus org?
>
> Cheers!
> Bernat.
>
>
> 2014-04-25 17:32 GMT+02:00 Manfred Kröhnert <[hidden email]>:
>
>> If the project would be the only one in the gh organization you could
>> also
>> decide on a main repository and add the other accounts as collaborators.
>>
>> If you plan to have multiple repos an organization might be worth the
>> extra effort.
>>
>> Best,
>> Manfred
>>  Am 25.04.2014 17:28 schrieb "Bernat Romagosa" <
>> [hidden email]>:
>>
>>  Cool, I submitted the issue. Let's move forward to create the Ludus gh
>>> org and I'll start reviewing everything and writing the full
>>> documentation.
>>>
>>>
>>> 2014-04-25 17:02 GMT+02:00 H. Hirzel <[hidden email]>:
>>>
>>>> P.S. As you have only one hour and if the cloning exercise is not
>>>> successful please just post your change requests as issues
>>>>
>>>>       https://github.com/philippeback/Ludus/issues
>>>>
>>>> I assume the fixes are minor.
>>>>
>>>> On 4/25/14, H. Hirzel <[hidden email]> wrote:
>>>> > On 4/25/14, Bernat Romagosa <[hidden email]> wrote:
>>>> >>>
>>>> >>> In which repo did you do the change?
>>>> >>>
>>>> >>> Oh I cloned the phil's repo locally and made the changes there.
>>>> >
>>>> > You have to fork Phil's repo first (through the github web site)
>>>> >
>>>> > This gives you
>>>> >        https://github.com/bromagosa/Ludus
>>>> >
>>>> > and then clone your fork.
>>>> >
>>>> >      git clone  https://github.com/bromagosa/Ludus
>>>> >
>>>> > Then you commit locally and then do
>>>> >
>>>> >    git push https://github.com/bromagosa/Ludus
>>>> >
>>>> > Then issue a pull request through the web interface:
>>>> > In your fork click on 'Pull Request' on the right hand side of the
>>>> > screen and check if it is fine and comment if necessary and send it
>>>> > off.
>>>> >
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "amber-lang" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [hidden email].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Bernat Romagosa.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups
>>> "amber-lang" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an
>>> email to [hidden email].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "amber-lang" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [hidden email].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Bernat Romagosa.
>
> --
> You received this message because you are subscribed to the Google Groups
> "amber-lang" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [hidden email].
> For more options, visit https://groups.google.com/d/optout.
>

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
Bernat Romagosa.