Thanks PJ. I hope to put some effort into Pekko over the next few weeks, so this comes at the right time! We have a few components currently using Akka and would much prefer to move to a community fork than either maintain an internal fork or rewrite from scratch. I'll take a look and see what we can do.
Cheers, --KW 8-) -- Keith Wansbrough he/him PRINCIPAL SOFTWARE ENGINEER Azure for Operators Office: +44 131 662 1212 [email protected] https://github.com/kw217 -----Original Message----- From: Matthew Benedict de Detrich <[email protected]> Sent: Thursday, January 5, 2023 4:58 PM To: [email protected] Subject: [EXTERNAL] Re: M0 release for incubator-pekko repo [You don't often get email from [email protected]. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] I agree with the sentiment that in general we should be focusing on pekko-core (in any case it's necessary for all of the other pekko modules). As mentioned in my earlier email today pekko-core is in a good state to work on right now, so it should be quite practical to split out the mentioned work amongst the community. The main technical task to be done is to figure out how migrating from an Akka to Pekko cluster would work. Regards -- Matthew de Detrich Aiven Deutschland GmbH Immanuelkirchstraße 26, 10405 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen m: +491603708037 w: aiven.io e: [email protected] On 5. Jan 2023 at 16:16 +0100, PJ Fanning <[email protected]>, wrote: > Hi everyone, > > I'm going to ignore that there are other pekko git repos. A lot of the > same work needs to be done for those repos but it simplifies the > conversation to ignore them in this thread. We can come back to them > later. > > There has been good progress but there is a lot still to do. Some of > the key issues remaining include. > * getting the Apache license headers into the source files > * getting the nightlies published > * getting the doc site up > * careful review of the docs to remove any remaining references to > Lightbend or Akka (including logos) > * new look and feel for the docs (just so they don't look exactly like > the Akka ones) > * review the automated test failures > * source and binary distributions > (https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit > hub.com%2Fapache%2Fincubator-pekko%2Fissues%2F78&data=05%7C01%7Ckeith. > wansbrough%40microsoft.com%7C7fe1bf8cc3124e5f972808daef3e0352%7C72f988 > bf86f141af91ab2d7cd011db47%7C1%7C0%7C638085346898446381%7CUnknown%7CTW > FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6 > Mn0%3D%7C3000%7C%7C%7C&sdata=nkW09wiJ0vZMOSn%2FR7U8Gql%2FvC820cEaC7%2F > XUdQjfM0%3D&reserved=0) > * upgrade dependency jars if they have CVEs (unless we need to make > major changes to facilitate the upgrade) > > Some of these tasks are in progress but most of the tasks could be > taken on by willing volunteers. > > There may be an argument that we could try an early M0 or M1 release > to allow outside lib maintainers and other interested parties to try > out the new libs. There are probably not many of the items above that > could be delayed to a later milstone though - possibly some of the doc > and test tasks. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For > additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
