On Wed, Mar 14, 2018 at 9:53 PM Billie Rinaldi <[email protected]>
wrote:

> On Wed, Mar 14, 2018 at 4:32 PM, Mike Drob <[email protected]> wrote:
>
> > On Wed, Mar 14, 2018, 2:26 PM Billie Rinaldi <[email protected]>
> > wrote:
> >
> > > In the active thread "[VOTE] Retire HTrace from Incubation" Christopher
> > > Tubbs brought up the idea to make HTrace a subproject of an existing
> TLP.
> >
> > This would mitigate the issues of the community being inactive and the
> core
> > > instrumentation library not requiring ongoing development.
> >
> >
> > Does moving to a subproject out another tlp necessitate changing Java
> > package names prior to release? That would put a damper on user adoption
> > again.
> >
>
> I'm not sure. I'm not aware of a restriction on the package names of
> subprojects, but that would be a good thing to verify. The subproject idea
> would be less appealing if it still required all the downstream projects to
> change their instrumentation.
>
>
A conversation about package naming came up on the incubator mailing lists
last year [1] (and apparently not for the first time), and the conclusion
seemed clear to me: package naming "best practice" is to have
"org.apache.*", but there's no hard requirement to name packages any
particular way. As long as the namespace isn't colliding with other
packages, I'm certain it would not be a problem to keep the naming of an
already existing "org.apache.*" naming scheme. Maven groupIds are a similar
thing to think about... but I'm sure that wouldn't take more than
coordination with INFRA to ensure repository.apache.org is configured
correctly or to simply adopt the parent project's groupId. Either way, I
can't imagine it being a problem.

[1]:
https://lists.apache.org/thread.html/efff94b00150fefed36f73d09bc90caae66279aba9ed414b329aec85@%3Cgeneral.incubator.apache.org%3E


>
> >
> > It's a choice we could make now (assuming we were able to find a TLP
> > > willing to adopt HTrace
> >
> > as a subproject),
> >
> > The Skywalking podling expressed some interest in the vote thread.
> >
> >
> >
> > or we could allow HTrace to retire and then revisit the
> > > subproject idea at a future time if someone becomes interested in
> > patching
> > > and releasing a new version of HTrace.
> > >
> > > So far, the people who have expressed interest in being involved with
> > > HTrace as a possible subproject are Christopher, Masatake, and myself.
> Is
> > > anyone else in the community interested in this idea?
> > >
> >
>

Reply via email to