Ok I will contact the editor telling that there are some wishes from the
community to do something.
After we can brainstorm on what should be purpose and outline.
Stef
> On 1 Mar 2019, at 18:21, Ben Coman wrote:
>
> Obviously its good to be circumspect at such an earlier stage,
> but I can
Obviously its good to be circumspect at such an earlier stage,
but I can imagine a few "good" editors who publishing a book would really
lend some legitimacy and exposure to Pharo.
That would be overall beneficial even if the book is not free.
Stef, I am interested to know more.
cheers -ben
On
There is a new Pharo build available!
The status of the build #110 was: FAILURE.
The Pull Request #2721 was integrated: "2587-Cannot-remove-a-Trait"
Pull request url: https://github.com/pharo-project/pharo/pull/2721
Issue Url: https://pharo.fogbugz.com/f/cases/2587
Build Url:
There is a new Pharo build available!
The status of the build #109 was: SUCCESS.
The Pull Request #2739 was integrated: "2293-Failing-tests-on-Pharo-8"
Pull request url: https://github.com/pharo-project/pharo/pull/2739
Issue Url: https://pharo.fogbugz.com/f/cases/2293
Build Url:
There is a new Pharo build available!
The status of the build #108 was: SUCCESS.
The Pull Request #2364 was integrated: "2363 Add
ProperManifestCategorizationTest as new release test"
Pull request url: https://github.com/pharo-project/pharo/pull/2364
Issue Url:
this is why all the pharo material are creative commons :)
> On 1 Mar 2019, at 10:00, Thomas Dupriez wrote:
>
> Hello,
> The timing of this mail is interesting, because just yesterday I stumbled on
> the "Free Software Needs Free Documentation" preface of the GDB documentation.
>
> It's a
Hello,
The timing of this mail is interesting, because just yesterday I
stumbled on the "Free Software Needs Free Documentation" preface of the
GDB documentation.
It's a dozen paragraph so not exactly a short read, but the gist of it
is that the author urges other authors to use free
