You are right and I like this the most. Will change any repo I see ð Norbert
Am 08.07.2017 um 14:54 schrieb Gabriel Cotelli <g.cotelli@gmail.com>:
We're using source, because you know in Smalltalk we don't like to invent abbreviations ;)
On Jul 8, 2017 07:18, "Esteban Lorenzano" <estebanlm@gmail.com> wrote:
On 8 Jul 2017, at 09:29, Tim Mackinnon <tim@testit.works> wrote:
Hi Peter - I just hit this yesterday with your kind help deciphering SmalltalkCI, and I have to confess that "src" was my inclination over repository for the reason you mention in that it is a repository already.
I noticed other STCi projects have used "packages" .
I would vote for "src" so other newcomers more easily understand what it is compared to where they came from.
yes, I agree⦠even if at first is me the one who used mc, I think âsrcâis better convention, now (thatâs why pharo is using it :P)
Esteban
I also think it would be helpful for iceberg to default to using that so we get some consistency?
Tim
Sent from my iPhone
On 7 Jul 2017, at 17:03, Peter Uhnak <i.uhnak@gmail.com> wrote:
On Fri, Jul 07, 2017 at 04:53:20PM +0200, Denis Kudriashov wrote: Hi.
I though it was already done :) One notice. Should we all follow standard convention on repo structure? Because source directory in beacon is called "repository" instead "src" like in other repos.
There is no standard convention for Pharo repos on github.
In pharo-project I see
* repository 3x * mc 3x * src 1x (not smalltalk code)
And the rest of the github uses a variety of options
* nothing - imho disorganized and very messy if you have several packages * repository - I've been using it and recommending it for ~2 years; also used by filetree and metacello repos ;) - Argument could be made that git is already a repository so it could be confusing * mc - because MontiCello/MetaCello I guess? I don't know how much this makes sense in the light of Iceberg * src - quite common in other programming languages * packages - well, the folder does contain just packages
Someone could mine github to find precise numbers... but current usage shouldn't be a deciding factor.
Peter
2017-07-07 16:45 GMT+02:00 Norbert Hartl <norbert@hartl.name>:
I used the git migration tool of Peter Uhnak to migrate Beacon from smalltalkhub to github. It is available now here
https://github.com/pharo-project/pharo-beacon
I just need to know how I can switch a smalltalkhub project to read-only.
FYI,
Norbert