You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a concept of "primary" vs "satellite" libraries, largely based on whether the library is more managed by its originator vs TL as a whole. We should make sure that:
We have a crisp statement about what these concepts mean.
We know exactly which libraries fall into which categories.
Note that probably the large majority of the ecosystem falls into the larger satellites. (Eg, Davenverse and http4s are each north of 40 libraries.) We should think about how to present these as a coherent ecosystem while still giving the individual projects their due, but step one is making sure we know what they are.
The text was updated successfully, but these errors were encountered:
jducoeur
added
the
marketing
Tasks that are needed in order to create a more unified and coherent TL "brand"
label
Jul 19, 2022
There are two levels described in the charter: Organization Projects (section 8) and Affiliate projects (section 9). This replaces the old "member" vs. "incubator" delineation. The newer model is not yet explained anywhere in non-charter speak.
jducoeur
changed the title
Clarify which libraries are in which state
Clarify which libraries are in which state (aka, map out the ecosystem)
Jul 19, 2022
We have a concept of "primary" vs "satellite" libraries, largely based on whether the library is more managed by its originator vs TL as a whole. We should make sure that:
Note that probably the large majority of the ecosystem falls into the larger satellites. (Eg, Davenverse and http4s are each north of 40 libraries.) We should think about how to present these as a coherent ecosystem while still giving the individual projects their due, but step one is making sure we know what they are.
The text was updated successfully, but these errors were encountered: