Smalltalk › Pharo › Pharo Smalltalk Developers

Slack, fragmentation and design information

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

29 messages Options

Stephan Eggermont-3

Slack, fragmentation and design information

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 using the free version, and cannot afford to use the
commercial version, we have no long-time storage of the design
discussions. This contrasts with our mailing lists, that have a
long-term archive. There was some discussion about this, and I'm not
aware of that resulting in an accessible, easy to access archive. Also,
we have not succeeded in summarizing design discussions from slack to
the mailing lists. The resulting gap in design information forms an
enormous long-term risk for our community. Without the design
discussions it is much more difficult to later understand why decisions
were taken. We cannot afford to let this short-term ease-of-use destroy
Pharo's community history, and thereby Pharo. Let us fix this.

Stephan

EstebanLM

Re: Slack, fragmentation and design information

Hi Stephan,

> On 10 Feb 2017, at 10:27, Stephan Eggermont <[hidden email]> 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 and how to do things has moved from the mailing lists to Slack. As we're using the free version, and cannot afford to use the commercial version, we have no long-time storage of the design discussions. This contrasts with our mailing lists, that have a long-term archive. There was some discussion about this, and I'm not aware of that resulting in an accessible, easy to access archive. Also, we have not succeeded in summarizing design discussions from slack to the mailing lists. The resulting gap in design information forms an enormous long-term risk for our community. Without the design discussions it is much more difficult to later understand why decisions were taken. We cannot afford to let this short-term ease-of-use destroy Pharo's community history, and thereby Pharo. Let us fix this.

I share many of what you say… but in the other point of view, Slack as really worked and there is a lot more happening now in Slack + mailing list than what was before just in mailing list.
But most of that is lost because of Slack policies (also Slack pricing model is impossible for a community as ours), and we need to find a solution for that.

Last days we were experimenting with @kilon again on use discord as a substitute and I find that for now it works really well and with a bit of work we can have all what you want: discord incorporated a search function (and they do not have the 10k limit) and we could do a bot that logs everything that happens there and stores that into gists (or whatever, but gists seems like a good idea).

With this we would have enhanced the availability of those discussions (it remains the fact that immediate communication is worst organised than mails, but well… we need to try)

Esteban

>
> Stephan
>
>

SergeStinckwich

Re: Slack, fragmentation and design information

On Fri, Feb 10, 2017 at 10:58 AM, Esteban Lorenzano <[hidden email]> wrote:
> Hi Stephan,
>
>> On 10 Feb 2017, at 10:27, Stephan Eggermont <[hidden email]> 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 and how to do things has moved from the mailing lists to Slack. As we're using the free version, and cannot afford to use the commercial version, we have no long-time storage of the design discussions. This contrasts with our mailing lists, that have a long-term archive. There was some discussion about this, and I'm not aware of that resulting in an accessible, easy to access archive. Also, we have not succeeded in summarizing design discussions from slack to the mailing lists. The resulting gap in design information forms an enormous long-term risk for our community. Without the design discussions it is much more difficult to later understand why decisions were taken. We cannot afford to let this short-term ease-of-use destroy Pharo's community history, and thereby Pharo. Let us fix this.

Yes I agree with your concerns.

> I share many of what you say… but in the other point of view, Slack as really worked and there is a lot more happening now in Slack + mailing list than what was before just in mailing list.
> But most of that is lost because of Slack policies (also Slack pricing model is impossible for a community as ours), and we need to find a solution for that.

Yes this is too expensive for the Pharo consortium ?

> Last days we were experimenting with @kilon again on use discord as a substitute and I find that for now it works really well and with a bit of work we can have all what you want: discord incorporated a search function (and they do not have the 10k limit) and we could do a bot that logs everything that happens there and stores that into gists (or whatever, but gists seems like a good idea).
>
> With this we would have enhanced the availability of those discussions (it remains the fact that immediate communication is worst organised than mails, but well… we need to try)

and move all the community on discord ? Or use an open-source slack
like : https://about.mattermost.com/
and host our own chat server.

--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

EstebanLM

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

> On 10 Feb 2017, at 11:28, Serge Stinckwich <[hidden email]> wrote:
>
> On Fri, Feb 10, 2017 at 10:58 AM, Esteban Lorenzano <[hidden email]> wrote:
>> Hi Stephan,
>>
>>> On 10 Feb 2017, at 10:27, Stephan Eggermont <[hidden email]> 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 and how to do things has moved from the mailing lists to Slack. As we're using the free version, and cannot afford to use the commercial version, we have no long-time storage of the design discussions. This contrasts with our mailing lists, that have a long-term archive. There was some discussion about this, and I'm not aware of that resulting in an accessible, easy to access archive. Also, we have not succeeded in summarizing design discussions from slack to the mailing lists. The resulting gap in design information forms an enormous long-term risk for our community. Without the design discussions it is much more difficult to later understand why decisions were taken. We cannot afford to let this short-term ease-of-use destroy Pharo's community history, and thereby Pharo. Let us fix this.
>
> Yes I agree with your concerns.
>
>> I share many of what you say… but in the other point of view, Slack as really worked and there is a lot more happening now in Slack + mailing list than what was before just in mailing list.
>> But most of that is lost because of Slack policies (also Slack pricing model is impossible for a community as ours), and we need to find a solution for that.
>
> Yes this is too expensive for the Pharo consortium ?

yes it is.
Is just not prepared for open source communities like ours.

>
>> Last days we were experimenting with @kilon again on use discord as a substitute and I find that for now it works really well and with a bit of work we can have all what you want: discord incorporated a search function (and they do not have the 10k limit) and we could do a bot that logs everything that happens there and stores that into gists (or whatever, but gists seems like a good idea).
>>
>> With this we would have enhanced the availability of those discussions (it remains the fact that immediate communication is worst organised than mails, but well… we need to try)
>
> and move all the community on discord ?

this is what I would like to propose, because...

> Or use an open-source slack

the problem with this is that we have to host it… and then is more problems for maintenance, etc.

Esteban

> like : https://about.mattermost.com/
> and host our own chat server.
>
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/
>

philippeback

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

I am frustated by this too and indeed we need a way to keep the messages.

I am about done with my wrapping of LibStrophe in Pharo with , which provides a XMPP/Jabber client to Pharo.

So, if someone can activate the XMPP gateway on our Slack instance, we will have a way to archive the contents (and possibly post a kind of digest into a mailing list).

https://get.slack.help/hc/en-us/articles/201727913-Connect-to-Slack-over-IRC-and-XMPP

Phil

On Fri, Feb 10, 2017 at 11:42 AM, Esteban Lorenzano <[hidden email]> wrote:

> On 10 Feb 2017, at 11:28, Serge Stinckwich <[hidden email]> wrote:
>
> On Fri, Feb 10, 2017 at 10:58 AM, Esteban Lorenzano <[hidden email]> wrote:
>> Hi Stephan,
>>
>>> On 10 Feb 2017, at 10:27, Stephan Eggermont <[hidden email]> 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 and how to do things has moved from the mailing lists to Slack. As we're using the free version, and cannot afford to use the commercial version, we have no long-time storage of the design discussions. This contrasts with our mailing lists, that have a long-term archive. There was some discussion about this, and I'm not aware of that resulting in an accessible, easy to access archive. Also, we have not succeeded in summarizing design discussions from slack to the mailing lists. The resulting gap in design information forms an enormous long-term risk for our community. Without the design discussions it is much more difficult to later understand why decisions were taken. We cannot afford to let this short-term ease-of-use destroy Pharo's community history, and thereby Pharo. Let us fix this.
>
> Yes I agree with your concerns.
>
>> I share many of what you say… but in the other point of view, Slack as really worked and there is a lot more happening now in Slack + mailing list than what was before just in mailing list.
>> But most of that is lost because of Slack policies (also Slack pricing model is impossible for a community as ours), and we need to find a solution for that.
>
> Yes this is too expensive for the Pharo consortium ?

yes it is.
Is just not prepared for open source communities like ours.

>
>> Last days we were experimenting with @kilon again on use discord as a substitute and I find that for now it works really well and with a bit of work we can have all what you want: discord incorporated a search function (and they do not have the 10k limit) and we could do a bot that logs everything that happens there and stores that into gists (or whatever, but gists seems like a good idea).
>>
>> With this we would have enhanced the availability of those discussions (it remains the fact that immediate communication is worst organised than mails, but well… we need to try)
>
> and move all the community on discord ?

this is what I would like to propose, because...

> Or use an open-source slack

the problem with this is that we have to host it… and then is more problems for maintenance, etc.

Esteban

> like : https://about.mattermost.com/
> and host our own chat server.
>
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/
>

kilon.alios

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

I have been pushing for Discord because

a) There is no need to host and maintain as Esteban said

b) There a ton of communities already using it and its by far the second most mature chat client after Slack

c) It has a very powerful Python API.... yes I know.... I know its no Pharo but still it makes it very easy to make bots that automate a lot of staff. I am using a bot that fetches RSS feeds (Although not sure how well this is working) connects to the reddit forum and of course fetches git commits

d) The team listens to its users

e) for personal reason.... all my favorite software (Blender, Unreal etc) is using it

I am also making my own bot . I could try to add a way for the bot to connect the mailing list with the Discord channel turn the mailing lists discussions to Discord discussions and vice versa but I have not done this before so no promises. I do have find a website that turns pretty much anything to webhooks which is what Discord uses (probably Slack too)

https://ifttt.com/discover

I could do the same with Slack , meaning to send Slack messages to Discord and Discord to Slack, I think I found one bot that already does this.

In short we can unite everything under one roof and let people keep using whatever people feel comfortable with (Slack, mailing lists, world.st forum, reddit , google hangouts , youtube , github and anything with webhooks or some form of web API)

Also the Bot could store its own log even in the unlikely scenario of a nuclear explosion in Discord servers we wont lose our valuable data. Though I think I saw somewhere that Discord allows to backup and export the data so that may be proven unnecessary.

On the other hand I will have to find a way to host my bot , but that is not a big deal , the bot is a simple python application and there are a ton of websites which offer hosting for python applications for free.

Its getting there but will need time.

Also my library Atlas can be used to access the APIs of all these chat software, Slack and Discord included, because Atlas allows you to use python libraries from inside Pharo. So its possible to have tools in the image for those of you that you love never having to leave the image that take advantage of these technologies. I wont be doing this though because a) porting APIs is a project by itself b) most of the code I find is python code and that makes it an easy copy paste approach (the vast majority of it is GPL or MIT licensed)

Marcus Denker-4

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

In reply to this post by SergeStinckwich

>
>> I share many of what you say… but in the other point of view, Slack as really worked and there is a lot more happening now in Slack + mailing list than what was before just in mailing list.
>> But most of that is lost because of Slack policies (also Slack pricing model is impossible for a community as ours), and we need to find a solution for that.
>
> Yes this is too expensive for the Pharo consortium ?
>
It is per active member… which is defined as “has logged in the last 14 days”. We have 322 members. No idea how many
are active according to that definition.

Fot 322 it would be: $8 per user per month. Which means $2576 per month or $25772 per year (taking the special yearly price into account).

Marcus

fstephany

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

There is a special price for non-profits organization:

> The Slack for Nonprofits program offers eligible organizations a free upgrade to our Standard plan for teams of up to 250 members. For eligible teams above that size, we offer an 85% discount on the Standard plan.

With 322 users it means that we still have to pay...

See https://get.slack.help/hc/en-us/articles/204368833-Slack-for-Nonprofits for more information.

On Fri, Feb 10, 2017 at 1:18 PM, denker <[hidden email]> wrote:

>
>> I share many of what you say… but in the other point of view, Slack as really worked and there is a lot more happening now in Slack + mailing list than what was before just in mailing list.
>> But most of that is lost because of Slack policies (also Slack pricing model is impossible for a community as ours), and we need to find a solution for that.
>
> Yes this is too expensive for the Pharo consortium ?
>
It is per active member… which is defined as “has logged in the last 14 days”. We have 322 members. No idea how many
are active according to that definition.

Fot 322 it would be: $8 per user per month. Which means $2576 per month or $25772 per year (taking the special yearly price into account).

Marcus

HilaireFernandes

Re: Slack, fragmentation and design information

In reply to this post by Stephan Eggermont-3

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 and makes it easy to share
> pictures and snippets. As a result a large part of the communication about

--
Dr. Geo
http://drgeo.eu

http://drgeo.eu

HilaireFernandes

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

In reply to this post by kilon.alios

I just saw Blender developers seems to use IRC (#blendercoders @
irc.freenode.net), 187 users. Ruby too at #ruby 917 users

Le 10/02/2017 à 12:29, Dimitris Chloupis a écrit :
> e) for personal reason.... all my favorite software (Blender, Unreal
> etc) is using it

--
Dr. Geo
http://drgeo.eu

http://drgeo.eu

philippeback

Re: Slack, fragmentation and design information

In reply to this post by HilaireFernandes

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 <[hidden email]> wrote:

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 and makes it easy to share
> pictures and snippets. As a result a large part of the communication about

--
Dr. Geo
http://drgeo.eu

Esteban A. Maringolo

Re: Slack, fragmentation and design information

2017-02-10 14:59 GMT-03:00 [hidden email] <[hidden email]>:
> 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 simple wiki to collect the shared
knowledge, recipes, and other stuff.

Esteban A. Maringolo

kilon.alios

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

In reply to this post by HilaireFernandes

Actually your numbers are pretty low

#blendercoders indeed has 187 , but those are the actual C coders working on the blender source (which I do not do), so its an equivalent of our phraro-dev, the equivalent of pharo-users is #blender with 360 members and the #blenderpython with 70 members which are people like me that work on blender addons using python (all these are online users of course)

BUT.... the blender community is enormous, its theorised since its impossible to know for sure that is around 1 million users, both professional and hobbists. As a result of this the community is highly fragmanted as all community of similar size are because they are impossible to be contained.

In Discord I am on 2 blender servers one has 175 online users and the other 75 online users. As such I have little reason anymore to use IRC and especially Slack (the only thing in Slack of interest to me is Pharo).

Also I am a game developer and Discord has become the default online chat tool for game developers and gamers aline the same way Slack has become the default online chat tool for developers.

Unreal server I am using on Discord has over 1200 users online , countless dedicate channels and a great deal of Unreal game developers use Blender so for me Discord by far the best choice for what I am doing.

Also a problem with IRC is that you see people that are online but they never say a word so they are online but always AFK. In Discord if you are afk there is a yellow icon to indicate that , from what I am seeing people participating in Discord tend to be far more active than people participating in IRC.

On Fri, Feb 10, 2017 at 6:46 PM Hilaire <[hidden email]> wrote:

I just saw Blender developers seems to use IRC (#blendercoders @
irc.freenode.net), 187 users. Ruby too at #ruby 917 users

Le 10/02/2017 à 12:29, Dimitris Chloupis a écrit :
> e) for personal reason.... all my favorite software (Blender, Unreal
> etc) is using it

--
Dr. Geo
http://drgeo.eu

philippe.back@highoctane.be

Re: Slack, fragmentation and design information

In reply to this post by Esteban A. Maringolo

I miss the Squeak wiki Pharo style.

Phil

Le 10 févr. 2017 19:06, "Esteban A. Maringolo" <[hidden email]> a écrit :

2017-02-10 14:59 GMT-03:00 [hidden email] <[hidden email]>:
> 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 simple wiki to collect the shared
knowledge, recipes, and other stuff.

Esteban A. Maringolo

kilon.alios

Re: Slack, fragmentation and design information

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 problem we have you covered there too create a gist for it , link it in the wiki and we will add it back to book. Gists even offer their own version control which means you can keep working and improving your code snippet for years to come without braking the workflow.

Then its a question of copy pasting the contents to pillar and adding them in our books , or if you do not mind the extra work write it in pillar directly and add it to the relevant book

All books can be added to CI and generate automagically html pages for direct access , we do this already with PBE 5.

Our Pharo "wiki" is easier to use and far more powerful than anything Squeak ever had, no offence intended of course to the original creators and maintainers of Squeak wiki.

Also github offers hosting of static webpages we could have a website hosted as github repo made with pillar that link to all wikis, gists and book artifacts. I can create this in an hour of work its not big deal. I would have done this myself but Stef already has added the books to Pharo.org which I find is more or less the same thing.

On Fri, Feb 10, 2017 at 10:15 PM [hidden email] <[hidden email]> wrote:

I miss the Squeak wiki Pharo style.

Phil

Le 10 févr. 2017 19:06, "Esteban A. Maringolo" <[hidden email]> a écrit :
2017-02-10 14:59 GMT-03:00 [hidden email] <[hidden email]>:
> 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 simple wiki to collect the shared
knowledge, recipes, and other stuff.

Esteban A. Maringolo

philippeback

Re: Slack, fragmentation and design information

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 <[hidden email]> wrote:

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 problem we have you covered there too create a gist for it , link it in the wiki and we will add it back to book. Gists even offer their own version control which means you can keep working and improving your code snippet for years to come without braking the workflow.

Then its a question of copy pasting the contents to pillar and adding them in our books , or if you do not mind the extra work write it in pillar directly and add it to the relevant book

All books can be added to CI and generate automagically html pages for direct access , we do this already with PBE 5.

Our Pharo "wiki" is easier to use and far more powerful than anything Squeak ever had, no offence intended of course to the original creators and maintainers of Squeak wiki.

Also github offers hosting of static webpages we could have a website hosted as github repo made with pillar that link to all wikis, gists and book artifacts. I can create this in an hour of work its not big deal. I would have done this myself but Stef already has added the books to Pharo.org which I find is more or less the same thing.

On Fri, Feb 10, 2017 at 10:15 PM [hidden email] <[hidden email]> wrote:
I miss the Squeak wiki Pharo style.

Phil

Le 10 févr. 2017 19:06, "Esteban A. Maringolo" <[hidden email]> a écrit :
2017-02-10 14:59 GMT-03:00 [hidden email] <[hidden email]>:
> 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 simple wiki to collect the shared
knowledge, recipes, and other stuff.

Esteban A. Maringolo

kilon.alios

Re: Slack, fragmentation and design information

I fail to see the problem here

On Sat, Feb 11, 2017 at 1:52 AM [hidden email] <[hidden email]> 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.

Phil

On Fri, Feb 10, 2017 at 9:30 PM, Dimitris Chloupis <[hidden email]> wrote:
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 problem we have you covered there too create a gist for it , link it in the wiki and we will add it back to book. Gists even offer their own version control which means you can keep working and improving your code snippet for years to come without braking the workflow.

Then its a question of copy pasting the contents to pillar and adding them in our books , or if you do not mind the extra work write it in pillar directly and add it to the relevant book

All books can be added to CI and generate automagically html pages for direct access , we do this already with PBE 5.

Our Pharo "wiki" is easier to use and far more powerful than anything Squeak ever had, no offence intended of course to the original creators and maintainers of Squeak wiki.

Also github offers hosting of static webpages we could have a website hosted as github repo made with pillar that link to all wikis, gists and book artifacts. I can create this in an hour of work its not big deal. I would have done this myself but Stef already has added the books to Pharo.org which I find is more or less the same thing.

On Fri, Feb 10, 2017 at 10:15 PM [hidden email] <[hidden email]> wrote:
I miss the Squeak wiki Pharo style.

Phil

Le 10 févr. 2017 19:06, "Esteban A. Maringolo" <[hidden email]> a écrit :
2017-02-10 14:59 GMT-03:00 [hidden email] <[hidden email]>:
> 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 simple wiki to collect the shared
knowledge, recipes, and other stuff.

Esteban A. Maringolo

Uko2

Re: Pharo wiki

In reply to this post by philippe.back@highoctane.be

I try to use StackOverflow documentation to document some Pharo stuff. It’s very limited, but it has all the collaborative stuff from StackOverflow, so somehow I believe there is less effort needed to manage permissions.

Uko

On 10 Feb 2017, at 21:14, [hidden email] <[hidden email]> wrote:

I miss the Squeak wiki Pharo style.

Phil

Le 10 févr. 2017 19:06, "Esteban A. Maringolo" <[hidden email]> a écrit :
2017-02-10 14:59 GMT-03:00 [hidden email] <[hidden email]>:
> 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 simple wiki to collect the shared
knowledge, recipes, and other stuff.

Esteban A. Maringolo

alistairgrant

Re: Pharo wiki

On 12 February 2017 at 09:22, Yuriy Tymchuk <[hidden email]> wrote:
> I try to use StackOverflow documentation to document some Pharo stuff. It’s
> very limited, but it has all the collaborative stuff from StackOverflow, so
> somehow I believe there is less effort needed to manage permissions.
>
> Uko

Uko, thanks for mentioning this, I wasn't aware of it, and will try
and contribute a bit to build the knowledge base (I don't believe email
or chat (slack, discord, etc.) even with a searchable history, can
replace a wiki for documentation).

There's been quite a bit of discussion in the past about in-image
documentation vs external documentation (e.g. wikis, books, etc.). While I
like the idea of having the documentation in image, the delays and cost of
getting documentation in to the core image currently makes it largely
impractical to have the same level of contribution as a wiki.

Recently I've seen in a couple of places people mentioning that github
and/or gitlab allow simple editing of files in the web interface and
directly generating pull requests.

Given that the class comment is stored in a separate file, could this
help facilitate the development of in-image documentation?

If there's no one that knows more about this than me, and there is some
interest, I'm happy to investigate a bit further.

Cheers,
Alistair

stepharong

Re: Pharo wiki

In reply to this post by Uko2

remember that we have this

http://pharo.gemtalksystems.com

stef

On Sat, 11 Feb 2017 23:22:11 +0100, Yuriy Tymchuk <[hidden email]> wrote:

I try to use StackOverflow documentation to document some Pharo stuff. It’s very limited, but it has all the collaborative stuff from StackOverflow, so somehow I believe there is less effort needed to manage permissions.

Uko

On 10 Feb 2017, at 21:14, [hidden email] <[hidden email]> wrote:

I miss the Squeak wiki Pharo style.

Phil

Le 10 févr. 2017 19:06, "Esteban A. Maringolo" <[hidden email]> a écrit :
2017-02-10 14:59 GMT-03:00 [hidden email] <[hidden email]>:
> 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 simple wiki to collect the shared
knowledge, recipes, and other stuff.

Esteban A. Maringolo

Using Opera's mail client: http://www.opera.com/mail/