Closed michalbundyra closed 6 years ago
@weierophinney It's now updated.
@weierophinney I've added ability to create package in any organization as you suggested. I'm not 100% sure it should be like that in ZF maintainers repository. There are more things should be changed when creating package in another organization.
I've added ability to create package in any organization as you suggested. I'm not 100% sure it should be like that in ZF maintainers repository.
One reason I'm interested in it is for when we prototype packages as individuals that will later be imported to a ZF organization. In these cases, having a custom namespace and package name allows publishing the proof-of-concept such that it doesn't require the ability to be a member of a ZF org in order to register it on Packagist. In the meantime, folks can test it out, refine it, etc. before it becomes an official component — and once it does, it already has the correct structure and expected files.
I found out much easier and clearer to use
symfony/console
than basic script as I did in #26Here is proposition for creating new package from templates, as @weierophinney suggested in https://github.com/zendframework/maintainers/pull/26#issuecomment-342858670 and based on his library weierophinney/zf-component-template
Usage:
The namespace will be chosen automatically if can be determined unambiguously, otherwise the question will be asked with propositions. At the end of the process we have a question if we should initialize git in the package.
Any suggestions appreciated. :smile:
If it will be accepted I'd like to rewrite other commands to use symfony/console and symfony commands.