Hello everybody,
I just joined the squeak mailing list and created an account on Squeak Map although I know Squeak for almost two years. For various reasons I could not spend much time to try and write a lot of lines of Smalltalk, but know I have more time for myself, so I would like to get involved in the Squeak development process.
I'm an IT engineer, I have skills in other programming languages as Java, C++, Perl, Python, Ruby and also in Smalltalk although I am far from beeing an expert with that last one.
I read the "Community" part of Squeak web site, but I do not really know where to start.
So if you agree to accept my contribution, maybe someone could tell me what's next.
Best regards Greetings
Adrien Sebbane
ps: I'm french so excuse me if I look awkward in my expressions ! :)
Hi Adrien!
Adrien Sebbane adrien.sebbane@wanadoo.fr wrote:
Hello everybody,
I just joined the squeak mailing list and created an account on Squeak Map although I know Squeak for almost two years. For various reasons I could not spend much time to try and write a lot of lines of Smalltalk, but know I have more time for myself, so I would like to get involved in the Squeak development process.
I'm an IT engineer, I have skills in other programming languages as Java, C++, Perl, Python, Ruby and also in Smalltalk although I am far from beeing an expert with that last one.
I read the "Community" part of Squeak web site, but I do not really know where to start.
So if you agree to accept my contribution, maybe someone could tell me what's next.
It all depends on what you want to do. :) Squeak is a large community with tons of projects going on in parallell. This list (setools) was created specifically to support various efforts in "tools for software engineering". This can be new kinds of browsers - the OmniBrowser base is getting more and more traction, or any other kind of tool of course. :)
One project that happens to be housed on this list (we are thinking of possibly creating our own) is Gjallar - an advanced open source web based issue tracker. We have www.gjallar.se with more info about it.
If issue tracking sounds interesting, then join us on IRC on channel #gjallar - or just reply to this post. :) We gladly want more developers getting into the Gjallar code base.
Gjallar is still in development but getting closer and closer to a very interesting "state". We are using it for Gjallar itself already - but then we are not pushing its capabilities. Gjallar is not only for "bug tracking" - it is built for more diverse and advanced needs and is quite capable/promising in its design and technology.
Best regards Greetings
Adrien Sebbane
ps: I'm french so excuse me if I look awkward in my expressions ! :)
No problem!
regards, Göran
ps: I'm french so excuse me if I look awkward in my expressions ! :)
You're not the only one :-)
Alexandre
Hi Adrien,
welcome ! The mailing list you subscribed to is not the main one. You might want to subscribe to squeak-dev: http://lists.squeakfoundation.org/mailman/listinfo/squeak-dev. There is a french mailing list too: http://lists.squeakfoundation.org/mailman/listinfo/squeak-fr.
If you want a squeak image to start developing on, I advise you to use the squeak-dev image: http://damien.cassou.free.fr/squeak-dev/.
Bye
Hello All,
I was dissappointed when we decided to remove images from the main gjallar repository, so I have been seeking a solution.
For managing gjallar images with mercurial I have attempted to use mecurial queues but this was not really workable. Instead I have been successfully using nested repositories.
To set this up,
You clone the main repository as usual. so the gjallar/.hg directory is the repository.
Then in the dist directory where you are typically working you initialize a second repository.
hg init
then you
hg add Gjallar0.4.image hg add Gjallar0.4.changes hg commit
these are added and committed to the new inner gjallar/dist/.hg repository!
So when you want to make changes to the outer repository just cd .. , into the outer gjallar directory and make your changes adds/updates/commits/push/pulls from there
This scheme theoretically allows you to commit a snapshot of your image and also the database state if you add that as well. You can of course return to any previous snapshotted state, and I dont think it uses as much disk as having lots of images as per my usual practice. Its great!
Keith
setools@lists.squeakfoundation.org
-
Adrien Sebbane -
Bergel, Alexandre -
Damien Cassou -
goran＠krampe.se -
Keith Hodges