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.

Sign up for GitHub

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

Jump to bottom

Change folder names in repo to reflect "community" reference #68

Open
szul opened this issue Jul 28, 2019 · 2 comments
Open

Change folder names in repo to reflect "community" reference #68

szul opened this issue Jul 28, 2019 · 2 comments
Labels
build Related to CI, builds, and/or deployments question Further information is requested

Comments

@szul
Copy link
Contributor

szul commented Jul 28, 2019

Currently, the libraries folder has each package, and each package is prefixed with "botbuilder-". Should we change that prefix to be "botbuildercommunity-"? Should we remove the prefix entirely?

For reference, the NPM packages are scoped to the @botbuildercommunity organizations, so the botbuilder-adapters folder aligns with the @botbuildercommunity/adapters NPM package.

This is more an internal repository structure question/change than anything.

Opinions?
@szul szul added question Further information is requested build Related to CI, builds, and/or deployments labels Jul 28, 2019
@szul
Copy link
Contributor Author

szul commented Aug 31, 2019

Closing for now. Could revisit later.

@szul szul closed this as completed Aug 31, 2019
@szul szul reopened this Jan 4, 2020
@szul szul mentioned this issue Jan 4, 2020
Closed
@iMicknl
Copy link
Contributor

iMicknl commented Feb 11, 2020

To be honest, I would keep it like botbuilder-[package-name] for now. By changing the README in #151, it is already more structured and readable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
build Related to CI, builds, and/or deployments question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@szul @iMicknl