Re: Migrating XML support to github/PharoContributions/

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

Re: Migrating XML support to github/PharoContributions/

monty-3
I will move it to github, if that makes things easier for everyone else.

___
montyos.wordpress.com


> Sent: Wednesday, January 30, 2019 at 3:13 PM
> From: "Sven Van Caekenberghe" <[hidden email]>
> To: "Pharo Development List" <[hidden email]>
> Cc: monty <[hidden email]>
> Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
>
>
>
> > On 3 Oct 2018, at 07:43, monty <[hidden email]> wrote:
> >
> > I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them.
>
> Has there been any progress in this area ?
>
> It would be really great if this important project moved to GitHub.
>
> Sven
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

NorbertHartl
Yes, please. Do you know https://github.com/peteruhnak/git-migration ? That is a good way to preserve commit history in git. If you have trouble contact me please.

Norbert


Am 07.03.2019 um 11:19 schrieb monty <[hidden email]>:

I will move it to github, if that makes things easier for everyone else.

___
montyos.wordpress.com


Sent: Wednesday, January 30, 2019 at 3:13 PM
From: "Sven Van Caekenberghe" <[hidden email]>
To: "Pharo Development List" <[hidden email]>
Cc: monty <[hidden email]>
Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/



On 3 Oct 2018, at 07:43, monty <[hidden email]> wrote:

I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them.

Has there been any progress in this area ?

It would be really great if this important project moved to GitHub.

Sven




Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

Torsten Bergmann
In reply to this post by monty-3
Hi monty,

yes - it is easy with https://github.com/peteruhnak/git-migration

It would be good to make it available on the more general location: https://github.com/pharo-contributions 
If you tell us your github name we can add you as member.

Note that Peter seem to have converted already one of the projects the XMLParser is dependent on: "OrderPreservingDictionary"
which lives at: https://github.com/pharo-contributions/OrderPreservingDictionary
It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address).

I guess we should also convert "Pastell" which is also helpful for XML processing and has XMLParser as dependency.

I can also help converting - just contact me or Norbert on Discord.

Thanks
Torsten (a.k.a "astares" on Discord)


> Gesendet: Donnerstag, 07. März 2019 um 11:19 Uhr
> Von: "monty" <[hidden email]>
> An: [hidden email]
> Betreff: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
>
> I will move it to github, if that makes things easier for everyone else.
>
> ___
> montyos.wordpress.com
>
>
> > Sent: Wednesday, January 30, 2019 at 3:13 PM
> > From: "Sven Van Caekenberghe" <[hidden email]>
> > To: "Pharo Development List" <[hidden email]>
> > Cc: monty <[hidden email]>
> > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
> >
> >
> >
> > > On 3 Oct 2018, at 07:43, monty <[hidden email]> wrote:
> > >
> > > I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them.
> >
> > Has there been any progress in this area ?
> >
> > It would be really great if this important project moved to GitHub.
> >
> > Sven
> >
> >
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

ducasse
In reply to this post by monty-3
Thanks Monty
I had on my todo to port OrderedPreserving.
If you want I can do it because I wanted to integrate it in the collection of collections I’m slowly building.
So let me know.

Stef

> On 7 Mar 2019, at 11:19, monty <[hidden email]> wrote:
>
> I will move it to github, if that makes things easier for everyone else.
>
> ___
> montyos.wordpress.com
>
>
>> Sent: Wednesday, January 30, 2019 at 3:13 PM
>> From: "Sven Van Caekenberghe" <[hidden email]>
>> To: "Pharo Development List" <[hidden email]>
>> Cc: monty <[hidden email]>
>> Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
>>
>>
>>
>>> On 3 Oct 2018, at 07:43, monty <[hidden email]> wrote:
>>>
>>> I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them.
>>
>> Has there been any progress in this area ?
>>
>> It would be really great if this important project moved to GitHub.
>>
>> Sven
>>
>>
>



Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

ducasse
In reply to this post by Torsten Bergmann


> On 7 Mar 2019, at 19:59, Torsten Bergmann <[hidden email]> wrote:
>
> Hi monty,
>
> yes - it is easy with https://github.com/peteruhnak/git-migration
>
> It would be good to make it available on the more general location: https://github.com/pharo-contributions 
> If you tell us your github name we can add you as member.
>
> Note that Peter seem to have converted already one of the projects the XMLParser is dependent on: "OrderPreservingDictionary"
> which lives at: https://github.com/pharo-contributions/OrderPreservingDictionary
> It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address).

Ah cool I was about to do it.


>
> I guess we should also convert "Pastell" which is also helpful for XML processing and has XMLParser as dependency.
>
> I can also help converting - just contact me or Norbert on Discord.
>
> Thanks
> Torsten (a.k.a "astares" on Discord)
>
>
>> Gesendet: Donnerstag, 07. März 2019 um 11:19 Uhr
>> Von: "monty" <[hidden email]>
>> An: [hidden email]
>> Betreff: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
>>
>> I will move it to github, if that makes things easier for everyone else.
>>
>> ___
>> montyos.wordpress.com
>>
>>
>>> Sent: Wednesday, January 30, 2019 at 3:13 PM
>>> From: "Sven Van Caekenberghe" <[hidden email]>
>>> To: "Pharo Development List" <[hidden email]>
>>> Cc: monty <[hidden email]>
>>> Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
>>>
>>>
>>>
>>>> On 3 Oct 2018, at 07:43, monty <[hidden email]> wrote:
>>>>
>>>> I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them.
>>>
>>> Has there been any progress in this area ?
>>>
>>> It would be really great if this important project moved to GitHub.
>>>
>>> Sven
>>>
>>>
>>
>>
>



Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

Torsten Bergmann
Stef wrote:
> > Note that Peter seem to have converted already one of the projects the XMLParser is dependent on: "OrderPreservingDictionary"
> > which lives at: https://github.com/pharo-contributions/OrderPreservingDictionary
> > It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address).
>
> Ah cool I was about to do it.

From the history I guess Peter did it.

But we should redo it once we know Monty's github user account name to have him linked in the
history of commits and honour his authorship.

@Monty: can you tell us your github account user name/ github home?

Thx
T.

Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

Peter Uhnak
>  It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address).

That's not the case, maybe you are confused by the latest handful of commits that I made directly.
The rest is migrated with monty's mail; you can see "monty authored and peteruhnak committed", or look at the patch of any commit https://github.com/pharo-contributions/OrderPreservingDictionary/commit/e41451f014e15be52c14c832d082e1f73a576cb3.patch

Associating the mail with a github account should be enough.

Peter

On Thu, Mar 7, 2019 at 11:06 PM Torsten Bergmann <[hidden email]> wrote:
Stef wrote:
> > Note that Peter seem to have converted already one of the projects the XMLParser is dependent on: "OrderPreservingDictionary"
> > which lives at: https://github.com/pharo-contributions/OrderPreservingDictionary
> > It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address).
>
> Ah cool I was about to do it.

From the history I guess Peter did it.

But we should redo it once we know Monty's github user account name to have him linked in the
history of commits and honour his authorship.

@Monty: can you tell us your github account user name/ github home?

Thx
T.
Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

Pharo Smalltalk Developers mailing list

I thought xml support is already migrated by Sven?

https://github.com/svenvc/XML-Support-Pharo

Or do I mix something up here?

------------
Something else:

In case someone wants to use it: I used Peters nice migration tool for ...
http://smalltalkhub.com/#!/~PharoExtras/LDAP/
... and put it to:
https://github.com/a2b-alb/PharoExtras-LDAP

I don't know if this is the right place or if you would rather have it under ...
https://github.com/pharo-contributions/
... or somewhere else.

------------
I started trying to do the same migration process for ...
http://www.smalltalkhub.com/#!/~Pier/Pier3
... but I failed on errors loading older mcz files:

"instance of ByteString did not understand #peek"
on: MCMczReader >> contentsForMember:
(ZnInvalidUTF8: Illegal leading byte for utf-8 encoding)

Is this wrong encoding or corrupted files ?
How to treat these files ? -> Is just ignoring this majority of failing mcz files via migration ignoredFileNames: #()
ok ?

------------
As a workaround I then left the history versions behind and took only the newest mcz files. But I am not sure which package version "is in harnmony" with the other ones...  ;-)
-> While trying out which versions of the ConfigurationOfPier3 load in a p7 image only the #stable one loaded without problems. The newer ones didn't.

I did this by first loading as much pier3 dependencies (seaside, magritte, ...) from the new github repos. So I can then say ...
onConflict: [ :e | e useLoaded ];
... when loading pier3 from smaltalkhub.

Can someone who knows pier3 better than me, give me a hint on which package versions combinations are the ones to go with ?
-> Is to just start with the newest mcz files the way to go? Or should I use the #stable ConfigurationOfPier3 ?

best,
Albrecht

On 08.03.19 08:10, Peter Uhnak wrote:
>  It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address).

That's not the case, maybe you are confused by the latest handful of commits that I made directly.
The rest is migrated with monty's mail; you can see "monty authored and peteruhnak committed", or look at the patch of any commit https://github.com/pharo-contributions/OrderPreservingDictionary/commit/e41451f014e15be52c14c832d082e1f73a576cb3.patch

Associating the mail with a github account should be enough.

Peter

On Thu, Mar 7, 2019 at 11:06 PM Torsten Bergmann <[hidden email]> wrote:
Stef wrote:
> > Note that Peter seem to have converted already one of the projects the XMLParser is dependent on: "OrderPreservingDictionary"
> > which lives at: https://github.com/pharo-contributions/OrderPreservingDictionary
> > It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address).
>
> Ah cool I was about to do it.

From the history I guess Peter did it.

But we should redo it once we know Monty's github user account name to have him linked in the
history of commits and honour his authorship.

@Monty: can you tell us your github account user name/ github home?

Thx
T.
Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

Pharo Smalltalk Developers mailing list
In reply to this post by Peter Uhnak

I thought xml support is already migrated by Sven?

https://github.com/svenvc/XML-Support-Pharo

Or do I mix something up here?

-------------
Something else:

In case someone wants to use it: I used Peters nice migration tool for ...
http://smalltalkhub.com/#!/~PharoExtras/LDAP/
... and put it to:
https://github.com/a2b-alb/PharoExtras-LDAP

I don't know if this is the right place or if you would rather have it under ...
https://github.com/pharo-contributions/
... or somewhere else.

-------------
I started trying to do the same migration process for ...
http://www.smalltalkhub.com/#!/~Pier/Pier3
... but I failed on errors loading older mcz files:

"instance of ByteString did not understand #peek"
on: MCMczReader >> contentsForMember:
(ZnInvalidUTF8: Illegal leading byte for utf-8 encoding)

Is this wrong encoding or corrupted files ?
How to treat these files ? -> Is just ignoring this majority of failing mcz files via migration ignoredFileNames: #()
ok ?

-------------
As a workaround I then left the history versions behind and took only the newest mcz files. But I am not sure which package version "is in harnmony" with the other ones...  ;-)
-> While trying out which versions of the ConfigurationOfPier3 load in a p7 image only the #stable one loaded without problems. The newer ones didn't.

I did this by first loading as much pier3 dependencies (seaside, magritte, ...) from the new github repos. So I can then say ...
onConflict: [ :e | e useLoaded ];
... when loading pier3 from smaltalkhub.

Can someone who knows pier3 better than me, give me a hint on which package versions combinations are the ones to go with ?
-> Is to just start with the newest mcz files the way to go? Or should I use the #stable ConfigurationOfPier3 ?

best,
Albrecht

On 08.03.19 08:10, Peter Uhnak wrote:
>  It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address).

That's not the case, maybe you are confused by the latest handful of commits that I made directly.
The rest is migrated with monty's mail; you can see "monty authored and peteruhnak committed", or look at the patch of any commit https://github.com/pharo-contributions/OrderPreservingDictionary/commit/e41451f014e15be52c14c832d082e1f73a576cb3.patch

Associating the mail with a github account should be enough.

Peter

On Thu, Mar 7, 2019 at 11:06 PM Torsten Bergmann <[hidden email]> wrote:
Stef wrote:
> > Note that Peter seem to have converted already one of the projects the XMLParser is dependent on: "OrderPreservingDictionary"
> > which lives at: https://github.com/pharo-contributions/OrderPreservingDictionary
> > It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address).
>
> Ah cool I was about to do it.

From the history I guess Peter did it.

But we should redo it once we know Monty's github user account name to have him linked in the
history of commits and honour his authorship.

@Monty: can you tell us your github account user name/ github home?

Thx
T.
Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

ducasse


On 8 Mar 2019, at 11:08, Albrecht Baur <[hidden email]> wrote:


From: Albrecht Baur <[hidden email]>
Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
Date: 8 March 2019 at 11:08:44 CET


I thought xml support is already migrated by Sven?

https://github.com/svenvc/XML-Support-Pharo

Or do I mix something up here?

-------------
Something else:

In case someone wants to use it: I used Peters nice migration tool for ...
http://smalltalkhub.com/#!/~PharoExtras/LDAP/
... and put it to:
https://github.com/a2b-alb/PharoExtras-LDAP

I don't know if this is the right place or if you would rather have it under ...
https://github.com/pharo-contributions/
... or somewhere else.

Thanks 
and it would be good. 


-------------
I started trying to do the same migration process for ...
http://www.smalltalkhub.com/#!/~Pier/Pier3
... but I failed on errors loading older mcz files:

"instance of ByteString did not understand #peek"
on: MCMczReader >> contentsForMember:
(ZnInvalidUTF8: Illegal leading byte for utf-8 encoding)

Is this wrong encoding or corrupted files 

How to treat these files ? -> Is just ignoring this majority of failing mcz files via migration ignoredFileNames: #()
ok ?

I wonder if the MCMCZ was not about the delta between two commits but may be I’m wrong. 
BTW this is great to see someone pushing pier. 
I would like to see how a new version of pillar can be pushed back into pier. 


-------------
As a workaround I then left the history versions behind and took only the newest mcz files. But I am not sure which package version "is in harnmony" with the other ones...  ;-)
-> While trying out which versions of the ConfigurationOfPier3 load in a p7 image only the #stable one loaded without problems. The newer ones didn’t.


Seriously for Pier I would first focus on making it work with the latest version and we can always say that the historuy
is in another repo. 


I did this by first loading as much pier3 dependencies (seaside, magritte, ...) from the new github repos. So I can then say ...
onConflict: [ :e | e useLoaded ];
... when loading pier3 from smaltalkhub.

Can someone who knows pier3 better than me, give me a hint on which package versions combinations are the ones to go with ?
-> Is to just start with the newest mcz files the way to go? Or should I use the #stable ConfigurationOfPier3 ?

Use the configuration because I have no clue. 
Esteban was extending pier in the past. 




best,
Albrecht

On 08.03.19 08:10, Peter Uhnak wrote:
>  It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address).

That's not the case, maybe you are confused by the latest handful of commits that I made directly.
The rest is migrated with monty's mail; you can see "monty authored and peteruhnak committed", or look at the patch of any commit https://github.com/pharo-contributions/OrderPreservingDictionary/commit/e41451f014e15be52c14c832d082e1f73a576cb3.patch

Associating the mail with a github account should be enough.

Peter

On Thu, Mar 7, 2019 at 11:06 PM Torsten Bergmann <[hidden email]> wrote:
Stef wrote:
> > Note that Peter seem to have converted already one of the projects the XMLParser is dependent on: "OrderPreservingDictionary"
> > which lives at: https://github.com/pharo-contributions/OrderPreservingDictionary
> > It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address).
>
> Ah cool I was about to do it.

From the history I guess Peter did it.

But we should redo it once we know Monty's github user account name to have him linked in the
history of commits and honour his authorship.

@Monty: can you tell us your github account user name/ github home?

Thx
T.



Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

ducasse
I was in rush when I wrote the first answer

I thought xml support is already migrated by Sven?

https://github.com/svenvc/XML-Support-Pharo

Or do I mix something up here?


Sven did not migrate the history

-------------
Something else:

In case someone wants to use it: I used Peters nice migration tool for ...
http://smalltalkhub.com/#!/~PharoExtras/LDAP/
... and put it to:
https://github.com/a2b-alb/PharoExtras-LDAP

I don't know if this is the right place or if you would rather have it under ...
https://github.com/pharo-contributions/
... or somewhere else.

Thanks 
and it would be good. 

I do not know what is the best process to add something to pharo-contributions. 
May be we should fork your version and put it there and that people continue to contribute
using PRs. 
What do you think?

-------------
I started trying to do the same migration process for ...
http://www.smalltalkhub.com/#!/~Pier/Pier3
... but I failed on errors loading older mcz files:

"instance of ByteString did not understand #peek"
on: MCMczReader >> contentsForMember:
(ZnInvalidUTF8: Illegal leading byte for utf-8 encoding)

Is this wrong encoding or corrupted files 

How to treat these files ? -> Is just ignoring this majority of failing mcz files via migration ignoredFileNames: #()
ok ?

I wonder if the MCMCZ was not about the delta between two commits but may be I’m wrong. 
BTW this is great to see someone pushing pier. 
I would like to see how a new version of pillar can be pushed back into pier. 


-------------
As a workaround I then left the history versions behind and took only the newest mcz files. But I am not sure which package version "is in harnmony" with the other ones...  ;-)
-> While trying out which versions of the ConfigurationOfPier3 load in a p7 image only the #stable one loaded without problems. The newer ones didn’t.


Seriously for Pier I would first focus on making it work with the latest version and we can always say that the historuy
is in another repo. 


I did this by first loading as much pier3 dependencies (seaside, magritte, ...) from the new github repos. So I can then say ...
onConflict: [ :e | e useLoaded ];
... when loading pier3 from smaltalkhub.

Can someone who knows pier3 better than me, give me a hint on which package versions combinations are the ones to go with ?
-> Is to just start with the newest mcz files the way to go? Or should I use the #stable ConfigurationOfPier3 ?

Use the configuration because I have no clue. 
Esteban was extending pier in the past. 





Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

Pharo Smalltalk Developers mailing list
On 08.03.19 13:51, ducasse wrote:

In case someone wants to use it: I used Peters nice migration tool for ...
http://smalltalkhub.com/#!/~PharoExtras/LDAP/
... and put it to:
https://github.com/a2b-alb/PharoExtras-LDAP

I don't know if this is the right place or if you would rather have it under ...
https://github.com/pharo-contributions/
... or somewhere else.

Thanks 
and it would be good. 

I do not know what is the best process to add something to pharo-contributions. 
May be we should fork your version and put it there and that people continue to contribute
using PRs. 
What do you think?

We could fork my version as you described or we could do the migration again to have a clean push into an new repo e.g. github.com/pharo-contributions/LDAP

(I can do this if you want - I have still the snippets here... I just wanted to have LDAP on a save place because I need it and decided not to place it in my private gitlab instance...)

If someone (CyrilFerlicot I think?) creates github.com/pharo-contributions/LDAP or something and adds me (a2b-alb) I'll push it

Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

ducasse
Thanks. 
I sent you an invit. 

Stef

On 8 Mar 2019, at 14:22, Albrecht Baur <[hidden email]> wrote:


From: Albrecht Baur <[hidden email]>
Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
Date: 8 March 2019 at 14:22:43 CET


On 08.03.19 13:51, ducasse wrote:

In case someone wants to use it: I used Peters nice migration tool for ...
http://smalltalkhub.com/#!/~PharoExtras/LDAP/
... and put it to:
https://github.com/a2b-alb/PharoExtras-LDAP

I don't know if this is the right place or if you would rather have it under ...
https://github.com/pharo-contributions/
... or somewhere else.

Thanks 
and it would be good. 

I do not know what is the best process to add something to pharo-contributions. 
May be we should fork your version and put it there and that people continue to contribute
using PRs. 
What do you think?

We could fork my version as you described or we could do the migration again to have a clean push into an new repo e.g. github.com/pharo-contributions/LDAP

(I can do this if you want - I have still the snippets here... I just wanted to have LDAP on a save place because I need it and decided not to place it in my private gitlab instance...)

If someone (CyrilFerlicot I think?) creates github.com/pharo-contributions/LDAP or something and adds me (a2b-alb) I'll push it




Reply | Threaded
Open this post in threaded view
|

Re: Migrating XML support to github/PharoContributions/

Stephan Eggermont-3
In reply to this post by Pharo Smalltalk Developers mailing list
Albrecht Baur via Pharo-dev
<[hidden email]> wrote:

I started trying to do the same migration process for ...
http://www.smalltalkhub.com/#!/~Pier/Pier3
... but I failed on errors loading older mcz files:

"instance of ByteString did not understand #peek"
on: MCMczReader >> contentsForMember:
(ZnInvalidUTF8: Illegal leading byte for utf-8 encoding)

That needs a bugfix, old mczs might not be utf8. You can probably retry
with latin1 or macroman. Beware of issues like
https://lists.gforge.inria.fr/pipermail/pharo-project/2009-May/008990.html

You might find WideString there, different encodings, or a dropped leading
character, and code where the method contents are changed but the timestamp
didn’t and the other way around

Stephan