Hmm, we're getting a bit off topic, I fear. There are lots of very useful packages available for Pharo (and tons more historic ones). They become easier to use/find if: - they are in a public monticello repository - they have documentation (internal and external) - they have a metacello configuration - they have their metacello configuration where the configuration browser can find them - they have a CI job - they have metacello catalog methods (very new) What Stef wants it to make it even easier for people to learn about what is available using a nice, sexy catalog you browse. Call it marketing, sales, a store, a marketplace, the name does not matter a lot (but I agree, if no actual sales for money are involved, and it would not, the name should not be confusing). So, let's make the catalog real ! On 12 Mar 2014, at 14:41, Sebastian Sastre <sebastian@flowingconcept.com> wrote:
On Mar 12, 2014, at 10:27 AM, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
If it's not on sale, I wouldn't name it market nor store. :)
+1
Which leads to the question:
can my company sell a product there? how? what are the steps?
I donât want to sound brutal here but market is raw, so I say this as a realist friend:
If thatâs not clear first, then naming it "store" would not make it one
Said that, itâs certainly an innovation in our niche worth exploring.
U8 is trying that model, not sure about resultsâ¦
so low expectations, but starting has a lot of merit
Without the start you donât even have the chance
So, looking forward to hear news about this
PS: hey.. BTW.. releasing a crazy idea here⦠what about making the other part of a market? I mean the demand. Do we even know what the demand is or would be? A Pharo market place would have a place to submit a demand? like making an offer to pay X for mapping some Y API for example?
Would that make sense?