Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add charm-dev-12f blueprint #40

Closed
wants to merge 1 commit into from
Closed

Conversation

weiiwang01
Copy link
Contributor

charm-dev-12f blueprint is an educational blueprint for a 12-factor charm tutorial similar to the charm-dev blueprint.

@townsend2010
Copy link
Contributor

townsend2010 commented Jan 29, 2024

Hi @weiiwang01!

Thank you for this!

We have been discussing within the team how best to deal with Blueprints that are closely related or simply different versions of another Blueprint. We've had requests in the past to have different charm-dev Blueprints that specify a different Juju version and we pushed back then because we feel it is confusing for end users to see all of the slightly different but related Blueprints when using multipass find. Also, the way these are now, a beneficial change in say the original charm-dev Blueprint would not be propagated to the other charm-dev Blueprints.

That said, we also don't want to discourage inclusion of Blueprints that help facilitate development either. I think at this point, I would be willing to include a few different charm-dev Blueprints with the notion that we (the Multipass Team) need to make this experience better. The description of the Blueprints will need to be pretty specific to help differentiate the different charm-dev Blueprints.

@weiiwang01
Copy link
Contributor Author

weiiwang01 commented Jan 30, 2024

Hi @weiiwang01!

Thank you for this!

We have been discussing within the team how best to deal with Blueprints that are closely related or simply different versions of another Blueprint. We've had requests in the past to have different charm-dev Blueprints that specify a different Juju version and we pushed back then because we feel it is confusing for end users to see all of the slightly different but related Blueprints when using multipass find. Also, the way these are now, a beneficial change in say the original charm-dev Blueprint would not be propagated to the other charm-dev Blueprints.

That said, we also don't want to discourage inclusion of Blueprints that help facilitate development either. I think at this point, I would be willing to include a few different charm-dev Blueprints with the notion that we (the Multipass Team) need to make this experience better. The description of the Blueprints will need to be pretty specific to help differentiate the different charm-dev Blueprints.

@townsend2010 Thank you for your reply! There has been some discussion recently within our team, and the conclusion is that the charmcraft and rockcraft feature branch (edge/12f) should be merged into the mainstream. If that's the case, then this blueprint would no longer be needed. Instead, I think rockcraft will be included in the charm-dev blueprint. But since rockcraft plays a more important role in charm development, it would be reasonable to include it in the charm-dev blueprint. I will close this pull request and submit a new one once I receive confirmation from the Starcraft team.

@townsend2010
Copy link
Contributor

Hi @weiiwang01!

Ok, thank you for the update. Since you mentioned that this is be closed, I will do that now. We will be on the look out for any PR's against the charm-dev Blueprint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants