A global Information System for Smalltalk, a system directed towards smalltalk projects and **people** (I mean smalltalkers whether dev or user) :). Ideally directed towards all smalltalk flavors (because more than the code, design discussions, algorithms are the most valuable information and this is just too sparse now) but that could be just Pharo/Squeak as a start, or even just Pharo to avoid too much hassle... I might not be really clear below but here's what I'd love as a central repository/system for smalltalkers (if Santa exists, he will understand me anyway ;o) ). This system will be before all oriented towards community, people, developpers so people can discuss design, see the profile of other smalltalkers, have an overall view on a project, its state, what people think about, etc etc... We need a better VISIBILITY on the existing (projects and people), and retrieval according to our taste... We need to characterize projets and above all people (that's the difficult point because this could led to offensive remarks. We should think a lot on how to objectively characterize developpers and then projects to stay polite and nice) Here are some examples of the kind of mechanisms I'd like in such a tool: (1) I like a lot Mr. R. developing style. Far more professional than what I can do, so I trust his project if I need to reuse. For some people, this might be too much engineered (any resemblance to persons living or programming in smalltalk is purely coincidental ). Anyway, I **trust** his projects and what he thinks on others. So I'd like to get the appropriate feedback (ie. what are the projects he cares about). (2) Mr C. has a similar profile as me, so I'm "automatically" interested in what he does and what he thinks (comments, discussion), etc... (3) Automatic discovery and notifications on "pieces of interest" -> project, dicussions, etc... (for instance, I'm not that interested right now in VM stuffs...) To me, it's just a discussion on how to characterize a project and a smalltalker (I don't say it's easy), then how to compare them (I can help there - on comparison on fuzzy entities). All the rest is UI and Tool stuffs. ***One simple subset and starting point would be to have a simple web page by smalltalkers*** Each user/developper will be automatically registered on that system (be the page be private by default) This page (url - maybe just the fragment) could be the unique identifier of the developer. No more initials, or combination of names, instead we have a classic login/password. Then it could be the entry point for a larger system... why not in squeaksource 2 ? Thanks Santa, I hope you get the idea :) YAD Cédrick (Yet Another Dreamer) ps: to finish some random thoughts: -Organised by projets -- project (code + comments by other + vote + blog) -- platforms (backup for legacy ones - ex: works for squeak 3.8, so we keep a **working** one click version somewhere) -- documentation (for a specific version) - again blog + interactive documentation (video associated to specific versions, **list of Deubug It methods in certain context***) -- code indicators (number of...) -- code (bleeding) + RC versions (+comments from others) (metacello ? only pharo... metametacello :) ) - dependancies... -- have a clear "time scale" of the project (when started, when released, still developped...) -Organized by people/group --profile/group description, interest, ... --automatic mailing list for groups --all projects done, even just started