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 first draft of package guidelines for inclusion in the setup #25

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Mark-H
Copy link
Collaborator

@Mark-H Mark-H commented Aug 9, 2017

As discussed on the last call, I'd work on a draft for guidelines on selecting packages to include in the setup. This is the first draft of that and I'd love to hear what people think.

@Mark-H
Copy link
Collaborator Author

Mark-H commented Aug 10, 2017

Vasily commented in slack that his extras don't have (public) bug trackers because they attracted too many support questions. Instead bugs are typically reported via email or comments on new release announcements (modx.pro). Maybe the guideline for a bug tracker needs to be dropped or adjusted to allow alternative ways of handling bug reports?

The reasons I included it initially were to make sure there's a place for people to report issues they come across, and also for them to see if a project has known issues, but I can appreciate that bug trackers aren't always the best way to do that (as modmore doesn't have public trackers for premium extras either).

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