Developers should be allowed to monetize their applications as they so wish. I don't see us offering this specific functionality to charge for imports in the future, but you are free to build APIs that you charge for or compiled JARs for sale.
I'm of the opinion, however, that the open source projects that exist are going to be challenging to compete against unless you are able to provide high quality support. On Tue, Mar 9, 2010 at 8:48 AM, mstodd <[email protected]> wrote: > I wouldn't say that I'm ethically opposed to such a code repository, > but it is against the spirit of Google code and Python as a whole. > > If you have something cool to share to the community, rather than > going out of your way to obfuscate it or keep it from the community, > just give it and make the community better. You'll be rewarded more > that way. > > On Mar 9, 9:00 am, Peter Cooper <[email protected]> wrote: >> Please explain how one can include a Python or Java "module" of unknown >> provenance and reliability into a working or developing app, without having >> access to "source." >> >> I am ethically opposed to the concept proposed in this post for a >> "monetized" code repository. For my part, Google should host the Python >> equivalent of CPAN. Google leaves a great deal to developers, as it should >> be, so that apps can evolve naturally. Open source is one methodology for >> natural development. >> >> >> >> On Tue, Mar 9, 2010 at 2:26 PM, pca <[email protected]> wrote: >> > Hi, >> >> > I'm developing a software module for python and I'm looking for ways >> > to monetize it. It's not so easy :-( but GAE could provide a nice >> > answer. >> >> > It would be great if GAE would have a "module store", i.e. a place >> > where developers like me would post a module, and where developers on >> > GAE would be able to select a module from the store, for a licence and/ >> > or maintenance fee, so that they are included in their app. This >> > would also work on the app server, so that developers can debug their >> > app+module locally. They would NOT have access to the source code of >> > the modules though. Also, GAE developers could decide to updgrade to >> > the newer versions of modules. >> >> > Any comments on this ? >> >> > By the way, the module I'm developing implements a rule-engine for the >> > "model" part of the Model-View-Controller architecture, thus >> > accelerating development on GAE. It could be translated to Java too, >> > so the question applies for Java too. >> >> > PC >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Google App Engine" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]<google-appengine%[email protected]> >> > . >> > For more options, visit this group at >> >http://groups.google.com/group/google-appengine?hl=en.- Hide quoted text - >> >> - Show quoted text - > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
