Perl 6 - the future is here, just unevenly distributed

IRC log for #metacpan, 2014-01-28

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:16 jibsheet joined #metacpan
02:31 klapperl joined #metacpan
07:31 dpetrov_ joined #metacpan
11:15 [Sno] joined #metacpan
11:28 dolmen joined #metacpan
11:31 bowtie_ joined #metacpan
12:34 ribasushi joined #metacpan
13:22 dpetrov_ joined #metacpan
13:49 dpetrov_ joined #metacpan
13:59 metacpan joined #metacpan
13:59 metacpan [metacpan-web01] oalders pushed 5 new commits to master: http://git.io/GX2PcQ
13:59 metacpan metacpan-web/master 17223fe Thomas Sibley: Link RT subject tag style ticket references, i.e. "[rt.cpan.org #NNN]" and "rt.cpan.org #NNN"
13:59 metacpan metacpan-web/master 46b80e1 Thomas Sibley: Link PR#NN, PR:NN, and PR-NN to Github in changelogs...
13:59 metacpan metacpan-web/master 6472bcb Thomas Sibley: These aren't patterns, they're substrings.  Escape any metachars.
13:59 metacpan left #metacpan
13:59 dipsy [ Comparing 351202433f37...0875a09623cc · CPAN-API/metacpan-web · GitHub ]
14:00 oalders trs++
15:13 ribasushi bricas: sorry traveling, hence no reply
15:14 ribasushi bricas: the main complaint is that the spec has no concept of line continuations, nor does it define multiple level of nesting
15:14 ribasushi bricas: if it intends to be explicitly lax about it, then asking for a specific format of the top level alone is useless and ought to be removed, leaving only the distribution/date concern in the spec
15:15 ribasushi bricas: basically it is still utterly unclear what the spec is trying to achieve, and what its focus is
16:05 priodev joined #metacpan
16:09 bricas ribasushi: I don't disagree with you in regards to the multi-line/nested changes part. definitely a gap in the spec which I hope to eventually address.
16:10 bricas ribasushi: i do believe the general purpose has been laid out though: It is intended as a guide for module authors to encourage them to write meaningful changelogs as well as provide a programmatic interface to reliably read and write Changes files.
16:10 ribasushi bricas: the problem with "eventually addressing" it is that there are currently drives like http://questhub.io/realm/perl/quest/51f0fd8e18ba7dcf4b000040 and http://blogs.perl.org/users/gabor_szabo/2014/01/low-hanging-fruit.html
16:10 dipsy [ Questhub.io ] [ Low hanging fruit | Gabor Szabo [blogs.perl.org] ]
16:11 ribasushi bricas: so what you are basically doing is knowingly setting people up for double work, I find that not ok
16:11 ribasushi and think you ought to publicly state that the spec is in fact incomplete
16:11 ribasushi on the general purpose - it is not clear how much "reliably read and write Changes files" you want to achieve programatically
16:12 ribasushi this can not be a creeping goal bordering of "every bit of it"
16:12 ribasushi because after all changelogs are primarily for people to read
16:12 ribasushi bricas: so on both fronts you are in essence confirming my fears ;)
16:16 bricas ribasushi: clearly people will disagree, and that's cool. if someone wants to write their changelogs in yaml or markdown, or some other format -- that's good by me. they just won't be able to take advantage of whatever comes out of the tools/processes/whatever we create.
16:16 bricas ribasushi: this is totally opt-in.
16:18 bricas ribasushi: i apologize if things aren't quite what you expect.
16:19 ribasushi bricas: the problem with "opt-in" is that you don't get 20 chances to do it over and over again
16:19 bricas ribasushi: as an aside, i changed jobs about a year and a half ago -- i no longer do perl on the daily. sadly, things like this project will suffer as a result.
16:20 ribasushi bricas: in fact metacpan already has code in place conflicting with how the spec wants things, and that's on the simplest level
16:20 ribasushi bricas: right - so communicate *that*
16:20 ribasushi bricas: ask for help with maint and design stuff like that
16:21 ribasushi bricas: I want to reiterate - I do not have a huge problem with the spec being quite incomplete - I have a problem with this not being clearly communicated and people doing misguided work as a result
16:23 bricas patches always welcome -- says so on the site :)
16:36 ribasushi bricas: this is a cop-out, equivalent to "meh, the spec is incomplete, but good enough, let people convert. If they did it once, they can do it again in the future when someone ens up fixing the spec"
16:36 ribasushi bricas: if that's your actual position - there's not much else I can do
16:39 priodev joined #metacpan
17:21 sivoais joined #metacpan
17:28 priodev joined #metacpan
17:52 bricas ribasushi: there's nothing i can do this very instant other than hear you out and address the concerns as time permits.
17:53 bricas ribasushi: speaking of that -- as far as nested changes go, would whitespace indentation be good enough?
17:54 bricas the current parser uses that right now, just not recursively.
17:59 sivoais joined #metacpan
18:00 sivoais joined #metacpan
18:06 trs oalders: thanks for the merge!
18:06 oalders :)  thanks for adding the tests.  wasn't a huge deal, but i figured it would be helpful
18:07 trs no problem.
18:55 sivoais joined #metacpan
18:57 AirDisa joined #metacpan
20:31 sschu joined #metacpan
20:36 sschu left #metacpan
23:20 AirDisa joined #metacpan

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary