On Wed, Mar 14, 2018 at 4:32 PM, Mike Drob <md...@mdrob.com> wrote: > On Wed, Mar 14, 2018, 2:26 PM Billie Rinaldi <billie.rina...@gmail.com> > 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. > > 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? > > >
