Setools July 2006

setools@lists.squeakfoundation.org

10 participants
15 discussions

Gjallar (previously known as Q2) next steps!
by goran＠krampe.se 04 Aug '06

04 Aug '06

Hi! What I intend to try do this week is: 1. Set up a swiki with info at http://swiki.krampe.se/gjallar (unless someone has a better name FAST). The swiki is up already in fact, readonly - see development model below. 2. Prepare one or two documents we already have (need to scan them so that they do not contain any sensitive info). I added a short introduction that I cut out from a different doc, it is a bit rough around the edges but even though it is more of a "selling the dev env"-doc it does contain some other small bits. 3. Harass my project leader further to nail the license so that we can publish code. 4. Prepare a ready to download "dev env" so that people can join and get started without having to put all pieces together manually. 5. Prepare a dev "howto" describing some doits etc. When we get more momentum we can turn the Swiki into a nice website and get a logo - it is funny how important such things are. :) I am doing now 1-3 now, 4-5 is not interesting until I have nailed the license and can publish the code. Regarding the model for development I will probably want to run this project like this to begin with: - I am the project leader and will give developer access to developers. I will act a bit like Linus does by reviewing and integrating contributions into the "official" codebase. - Developers wishing to participate simply contact me and will be given write access to the MC repo and to the Swiki. Each developer should also describe himself with at least one sentence on the Gjallar Swiki so that we always have a list of the team. - There is nothing stopping any of the developers joining to start their own official "branches" in the Gjallar repo, but I would like to discuss that need first. - The Monticello repo will be open for developers to publish their versions into without review. So fixes or enhancements can simply be pushed there. Then I will either pick them up and integrate into the official codebase or we will move them into some contributions directory if integration for some reason is not good. - Initially we don't create yet-another-mailinglist, we can probably start by using this one. - Only code licensed under the MIT license will be let in, given that Gjallar uses that license. :) - As soon as possible I will set up a Gjallar system for issue tracking of Gjallar itself. Eating our own dog food. Please comment on the above. regards, Göran PS. Sorry for the lack of code - I really am trying to get it decided, but people are still away on vacation here etc.

5 21

Q2 got accepted as a Demonstration at OOPSLA
by goran＠krampe.se 01 Aug '06

01 Aug '06

Hi folks! Ok, got an email today saying my Demonstration of the Q2 issue tracker got accepted to OOPSLA! Fun! So if you are going to OOPSLA, see you there! And on another note - I have a few name proposals for the project: 1. Yeti - YET another Issue tracker (or YEt another Tracker for Issues). It is a short catchy name, there doesn't seem to be many other OSS projects having the name and ideas for a logo should be easy. :) 2. Seshat (or Sashet) - An Egyptian Goddess. The goddess of libraries and record keeping, it means "female scribe". So it is really fitting but the name itself is hard to say and not as catchy as Yeti. Well, I probably have a lot more ideas for a name, but currently I am leaning strongly towards Yeti. What do you say? A cool and catchy name is quite important, funny enough. regards, Göran PS. I am still on vacation, will start working next week. Then I will start to open up the project on a public site. Even though the customer has decided to go open source, the license is not yet set - so I have to get that decided first, but it should be quick (MIT most probably). PPS. If you guys have any questions about the system, feel free to post. Otherwise there will be much more info coming up next week (design documents etc)., and if I get the time - a downloadable demo.

5 8

Teamleader and Cooperator
by Hans N Beck 26 Jul '06

26 Jul '06

Hi, Marcus Denker has suggested to make an entry at http://www.squeak.org/ Community/Teams for our Software Engineering Team. Great ! For this, a team leader and a cooperator should be pointed out :-) If possible, I would like to make the team leader :-) But of course, if any other has better suggestions .... ;-) The entry I suggest would be: Name: Software Engineering Team Description: Developing software engineering tools in and for (but not only for) squeak Regards Hans

6 6

Source of Mondrian
by Alexandre Bergel 24 Jul '06

24 Jul '06

https://www.cs.tcd.ie/Alexandre.Bergel/Mondrian/ Perhaps I will give a try this week end, else Wednesday I will meet Adrian. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

5 25

EMOF Spec
by Hans N Beck 23 Jul '06

23 Jul '06

Hi, where can I find more infos to EMOF Spec ? It seems that it is not available on the page from OMG (only the MOF). Regards Hans

2 1

Using Mondrian with Moose
by HNBeck＠t-online.de 12 Jul '06

12 Jul '06

2 1

Rendering for Mondrian
by Hans N Beck 11 Jul '06

11 Jul '06

Hi, asking Bert Freudenberg for Balloon2D it comes out, that Balloon2D would be an interesting way to render the visualizations, because of Anti-Aliasing and a little bit more abstract interface for the rendering layer (roughly spoken Balloon2D would be nearer to VW HotDraw than plain Morphic) What would you guys think ? Regards Hans

2 1

Using Connectors for mondrian port ?
by Hans N Beck 11 Jul '06

11 Jul '06

Hi "Mondrians", should we use connectors for implementing the graphic part ? For drawing graphs it may be helpful :-) Regards Hans

1 0

Mondrian Version
by Hans N Beck 09 Jul '06

09 Jul '06

Hi, now I've loaded Bundle "1.0" from Store (and Bundle "Mondrian Development 1.2.194). Is that right ? Regards Hans

2 1

Fwd: CALL FOR 3.9 Final changes
by Alexandre Bergel 08 Jul '06

08 Jul '06

I did some fix and enhancement for OB. What do you think about them ? Should we include them in 3.9 ? Cheers, Alexandre Anfang der weitergeleiteten E-Mail: > Von: stéphane ducasse <ducasse(a)iam.unibe.ch> > Datum: July 6, 2006 8:44:49 AM GMT+01:00 > An: The general-purpose Squeak developers list <squeak- > dev(a)lists.squeakfoundation.org> > Betreff: CALL FOR 3.9 Final changes > Antwort an: The general-purpose Squeak developers list <squeak- > dev(a)lists.squeakfoundation.org> > > Hi all > > next week we will gather at my place and work on 3.9 final. > We would ****really**** appreciate that the other package maintainers > mention the new versions of packages for 3.9. > > This is the third time I asked and so far I got nearly no feedback > except > from the network and morphic packages maintainer. May be we should > fork for the other packages. > > If you have important bugs fixes that you want to see harvested > please reply to this email > and put link to the mantis entry. > > Stef > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 15

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Setools July 2006