Our lives are already so flooded with advertising, spam, and scams... do we
really want another vector to watch out for, be irritated by, and ignore?

Gary


On Fri, Aug 22, 2025, 04:53 Olivier Lamy <ol...@apache.org> wrote:

> Hi,
> While having a play with npm recently, I came across this message:
> 117 packages are looking for funding
>    run `npm fund` for details
>
> That got me thinking, why don’t we have something similar in the Maven
> ecosystem?
>
> Plenty of the artifacts published to Maven Central come from
> individuals who’d probably appreciate a small donation (a bit of “beer
> money”), or from companies that provide professional or commercial
> support for their open-source libraries. GitHub already offers a
> funding button, but in the Maven world, we don’t help surface this
> sort of information.
>
> So here’s an idea: what if projects could include
> documented/formalised metadata in their POMs that Maven core and/or
> plugins could use? Since we can’t change the POM structure itself, we
> could start with some standardised properties, for example:
>
> <properties>
>   <support.commercial.0>URL</support.commercial.0>
>   <support.eol.0>DATE</support.eol.0>
>   <support.security.0>DATE</support.security.0>
>   <support.commercial.1>URL</support.commercial.1>
>
>   <funding.url.0>URL</funding.url.0>
>   <funding.url.1>URL</funding.url.1>
> </properties>
>
> We could then imagine new goals such as:
> - dependency:fund
> - dependency:support
>
> And, just like npm, Maven could finish the build with a simple summary:
>
> X artefacts have commercial support or are looking for funding
>    run mvn dependency:fund or mvn dependency:support for details
>
> To be clear, this isn’t about Apache Maven requiring the metadata, but
> rather about encouraging a general convention for artifacts in Maven
> Central.
>
> What do you reckon?
>
> Cheers,
> Olivier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Reply via email to