Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-14 Thread Dimitris Chloupis
The thing that annoy me the most with C2 is that almost each time I googled Smalltalk when I wasstill a beginner with Pharo and Smalltalk this came up often http://wiki.c2.com/?WhyIsSmalltalkDead But yes I agree, its nice to have a place to put information and never worry about it getting delete.

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-14 Thread Pierce Ng
On Mon, Feb 13, 2017 at 11:51:23PM +, Dimitris Chloupis wrote: > wiki. They end messy and very badly documented. Especially c2 is quite a > mess, probably the worst wiki I have ever seen. To me the lack of organization is in the nature of a wiki. It's like a place to be explored. Must be said

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-13 Thread Stephan Eggermont
On 13/02/17 16:39, Esteban A. Maringolo wrote: If haven't used the c2 wiki or the squeak wiki then you haven't experienced what it meant, at that time, to find everything there, or expand articles with your own content. It was really useful, c2 still is. The squeak wiki is also still very valua

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-13 Thread Dimitris Chloupis
> It's not a problem, it's a dynamics thing. GitHub isn't the same, I > haven't seen big wikis hosted there for a long time. In the long run > Pareto appears, and only a fraction of the users create most of the > content, but it is still useful. > > There is a very good reason for this. The rise o

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-13 Thread Alistair Grant
On 14 February 2017 at 02:39, Esteban A. Maringolo wrote: > ... > In my previous job we used Squeak's Swiki for years and then we > migrated it to Atlassian's Confluence (due to better user support), > and it is amazing how powerful and undervalued a wiki is. > > Wiki's value is like compound inte

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-13 Thread Esteban A. Maringolo
2017-02-10 21:09 GMT-03:00 Dimitris Chloupis : > On Sat, Feb 11, 2017 at 1:52 AM p...@highoctane.be > wrote: >> >> Am still finding useful stuff on Squeak wiki, sorry. >> The point of a Wiki is to capture discussions over a given topic and make >> it grow into something more structured over time.

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-10 Thread Dimitris Chloupis
I fail to see the problem here On Sat, Feb 11, 2017 at 1:52 AM p...@highoctane.be wrote: > Am still finding useful stuff on Squeak wiki, sorry. > The point of a Wiki is to capture discussions over a given topic and make > it grow into something more structured over time. Like original c2 wiki. >

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-10 Thread p...@highoctane.be
Am still finding useful stuff on Squeak wiki, sorry. The point of a Wiki is to capture discussions over a given topic and make it grow into something more structured over time. Like original c2 wiki. Phil On Fri, Feb 10, 2017 at 9:30 PM, Dimitris Chloupis wrote: > If you miss it so much we have

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-10 Thread Dimitris Chloupis
If you miss it so much we have something much better Github wikis, we never use Each of our books is hosted in a Github repo and each repo always comes with its own wiki using very simple markdown as everything else in Github You do not have content but only a snippet of code to offer ? No probl

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-10 Thread philippe.b...@highoctane.be
I miss the Squeak wiki Pharo style. Phil Le 10 févr. 2017 19:06, "Esteban A. Maringolo" a écrit : > 2017-02-10 14:59 GMT-03:00 p...@highoctane.be : > > Mass adoption and hyper reduced friction to get people on board. > > > > For me: I have 10+ slack teams in my slack client and there is really

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-10 Thread Esteban A. Maringolo
2017-02-10 14:59 GMT-03:00 p...@highoctane.be : > Mass adoption and hyper reduced friction to get people on board. > > For me: I have 10+ slack teams in my slack client and there is really no > point in having more clients on the desktop. +1 to this. This is key. Maybe what we're missing is a sim

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-10 Thread p...@highoctane.be
Mass adoption and hyper reduced friction to get people on board. For me: I have 10+ slack teams in my slack client and there is really no point in having more clients on the desktop. Phil On Fri, Feb 10, 2017 at 5:30 PM, Hilaire wrote: > Please excuse my ignorance but what are the advantages o

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-10 Thread Hilaire
Please excuse my ignorance but what are the advantages of Slack over other instant messaging system like IRC or Jabber? Hilaire Le 10/02/2017 à 10:27, Stephan Eggermont a écrit : > The past year we have started using Slack to communicate in real-time > about Pharo. It has nice (mobile) clients an

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-10 Thread Serge Stinckwich
On Fri, Feb 10, 2017 at 10:58 AM, Esteban Lorenzano wrote: > Hi Stephan, > >> On 10 Feb 2017, at 10:27, Stephan Eggermont wrote: >> >> The past year we have started using Slack to communicate in real-time about >> Pharo. It has nice (mobile) clients and makes it easy to share pictures and >> sn

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-10 Thread Esteban Lorenzano
Hi Stephan, > On 10 Feb 2017, at 10:27, Stephan Eggermont wrote: > > The past year we have started using Slack to communicate in real-time about > Pharo. It has nice (mobile) clients and makes it easy to share pictures and > snippets. As a result a large part of the communication about design

[Pharo-dev] Slack, fragmentation and design information

2017-02-10 Thread Stephan Eggermont
The past year we have started using Slack to communicate in real-time about Pharo. It has nice (mobile) clients and makes it easy to share pictures and snippets. As a result a large part of the communication about design and how to do things has moved from the mailing lists to Slack. As we're u