I had a very similar dilemma myself when putting together a project of mine a few months ago. However, at the end of the day, I felt that keeping the license of the solution (or core solution) as MIT was the best option irrespective, and my thoughts came from the following areas in which monetisation can be substantiated.
- Labor costs for staff, which include developers, network administrators, and support officers.
- Costs incurred for resources, server infrastructure, office resources and so fourth.
- And of course marketing and sales of the solution.
The key is to communicate this substation, therefore asking customers for donations, i feel, becomes irrelevant if you can do that effectively. So really the gist is "it's great that the software is free but someone has to run it and even more so someone has to keep supporting it".
Ideally, my opinion on monetisating comes from the business model which encapsulates the solution, therefore licensing the end product can just be focused around the tangibles that inherently make up the business side of a SaaS company.
I think the most murky part of this dilemma comes from professional services and enterprise grade solutions because this is where custom and closed treatment maybe needed for the client. Plus other issues come more from a security standpoint and trade secret standpoint than anywhere else. For instance customisation on top of a SaaS platform via APIs or integration work may require the asset (or code) to be closed source from the perspective to satisfy the clients' needs, but this has always been an issue and is not a SaaS centric problem as the argument only comes during the purchase cycle of a company and the IT manager asks the question "can our business trust open source?".
Thanks for the kind words. To answer your question, I can say I had a many reasons to create this document. First and foremost I’d like to create an open source project around these specifications and see if I could generate interest and invite contributors to jump on board. Second, is to provide a working document for the community scrutinize and critique as it’s still very much work in progress, and before committing to building the solution I wanted to ensure what is built is done so in a way that gains acceptance and use.
Also, I see that Cloud and more particularly SaaS has a lot of bias surrounding it’s use both from a commercial and personal perspective. This largely has to do with how SaaS providers store and use peoples’ data. My aim with PAL is to create a flexible solution that takes all perspectives into consideration based on the type of offering and what is acceptable by the customer or user of the SaaS offering.
I could go on further to say that since SaaS has become such a large segment of the Cloud market I also feel it’s important to keep as much of it as open and free as possible as to allow smaller players the chance to offer SaaS solutions. Since the market is largely dominated by Big Tech this is becoming increasingly more difficult and that has a lot to do with the lack of resources available to smaller companies. It may not seem apparent to most people especially those in countries where internet services are easily available but currently where I’m located, a country where the economy suffers greatly, the low cost of establishing SaaS solutions for businesses vs offering custom built in-house solutions is a far more feasible option.
Anyway, I hope the you find the contents of the document useful and helps you in some way with your project :)
Although there are literally dozens of tools out there that aim to facilitate SaaS, if you look at the definition of SaaS and what makes SaaS, SaaS. Things like “on demand” activation, licensing models, and resource management are the key definition points, not so much the nuts and bolts libraries needed behind the scenes.
Being a martial arts / sports teacher with about 20 odd years of experience dealing with both soft and hard styles. I can’t really speak from a formal medical background but only really from an experience and results based perspective.
I see more and more people attending these types of activities because of “doctors orders”. And in many cases I see sports of any from just compliment whatever regiment the doctor has set out for the patient to begin with. I guess this is where physio has its place in the medical world as well, where patients need specific exercises to help with specific injuries.
Anyway, I want to point out the differences between the soft and hard approaches in the martial arts because I think it’s relevant. Not only are both approaches pretty much contradictory to each other but I find that what people find case-by-case within each practice can differ completely, which makes the whole thing quite subjective and difficult to measure.
The hard approaches are more fueled around explosive movements and repetitive training. From the students’ perspective the left to right body movement from this type of training is something that I’ve seen people with strokes or brain related illnesses use as a tool to help rebalance their motor coordination. In some cases I’ve heard people recommend dance because of the left right approach that comes with dancing, so not much to do with the style itself but rather the constant reshifting from the left to the right during training helps in this area, which has more to do with training methodology.
Where as for the softer arts, although you usually have to explain the advantages to the student, soft arts are more geared around slow movement and are aimed around longevity.
Personally I’m a bigger fan of the softer arts, simply because I prefer low resistance training myself, plus anyone with an injury who is looking for a sport, low resistance will be the better approach.
The issue I have with soft styles is that I have read a bit about Tai Chi and the medical studies surrounding Tai Chi. Sufficed to say the medical studies in this particular area have not gone well, in many cases citing little to no evidence that soft styles help with age reduction.
Although the evidence us martial arts teachers rely on are the case studies of our masters, for instance master x from martial art y lived until he was 100 and that’s because he practiced martial art y since he was 10, and so fourth. What I’d find interesting is if there are more substantial studies made in this area, I mean after all finding the fountain of youth is pretty much everyone’s dream.
Though I agree with the sentiment of the article, I believe AMP can easily be thwarted by efficient website structuring and use of libraries with mobile efficiency in mind. What is good about the AMP indexing process is that, I think, Google still favors the non-AMP version of the site if the AMP site is less efficient than the standard version.
Should the threshold not be met, then a reduced, non-interactive version of the site loads using the same HTML, as non critical HTML can be moved into templates if needed, and the "Critical Rendering Path" is used to form a decision on how the site should download the sites' elements using DSO. Since images, CSS and JavasSript make up the bulk of the download footprint.
DSO aims at optimising the footprint via the following concepts.
- Offering only the CSS files relevant for breakpoints just for that device;
- Scaling down images and lazy loading them at the lowest possible resolution;
- Blocking out elements of HTML using "display: none" for areas that wont be loaded; and
- Most importantly, only download the minimum Javascript libraries for non interactive viewing.
There are other features DSO has such as background downloading for full interactive after non-interactive has loaded; prompting the user and asking if the interactive version is to be downloaded later, and a few other things. However, I haven't completed the entire project as I was side tracked with other projects but building a solution such as this that works along side WebPack would be the best senario.
Further, I'm not too sure if there are other solutions out there similar to DSO since I stopped development, but surely sidestepping AMP should be a rather straightforward process.
Although I don't actively lurk on IRC, I do use it from time to time, especially for support for programming or open source projects, as Freenode seems to be the place to go these days.
I grew up using it and found it a great tool for people to connect and even contribute to projects or just programming in general. I feel even to this day, the ambiance created by IRC "back in the day" with all its contrived features such as server linking and splits, channel ops, bots, and opers still haven't been captured by any of the social media giants even today.
The best things I found about IRC were, TCL scripts, Eggrop bots, and all of the Ascii art that people would use.
I’m not too sure if it covers table changes but MySQL comes with a slow log tool which tells you what queries are causing performance issues and if need be help optimize query requests itself, indexing even though is painstaking is perhaps the best way to fix the issue in the long run but to track down the slow queries in the first place and mitigate against them individually I’d use slow log.