- Esug-list - lists.esug.org

Call for Participation Smalltalk Directions
by Stéphane Ducasse Dec. 5, 2011

Dec. 5, 2011

Hi guys I encourage you to send article to Smalltalk Directions Stef 19th–21st March 2012, Biloxi, Mississippi Smalltalk Directions is a refereed symposium that will be co-located with the Smalltalk Industry Conference (STIC) in March 2012. The Smalltalk Directions Symposium will run in parallel with STIC, offering a parallel track of presentations of refereed academic work that will be open to all attendees of STIC. We solicit research papers concerned with the future of the Smalltalk language, forward-looking applications of Smalltalk and Smalltalk-inspired languages, and the core technologies supporting such languages, including but not limited to: 1. Libraries & Frameworks 2. Language extensions and contractions 3. Implementation technologies, such as Virtual machines, compilers, instruction sets, garbage collection 4. Object persistence 5. Distributed objects 6. Program development tools and environments 7. Using Smalltalk to educate future object-oriented programmers 8. Design Patterns in and for Smalltalk 9. Modelling 10. Meta-programming 11. Domain-specific languages implemented in Smalltalk 12. Smalltalk on the web Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm; this site also contains links to useful information on how to write effective submissions. We are working to have accepted papers appear in the ACM Digital library. A special issue of the Journal of Object Technology will be published in conjunction with the symposium. The authors of selected papers will be invited to submit an extended version of their Smalltalk Directions submission to this special issue, which will then conduct its own reviewing precess. Papers must be submitted electronically using EasyChair (https://www.easychair.org/conferences/?conf=smalltalkdirections2) Important Dates Paper submission deadline 6th January 2012 Author notification 4th February 2012 Final version deadline 24th February 2012 Symposium 19th– 21st March 2012 Organizing Committee Andrew P Black Portland State University, USA black(a)cs.pdx.edu Ralph Johnson University of Illinois, Urbana-Champaign, USA rjohnson(a)illinois.edu Roger Whitney San Diego State University whitney(a)cs.sdsu.edu David West New Mexico Highlands University dmwest(a)nmhu.edu

1 0

Call for your input on questions you ask yourselves during merge
by Stéphane Ducasse Dec. 4, 2011

Dec. 4, 2011

Hi guys We are writing some articles on the work of veronica to support merging activities. We need your input great smalltalk community :) What are the questions that you ask yourselves when you are/want to merge some code in your project? We would like to do a compilation of questions and also evaluate how the solution of veronica solves them or part of them. Here are some typical questions we asked ourselves. - What other changes did this change require? - Can I integrate this change right now? - How large it is? - Who made it? - Is it still valid (when I'm working on an old change)? - Is this change impacted by a change that happened in another branch of my software? Stef D., Andy K. and Veronica U.

13 15

Re: [Esug-list] ESUG Video upload continuing...
by Marcus Denker Dec. 1, 2011

Dec. 1, 2011

On Nov 28, 2011, at 5:29 PM, Sean P. DeNigris wrote: > > Marcus Denker-4 wrote >> >> We are slowly, but steadily uploading videos to Youtube. >> > > Will someone add a link from the ESUG 2011 page (like the one for 2010). > The Playlists are: ESUG 2008: http://www.youtube.com/playlist?list=PL4A297B9019B3884D ESUG 2009: http://www.youtube.com/playlist?list=PL74E35D8EC7E756AE ESUG 2010: http://www.youtube.com/playlist?list=PL431285A978F581BB ESUG 2011: http://www.youtube.com/playlist?list=PL813665D04A2E4C0A I will add them to all the conference pages. -- Marcus Denker -- http://marcusdenker.de

2 1

ESUG Video upload continuing...
by Marcus Denker Nov. 28, 2011

Nov. 28, 2011

Hi, We are slowly, but steadily uploading videos to Youtube. http://www.youtube.com/user/esugboard There are now 50 videos already. The idea is to upload all videos we have from 2008, 2009, 2010 and 2011. In addition, the "Deep into Smalltalk" tutorials. If you want to be notified about single uploads, there are multiple possibilities: - subscribe to Youtube, turn on email notification. This way you get title, screnshot and the Abstract via mail of every video uploaded. - subscribe to http://twitter.com/#!/esugsmalltalk Youtube sends a tweet automatically for every upload. (Please retweet the ones you like!) Marcus -- Marcus Denker -- http://marcusdenker.de

3 2

fosdem smalltalk devroom
by Paolo Bonzini Nov. 28, 2011

Nov. 28, 2011

Hi all, is there a mailing list or website set up for discussing the program for the devroom? Thanks, Paolo

2 2

Re: [Esug-list] Antwort: Call for your input on questions you ask yourselves during merge
by Stéphane Ducasse Nov. 26, 2011

Nov. 26, 2011

tx :) On Nov 24, 2011, at 1:38 PM, Thorsten.Seitz(a)deutschebahn.com wrote: > - When the version to be merged into the trunk is on a branch which I > already did merge a couple of versions earlier I want to have to see/think > about only those changes that are new (i.e. the changes between the version > last merged and the current version to be merged and not all changes > between the current version to be merged and the trunk version to be merged > into) > > e.g. > > 1.0 -> 2.0 -> 3.0 -> 4.0 -> 5.0 -> 6.0 -> 7.0 Trunk > \ / / ?? questions asked here > \ / / > -> 2.1 -> 2.2 -> 2.3 -> 2.4 Branch > > The branch version 2.2 has already been merged into trunk version 5.0 some > time earlier. > Therefore I'd like to merge only the changes between 2.2 and 2.4 into 7.0. > I don't know what Pharo does but VisualWorksdisplays all changes between > 2.4 and 7.0 while giving additional information about the last common > version which is determined to be 2.0 because previous merges are not > considered. > This forces me to think about how to merge all changes up to version 2.2 > once again. > We fixed that in our tools, of course (in VW 7.6), offering an additional > merge option which only merges the changes since a user selected common > version. > > Regards > Thorsten > > > Thorsten Seitz > Development Center Architekturkonzeption und -entwicklung (T.SVD 32) > > DB Systel GmbH > Raum 5C.136, Alfred-Herrhausen-Allee 1, 65760 Eschborn > Tel. 069 265-48245, intern 955- > _________________________________________________________________________________ > > Der DB-Konzern im Internet >> http://www.deutschebahn.com > > Sitz der Gesellschaft: Frankfurt am Main > Registergericht: Frankfurt am Main, HRB 78707 > USt-IdNr.: DE252204770 > Geschäftsführer: Detlef Exner (Vorsitzender), Dr. Burkhard Klanke, Dr. > Klaus Rüffler > Vorsitzender des Aufsichtsrates: Dr. Rolf Kranüchel > > > |------------> > | Von: | > |------------> >> --------------------------------------------------------------------------------------------------------------------------------------------------| > |Stéphane Ducasse <stephane.ducasse(a)inria.fr> | >> --------------------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | An: | > |------------> >> --------------------------------------------------------------------------------------------------------------------------------------------------| > |ESUG Members <esug-list(a)lists.esug.org> | >> --------------------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | Datum: | > |------------> >> --------------------------------------------------------------------------------------------------------------------------------------------------| > |23.11.2011 16:58 | >> --------------------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | Betreff: | > |------------> >> --------------------------------------------------------------------------------------------------------------------------------------------------| > |[Esug-list] Call for your input on questions you ask yourselves during merge | >> --------------------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | Gesendet | > | von: | > |------------> >> --------------------------------------------------------------------------------------------------------------------------------------------------| > |esug-list-bounces(a)lists.esug.org | >> --------------------------------------------------------------------------------------------------------------------------------------------------| > > > > > > Hi guys > > We are writing some articles on the work of veronica to support merging > activities. We need your input great smalltalk community :) > What are the questions that you ask yourselves when you are/want to merge > some code in your project? > We would like to do a compilation of questions and also evaluate how the > solution of veronica solves them or part of them. > > Here are some typical questions we asked ourselves. > - What other changes did this change require? > - Can I integrate this change right now? > - How large it is? > - Who made it? > - Is it still valid (when I'm working on an old change)? > - Is this change impacted by a change that happened in another > branch of my software? > > Stef D., Andy K. and Veronica U. > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > > >

5 4

Fwd: [Pharo-project] INRIA Postdoc position: security in dynamic languages
by Mariano Martinez Peck Nov. 26, 2011

Nov. 26, 2011

---------- Forwarded message ---------- From: stephane ducasse <stephane.ducasse(a)free.fr> Date: Sat, Nov 26, 2011 at 4:55 AM Subject: [Pharo-project] INRIA Postdoc position: security in dynamic languages To: An open mailing list to discuss any topics related to an open-source Smalltalk <Pharo-project(a)lists.gforge.inria.fr> Postdoc Position • Duration: 3 years • Starting date: end 2011 • Where: RMOD team at INRIA Lille Nord Europe http://rmod.lille.inria.fr • Salary: 55 Keuros net (before taxes) Keywords: dynamic languages, security, information flow, Smalltalk, Javascript The position will take place in the context of the Systematic Resilience project. We will focus on the following main tasks: • Identification and understanding of security problems in Javascript and other dynamic languages • Study and analyze existing approaches towards securing Javascript (Caja, isolates...) • Comparison of different approaches to secure dynamic applications (Zope model, ZTK), Ruby • Study of Mirrors/Capabilities as a basis for security in Javascript • Proposition of an safe architecture for Resilience Please contact Stephane Ducasse (Stephane.Ducasse(a)inria.fr) for more information. http://rmod.lille.inria.fr/ http://stephane.ducasse.free.fr -- Mariano http://marianopeck.wordpress.com

1 0

18 months Postdoc position in Reengineering available
by Stéphane Ducasse Nov. 24, 2011

Nov. 24, 2011

> From: Stéphane Ducasse <stephane.ducasse(a)inria.fr> > Subject: 18 months Postdoc position in Reengineering available > Date: November 23, 2011 9:52:01 AM GMT+01:00 > To: ERCIM WG Software Evolution ERCIM WG Software Evolution Mailing List <evol(a)lists.inf.unisi.ch> > > http://rmod.lille.inria.fr/web/pier/blog/2011-05-22 > > Postdoc position in software engineering at University of Chile in cooperation with INRIA > > A post-doctoral research position is available with the Pleiad Lab (Universityof Chile) and the RMoD Group (INRIA Lille Nord Europe). The position is scheduled to start in January 2012, but earlier dates are possible. The phd should be defended no prior than 2010. > > The position is targeted for research on software maintenance and software visualization. Validation of research hypotheses will be carried out using the Pharo programming language. Experience with it, or any other Smalltalk dialect, is a plus (but not necessary). > > The postdoctoral researcher will be expected to develop independent research initiatives within the scope of the position, design and contribute to the research experiments conducted by Pleiad and RMoD. There is no teaching duty associated with this position. > > Both Pleiad and RMoD offer a creative, productive and multicultural staff and students, with many collaboration opportunities. Pleiad and RMoD have an extensive expertise and an advanced infrastructure related to software analysis, data mining, testing, meta-modeling and language semantics. > > The position is funded by INRIA for a period of 18 months. In order to foster the collaboration between France and Chili, the candidate will have to share his time between Lille, France and Santiago, Chile. > > The candidate must hold a PhD in computer science. > > Contact Persons: > > • Alexandre Bergel and Stéphane Ducasse > • http://pleiad.dcc.uchile.cl > • http://rmod.lille.inria.fr > • http://www.pharo-project.org > • http://www.moosetechnology.org

1 0

Re: [Esug-list] Call for your input on questions you ask yourselves during merge
by mkobetic＠cincom.com Nov. 23, 2011

Nov. 23, 2011

"Alan Knight"<knight(a)acm.org> wrote: > Which parts of this are real changes and which are just because somebody > felt it was important to reformat everything? :-) Reformatting is relatively easy, but it would be really nice if the tooling could identify (at least some) refactoring too. Best I've seen so far is barely identifying simple method renames, I'm fairly confident we could do better than that. On top of that most tools make it difficult to compare bits of code that don't reside in the exact same method. The fact of life is that code moves around as responsibilities get reallocated. A good merge tool should let me compare arbitrary bits of changes with ease. As it is the "art of merging" is primarily being able to pick out slightest differences by simply eyeballing chunks of code yourself. It seems that merge tools assume that the person merging is the one who wrote the change, that is often not the case. It's great that the obvious stuff can be merged automatically nowadays, but any non-trivial merge case requires actual understanding of the change.

2 1

Smalltalk job offer in Belgium
by Johan Brichau Nov. 22, 2011

Nov. 22, 2011

Dear Smalltalker, It appears that the ESUG mailinglist has removed the pdf attachment in my previous email. Therefore, I am resending this message. My apologies. We have an exciting open position, detailed in the following pdf: http://www.yesplan.be/docs/vacancy-software-engineer.pdf Please do not hesitate to send in your resume! However, mind that applicants will be required to work on-site in Gent (Belgium). Best regards! -- Johan Brichau Software architect Yesplan -- Event Planning Software johan(a)yesplan.be

1 0