The projects is indeed invisible to non committers 🤷♂️ The milestone of course is visible.
On Fri, Feb 3, 2023 at 3:27 PM Matthew Benedict de Detrich <[email protected]> wrote: > > The main thing that I don't like is that you don't seem to be able to > create subtasks of tasks. > > So I think this as a concept is alien to github, there is no such thing as > sub tasks of tasks. At least from what I can tell, you just link tasks to > another (often just by literally placing a link to the task somewhere in > the comment) and if. you want something like "subtasks" or lets say an > "epic" this would be done with labels. > > Thanks for setting this up though, ill try and have a look at it. > > On Fri, Feb 3, 2023 at 2:07 PM PJ Fanning <[email protected]> wrote: > > > I enabled Github projects but am a little disappointed by its feature > set. > > I've never used it before. > > > > https://github.com/orgs/apache/projects/220/views/1 > > > > I'm not sure about access - in theory, any member of the Apache > committers > > Github group can access it. We may be able to invite other people (looks > > like there is an invite box). If does not look like we can make it fully > > public. > > > > The main thing that I don't like is that you don't seem to be able to > > create subtasks of tasks. > > > > The 2 tasks I added are high level and should be replaced with smaller > > tasks. I just added them to see how they appear in the various views. > > > > It could be worth looking at alternatives like adding a page to > > https://cwiki.apache.org/confluence/display/PEKKO or using a shared > > Google Sheet. > > > > > > > > On 2023/02/02 17:26:13 Matthew Benedict de Detrich wrote: > > > Agreed, github projects was created to solve this problem. > > > > > > On Thu, Feb 2, 2023 at 4:18 PM PJ Fanning <[email protected]> > wrote: > > > > > > > We could try using GitHub projects. I would just use the main pekko > > github > > > > repo instead of creating more repos. We have a lot already. > > > > > > > > On Thu 2 Feb 2023, 15:29 Claude Warren, Jr, <[email protected] > > > > .invalid> > > > > wrote: > > > > > > > > > I think we could create a new project called "First Pekko core > > > > prerelease" > > > > > (or something like that) and put all of the issues into the > project, > > so > > > > we > > > > > have a quick overview of all the bits that need fixing before we > can > > move > > > > > on to other modules. > > > > > > > > > > > > > > > On Mon, Jan 16, 2023 at 8:46 PM Matthew Benedict de Detrich > > > > > <[email protected]> wrote: > > > > > > > > > > > Commenting where I can > > > > > > > > > > > > On Mon, Jan 16, 2023 at 5:43 PM Keith Wansbrough > > > > > > <[email protected]> wrote: > > > > > > > > > > > > > Hi folks, > > > > > > > > > > > > > > Following up on PJ's list of key issues remaining and my offer > to > > > > help > > > > > > > out, I've had a stab at working out the status of each of those > > > > issues > > > > > - > > > > > > in > > > > > > > particular, is someone already working on it and if so where? > > > > > > > > > > > > > > I've also identified a couple of other issues I think are worth > > > > > > addressing > > > > > > > at this stage. > > > > > > > > > > > > > > Please can you check I've got this right? Then I can pick an > open > > > > issue > > > > > > to > > > > > > > work on, and maybe others can do so too. > > > > > > > > > > > > > > Key issues remaining in incubator-pekko: > > > > > > > > > > > > > > > * getting the Apache license headers into the source files > > > > > > > > > > > > > > Blocked on https://github.com/apache/incubator-pekko/issues/38 > ? > > > > > > > > > > > > > This is actually done, I have closed the github issue to reflect > > this. > > > > > > > > > > > > > > > > > > > > > * getting the nightlies published > > > > > > > > > > > > > > In progress at > > https://github.com/apache/incubator-pekko/issues/103 > > > > > > > > > > > > Indeed, I am working on this (see > > > > > > https://github.com/apache/incubator-pekko/pull/105). Note that > the > > > > > publish > > > > > > terminology is currently being overloaded, currently the first > > > > iteration > > > > > > of Apache nightlies is working (see > > > > > > https://github.com/apache/incubator-pekko/pull/60) but this is > > > > according > > > > > > to > > > > > > Apache's release guidelines which is basically just copying > > content to > > > > a > > > > > > folder (done by rsync). This is separate to an actual Maven > > publish to > > > > a > > > > > > nexus repo (which is what I am working on now). > > > > > > > > > > > > > > > > > > > > > > > > > > > > * getting the doc site up > > > > > > > > > > > > > > In progress at > > https://github.com/apache/incubator-pekko/issues/99 ? > > > > > > > > > > > > > > > * careful review of the docs to remove any remaining > > references to > > > > > > > > Lightbend or Akka (including logos) > > > > > > > > > > > > > > In progress at > > https://github.com/apache/incubator-pekko/pull/100 > > > > > > > > > > > > > > > * new look and feel for the docs (just so they don't look > > exactly > > > > > like > > > > > > > > the Akka ones) > > > > > > > > > > > > > > In progress at > > https://github.com/apache/incubator-pekko/issues/92 ? > > > > > > > > > > > > > > > * review the automated test failures > > > > > > > > > > > > > > Seems open for contribution - I can't find an issue or PR for > > this. > > > > > > > > > > > > > > > * source and binary distributions > > > > > > > > > > > > > > In progress at > > https://github.com/apache/incubator-pekko/issues/85 > > > > > (see > > > > > > > also https://github.com/apache/incubator-pekko/issues/78) > > > > > > > > > > > > > I wouldn't say this in progress, rather some prototyping/initial > > > > > thinking > > > > > > needs to be done on which sbt plugin to use. > > > > > > > > > > > > > > > > > > > > > * upgrade dependency jars if they have CVEs (unless we need > to > > make > > > > > > > > major changes to facilitate the upgrade) > > > > > > > > > > > > > > This is blocked for now; see explanation at > > > > > > > https://github.com/apache/incubator-pekko/issues/101 > > > > > > > > > > > > > > I also see a few other things that need to be done: > > > > > > > > > > > > > > * Create a migration guide. > > > > > > > > > > > > > I am going to make an issue tangentially related to this because > > there > > > > > are > > > > > > non trivial technical tasks to solve for migrating, i.e. wire > > > > > > incompatibility when migrating currently running Peko clusters. > > > > > > > > > > > > > > > > > > > > * Improve README and contribution guide, e.g., to make clear > the > > > > > current > > > > > > > status and how to help right now (in our pre-v1.0 state), how > to > > > > build > > > > > > and > > > > > > > test locally, etc. > > > > > > > > > > > > > > * Resolve issues identified by podling scan ( > > > > > > > https://incubator.apache.org/clutch/pekko.html - currently > > reports > > > > > many > > > > > > > things missing which we do have; looks like this might be > simply > > due > > > > to > > > > > > > http://pekko.incubator.apache.org/ being a 404 at the moment. > > > > > > > > > > > > > > Thanks! > > > > > > > > > > > > > > --KW 8-) > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: Keith Wansbrough > > > > > > > Sent: Thursday, January 5, 2023 5:17 PM > > > > > > > To: [email protected] > > > > > > > Subject: Re: M0 release for incubator-pekko repo > > > > > > > > > > > > > > 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] > > > > .INVALID> > > > > > > > Sent: Thursday, January 5, 2023 4:58 PM > > > > > > > To: [email protected] > > > > > > > Subject: Re: M0 release for incubator-pekko repo > > > > > > > > > > > > > > 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] > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > 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] > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > 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] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > -- > > 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] >
