juneau-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Blackmon <sblack...@apache.org>
Subject Re: Split Juneau into separate named subprojects?
Date Thu, 17 Aug 2017 19:53:39 GMT
There are plenty of examples of TLPs that operate one or more sub-projects
- sometime each has a separate management committee and sometimes not.  In
some cases sub-projects go on to become TLPs as well.

I agree that juneau-core and juneau microservice are different enough and
each useful enough to be used, documented and branded stand-alone.
However, I would propose we focus on growing one community using all the
great capabilities in Juneau and the PMC can revisit sub-dividing into
sub-projects after graduation.

Sent from Astro <https://www.helloastro.com> for Mac

On Aug 10, 2017 at 8:37 AM, James Bognar <jamesbognar@apache.org> wrote:

I've been wondering this for a while and decided to mention it.

Does it make sense to split up the Juneau Core and Juneau REST into
separate subprojects? (i.e. all managed together, but externally have
different names?) For example, the REST subproject would be rebranded as
Apache Anchorage, and Apache Juneau would refer to only the core
libraries. They would still belong to the same 'ecosystem' and release
schedules, but would just be called by two different names externally.

The core libraries are often used independently of the REST libraries. The
current branding strongly suggests Juneau is a REST library when it's
really much more than that. The 'core' gives the impression that it's not
meant to be used as a standalone feature.

Are there any precedents for a single project being reflected as multiple
TLP names?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message