We have made some project with adding to our committer list and the PPMC [1].
We have also upgraded our POMs to use Apache in the name - but it will be many months before all of our modules have releases, so it will be a while before this starts to become more visible. If there are no objections, I intend to open a vote thread in the next few days. [1] https://incubator.apache.org/clutch/pekko.html On 2024/01/24 05:49:08 Matthew de Detrich wrote: > > There is an issue with project naming here [2] as the names need to be in > the form “Apache …" > > So regarding the project naming with Maven Repository being an Apache rule, > this entire thing is fishy > and I will explain why. > > What you are seeing at https://mvnrepository.com is a pretty printed field > of an > XML file (specifically pom.xml) which is not even meant to be human > readable. For example with > https://mvnrepository.com/artifact/org.apache.pekko/pekko-stream_3/1.0.2, > when you see "Pekko Stream" > there is no such data inside of the pom.xml that states "Pekko Stream". You > can view the pom.xml yourself > at > https://repo1.maven.org/maven2/org/apache/pekko/pekko-stream_3/1.0.2/pekko-stream_3-1.0.2.pom > and > what you see is that there is a <name>pekko-stream</name> xml node which > the https://mvnrepository.com > is manually parsing and then pretty printing as "Pekko Stream" which is > what you see on the website > > I have made a PR at > https://github.com/mdedetrich/sbt-apache-sonatype/pull/31 > that adds the `apache-` prefix to the <name> xml node so that > https://mvnrepository.com will display it as > "Apache <x>" where <x> is the name of the artifact after the pretty > printing but the point I am trying to > make here is that its completely unclear what this <name> field should > actually be and I would like to see > where the formal ASF for this is. > > Normally the <name> field is the same as <artifactId> which is why its > pekko-stream in the first place but > I have no idea whether the <name> (using the Pekko Stream example) should > be "apache-pekko-stream" > or "Apache Pekko Stream". > > On Sun, Jan 21, 2024 at 9:15 AM Justin Mclean <jus...@classsoftware.com> > wrote: > > > Hi, > > > > The Pekko website has some minor issues regarding our trademark policy, > > e.g., the use of trademark symbols. > > > > There is an issue with project naming here [2] as the names need to be in > > the form “Apache …" > > > > Who manages this? [1] Does the entire PPMC have access to manage it? > > > > But they are very minor concerns. My main concern is the small community > > size. Only a couple of people contribute significantly to the project. > > Also, during incubation, only 2 committers and 1 PPMC member have been > > added, we usually expect a minimum of 3. > > > > Kind Regards, > > Justin > > > > 1. https://twitter.com/ApachePekko > > 2. https://mvnrepository.com/artifact/org.apache.pekko > > > > -- > > Matthew de Detrich > > *Aiven Deutschland GmbH* > > Immanuelkirchstraße 26, 10405 Berlin > > Alexanderufer 3-7, 10117 Berlin > > Amtsgericht Charlottenburg, HRB 209739 B > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > *m:* +491603708037 > > *w:* aiven.io *e:* matthew.dedetr...@aiven.io > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org For additional commands, e-mail: dev-h...@pekko.apache.org
