From @wchristian

Operating under a tuit shortness but want this to be retained​:

Right now the process of submitting bugs/patches is not documented well and has a very high barrier of entry. By adding some documentation to the perl repo this might be improved at least.

Details in attached IRC log.

--
With regards,
Christian Walde

From @wchristian

[2018-08-21 16​:31​:38] <Mithaldu_> can we propose branches via github yet or do i need to learn how to do git patches on windows again
[2018-08-21 16​:31​:46] <khw> The windows vm attached to dromedary doesn't appear to have either gmake nor dmake. It appears to be Microsoft Visual Studio 10.0. Did these come along later?
[2018-08-21 16​:31​:58] <ilmari> khw​: it has nmake, afaik
[2018-08-21 16​:32​:06] <alh> You can hand a link to the patch in your email, I think we'll be reasonable about it
[2018-08-21 16​:32​:09] <Mithaldu_> gmake is relatively new to the toolchain
[2018-08-21 16​:32​:18] <Mithaldu_> alh​: woop
[2018-08-21 16​:32​:41] <ilmari> 'git format-patch blead' doesn't work on windows?
[2018-08-21 16​:32​:46] → Hinrik joined (hinrik@​u.nix.is)
[2018-08-21 16​:32​:47] → atomicstak joined (matt@​u.nix.is)
[2018-08-21 16​:32​:54] <khw> It does have nmake, but that doesn't do parallel compiling/testing, so is slow
[2018-08-21 16​:33​:25] <Mithaldu_> https://github.com/Perl/perl5/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc # cute
[2018-08-21 16​:33​:27] <alh> Mithaldu_​: Oh, if you open a pull request, you can append '.diff' to the end of it '/pull/32.diff' and you'll get a unified patch
[2018-08-21 16​:34​:41] <Mithaldu_> alh​: useful
[2018-08-21 16​:35​:14] <khw> should these hints be documented somewhere?
[2018-08-21 16​:35​:34] <Mithaldu_> ilmari​: i don't know, and i'd prefer not to spend time on learning the details of that if i can avoid it, but heck, now i'm also remembering i can't send perlbugs with a web interface so i need to figure out again how to make emails for that
[2018-08-21 16​:35​:49] <alh> Can you run perlbug?
[2018-08-21 16​:36​:01] <Mithaldu_> yeah but i don't have sendmail
[2018-08-21 16​:36​:09] <Mithaldu_> last i remember i had to have it make a file
[2018-08-21 16​:36​:09] <alh> So, it's awful
[2018-08-21 16​:36​:13] <alh> But I usually run it and have it make a file
[2018-08-21 16​:36​:15] <alh> And then copy
[2018-08-21 16​:36​:18] <Mithaldu_> and then i copied the file to my email client
[2018-08-21 16​:36​:20] <alh> Yup
[2018-08-21 16​:36​:27] <Mithaldu_> which is very dumb
[2018-08-21 16​:36​:28] <xenu> Mithaldu_​: you can just send email to perlbug@​perl.org, you *don't* have to use that stupid template
[2018-08-21 16​:36​:30] <khw> I've gotten used to it
[2018-08-21 16​:36​:34] <xenu> you just have to make sure that your email contains word 'perl'
[2018-08-21 16​:36​:38] <xenu> otherwise it will be discarded
[2018-08-21 16​:36​:38] <Mithaldu_> xenu​: oh
[2018-08-21 16​:36​:40] <Mithaldu_> neat
[2018-08-21 16​:37​:46] → Bucciarati joined (buccia@​u.nix.is)
[2018-08-21 16​:38​:06] <Mithaldu_> khw​: perlhack documents some of it, but also assumes perlbug works entirely
[2018-08-21 16​:38​:06] <xenu> also i'm not sure if attachements are allowed, so just to be safe, if you want to attach something, attach it in a reply to your ticket
[2018-08-21 16​:38​:19] <Mithaldu_> also perlhack is kind of hidden deep in the pod bowels
[2018-08-21 16​:38​:24] <alh> They are
[2018-08-21 16​:38​:34] <xenu> iirc bulk88 had problems with that
[2018-08-21 16​:38​:47] <Mithaldu_> a README.contributing or similar would be nice
[2018-08-21 16​:39​:00] <Mithaldu_> also, fun fact, all i want right now is to propose a doc fix
[2018-08-21 16​:39​:09] <Mithaldu_> so yay, high barrier of entry
[2018-08-21 16​:39​:25] <alh> You could try the "Send a bare email to perlbug with a patch attachment"
[2018-08-21 16​:39​:27] <alh> And if that works great!
[2018-08-21 16​:39​:40] <Mithaldu_> right
[2018-08-21 16​:39​:44] <alh> If it's a simple "this word or sentence is wrong" you can probably mention it here and someone may fix it
[2018-08-21 16​:39​:48] <alh> But yeah, I hear you
[2018-08-21 16​:39​:49] <xenu> Mithaldu_​: there are other problems like perlbug@​perl.org not working at all for some people
[2018-08-21 16​:40​:02] <xenu> our bug reporting system is *insane*
[2018-08-21 16​:40​:22] <xenu> and i'm surprised that we get bug reports from non-p5p people at all
[2018-08-21 16​:40​:26] <Mithaldu_> the bug is more, as khw mentions​: all of this should be documented, and the docs for it easy to find, even if it's just a file saying "look at pod/perlhacks.pod"
[2018-08-21 16​:40​:54] <Mithaldu_> and maybe not do this​: #11
[2018-08-21 16​:41​:28] <alh> You planning on writing the file or opening a bug saying the file should be written?
[2018-08-21 16​:41​:29] <alh> =x
[2018-08-21 16​:42​:00] <Mithaldu_> i'm empted to copy the irc log and dump it into an email? :P
[2018-08-21 16​:42​:08] <alh> x.x
[2018-08-21 16​:42​:10] <alh> It's a start
[2018-08-21 16​:42​:13] <Mithaldu_> i have an extreme lack of tuits at the moment
[2018-08-21 16​:42​:25] <alh> Give me your mailing address I can send you a bunch I got from liz and wendy
[2018-08-21 16​:42​:33] <Mithaldu_> haha
[2018-08-21 16​:42​:46] → avar joined (avar@​u.nix.is)
[2018-08-21 16​:42​:50] <Mithaldu_> all i wanted is to try and not get knowledge lost, but even keeping the knowledge in itself costs a surprising amount of time
[2018-08-21 16​:43​:13] <Mithaldu_> so i guess i'll send two mails to perlbug

From @jkeenan

On Tue, 21 Aug 2018 14​:48​:11 GMT, walde.christian@​gmail.com wrote​:

Operating under a tuit shortness but want this to be retained​:

Right now the process of submitting bugs/patches is not documented
well and has a very high barrier of entry. By adding some
documentation to the perl repo this might be improved at least.

Details in attached IRC log.

Can you work this into a patch?

Those of us, including myself, who read all New submissions to rt.perl.org, will need some persuasion to agree with your claim that the barrier to entry is "very high".

So a specific patch would help move the discussion forward.

Thank you very much.
--
James E Keenan (jkeenan@​cpan.org)

The RT System itself - Status changed from 'new' to 'open'

Is this now fixed by our use of github?

Is this now fixed by our use of github?

No specific patch was ever proposed. And we've certainly had lots of patches (in the form of pull requests) submitted since that conversion took place. So +1 to closing.

Yeah, Github use fixes this.