Add drafts for feedback on talks of the second day

1 files changed, 95 insertions, 5 deletions

diff --git a/_posts/2018-08-15-the-perl-conference-in-glasgow.adoc b/_posts/2018-08-15-the-perl-conference-in-glasgow.adoc
index 0c5e3b1..f2fa60d 100644
--- a/_posts/2018-08-15-the-perl-conference-in-glasgow.adoc
+++ b/_posts/2018-08-15-the-perl-conference-in-glasgow.adoc
@@ -44,11 +44,8 @@ with. However, this should go both ways: we should also not use logical
 fallacies to promote her ideology. Most notably, she pointed out the
 https://en.wikipedia.org/wiki/Argumentum_ad_populum[_argumentum ad populum_].
 This basically means that just because a lot of people do or say something,
-doesn't make it right. And this applies to this idea that we need to push the
-diversity ideology, with concepts like a code of conduct footnote:[I personally
-prefer calling it a "code of misconduct", as these documents are mostly used to
-draft a list of misconducts that will bring repurcussions with them, not detail
-how the community tries to better itself.], in the Perl community.
+doesn't make it right. And this applies to the idea that we need to push the
+diversity ideology in the Perl community.
 
 Another thing which slightly bothered me is the useless spin into radical
 feminist ideology, which has no place on the Perl conference. We're not at a
@@ -168,3 +165,96 @@ It might be interesting to run this application of grammars on every Perl 6
 release to gather more information on the speed improvements of Perl 6, much
 like Tux's `Text::CSV` runs.
 
+== Releasing a Perl 6 Module
+
+Personally, I prefer GitLab over GitHub, as they have much better testing
+functionality, and they actually release their own platform as an open source
+package. I'd like more GitLab love from the community and speakers as well if
+possible. This would also make the speakers CI configuration simpler, for which
+he currently uses a `.travis.yml` file. This requires him to build Perl 6 from
+source every test run, wasting quite a lot of time.
+
+A number of directories were listed which are standard in Perl 6 module
+skeletons. However, the `resources` directory was left out of it, which should
+get its fair share of love as well. Files listed in here can be made accessible
+through the `%?RESOURCES` variable in your program, allowing you to easily
+bundle additional resources with your moule.
+
+It was also noted that there's a module to help you set up this module
+skeleton, `mi6`. The speaker also noted that it doesn't seem to add much once
+you know how a Perl 6 module is organized, and I tend to agree with this.
+Actually, I made a module precisely because I agree to him here, `App::Assixt`.
+This module intends to smoothen the entire course of module development, not
+just the creation of a skeleton file. It will take care of keeping your
+`META6.json` up to date, and ease uploading your module to CPAN as well.
+
+Lastly, the speaker says the `META6.json` documentation can be found in S22.
+While this is technically correct, S22 is *not* the implementation's
+documentation, this lives in the official Perl 6 documentation instead. S22
+offers many additional information to be stored in the `META6.json`, but using
+these fields will actually break installation of your module through `zef`,
+rendering it unusable by others. I would strongly recommend people not to use
+S22 when trying to figure out what they can or cannot do with their
+`META6.json`.
+
+== How to become CPAN contributor?
+
+Submitting a pull request (or more correctly named, merge request) to a
+repository is possibly the most straightforward way to help out other projects.
+However, sometimes it will take a long time to get a response. The speaker
+notes this can actually be on the scale of years. I have authored a number of
+modules myself, and have been in the situation where I had not realized I got a
+merge request from another person (same goes for issue reports). I would
+recommend people who are not getting timely responses to their contributions to
+contact the maintainer via other channels which are more suited for
+communications. Think of email or irc, for instance. You'll generally have a
+much better chance of getting a timely response from the author, and then you
+can work out your contribution and see if you can get it merged into the main
+project.
+
+The speaker also lists a couple of ways to get started with contributing to
+modules. One thing I missed in particular was the Squashatons for Perl 6. These
+generally offer a good entry point to help out with the language's development
+and the ecosystem's maintainance.
+
+Near the end, it was pointed out that it is a good idea to have a thick skin.
+Even when it's not intended, people can come accross as rude. This is in
+opposition to the talking point of the speaker yesterday (_Discourse Without
+Drama_), but he does raise a good point here. People oftentimes don't mean to
+insult you, but context is easily lost in written communications. Try to stay
+mature and professional, you can simply ask for clarification. If you feel the
+person remains hostile towards you, walk away. There's plenty of other projects
+that would love your contributions!
+
+== Conference Organizers & European Perl Mongers Organiser's Forum 2018 BoF
+
+Well, that's certainly a mouth full for a heading, and it even contains an
+abbreviation! This event was not a presentation, but a platform to exchange
+ideas together.
+
+One of the items that were up for discussion was _A Conference Toolkit_, or ACT
+for short.  This is the platform used to organize Perl events, such as this
+conference and Perl workshops throughout the world. However, ACT is dated.
+They enabled HTTPS a short while ago, but it's still not the default because
+people don't want to risk breaking the platform. I think this is indication
+enough that it might be time to make something new to replace it.
+
+And I'm not alone in that sentiment, it seems. However, ACT is big and contains
+a lot of data we don't want to lose. It's a massive undertaking to make a new
+tool that works at least as well, and allows us to make use of the old data as
+well. There is a Trello board available that lists all the features that would
+be required to implement, so that's a good start already. I think now it needs
+a dedicated product owner with people contributing code, so a start can be
+made. This does seem like a touchy subject, since I'm far from the first person
+to want this. Many before me have tried and failed already.
+
+As such, I'd propose not making it a Perl centric tool. Make it a modular,
+generic event organizing tool. Get a good database design that we can import
+our old data into, so nothing is lost, but things can be converted to be more
+useful for our current needs. This way, we can work in small steps, and maybe
+even reach contributors from outside the regular Perl circles. This might even
+bring in new partnerships (or sponsors) towards the Perl community.
+
+Personally, I'd like to see something like this to be written in Perl 6. This
+way, it could also be used as a showcase project for Perl 6.
+