Thanks Paul and Damitha! I'll be happy to go out and talk to partners (e.g. there are people I know at MongoDB, MariaDB, TomEE, Jetty, etc.) - but indeed we need to get the basics in place on our end. I am new to this community so not sure how these things can be done.
Setting up a github repo for cartridges: who and how can do that? Adding cartridge catalog to the Apache Stratos website - who can do that? Modifying the front-page of the Apache Stratos site so it has a section on the latest/changed/promoted cartridges - again, who can do that? For blogs, I assume there is no such thing as Apache Stratos blog - is there? Any plans to have one? Dmitry On Wed, Apr 23, 2014 at 4:06 AM, Paul Fremantle <[email protected]> wrote: > Dmitry > > I completely agree. > > Firstly, we need a place for the cartridges to live. I would assume that > these aren't necessarily all going to live in the core codebase. So what > about setting up a github repo for these. > > I also would suggest we start by actually creating a bunch ourselves and > then asking the relevant teams for help in validating. So for example, we > have already seen e.g. MongoDB cartridges, so maybe we could publish a > Mongo cartridge and then get feedback from the Mongo team on what we can do > to tweak it. > > Another useful thing is from a marketing point of view would be to jointly > publish blogs on how to use these cartridges. > > Paul > > > On 22 April 2014 01:21, Dmitry Sotnikov <[email protected]> wrote: > >> Guys, >> >> I suggest that we start reaching out to various teams producing >> application servers and databases and help them create Apache Stratos >> cartridges and promote them. >> >> For that, we need to have a good list of things that we provide to these >> partner teams - so partners understand what they get. >> >> My guess is that they would mostly benefit from technical help creating >> the cartridges and from co-marketing their efforts. >> >> Technical is pretty straight-forward: they can use documentation >> [1]<https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Creating+a+Cartridge>and >> our help, right? >> >> From co-marketing perspective, can we add a section on the website with >> cartridge catalog and also have the latest cartridges and news about them >> promoted on the front page of Apache Stratos? >> >> Obviously we can promote with all the social media channels that we have. >> >> What else do we have in terms of promoting cartridges? >> >> There is no Stratos blog or Stratos newsletter, are there? Are there >> plans to start these? >> >> We can invite them to public hangouts, right? >> >> And they can contribute session submissions to ApacheCon... >> >> Anything else they will get from participating? >> >> I think once we finalize the list of gives, we can create the text we can >> start sending out, and then have a list of the teams we reach out to - >> between us all here we will probably always have someone who knows someone >> in these potential partner teams. >> >> [1] >> https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Creating+a+Cartridge >> >> -- >> Dmitry Sotnikov >> VP of Cloud; WSO2, Inc.; http://wso2.com/ >> email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov >> Lean . Enterprise . Middleware >> >> <http://wso2.com/events/> >> > > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, Apache Member > > UK: +44 207 096 0336 > US: +1 646 595 7614 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > [email protected] > > wso2.com Lean Enterprise Middleware > > Disclaimer: This communication may contain privileged or other > confidential information and is intended exclusively for the addressee/s. > If you are not the intended recipient/s, or believe that you may have > received this communication in error, please reply to the sender indicating > that fact and delete the copy you received and in addition, you should not > print, copy, retransmit, disseminate, or otherwise use the information > contained in this communication. Internet communications cannot be > guaranteed to be timely, secure, error or virus-free. The sender does not > accept liability for any errors or omissions. > -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware <http://wso2.com/events/>
