I did a separate repository, let me know if you want to be added as contributor
We should not "hijack" such projects into "private" STHub users like Hernan's private URL. SmalltalkHub already has team functionality and the according teams are already setup. Grease belongs to Seaside since it was developed by the seaside team. Therefore it should be a "Seaside team" project also on STHub as before. There are already team projects for the Seaside team. See http://smalltalkhub.com/#!/~Seaside with already migrated code. So for Grease we/or the seaside team should use: http://smalltalkhub.com/#!/~Seaside/Grease We should align with the seaside team/developers, otherwise we would add more confusion regarding the code move and the configuration. Thanks T.
On Aug 31, 2013, at 4:29 PM, Torsten Bergmann <astares@gmx.de> wrote:
I did a separate repository, let me know if you want to be added as contributor
We should not "hijack" such projects into "private" STHub users like Hernan's private URL. SmalltalkHub already has team functionality and the according teams are already setup.
Grease belongs to Seaside since it was developed by the seaside team. Therefore it should be a "Seaside team" project also on STHub as before.
yes but it does not have to be under Seaside
There are already team projects for the Seaside team. See http://smalltalkhub.com/#!/~Seaside with already migrated code.
So for Grease we/or the seaside team should use:
Good that you created it :)
We should align with the seaside team/developers, otherwise we would add more confusion regarding the code move and the configuration.
Indeed
Thanks T.
El 31/08/2013 11:29, Torsten Bergmann escribió:
I did a separate repository, let me know if you want to be added as contributor
We should not "hijack" such projects into "private" STHub users like Hernan's private URL. SmalltalkHub already has team functionality and the according teams are already setup.
Ok, but please keep the code updated because I have to fix Grease to work in Pharo 2.0
Grease belongs to Seaside since it was developed by the seaside team. Therefore it should be a "Seaside team" project also on STHub as before.
There are already team projects for the Seaside team. See http://smalltalkhub.com/#!/~Seaside with already migrated code.
So for Grease we/or the seaside team should use:
http://smalltalkhub.com/#!/~Seaside/Grease
We should align with the seaside team/developers, otherwise we would add more confusion regarding the code move and the configuration.
That is like saying everyone have to be in the Seaside team to upload just a fix in Grease? Cheers, Hernán
Thanks T.
Am 31.08.2013 um 17:00 schrieb Hernán Morales Durand <hernan.morales@gmail.com>:
El 31/08/2013 11:29, Torsten Bergmann escribió:
I did a separate repository, let me know if you want to be added as contributor
We should not "hijack" such projects into "private" STHub users like Hernan's private URL. SmalltalkHub already has team functionality and the according teams are already setup.
Ok, but please keep the code updated because I have to fix Grease to work in Pharo 2.0
Grease belongs to Seaside since it was developed by the seaside team. Therefore it should be a "Seaside team" project also on STHub as before.
There are already team projects for the Seaside team. See http://smalltalkhub.com/#!/~Seaside with already migrated code.
So for Grease we/or the seaside team should use:
http://smalltalkhub.com/#!/~Seaside/Grease
We should align with the seaside team/developers, otherwise we would add more confusion regarding the code move and the configuration.
That is like saying everyone have to be in the Seaside team to upload just a fix in Grease?
Then make a grease team. Grease was invented for Seaside by the seaside team, doesn't that make the Seaside team the official maintainer? Then yes, everyone who wants his fix in the official Grease repo has to be on that team or ask someone there to merge/integrate/upload. Best -Tobias
El 31/08/2013 12:45, Tobias Pape escribió:
Am 31.08.2013 um 17:00 schrieb Hernán Morales Durand <hernan.morales@gmail.com>:
El 31/08/2013 11:29, Torsten Bergmann escribió:
I did a separate repository, let me know if you want to be added as contributor
We should not "hijack" such projects into "private" STHub users like Hernan's private URL. SmalltalkHub already has team functionality and the according teams are already setup.
Ok, but please keep the code updated because I have to fix Grease to work in Pharo 2.0
Grease belongs to Seaside since it was developed by the seaside team. Therefore it should be a "Seaside team" project also on STHub as before.
There are already team projects for the Seaside team. See http://smalltalkhub.com/#!/~Seaside with already migrated code.
So for Grease we/or the seaside team should use:
http://smalltalkhub.com/#!/~Seaside/Grease
We should align with the seaside team/developers, otherwise we would add more confusion regarding the code move and the configuration.
That is like saying everyone have to be in the Seaside team to upload just a fix in Grease?
Then make a grease team. Grease was invented for Seaside by the seaside team, doesn't that make the Seaside team the official maintainer? Then yes, everyone who wants his fix in the official Grease repo has to be on that team or ask someone there to merge/integrate/upload.
Ok, if someone make a Grease team I will be happy to be part of :) Cheers, Hernán
On 31 Aug 2013, at 17:45, Tobias Pape <Das.Linux@gmx.de> wrote:
That is like saying everyone have to be in the Seaside team to upload just a fix in Grease?
Then make a grease team. Grease was invented for Seaside by the seaside team, doesn't that make the Seaside team the official maintainer? Then yes, everyone who wants his fix in the official Grease repo has to be on that team or ask someone there to merge/integrate/upload.
Does it really matter if you need to be on the Seaside team for contributing to only a specific sub project? For example, Damien recently contributed fixes to the configurations and therefore I added him to the Seaside team. Easy. done. Apart from that, it makes sense to move Grease to its own project. I'm not an author of Grease, but I did the move of Seaside to Smalltalkhub and raised the issue about Grease not having its proper project on the Seaside-dev mailinglist while doing this back in July. If I remember correctly, there was no opposition to moving it to its separate space if this helped development. The reason it did not happen yet is that I previously thought we needed to merge the two Grease versions from the two Seaside repositories to a single one. But now I realise that we should only move the most recent one (the one from Seaside31). ESUG is coming up. If we did not do it by then, talk to us. Cheers Johan
On Sep 1, 2013, at 9:11 AM, Johan Brichau <johan@inceptive.be> wrote:
On 31 Aug 2013, at 17:45, Tobias Pape <Das.Linux@gmx.de> wrote:
That is like saying everyone have to be in the Seaside team to upload just a fix in Grease?
Then make a grease team. Grease was invented for Seaside by the seaside team, doesn't that make the Seaside team the official maintainer? Then yes, everyone who wants his fix in the official Grease repo has to be on that team or ask someone there to merge/integrate/upload.
Does it really matter if you need to be on the Seaside team for contributing to only a specific sub project?
not really. you could be a contributor of a project (not a team), and not part of the team... you could be part of Grease project without having anything to do with the rest of Seaside.
For example, Damien recently contributed fixes to the configurations and therefore I added him to the Seaside team.
Easy. done.
Apart from that, it makes sense to move Grease to its own project. I'm not an author of Grease, but I did the move of Seaside to Smalltalkhub and raised the issue about Grease not having its proper project on the Seaside-dev mailinglist while doing this back in July. If I remember correctly, there was no opposition to moving it to its separate space if this helped development. The reason it did not happen yet is that I previously thought we needed to merge the two Grease versions from the two Seaside repositories to a single one. But now I realise that we should only move the most recent one (the one from Seaside31).
ESUG is coming up. If we did not do it by then, talk to us.
Cheers Johan
Soon smalltalkhub project will have inbox. Right now this is annoying :) Nicolas is aware of that.
I did a separate repository, let me know if you want to be added as contributor
We should not "hijack" such projects into "private" STHub users like Hernan's private URL. SmalltalkHub already has team functionality and the according teams are already setup.
Ok, but please keep the code updated because I have to fix Grease to work in Pharo 2.0
I can understand. We wanted for long time a Grease version that does not dirty our moose packages.
Grease belongs to Seaside since it was developed by the seaside team. Therefore it should be a "Seaside team" project also on STHub as before.
There are already team projects for the Seaside team. See http://smalltalkhub.com/#!/~Seaside with already migrated code.
So for Grease we/or the seaside team should use:
http://smalltalkhub.com/#!/~Seaside/Grease
We should align with the seaside team/developers, otherwise we would add more confusion regarding the code move and the configuration.
That is like saying everyone have to be in the Seaside team to upload just a fix in Grease?
Cheers,
Hernán
Thanks T.
On 31 Aug 2013, at 23:00, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Ok, but please keep the code updated because I have to fix Grease to work in Pharo 2.0
I can understand. We wanted for long time a Grease version that does not dirty our moose packages.
Does that mean that: - if Moose does not load Grease, that Moose implements (a part of) Grease? - if Moose loads Grease, that Moose overwrites (a part of) Grease? In either case, does it not make sense to use Grease and contribute the changes there, rather than fork a specific version of Grease? Johan
I can understand. We wanted for long time a Grease version that does not dirty our moose packages.
Does that mean that: - if Moose does not load Grease, that Moose implements (a part of) Grease? no ;)
- if Moose loads Grease, that Moose overwrites (a part of) Grease? no :)
In either case, does it not make sense to use Grease and contribute the changes there, rather than fork a specific version of Grease?
Yes but for that there needs to have a place to publish changes And a maintained Configuration. In our case, the situation is much simpler. Pharo added trimBoth in String (because "THERE IS NO POINT TO KEEP COOL CODE OF CORE SYSTEM CLASSES IN EXTERNAL PACKAGES" - remember that this is the motto of Pharo - systematically get a better infrastructure) - I know that you know but other readers of this email may not be (yet) brainwashed :). So since the configuration (which is the tool to say for Pharo1.4 load version 123, for Pharo2.0 load version (without trimboth)â¦. was not updated we got redefinition in grease on String methods. With have the right tool to manage complexity we should just use them instead of a packages list and a gofer script. Stef
participants (6)
-
Esteban Lorenzano -
Hernán Morales Durand -
Johan Brichau -
Stéphane Ducasse -
Tobias Pape -
Torsten Bergmann