[perl6/specs] bd42b6: s/cause/excuse/
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: bd42b63230f42a0bacf79a224aec9bcaf4a6ac79 https://github.com/perl6/specs/commit/bd42b63230f42a0bacf79a224aec9bcaf4a6ac79 Author: Larry Wall Date: 2013-11-04 (Mon, 04 Nov 2013) Changed paths: M S17-concurrency.pod Log Message: --- s/cause/excuse/ Broken promises don't have causes, they have excuses. :) (Plus .excuse is the same length as .result for better alignment, fwiw.)
[perl6/specs] 7b9010: Conjectures, s/keeper/vow/ to stay non-commital
Branch: refs/heads/master
Home: https://github.com/perl6/specs
Commit: 7b9010f562d9f061d073608ca1d2e8974dfd312d
https://github.com/perl6/specs/commit/7b9010f562d9f061d073608ca1d2e8974dfd312d
Author: Larry Wall
Date: 2013-11-04 (Mon, 04 Nov 2013)
Changed paths:
M S17-concurrency.pod
Log Message:
---
Conjectures, s/keeper/vow/ to stay non-commital
Speculations in some spots that could have better syntax.
The word "keeper" kind of implies you're going to keep the promise,
when in fact you might break it. To avoid this overtone, as well
as other unfortunate meanings of "keeper" ("Yep, he's a keeper!"),
we rename the internal stewardship of the promise to "vow".
[perl6/specs] eb0f21: unspec statement_prefix:lift
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: eb0f21689e70b3280745e2da8c980553e3683da9 https://github.com/perl6/specs/commit/eb0f21689e70b3280745e2da8c980553e3683da9 Author: Larry Wall Date: 2013-11-04 (Mon, 04 Nov 2013) Changed paths: M S04-control.pod Log Message: --- unspec statement_prefix:lift This is going away in favor of better parameter declarations that can implicitly default to operators as seen by the caller.
[perl6/specs] f597d2: Scheduler refinements/defilements
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: f597d201ed23e052bcafb51cae03e42cc284827a https://github.com/perl6/specs/commit/f597d201ed23e052bcafb51cae03e42cc284827a Author: Larry Wall Date: 2013-11-04 (Mon, 04 Nov 2013) Changed paths: M S17-concurrency.pod Log Message: --- Scheduler refinements/defilements Renamed basic scheduler method to .cue Combined various other scheduler methods to use named parameters instead Added :at($instant) for a way to specify an absolute time Removed .outstanding because... Added .loads to give info on how many cues are in delayed/startable/running states
[perl6/specs] e17c32: missed some Subscribables -> Supply
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: e17c32ff194b9b63e87e0768d69c843e5d58e8ad https://github.com/perl6/specs/commit/e17c32ff194b9b63e87e0768d69c843e5d58e8ad Author: Larry Wall Date: 2013-11-04 (Mon, 04 Nov 2013) Changed paths: M S17-concurrency.pod Log Message: --- missed some Subscribables -> Supply
[perl6/specs] f0f514: Spec a statement-level construct for racing things
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: f0f514e20f6bb583db3a73ab1ef0901fe911b358 https://github.com/perl6/specs/commit/f0f514e20f6bb583db3a73ab1ef0901fe911b358 Author: Larry Wall Date: 2013-11-04 (Mon, 04 Nov 2013) Changed paths: M S17-concurrency.pod Log Message: --- Spec a statement-level construct for racing things
[perl6/specs] 9cfcf5: Some more s/Subscribable/Supply/
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 9cfcf5af3c49557b1282cc545446bc3e03598aa4 https://github.com/perl6/specs/commit/9cfcf5af3c49557b1282cc545446bc3e03598aa4 Author: Elizabeth Mattijsen Date: 2013-11-05 (Tue, 05 Nov 2013) Changed paths: M S17-concurrency.pod Log Message: --- Some more s/Subscribable/Supply/
Licensing: Perl 6 specification and test suite
Can I distribute and modify the Perl 6 specification documents and test suite under which conditions? If not, I propose that they should be distributed under the Artistic License 2.0.
Re: Licensing: Perl 6 specification and test suite
On Tue, Nov 5, 2013 at 3:09 PM, Kalinni Gorzkis wrote: > Can I distribute and modify the Perl 6 specification documents and test > suite under which conditions? If not, I propose that they should be > distributed under the Artistic License 2.0. > That is an excellent question. I've checked the git sources, and from what I can see, the examples repository is under AL 2.0, as is STD.pm, but the synopses are not. I'm unsure as to whether this is an artifact of how things got added to the git repository or not, perhaps someone else can clarify. -- Jan
Re: Licensing: Perl 6 specification and test suite
Hi, On 11/05/2013 03:16 PM, Jan Ingvoldstad wrote: On Tue, Nov 5, 2013 at 3:09 PM, Kalinni Gorzkis mailto:musicdenotat...@gmail.com>> wrote: Can I distribute and modify the Perl 6 specification documents and test suite under which conditions? If not, I propose that they should be distributed under the Artistic License 2.0. That is an excellent question. I've checked the git sources, and from what I can see, the examples repository is under AL 2.0, as is STD.pm, but the synopses are not. I'm unsure as to whether this is an artifact of how things got added to the git repository or not, perhaps someone else can clarify. historically the test suite comes from the 'Pugs' SVN repository, which I later migrated to git (when the SVN server failed, and nobody wanted to maintain it), and split it up into multiple repositorys. At that time, I didn't consider license questions, just getting the technical details worked out. The remainder of the Pugs SVN, which hasn't been split out into different repositories, now lives on github as perl6/mu, and it doesn't seem to have a catch-all license. Somehow I have always worked under the assumption that it is under the Artistic License 2, just as Rakudo and NQP, and community concensus seem to agree with me. Therefor I've added an AL2 LICENSE file to the perl6/roast repository, and I hope that any former or current contributor that disagrees with the choice of license speaks up soon. I have no idea if the AL2 is well suited for sets of documents, as the specification is. I'll leave that decision to Larry. Cheers, Moritz
Re: Licensing: Perl 6 specification and test suite
On Tue, Nov 5, 2013 at 3:36 PM, Moritz Lenz wrote: > I have no idea if the AL2 is well suited for sets of documents, as the > specification is. I'll leave that decision to Larry. > To anyone in doubt: please note that I'm not Larry, I'm not an authority, I'm just opinionated. :) Considering that the specification is sortof actually a language specification, I think there should at least be some terms regarding how this should apply. Forking the documentation, or creating derivative works, shouldn't be a problem, as long as it doesn't change the specification in itself, and thereby create confusion regarding what the Perl 6 specification is. Technically speaking, there shouldn't be a problem with pulling the Git repository, making changes, and proposing that these changes should be merged with the central Git repository for the specification – that is, after all, an approximation of how the specification is changed and developed by the community. -- Jan
Re: Licensing: Perl 6 specification and test suite
On Tue, Nov 05, 2013 at 03:36:47PM +0100, Moritz Lenz wrote: > Somehow I have always worked under the assumption that it is under > the Artistic License 2, just as Rakudo and NQP, and community > concensus seem to agree with me. Therefor I've added an AL2 LICENSE > file to the perl6/roast repository, and I hope that any former or > current contributor that disagrees with the choice of license speaks > up soon. Just to add my +1: I totally agree that perl6/roast is AL2, and I believe that to be entirely consistent with the way things were in the Pugs repository at the time of the split. Pm
Re: Licensing: Perl 6 specification and test suite
On Tue, Nov 05, 2013 at 04:21:12PM +0100, Jan Ingvoldstad wrote: > Considering that the specification is sortof actually a language > specification, I think there should at least be some terms regarding how > this should apply. Just to nit semantics a bit and push a little harder on something I've generally not pushed too much in the past... I believe that the Perl 6 language "specification" is actually the test suite. Synopsis 1 even indicates this somewhat explicitly: "Perl 6 is anything that passes the official test suite" and "... Perl 6 is defined primarily by its desired semantics, not by accidents of history." To me, the Synopses are primarily a detailed language description, and I'm increasingly wishing we wouldn't consider them as "the language specification"... > Forking the documentation, or creating derivative works, shouldn't be a > problem, as long as it doesn't change the specification in itself, and > thereby create confusion regarding what the Perl 6 specification is. ...and this is the exact reason for that wish. The documentation isn't the specification at all -- the test suite is. Pm
Re: Licensing: Perl 6 specification and test suite
On Tue, Nov 05, 2013 at 11:00:59AM -0600, Patrick R. Michaud wrote: > > Forking the documentation, or creating derivative works, shouldn't be a > > problem, as long as it doesn't change the specification in itself, and > > thereby create confusion regarding what the Perl 6 specification is. > > ...and this is the exact reason for that wish. The documentation isn't > the specification at all -- the test suite is. I should probably clarify. I think that referring to the Synopses as "specification" *increases* confusion on the issue, because it's the test suite that defines the language, not the Synopses. In some sense, perhaps the Synopses should be considered just another (human-readable prose) "implementation" of Perl 6. Just like any other Perl 6 implementation, a discrepancy between the Synopses and the test suite means that one of them needs updating (based on experience and evolution), but ultimately it's the test suite that determines what is or is not correct in the Perl 6 specification. Pm
Re: Licensing: Perl 6 specification and test suite
frettled, Right, it's just the AL2 requires you to thoroughly rename the project's main name(s) if you redistribute a modified version.. -Matthew On Tue, Nov 5, 2013 at 7:21 AM, Jan Ingvoldstad wrote: > On Tue, Nov 5, 2013 at 3:36 PM, Moritz Lenz wrote: > >> I have no idea if the AL2 is well suited for sets of documents, as the >> specification is. I'll leave that decision to Larry. >> > > To anyone in doubt: please note that I'm not Larry, I'm not an authority, > I'm just opinionated. :) > > Considering that the specification is sortof actually a language > specification, I think there should at least be some terms regarding how > this should apply. > > Forking the documentation, or creating derivative works, shouldn't be a > problem, as long as it doesn't change the specification in itself, and > thereby create confusion regarding what the Perl 6 specification is. > > Technically speaking, there shouldn't be a problem with pulling the Git > repository, making changes, and proposing that these changes should be > merged with the central Git repository for the specification – that is, > after all, an approximation of how the specification is changed and > developed by the community. > -- > Jan > -- Sent by the Internet - Login to LinkedIn to see my whole profile and Connect http://linkedin.com/in/mattswilson
Re: Licensing: Perl 6 specification and test suite
Perhaps these help? http://pugs.blogs.com/pugs/2005/02/day_28_609.html https://www.google.com/#q=site:http%3A%2F%2Fpugs.blogs.com%2F+licensing -- raiph On Tue, Nov 5, 2013 at 9:36 AM, Moritz Lenz wrote: > Hi, > > > On 11/05/2013 03:16 PM, Jan Ingvoldstad wrote: > >> On Tue, Nov 5, 2013 at 3:09 PM, Kalinni Gorzkis >> mailto:musicdenotat...@gmail.com>> wrote: >> >> Can I distribute and modify the Perl 6 specification documents and >> test suite under which conditions? If not, I propose that they >> should be distributed under the Artistic License 2.0. >> >> >> That is an excellent question. >> >> I've checked the git sources, and from what I can see, the examples >> repository is under AL 2.0, as is STD.pm, but the synopses are not. >> >> I'm unsure as to whether this is an artifact of how things got added to >> the git repository or not, perhaps someone else can clarify. >> > > historically the test suite comes from the 'Pugs' SVN repository, which I > later migrated to git (when the SVN server failed, and nobody wanted to > maintain it), and split it up into multiple repositorys. At that time, I > didn't consider license questions, just getting the technical details > worked out. > > The remainder of the Pugs SVN, which hasn't been split out into different > repositories, now lives on github as perl6/mu, and it doesn't seem to have > a catch-all license. > > Somehow I have always worked under the assumption that it is under the > Artistic License 2, just as Rakudo and NQP, and community concensus seem to > agree with me. Therefor I've added an AL2 LICENSE file to the perl6/roast > repository, and I hope that any former or current contributor that > disagrees with the choice of license speaks up soon. > > I have no idea if the AL2 is well suited for sets of documents, as the > specification is. I'll leave that decision to Larry. > > Cheers, > Moritz > -- raiph
[perl6/specs] bc9c55: [S99] Add STM and IC
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: bc9c55becbc0f43c0de3a4c6c0e6e3527ad4c47a https://github.com/perl6/specs/commit/bc9c55becbc0f43c0de3a4c6c0e6e3527ad4c47a Author: Bruce Gray Date: 2013-11-05 (Tue, 05 Nov 2013) Changed paths: M S99-glossary.pod Log Message: --- [S99] Add STM and IC
[perl6/specs] 039bbf: Some code example tweaks
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 039bbfdbf86308975581a690fca9801d499cff6a https://github.com/perl6/specs/commit/039bbfdbf86308975581a690fca9801d499cff6a Author: Elizabeth Mattijsen Date: 2013-11-05 (Tue, 05 Nov 2013) Changed paths: M S17-concurrency.pod Log Message: --- Some code example tweaks
perl6-language@perl.org
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 955852e867a01b73a5b32aeef820566440efb168 https://github.com/perl6/specs/commit/955852e867a01b73a5b32aeef820566440efb168 Author: lue Date: 2013-11-05 (Tue, 05 Nov 2013) Changed paths: M S32-setting-library/IO.pod Log Message: --- [S32::IO] Add starting definition of &glob Most likely needs quite a bit of improvement by others; this is just a first stab at things.
[perl6/specs] 2bd66d: Some more s/subscribable/supply/
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 2bd66db2132b70c20ae373f901929e222ed8617e https://github.com/perl6/specs/commit/2bd66db2132b70c20ae373f901929e222ed8617e Author: Elizabeth Mattijsen Date: 2013-11-05 (Tue, 05 Nov 2013) Changed paths: M S17-concurrency.pod Log Message: --- Some more s/subscribable/supply/
[perl6/specs] c01155: [S32] Use modern return type syntax
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: c01155abea2fef7b3a8e34c9a1b9679b9e578d8a https://github.com/perl6/specs/commit/c01155abea2fef7b3a8e34c9a1b9679b9e578d8a Author: Mouq Date: 2013-11-05 (Tue, 05 Nov 2013) Changed paths: M S32-setting-library/Callable.pod M S32-setting-library/Rules.pod M S32-setting-library/Str.pod Log Message: --- [S32] Use modern return type syntax
[perl6/specs] c148eb: Further update S32::Callable
Branch: refs/heads/master
Home: https://github.com/perl6/specs
Commit: c148eb989fe33862c813b8352d68f0015e9038e4
https://github.com/perl6/specs/commit/c148eb989fe33862c813b8352d68f0015e9038e4
Author: Mouq
Date: 2013-11-05 (Tue, 05 Nov 2013)
Changed paths:
M S32-setting-library/Callable.pod
Log Message:
---
Further update S32::Callable
Commit: 27d04b57d0f64c0010eca21614fcea4356b31c15
https://github.com/perl6/specs/commit/27d04b57d0f64c0010eca21614fcea4356b31c15
Author: Mouq
Date: 2013-11-05 (Tue, 05 Nov 2013)
Changed paths:
M S32-setting-library/Rules.pod
Log Message:
---
Restore `{...}`s elided in c0115ab
Compare: https://github.com/perl6/specs/compare/955852e867a0...27d04b57d0f6
