We've had an ongoing conversation around the difference between template and example repos. The reality is its not as simple as one would think. There are various cases for both types and sometimes they differ in their use. For example, a blog post may have a corresponding repo -- this is an example. But since that blog post was written at a certain point in time, that corresponding repo likely doesn't need to be kept up to date overtime unless we are also updating the blog post. But then there are cases when we have a repo that demonstrates something like a plugin (nextjs and nextjs-example). That repo is also an example and should be kept up to date overtime.
Then we have templates - a starting place for users. we have a lot of these scattered across the organization. We also have tools like create-harper that are meant to help bootstrap things for users and agents. Are all of our tempaltes compatible with that? Or should that tool only support certain templates? When does something cross the boundary from a template to being an example? Like is a basic caching implementation really a template or is that a basic example?
I believe in practicality, by defining what we really want to do with these repos we can help align on an actual organization
This issue can be closed by creating a document explaining the differences and the team agreeing on the alignment. Follow up work can be defining / building additional tooling and procedures for maintaining these repo types. But that will likely happen outside of this repo.
We've had an ongoing conversation around the difference between template and example repos. The reality is its not as simple as one would think. There are various cases for both types and sometimes they differ in their use. For example, a blog post may have a corresponding repo -- this is an example. But since that blog post was written at a certain point in time, that corresponding repo likely doesn't need to be kept up to date overtime unless we are also updating the blog post. But then there are cases when we have a repo that demonstrates something like a plugin (nextjs and nextjs-example). That repo is also an example and should be kept up to date overtime.
Then we have templates - a starting place for users. we have a lot of these scattered across the organization. We also have tools like
create-harperthat are meant to help bootstrap things for users and agents. Are all of our tempaltes compatible with that? Or should that tool only support certain templates? When does something cross the boundary from a template to being an example? Like is a basic caching implementation really a template or is that a basic example?I believe in practicality, by defining what we really want to do with these repos we can help align on an actual organization
This issue can be closed by creating a document explaining the differences and the team agreeing on the alignment. Follow up work can be defining / building additional tooling and procedures for maintaining these repo types. But that will likely happen outside of this repo.