I haven't been able to spend many brain cycles on this yet. It seems
that we need to define clearly what sort of features we will want to
include. It sounds like one of the best ways to get this started is to
get a sample project up on GitHub. This will help encourage people to
start contributing.
I know you have done some decent leg work in describing some features.
Perhaps we need to discuss them individually on this mailing list.
>
> For example, in this thread,
> http://groups.google.com/group/pinax-business/t/415c539b472ef308?hl=en
> I suggested some possible definitions of "social e-commerce":
>
> * a single vendor offering items for sale with social features like
> reviews, ratings, discussions, etc.
I would imagine this is going to be the most common use case. This is
what we can target the initial project to be based around.
> * a multi-vendor site offering items from many sources, like http://www.etsy.com/
> (or Amazon, for that matter).
I think this will be less likely, but should be considered when
implementing a single vender shop. That way it won't be too hard to
add in or expand out (what we build in initially).
>
> And then, thinking about a multi-vendor site, that could be:
> * multiple vendors in the same social environment, or
> * a multi-tenant hosted environment where each tenant is separate but
> maybe shares some group identity, or
> * something more like WebFaction where each vendor could set up their
> own webspace with Pinax e-commerce edition installed (maybe actually
> hosted by WebFaction), or
> * just an e-commerce project like the other example projects where
> each potential vendor sets up their own hosting, or
> * something else beyond my current imagination.
I see this is going to be pretty specific to how the site developer is
going want to do this. It will likely be outlined in some specs they
get. I'd like to allow as much as possible. Making everything as
flexible as possible giving the site developer a choice of how it
should work.
>
> Each of these possibilities has many obvious and non-obvious
> implications for degree of difficulty, etc.
Very true. I think the initial goal is to keep it simple. Look at
everything in terms of a good Django app and build on things this way.
It should hopefully make everything clearer as features are
implemented.
>
> The reason for all my questions is that I will soon start discussions
> about an actual multi-vendor social e-commerce project which may
> happen next fall or winter. The scope and direction of this project
> have yet to be determined. So I would find what other people have in
> mind to be very interesting.
The idea of a multi-vendor site interests me. My e-commerce site is a
multi-vender, single-vender setup. We sell product from multiple
vendors, but it is all managed by a single vendor (us). I am curious
as to what other people do and how they manage it.
--
Brian Rosner
http://oebfare.com