Here is my brief take on what defines the community. Many of us got started with WO before anyone came along and told us that we should not want a coherent, consistent, end-to-end stack that mostly “just worked”. So we naively started using it and found that it was a joy to work like this and very productive. When the industry mantra became that we needed to be able to choose our own “industry standard” disjoint, disparate pieces and glue them together using glue, sticky tape, and Spring, we ignored them. Those who joined in after that were either visionaries or insane. I am still not sure where to draw that line!
Which brings us to now. Most of us have decades of experience in software development and much of that using a toolset that gave us a complete scaffolding on which to hang our application specific logic. Dave Avendasora had a good analogy. WO says “You want a house? OK, here is a house that will suit 90% of people, fully built, and here are instructions on how to renovate what does not suit you. Oh, and we are going to surround that house with other houses, schools, stores, and hospitals as you are probably going to want those too”. The industry standard tools say, “You want a house? You don’t want a house. What? Are you stupid? You want total control! You want no vendor lock-in! Look, here is a bunch of lumber and construction tools, a cement, and look a bulldozer! A bulldozer! Go build whatever you need to exactly suit you”. We know how good things can be and we are not willing to settle for less. That is what defines us. That is why we are still here. While some of us, like Andrus, have gone away and re-created part of the goodness and added some new goodness, we are still all influenced by what we witnessed and worked with. Chuck From: <[email protected]> on behalf of Pascal Robert <[email protected]> Date: Monday, July 11, 2016 at 6:14 PM To: "[email protected]" <[email protected]> Subject: Summary of the State of the Community Dear members of the WO Community, At WOWODC 2016, we had many discussions about the future of the community. We also saw many tools to get forward. But before moving forward on the technical side, many attendees made a point: we should find out what unites us. Is this only because of WebObjects, or because we use WebObjects and Wonder for rapid development? Or because most of you are small teams and are doing full-stack development? So, before we decide to replace, or not, the tool stack, we want to know what defines the community and we want for feedback about this. As for the current operations, the WOCommunity Association still stay up at least until January 24th 2017. We have enough money to pay for the hosting and the store for the remaining of the year. We can also save some money by moving some of the podcasts to mirrors and by running Jenkins elsewhere, or maybe everything. If you want to host some of the podcasts (the older ones) or host Jenkins, please notify me. You can listen to the talk here: http://wocommunity.org/podcasts/wowodc/2016/State_of_the_Community.mp4 http://wocommunity.org/podcasts/wowodc/2016/State_of_the_Community_Followup.mp4 Also, Samuel Pelletier created a Slack channel to discuss the state of things, send an email to him or me if you wish to join the channel. Thanks. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]<mailto:[email protected]>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com This email sent to [email protected]<mailto:[email protected]>
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
