With regards to GitLab and Metacello. A couple of years ago, I looked
into adding GitLab support to Metacello, similar to `github:\\` for
downloading repository without requiring git to be installed and found
that there were issues[1] ... Now that was in 2014 and it's possible
that GitLab has fiddled with their zip download support, but I haven't
checked ...
`github://` is convenient but if you are moving to full git support and
expect everyone to be cloning projects into local repos (by hook or by
crook) not being able to download a zip version of the project is less
of a problem ...
Dale
[1]
https://github.com/dalehenrich/metacello-work/issues/287#issuecomment-59815235
On 6/27/16 7:05 PM, Ben Coman wrote:
On Tue, Jun 28, 2016 at 6:36 AM, Sean P. DeNigris <[email protected]> wrote:
stepharo wrote
maybe we need to consider deprecate the amber client
and use a full-pharo version.
Torsten what is the state of your solution?
Is it worth it to take another trip down this road of rolling-our-own source
code repo? Whatever we create, we accept the responsibility to maintain, and
with GitHub's social coding features, BitBucket for free private repo
hosting, and all the advances in Pharo-git integration, it seems our limited
resources would be most effectively committed elsewhere...
Jumping ahead to the end game of not needing to support development of
the repository backend ourselves,
there are a couple of levels to this...
1. Create a "SmalltalkHub" organisation on github and move *all*
repositories (maintaining privacy. Synchronize between the two servers
for a couple of years so as to not abandon old Pharo versions or break
existing Configurations, or build a thin forwarding service such that
requests received at smalltalkhub interact with github - perhaps this
is read only. Build a thin web SmalltalkHub home page with github
pages at smalltalkhub.io.
2. While GitHub gets most of the glory, its closed source and there
are some open source git options to consider like GitLab (MIT license)
or Gerrit (Apache license). This might be the path to choose if we
need some Smalltalk customizations like Smalltalk syntax highlighting.
The advantage of integrating with GitLab would be that the community
could use their hosted solution, but private companies could run their
own GitLab server if they have secrets they want to be more careful
about sharing with third parties.
3. We might run a GitLab/Gerrit server in place of the existing
Smalltalkhub server, and make it look the same for pre-git Pharo
clients. There would still be some administration cost, but a larger
community for support, features and bug fixing, or paid support
options.
* https://www.linux.com/learn/how-run-your-own-git-server
* https://about.gitlab.com/applications/
* https://www.gerritcodereview.com/
* https://gerrit-review.googlesource.com/Documentation/config-plugins.html
But these considerations shouldn't stop an intermediate solution.
cheers -ben
