Open twiro opened 7 years ago
Cool !
I've just added it to the main repo!
I've just added it to the main repo!
...now that was fast 👍
you're ok with these two suggestions? If so I'd add them to the readme of this repo as recommende best practices!
Added symphony-cms-extension
to all my extensions. :-) Should I add symphony-cms
as well?
I am not sure what to do with Members Forms – for the moment I added symphony-cms
there.
Added symphony-cms-extension to all my extensions. :-)
Cool :) Thank you!
Should I add symphony-cms as well?
I'd say why not... makes sense, increases visibility and might improve chances that interested users might stumble upon the repo.
I am not sure what to do with Members Forms – for the moment I added symphony-cms there.
Good question... what about introducing a third label like symphony-cms-utility
? Would make sense in my eyes - there are lots of intereresting utilities for symphony on github which are hard to find, so having a separate "topic" for these repos would definitively help!
All done.
@twiro I'll revise all of ours as soon as I get some time maybe I get @seanVella to update them :P
Haha! Thanks for the heads up, just updated my topics!
Thanks for your feedback & taking action!
So we agreed upon the following syntax for taggig Symphony-related repos:
symphony-cms
symphony-cms-extension
symphony-cms-utility
symphony-cms-ensemble
symphony-cms-event
symphony-cms-xy...
Fine 👍
I took this as a reason to finally add a second chapter to this repo that (among other best practices regarding extension publishing) recommends using the first two tags for extension repos. Would be great to get some feedback and maybe add some more information before releasing it.
I'll have hours of fun tagging those things, haha!
@twiro I should have tagged all "core" extensions and mine. Phew!
I should have tagged all "core" extensions and mine. Phew!
That's great! Thank you very much and welcome back Nicolas!
I guess you'll be super busy these first days/weeks, but if you find the time it would be great if you could have a look at what I wrote about recommendations regarding extension publishing and add your thoughts - especially about the questionable points mentioned here.
And let me know if you know of other extensions-development-resources than the ones I listed here - I'd like to put these information into the master-branch as soon as possible...
I think I've responded to everything, LMK if I miss something!
I am not sure what to do with Members Forms – for the moment I added symphony-cms there.
I think "symphony-cms-members" is also a thing now :)
Thanks. Done.
Looks like github just reinvented "tags" and introcuded "topics" to offer a "completely new way to discover similar repositories":
While this doesn't feel like a big innovation it's still pretty useful and it would be nice to have one or two "official recommended" labels for Symphony that could be documented here and promoted in the community as best practice to be used for tagging github-repos.
I'd suggest...
symphony-cms
for everything Symphony relatedsymphony-cms-extension
for Symphony extensions...as these two terms are pretty distinct and don't interfere with other systems/technologies like solely using
symphony
orextension
does. (sorry for abusing your first extension's repo as example @seanVella - but as topics are pretty new there aren't many symphony-related repos around that do have any topics attached ;)Any thoughts?