I prefer keeping a shorter name.

It feels a bit awkward that a user would have to write
`use apache_fory::Fory` or `use apache_fory_core::Fory`
instead of the more natural `use fory::Fory`.

I created the apache-fory crate as a placeholder to avoid potential
supply chain attacks,
not necessarily as the main crate name for day‑to‑day usage.

If we adopt `apache-fory`, we would need to ask users to alias it in
their Cargo.toml so they can still import it as fory in code. This
does work, but it adds extra steps for the user, and I’d prefer to
keep things simple.

----------------
Best,
Shawn Yang

On Tue, Oct 28, 2025 at 3:49 PM tison <[email protected]> wrote:
>
> This makes sense where avro is named as apache-avro [1]
>
> [1] https://crates.io/crates/apache-avro
>
> Although, Apache Arrow/Parquet/OpenDAL/... has a shorter name. Some of
> them are for keeping the previous usage before being transferred to
> the ASF; others consider that a shorter name is easier to use and
> remember.
>
> I agree with the former, while IMO as a new crate, we CAN use
> apache-foo as the crate name since it won't hurt.
>
> > there is an ASF requirement
>
> If you refer to the incubator guidelines, there are several
> discussions before IIRC on the [email protected] list, and we
> concluded that it's a guideline, not a requirement.
>
> Best,
> tison.
>
> PJ Fanning <[email protected]> 于2025年10月28日周二 15:24写道:
> >
> > Could we consider renaming https://crates.io/crates/fory to
> > https://crates.io/crates/apache-fory? For future releases.
> >
> > With pypi (python), there is an ASF requirement to prefix the name
> > with 'apache'. I'm not sure if we have an official requirement for
> > crates. It would still make sense to me, if we followed the
> > 'apache-fory' naming convention.
> >
> > ---------------------------------------------------------------------
> > 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]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to