IDEA: Switch to a shop-specific namespace for github/packagist #314
Comments
|
IMHO, I don't like using SS for anything (just personal feel out of respect). I'm more than happy to contribute to an organisation and don't feel as if this discourages ownership at all. If you simply don't want it on your github profile my thinking could be shopstripe, silvershop. Or you just ditch the silverstripe reference and have a generic name like AwesomeShopPHP(tm) which just happens to have SilverStripe as dependancy. |
|
Thanks @wilr . Yeah, it was good to write all this out to get a feel for what is actually involved. Sounding like its going to be more hassle than it is worth. If shop blows up to become an amazing product in itself, then perhaps this would be worth considering. I guess part of this idea stems from looking at the way swipestripe has its own brand, giving the appearance of an established module. But ultimately a module is only as good as it's code / documentation etc. If I do need to step away for a while, I think the main thing is giving people access to accept PRs who have a sense of ownership. With mark and you as collaborators, I feel more comfortable about that. |
|
I agree with @wilr that I'm not too happy about using |
|
To be honest, I'm not crazy about SilverShop but I could be persuaded. I think there are too many similar names out there - SwipeStripe, SilverCart, in the e-commerce space and plenty of others for other kinds of modules. |
|
How about Shoprlyify ;) |
|
Some ideas:
These are not too great… maybe we could find something that has a name on its own (does the name have to imply a shopping system? "magento" doesn't sound like e-commerce at first, does it?) |
|
I think a random word would work well, though I also like the idea of keeping "shop" in the name to maintain continuity. |
|
I'm with Mark on that, random word would be good. Like Shop / Store rather than cart or payment or anything. |
|
Tough call, especially as this is a potential stopper for us to move on. Maybe we could start with setting up a temporary org - we could just call it |
|
Considering the pain of changing all the paths and services and references etc I'd probably only want to put people through the pain once. Otherwise leaving as the status quo would be my thinking |
|
I was thinking to only do that during development on |
|
@jedateach are you still trading as Burnbright Web Solutions? I wonder would it be an option to just brand it as Burnbright or Burnbright Shop? |
|
Yes, but not in a big way. I think using burnbright will keep the project affiliated with me, whereas I'd like to see it enter some kind of shared domain, where ownership can be passed as needed. |
|
I'm fresh out of ideas. If we put it to a vote - ss-shop vs SilverShop - what would your votes be? |
|
I'd vote for SilverShop |
|
I'd go for SilverShop as well. |
|
+1 SilverShop |
|
+1 SilverShop On Tue, Dec 29, 2015 at 1:51 PM, Milan Jelicanin notifications@github.com
|
|
Looks like almost all the common domains are taken for silvershop (.org, .net, .com, .info), but silvershopmodule.org is available. |
|
silvershop.io is available, and it sounds nice :) If it's ok to participate, I would like to donate domain (and hosting resources if needed) for this project. |
|
Thank you @jelicanin! It's more than ok to participate! I like silvershop.io. Feel free to go ahead and pick up the domain name. Ideally you could share access with myself and Anselm, Will and/or Roman just to make logistics easier but I know with some registrars it's not so easy to do that. Send me an email or find my on Gitter and we can coordinate that and talk about hosting. As far as Github organization goes - any preferences on silvershop vs SilverShop vs silvershop.io? My vote is "silvershop". |
|
silvershop +1 |
|
I also like "silvershop" Maybe something with a stylized coin? Here's an idea:
|
|
@bummzack that's a good start! I remember Thomas from @NobrainerWeb was offering to help with the identity. Thomas I assume you're busy as always, but if you've got a moment, maybe you chip in with an idea here? |
|
Hi guys - yes we are super busy (soon hopefully with a big SS Shop solution!) What would we need to design? Logo, an identity (colours, fonts etc.) a onepage website explaning what SilverShop.io is? A silvershop theme - was thinking that we might do this as a SilverStripe T-shirt shop/Merchandise shop - what do you think? |
|
Sounds good to me. I think the most important step is the identity, followed by the website. When you talk about "theme", do you refer to the current shop templates/css? I wouldn't mind an overhaul of this, but I think most implementations of a webshop will customize the shop appearance anyways. The main thing that bugs me with the existing templates are the requirements that load in extra css files… but that's kinda off-topic now ;) |
|
I agree, perhaps it's a better idea to do a demo shop design |
|
Thomas, that sounds awesome! And I agree with @bummzack's order of priorities. |
|
This is great. Roman I like your "stylised coin" icon idea and I'm very happy to hear that Thomas and his team will be pitching in as well. I think a good next step would be to have a Google hangout or group skype call in the next week or so to iron out what needs to be built and kick around some ideas. This would be specifically around design/branding/theme, not looking at the future of the module as a whole (which also needs to happen but not at the same time). Would anyone be up for organising such hangout? If we held it at 9am GMT or 9pm GMT we could have both EU and NZ/AU folks present. |
|
I'm taking the liberty to use @bummzack's logo as an icon for the github org and twitter until anything else shows up. |
|
Sure, go ahead. Better than the random generated image or an Egg I guess :) |
|
This is now done :) 👍 to the community and everyone. Still finding few bits referencing the old site and still need to get a refreshed site up but github and packagist all good. |
|
Domain silvershop.io is still hanging unused. Also, hosting for demo shop is alocated so please let me know if/when is needed. |
|
Jelicanin perfect! Can you get the domain to GitHub pages? I think that's still my preference for hosting community content since it makes security and deployments easier but I don't know what's happening with demo site or documentation?? |
|
@jelicanin hey mate - remember me?? Sounds good. I agree with @wilr, just point it to the github pages. Regarding the demo shop, you could start by setting this one up on http://demo.silvershop.io: It should work out of the box - then we could always work on refining it. |
|
@anselmdk ofc mate :) Demo subdomain and hosting are ready, site is on the way :) |
|
@jelicanin Done github changes. http://silvershop.io/ now works and can be used :) |
|
it is alive :) |
As this module becomes more widely used by the community, I want to be able to step back from it if needed, and have it survive. I also want to encourage more people to take ownership of the module.
Part of the solution is getting capable maintainers on board, where I've now got @markguinn and @wilr as contributors.
The other part is to rename the vendor/namespace for the module and its submodules. I think this might help to decouple the module from me/my business so it becomes its own brand. Whilst I might loose the benefits of being directly associated, I think this might help to ensure the longevity of the module.
Naming ideas
As
silverstripe-shopwas disapproved, the next best thing isss-shop, as we already usess-shop.orgas the public domain name.Packages could be named as such:
ss-shop/coreorss-shop/shopss-shop/discountsss-shop/shippingss-shop/demoThis kind of naming would result in ambiguous fork names like
jedateach/core.So alternatively we could use:
ss-shop/silverstripe-shopss-shop/silverstripe-discountsGithub redirects
According to this blog post, redirects should all work fine.
Composer / packagist replacement
ajshort recently did a similar migration with his modules:
https://github.com/ajshort/silverstripe-gridfieldextensions (note the redirect)
https://github.com/silverstripe-australia/silverstripe-gridfieldextensions/blob/master/composer.json (note the “replace” block)
I had a few issues during this period with those modules, so I'm thinking that others might find the same.
Github Issues
Github issues apparently can't be migrated with ease. There are tools to automate migrations, but this ends up creating new issues. It might be a chance to tidy up the ~100 odd issues across all the submodules.
ss-shop.org, demo.ss-shop.org, docs.ss-shop.org
May need updating in various ways.
Travis, scruitinizer, gitter
May need updating in various ways.
The text was updated successfully, but these errors were encountered: