Err, OK… next question. How is this set? I can’t see any way to add a tag.
2 Likes
I tend to agree with this, even though we did set up a Classic Commerce area in support. I only see this as a temporary measure. We have classiccommerce.cc registered and I think this will eventually be the place for all support and discussion.
3 Likes
A hidden box 
Discourse has a lot of hidden features, but you should be able to see it when you create a new post:
4 Likes
Ahh… and if you click in the box it shows the tags in use already. That might be a useful feature (if people actually used it).
Are the tags site-wide, or can they be narrowed down to individual categories?
1 Like
Site-wide by default, but we can restrict certain tags to categories if we wanted to 
2 Likes
One of the most important things to me is ease of access.
In my experience to date, people have avoided using GitHub. Any reports of bugs in Classic SEO have been done via the forums which I personally don’t mind.
GitHub is a scary place for a lot of people, on top of which, you need a GitHub account to raise an issue. I just don’t think GitHub is a “friendly” environment for your average CP / WP plugin user.
I’m not saying the forums should be a free-for-all. I’m just saying it would be great to have a single point of access for information relating to a plugin’s development, and where anyone can make feature requests or raise issues with ease.
As for what is a “community plugin”. Given that Classic SEO is a ClassicPress research project, I would certainly consider that a community plugin.
Some people prefer GitHub. Others prefer the forums.
4 Likes
I don’t disagree, I just think it would open a can of worms that doesn’t need to be opened yet. If we were getting double or triple the number of new threads relating to the plugins then I would agree that it would probably be time to open a new category.
I think using tags for now makes sense
1 Like
Agree 
Asking people to raise an issue on github for a problem will eliminate 90% of your input.
1 Like
It’s cool that you don’t mind … it just sets a precedent that I would avoid.
I also mentioned social media. Indeed, I’m not a fan of sending users to GitHub. However, having an account to raise an issue is not much of a hurdle.
I see your point…just feel that encouraging support, release notes, feature requests, bug reports on the forum is not the answer.
1 Like
I think the reality is that this will happen in multiple places. So it may be necessary to monitor them all, and make announcements on them all. You may find you need to cater to different people’s “comfort zones”… for some Github is their second home (definitely not me); some live on social media (not me); I personally use forums a lot, and look in on Slack occasionally (but often miss stuff there as it moves too fast).
If you really want a centralised point then a specific website for the plugin may be the best option, or one for all your plugins (like @anon71687268).
1 Like
This is something we discussed earlier this year in the context of the plugin directory - we’ll need some sort of support forums for plugins, and it seems that this is pretty much the same thing.
Alas, we never decided how to do it, so perhaps this is a good time to revisit that discussion.
3 Likes
Yes, that’s exactly what I’m talking about. And instead of sending people to different websites all over the place (including the forums, slack, github), I definitely think it would be better to have one place where they can go.
My day job means that I don’t have the time to monitor all these different places which is why I choose to visit Slack only on the odd occasion. And to my mind, therein lies a different but related issue - the fact that all these different discussions are happening in different places.
But back to my original point, anything that makes life easier for the ClassicPress user has got to be a priority imho - as long as it doesn’t create problems for developers of course. Likewise, anything that keeps people here on ClassicPress instead of driving them away elsewhere has also got to be good. And remember, I’m only talking about “community plugins” here.
And just one small observation. Classic Commerce already has two forums - one under General Discussion and one under Support so there already seems to be a precedent. But I don’t see worms crawling all over the place. 
2 Likes
Yes, that was an early, messy development and led to a good discussion that clarified things I think. Starting here: ClassicCommerce or Classic Commerce? Status as a research plugin? - #9 by anon71687268
We will be putting the lid back on that can at some stage and I hope not too many worms get out. 
But I agree that it would be ideal to have one central place where you can search for plugins, download them and get support.
3 Likes
To be fair, I forgot that Classic Commerce had a support category (#support:classic-commerce) and a general category (#general-discussion:classiccommerce) so we have kind of already opened that can of worms.
Anyways, maybe a “plugin support” and “general plugin” category with tags enforced would be the best solution here.
1 Like
Whoops didn’t see this.
2 Likes
Maybe just make Plugin Support a subcategory of Plugins?
I think having it under the “Support” category makes sense, since I think that is were people would go first?
But that implies that it is “official” classipress support. I think it makes sense that if people have a problem with a plugin they go to the plugin forums.
2 Likes