[Pharo-users] How to contribute to Calypso when it relies on pharo-core editors?

Ben Coman btc at openinworld.com
Wed Jun 20 07:46:38 EDT 2018


On 20 June 2018 at 15:38, Guillermo Polito <guillermopolito at gmail.com>
wrote:

> Hi Tim,
>
> Yes, there you're experiencing the limits of our current process. We were
> studying the usage of git subtrees/submodules/subrepos but none of them
> seem a satisfying solution for what would give us a smooth contribution
> process.
>
> Now, we can enhance a bit the current status by adding calypso in the list
> of iceberg projects. I agree with this. Actually putting Pharo and Iceberg
> itself there is something we started to do slowly. There was this feeling
> that people would complain "agh but I only want to see my projects not the
> system ones". What I believe is that we are used to see and change all
> packages in the system, that's in our "blood" as pharoers. So seeing all
> loaded projects may confuse a bit newcomers but empower experts too...
>

Just random musing...
It must be common that projects depend on several repos, so perhaps Iceberg
could present repos in a two level tree.
The first level is a "project" of which "Pharo" would be one, with second
level holding Iceberg and Calypso.
This could be condensed by default so that adding extra default Pharo
system repos doesn't clutter much.
If this could somehow tie in with tracking the repos loaded by Baselines,
that would be super cool. i.e. Baseline=Project.

Then we don't use the existing subtree/submodule/subrepos, just baselines.
After all, those three standard options all started out as separate scripts
tacked onto git - its flexible like that.

cheers -ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/attachments/20180620/7492d20d/attachment.html>


More information about the Pharo-users mailing list