The Perl and Raku Conference (formerly knwn as YAPC::NA) is going strong! This year, we are celebrating 25 years, our silver anniversary, in the Silver State, Nevada! The main conference will be in Las Vegas on June 25-27, but there will be hackathons and possibly classes on the day before and the day after the conference (June 24th and 28th), so please consider joining us for the whole week!
The backbone of this conference has always been our tracks of "traditional" talks by community members and what we have come to call the "Hallway Track" the informal exchange of ideas and camaraderie that sparks new projects and fuels collaboration.
This year, we are pleased also to host the presentation of Papers and Posters accepted by the Science Perl Journal!
Registration is open, so your ticket can now be purchased.
Talk submissions are still open, and we are seeking proposals on a wide variety of subjects. This includes language features, personal projects, applications like Koha, and anything that may be of general interest to Perl and Raku programmers. (We had juggling and origami in the past. Fun!) * Talks can be 20 minutes or 50 minutes. Please submit through PaperCall. * Papers and Posters follow the guidelines of the Science Perl Journal. Links to both are also on https://tprc.us.
Speakers who are approved for a talk, paper, or poster will receive a free ticket to the event. The submission deadline is April 5th at 8pm EST, so please send us your submissions soon!
We are planning some special activities during the conference to celebrate our rich 25-year history.
Go now to https://tprc.us/ to check out what is planned and to book a room (see link to Alexis Park Resort under "Location"). Rooms start at only $75 per night, so it’s worth booking early!
The best way to register for the conference is at https://tprc2024.sched.com/tickets
Thanks, TPRC Admins
]]>Tony writes:
``` [Hours] [Activity] 2023/12/04 Monday 0.42 #21677 minor fix. testing 0.23 #21661 check smoke results, minor commit message edit, make PR 21683 1.90 #21680 testing, debugging 1.28 #21680 fixes, testing, push for CI 1.42 #21651 testing and reproduce, try a fix and testing, push
5.25
2023/12/05 Tuesday 0.30 #21677 research 0.95 #21664 apply to blead, perldelta, comment on original perlmonks post 0.82 #13814 research 0.38 #13814 try a different approach
3.07
2023/12/06 Wednesday 1.07 #13814 review CI results, documentation, testing, make PR 21693 2.48 #21692 review, comments, try to work out getlines() cleanup 1.52 #21692 finally figure it out, comment 0.13 #21686 testing and comment 0.57 #16535 research and close 0.12 #16529 research and close
5.97
2023/12/07 Thursday 0.38 #17457 rebase, retest, push for CI 2.03 #17435 testing, work on a fix, more testing 0.35 #21679 apply to blead, perldelta 0.75 #13814 changes per comments
3.61
2023/12/08 Friday 0.35 #21696 apply to blead, update dist/IO/Changes
0.60
2023/12/11 Monday 0.20 #21684 follow-up 0.72 #21701 research and comment 0.63 #21705 research and comment 0.60 #21702 testing, research and approve 0.08 #21706 review and approve 0.13 #21703 review and approve 0.08 #21699 review and approve 0.08 #21698 review and approve 0.08 #21704 review and approve 0.17 #21700 review and approve 1.03 #21701 testing, research, comment 0.13 #21708 review and approve
4.08
2023/12/12 Tuesday 1.02 #21712 review the code, testing, comment (not a bug) 0.68 #21684 apply to blead, look at regenning the deps
1.93
2023/12/13 Wednesday 0.27 #21705 research and comment 0.22 #21710 review and approve 2.38 #21714 review and approve, comment 0.27 #21711 review and approve 0.18 #21713 review and approve 0.40 #21676 review and approve
6.14
2023/12/14 Thursday 0.12 #21714 follow-up 1.83 #21701 testing and research, comment
2.58
2023/12/18 Monday 0.42 #21725 debugging, comment 1.38 #21716 debugging. research, comment, work on a fix, push
1.80
2023/12/19 Tuesday 1.08 #21716 minor fixes, testing and comments 0.62 #21725 add comment 0.85 #21719 review, research and comments
2.87
2023/12/20 Wednesday 0.45 #21723 review, research and approve 0.18 #21726 review, research (alternate openbsd libc anywhere?, apparently not), approve 0.23 #21728 review and approve 0.58 #21720 review, comments and approve 0.25 #21731 follow-up comment 0.70 #21636 re-work 1.03 #21636 more re-work, testing and push 0.50 #21732 testing and comment, work on fixing the most
3.92
2023/12/21 Thursday 0.08 #21732 review discussion, check CI results and create PR 21737 0.20 #21716 review discussion and comment 0.15 #21719 review updates and approve
1.48
Which I calculate is 43.3 hours.
Approximately 44 tickets were reviewed or worked on, and 5 patches were applied. ```
]]>Paul writes:
``` Hours:
1 = Allow space in -M
option
https://github.com/Perl/perl5/pull/21935
3 = Tidy up / remove builtin
unimport logic
https://github.com/Perl/perl5/pull/22002
https://github.com/Perl/perl5/pull/22009
5.5 = use VERSION
restrictions
https://github.com/Perl/perl5/pull/21980
https://github.com/Perl/perl5/pull/21997
https://github.com/Perl/perl5/pull/22057
1 = class.c bugfix https://github.com/Perl/perl5/pull/21957
2 = builtin::numify https://github.com/Perl/perl5/pull/21982
1 = Tests for class.c non-ASCII UTF-8 https://github.com/Perl/perl5/pull/21983
1.5 = Logical xor operator (^^) https://github.com/Perl/perl5/pull/21996
Total: 15 hours. ```
]]>Dave writes:
(this report covers two months)
This is my monthly report on work done during Jan,Feb 2024 covered by my TPF perl core maintenance grant.
I spent the last two months mainly on two goals.
1) Understanding XS better so that I can then decide how to update the XS ecosystem to better support a reference-counted stack; as an example, automatically removing the need to call XSUBs via a wrapper in some circumstances.
Doing this led me down a rabbit hole of realising how awful our current XS documentation is. Just about every section I read resulted in confusion, followed by time out to experiment and/or to look at the ParseXS src code to try to understand what the documentation was trying to tell me. It's also very out of date: telling us of exciting "new" features introduced 25 years ago.
The net result of this is that I now have about 1000 lines of notes on "things to fix in the XS docs". I intend sometime soon to completely revamp perlxs.pod and perlxstut.pod, based on these notes. Which is a bit of sidetrack from getting XS working better under PERL_RC_STACK builds. And doing PERL_RC_STACK was itself initially a sidetrack from doing more work on perl signatures. Such is often the way when working on perl.
2) General small tasks to help get blead into shape for the 5.40 release, such as analysing and reducing smoke failures, fixing bugs, and fixing any Deparse regressions that have crept in over the last year.
SUMMARY:
* 0:38 #21822: BBC: Blead Breaks Variable::Magic
* 1:20 #21876: BBC: 5.39.7 breaks GONZUS/Cache-utLRU-0.002000.tar.gz
* 3:21 #21969: clone-with-stack.t crash
* 2:17 fix Test -deparse failures
* 1:35 fix minitest failures
* 3:39 make __LINE__
etc Deparse batter
* 1:57 make stack reference counted
* 30:30 make stack reference counted - XS
* 19:46 process p5p mailbox
* 1:28 reduce build stderr noise
* 8:33 reduce smoke failures
TOTAL: * 75:04 (HH::MM)
]]>To nominate an individual, kindly complete the form at https://forms.gle/xQczcsRkguvaBDBn8.
In light of our community’s growing diversity, we kindly ask that the rationale for each nomination be articulated in a manner accessible to those who may not be familiar with the nominee.
For reference, previous recipients of this award can be found at https://whitecamel.org/.
]]>Dave writes:
This is my monthly report on work done during November-December 2023 covered by my TPF perl core maintenance grant.
I mainly continued my work on making the perl stack reference counted. As well as "unwrapping" a few more ops, I also took the opportunity to introduce some basic optimisations to get the speed of a PERL_RC_STACK perl interpreter build back closer to a vanilla build.
On my most recent branch (rc7, pushed today, 3rd Jan), the average of the 500 or so benchmarks in t/perf/benchmarks under PERL_RC_STACK has the following instruction read, conditional branches, etc results as compared to a vanilla perl build. 100% is unchanged, higher is better.
Ir 93.31
Dr 94.54
Dw 93.90
COND 92.50
IND 98.12
Note that the benchmark coverage is not yet comprehensive, and my optimising efforts will likely have been biased to make these numbers look better, rather than fixing the ops which aren't yet covered.
I've also made a start into looking at how XS code can be made (at least sometimes) to work directly under a ref-counted stack, rather than each XS call needing to be wrapped.
SUMMARY:
9:33 process p5p mailbox
TOTAL:
108:37 (HH::MM)
TPRC 2024 is being held in Las Vegas, NV from June 24-28 2024. You can submit your talk Ideas for TPRC 2024 at https://tprc.us/talks . Talk submission deadline is April 5th, Midnight UTC. Talks must be given live and in-person. If you are looking for any talk ideas, try out the conference wiki.
New this year, we are accepting submissions for a peer reviewed Science track. Those talks should be submitted at https://science.perlcommunity.org/
Visit the TPRC 2024 website at https://tprc.us/ Follow us on Twitter: @PerlConferences Like us on Facebook: The Perl Foundation (@tpf.perl) Subscribe to the mailing list: https://tprc.us/subscribe
]]>Tony continues to work hard in maintaining the core of Perl 5. This is his activity report for November 2023.
``` [Hours] [Activity] 2023/11/01 Wednesday 1.30 look into intermittent File-Find/t/taint.t failures: cannot reproduce 1.70 #21261 review, try to reproduce reported failures (logs expired), finally reproduce on windows, debugging
3.60
2023/11/02 Thursday 1.40 #21567 research and long comment and approve 0.08 #21513 review and approve 0.73 #21535 set up build environment
4.99
2023/11/06 Monday 0.58 github notifications, VM setup for khw to test locales /threads smoke issues 2.65 #21535 resolve win32 issues, signbit fallback problems, old VC support issues and lots of testing, start vc2015 download 1.38 #21535 get it installed and troubleshoot, testing, push for CI 0.70 bury MSVC 2013/aka VC12, it’s already dead, testing,
5.31
2023/11/07 Tuesday 1.38 diagnose vs2013 build failure, more testing, commit message and push to smoke-me 0.08 #21586 review and apply to blead 0.48 retiring vs2013: look over smoke results, fix and push
2.74
2023/11/08 Wednesday 0.92 #21621 review, comment 0.43 #21621 more review, more comment 0.72 #21550 review patches that led to this, comment 1.63 #21513 discussion with khw and research on smoke failures from merge, valgrind setup, testing, but valgrind appears
3.70
2023/11/09 Thursday 1.00 #21513 try to get valgrind working to debug this on dragonfly 0.85 #21535 apply to blead, update perldelta 0.27 retiring vs2013 support: open PR 21624
3.52
2023/11/10 Friday
1.12
2023/11/13 Monday 0.12 #21621 review updates and approve 0.73 #21624 updates, research and push for CI 1.40 #21469 setup test environment, testing and comment 1.10 #21623 re-work globvar.t, testing, start test on AIX5 0.70 #21623 test on HP-UX, push for smoke-me 0.20 #21635 review, research and approve 0.10 #21634 review and comment
5.10
2023/11/14 Tuesday 0.20 #21634 research, briefly comment 1.17 #21636 re-work 1.22 look into Dave’s Test-Harness SIGINT issue, comment on list 0.63 #21624 apply to blead, perldelta 0.47 #21629 review CI results, research and long-ish comment 0.32 #21623 re-check, make PR 21637
4.79
2023/11/15 Wednesday
0.63
2023/11/16 Thursday 1.75 review attributes thread 0.17 #21637 apply to blead and perldelta 0.87 #21633 test possible causes on dragonfly, find one, discuss with khw, report upstream as https://bugs.dragonflybsd.org/issues/3361 0.18 #21633 check for similar setlocale issue (not found) 0.33 #21638 review and approve 0.28 #21639, #21640 research and comment on each (they’re very
3.58
2023/11/17 Friday 0.20 github notifications 0.50 #21091 testing, comment
0.93
2023/11/20 Monday 0.58 github notifications 0.80 #21641 review, research, comment and approve 0.08 #21644 review and approve 0.22 #21612 review discussion, research and comment 0.60 #21647 review, testing and approve 0.47 #21642 start review 0.80 #21633 zoom setup, zoom with khw 1.72 #21642 more review, first pass done, need to do an
5.27
2023/11/21 Tuesday 0.10 github notifications 0.60 #21643 research, comment and approve 0.12 #21650 review and comment
1.62
2023/11/22 Wednesday 0.20 review list discussion 0.08 #21655 review and approve 0.60 #21653 review discussion, review code 0.27 #21653 more review and approve 0.63 #21654 research and comment
3.96
2023/11/23 Thursday 0.98 #21654 long-ish comment 0.57 #21642 more review, comment on minor issue and approve 0.20 #20308 re-review, comment and approve 0.35 #19426 rebase, testing and comment 1.87 #21654 testing, profiling, work on possible fix, re-work 1.68 #21654 profile patched version, push for CI, get an error,
5.65
2023/11/27 Monday 2.12 #21661 debugging, long-ish comment 1.30 #21654 try to work up a test
5.69
2023/11/28 Tuesday 0.60 #21636 review comments, research and follow-up comment 1.33 #21654 review CI results, testing, work up a skip, more testing, push for CI/smoke-me 0.77 #21670 review, testing, approve 0.15 #21666 research, review and approve
3.12
2023/11/29 Wednesday 0.08 #21591 apply to blead (I don’t think it needs perldelta) 0.12 #21654 adjust the sanitize check 1.00 #21562 comment 0.28 #21677 start to ask for response, look over libperl.t code and realize it’s fixed, comment 3.47 #21661 work on fix, testing, fix issues, more testing push
4.95
2023/11/30 Thursday 0.73 #21654 remove the performance tests, they were too flakey, minor re-work 1.48 #21661 work on regression tests, better commit message, push for smoke/CI 0.25 #21663 review and apply to blead 0.67 #21677 work on skip in maint, testing, push for CI 0.10 #21135 follow-up 0.08 #21677 check CI and make PR 21679 1.93 #13814 define new fatal once flag, try to work out warning
5.24
Which I calculate is 75.51 hours.
Approximately 42 tickets were reviewed or worked on, and 7 patches were applied.
```
]]>It is difficult to narrow down the depth of PEVANS activity in the Perl Core. Continuing to
modernise the Core is vital for the longevity of Perl and introduction of modern paradigms.
To do this without breaking Perl is an extra challenge. FOSDEM provided such an opportunty to
review what the Paul and the PSC has been upto, and may allow some insight of the builtin
excitement that
is due to land with Verson 5.40.
Date | Activity | Hours |
---|---|---|
2023/12/29 | updates to `meta`, next version | 2 |
2021/12/31 | further work on `meta`, add ->get method | 1 |
2024/01/03 | Further experimentation with `meta` | 1 |
2024/01/04 | `meta` experimental warnings | 2 |
2024/01/05 | more `meta` warnings | 1 |
2024/01/05 | meta get_or_add methods | 2 |
2024/01/11 | Initial poking at qt strings ( [PPC0019](https://github.com/Perl/PPCs/blob/main/ppcs/ppc0019-qt-string.md) ) | 3 |
2024/01/17 | `use VERSION` to import builtin bundle | 4 |
2024/01/19 | Reword builtin import for resetting | 3 |
2024/01/22 | Add `builtin::inf` and `builtin::nan` | 0.5 |
2024/01/25 | More inf + nan | 1 |
2024/01/25 | Improvements to pad tombstone handling | 4 |
2024/01/26 | Management of recent PRs | 1 |
2024/01/31 | lexical subroutine shadow warnings | 3 |
Paul has submitted a more detailed report of his activity:
Hours:
9 = Updates to the meta
module, a new CPAN release, adding a ->get
method, adding experimental warnings, ->get_or_add methods
https://metacpan.org/pod/meta
https://github.com/Perl/PPCs/blob/main/ppcs/ppc0022-metaprogramming.md
3 = Initial investigation into implementing PPC0019 "Quoted template strings" https://github.com/Perl/PPCs/blob/main/ppcs/ppc0019-qt-string.md
7 = Getting use VERSION
to import a feature bundle
https://github.com/Perl/perl5/pull/21850
1.5 = Adding builtin::inf and builtin::nan https://github.com/Perl/perl5/pull/21872
5 = Improvements to PADNAMEf_TOMBSTONE handling https://github.com/Perl/perl5/pull/21887
3 = Lexical subroutine shadow warnings https://github.com/Perl/perl5/pull/21915
]]>The Perl and Raku Foundation fosters continued development and use of Perl and Raku. As an open source programming language with a largely open source minded community, contributions to Perl and Raku are rarely rewarded. One of the many activities of The Perl and Raku Foundationhas been to reward these activities through Grants.
There are as many ideas as there are people reading this post, indeed it is likely that many people will have more than one idea. Indeed there will be many of you who have the skills and the time but need something to work on: see ideas suggested before. Here is an opportunity for conversion of an idea into invention, and benefit the community.
Type of Idea: Anything, code, documentation, teaching material, text book
Who can apply: Anybody, apart from members of the Perl Foundation
Conditions: The Project must benefit the community, even if it is a small part of the community
See Perl Core Develeopment Fund and Raku Development Fund pages
Type of Idea: Code that ends up contributing to Core Perl or Raku,
Who can apply: Any Core Perl Developer or contributor to Raku specification/implementation
Conditions: The project and the Author must be endorsed by someone with Perl Core Commit privilges or the Raku steering council
Type of Idea: A resource (a book, website, etc) that already exists, but needs to meet modern Perl standards
Who can apply: Someone holding the copyright to the original work
Conditions: A commitment to Publish. The Foundation will not ask for any royalties, but may offer editors to review the project standards.
A new Grant application for Raku. Tony O'Dell is proposing a project to develop a Raku Ecosystem written in Raku. This gets rid of a dependency on other languages and proprietary code to create a more sustainable environment. Tony has a number of Raku projects including the very important Fez, working with niner
, vrurg
, and ugexe
.
Author: Anthony O'Dell Country: USA Date Submitted: 22 Jan 2024
To create an open source infrastructure around raku ecosystems. This proposal to write this code in raku and make it available to the general public. The current state is that the underlying code is written in go and using proprietary AWS lambdas to make everything flow smoothly. The go lambdas are due to be deprecated in early January and this flow will become unmaintanable but usable in its current form.
This grant will deliver the following:
This proposal would benefit the raku community by providing a means of running a raku compatible ecosystem with strict auth, user management, group & role management. This would be a major lift for the raku ecosystems as it would decrease the reliance on shoe-horned solutions such as CPAN/PAUSE and manually maintained list of git repositories. This would also make raku more appealing to organizations considering raku as it would allow for centralized and private module ecosystems for private or proprietary code using already published, publicly available tools such as fez or mi6.
As the solution becomes public this also allows for collaboration with raku developers in fixing bugs, introducing new features, and improving security/reliability of an ecosystem.
This schedule will flow as my time allows as I currently have a day job and this happens around that schedule but will take less than a calendar quarter from the start of work.
This amount does not include operating costs and there is no intent to seek operating costs for the zef:
ecosystem.
220 hours * $60USD = $13,200
]]>2023 saw the publication of the second TPRF prospectus. This provides a valuable tool to share the aims and activities of the Foundation.
The 2024 prospectus is in development and will be published ahead of the annual conference in June in Las Vegas (https://tprc.us/tprc-2024-las/). If you have feedback on the 2023 prospectus or input to the next publication, please get in touch in February by emailing amber@perlfoundation.org.
This year, we are likely to see a greater shift across the digital world, and the most significant regulatory development our industry has experienced, particularly in the domains of security and sustainability. There is lots to do.
Our continued development is driven by initiatives from the volunteer board supported by a paid administrator and dedicated community.
I would like to express my personal gratitude to my fellow board members as well as the efforts invested by everyone across the Perl and Raku communities.
We must also not forget the wider Open Source and commercial communities and organisations whose work we build on.
Our conferences, administration, operations and support of the maintainers would not be possible without support from our sponsors and for this, we are all grateful.
With two nominations in 2023 (https://news.perlfoundation.org/post/ruthboardqapp, https://news.perlfoundation.org/post/bruceboardapp), I am pleased to announce that the Board voted in December and both candidates have been invited to join the board in January 2024.
I welcome both Bruce Gray and Ruth Holloway to the board of the Perl and Raku Foundation.
With this additional capacity, we expect that we can strengthen community support, and better develop fund raising.
Also, Todd Rinaldo will be taking on the infrastructure role for TPRF.
For the coming year, we will focus on developing sponsorships and funding. This includes increased outreach to current sponsors as well as identifying the significant users of Perl and Raku. This is important more than ever given the regulatory landscape changes.
> Do you work for a company who relies on Perl or Raku? What can we do to better support them? Would they support the Foundation, to support the sustainability and development of the languages and associated projects? If so, do get in contact with hello@perlfoundation.org
Our standing priority is to continue to support the Perl and Raku communities through our regular activities such as grant and fund management, legal and administrative matters, and conferences, plus many others.
Please share our prospectus and tell us what we should include in 2024, join us in Las Vegas and see how you can get involved https://www.perlfoundation.org/get-involved.html
Want to get to know us? Join the monthly communities meeting every third Friday of the month 17:30 UTC. You will be able to join us online using this Zoom Meeting: https://us02web.zoom.us/j/89049224605?pwd=cU5sTVdDR0x4bnRFQU4zR2dRQ0o2dz09
]]>We have received a Grant Application from Narcisse Mbunzama from the Democratic Republic of Congo. He has a track record in AI and Digital Security. He has previously applied for grants. The grant applied for relates to a planned hackathon; although the timeline for funding looks tight, for the purposes of this appication may be ignored; the dates are flexible. Personally I do find that the Open Source Community benefits globally whatever our backgrounds and cultures. Open Source Programming in general helps to level the IT playing field, and Perl has a critically important role to play.
2024 Perl Hackathon Day in the Democratic Republic of Congo
Narcisse Mbunzama
The 2024 Perl Hackathon Day in the Democratic Republic of Congo is an initiative designed to bring together developers, students, researchers, and Perl enthusiasts for a collaborative coding event. The primary objectives of this project are to facilitate learning, address coding challenges, fix bugs, and encourage contributions to Perl libraries. Beyond the technical aspects, the event aims to foster the creation of an active Perl community within the DRC and to promote the use of Perl programming language in the country.
Date: February 13, 2024
Location: Kinshasa city, Democratic Republic of Congo
Participants: Over 40 developers, students, and researchers from various regions of the DRC
Agenda: The event will include coding sessions, discussions, and collaborative projects focused on Perl development. Keynote speakers and mentors will be invited to provide guidance and insights.
I’m the Director of the DRC Developer Association, based in Kinshasa, with a rich background encompassing over 10 years of experience in coding across various programming languages, prominently including Perl. My commitment to advancing the programming community is evident through the series of coding training sessions and meetups that I have consistently organized since
I have demonstrated exceptional leadership and organizational skills in orchestrating a variety of tech events in Sub-Saharan Africa. My passion for fostering collaboration and knowledge exchange within the tech community is reflected in the successful coordination of meetups, workshops, and hackathons.
With a deep understanding of Perl and its application in diverse programming scenarios, I’m wellpositioned to spearhead the 2024 Perl Hackathon Day in the Democratic Republic of Congo. My extensive experience in community engagement, coupled with a track record of organizing impactful events, makes me an ideal candidate to drive the initiative. My dedication to promoting tech education and building a strong developer community in the Democratic Republic of Congo is evident in my consistent efforts over the years. My leadership role in the DRC Developer Association underscores my commitment to advancing the programming landscape in the region. As the director of the DRC Developer Association, I’m poised to leverage my expertise and network to ensure the success of the Perl Hackathon Day, contributing to the growth of the Perl community in the Democratic Republic of Congo and fostering lasting connections among developers, students, and researchers.
$5000 USD: The requested grant will be allocated to cover venue costs, promotional materials, food and drinks, and any additional logistics required to ensure the success of the Perl Hackathon Day in the Democratic Republic of Congo.
]]>This is the first report of Paul Evans' successful grant award. He continues his contributions to the Perl Core. His work is diverse and related to activities out of sight of much of the community. Currently we attribute much of the work of integrating a robust Perlish OOP Paradigm into the Core to Paul, but as member of the Perl Steering Council he has his hands on many components of this very important language. This is a tricky balancing act, respecting parts of what we like about Perl and retaining backwards compatibility, while at the same time making the core progressively more robust and feature rich. It is difficult to collect all his contributions to Perl but as part of his grant he has submitted three security releases in November and in December added av_unshift_sv
into Perl's Core PR #21731.
Date | Activity | Hours |
---|---|---|
**2023/11/25** | *Security releases * | **2** |
**2023/11/26** | *Security releases* | **2** |
**2023/11/28** | *Security releases* | **3** |
**2023/12/18** | * avunshiftsv - PR#21731* | **1** |
Within the vibrant tapestry of Perl and Raku conferences, Geoffrey has gonged hundreds of lightning talks at over fifty conferences on two continents, a testament to his enduring passion over two decades. At just five minutes each, Lightning Talks, a term coined at YAPC, give the experienced speaker a chance to start small. But his contributions extend beyond the limelight, as Geoffrey has been an orchestrator of conference magic, weaving his wizardry into the planning realm for over a decade. His legacy is etched in the collective memory of Perl and Raku enthusiasts worldwide, a luminary whose impact transcends the boundaries of time and space.
“Have Gong - Will Travel.” Since YAPC::NA 2003 in Boca Raton, R Geoffrey Avery has been the Keeper of the Gong, running the Lightning Talks at more than 50 Perl conferences on two continents. At just five minutes each, the Lightning Talks give the experienced speaker a chance to cover an extra topic quickly, or a new speaker the chance to start small. Today’s first time speaker could present a keynote a few conferences later. Are you ready for your five minutes of fame?
Since YAPC::NA 2011 in Asheville, Geoffrey has been part of the team organizing the conference in North America.
As announced previously, we will announce one award recipient every year. We plan to announce the 2024 recipient in December 2024. Geoffrey is always looking for the next speakers. Get in touch with him to speak in the Perl Conference 2024.
]]>