We are seeing a need to add an adilas URL (web address) on a per corp level vs on a per server level. Currently, most of our redirect options are all based on a per server basis. Also, we may need to go back in and change some of the existing links and hardcoded web links.

- We need some options for manual load balancing.

- Wayne was showing us his custom functions and how he is combining code into custom tags.

- We also talked about some of the aliases and how certain field names show up. As a side note, we will have to update our API socket documentation to note some of those changes.

- Wayne has been doing some mappings to certain relative and fully expanded paths.

- Lots of simplifying code and things. There is still tons to do, but we are starting to make progress.

- Having a centralized spot to help Wayne know about errors and/or issues with the transition to AWS.

- We need a community based process that allows us to publish wiki type information, definitions, best practices, etc. We may even want some of this wiki info to be automatically generated. We need to keep things up to date to make it relative and productive. As a side note, Wayne has setup and contributed to wiki type things and has some know how there. He will be a great resource on that stuff.

- Ways of harnessing the skills and knowledge to help others. Letting people be part of a cause and participating to the overall adilas community.

- Steve would really like the adilas users to have options to play, work, participate in the adilas community, learn, train, sales, place for their stuff, participate in the marketplace, sell their skills, contribute, etc. This could be part of the adilas marketplace, adilas world, the adilas café, etc. Lots of options.

- Being able to share our knowledge with others. Helping to speed up the process.

- Steve popped in and was saying that maybe we could use our WordPress and/or our news and updates section. We also have help files, web/API socket documentation, developer's notebook, user guides, elements of time, etc. We have also made and created a number of self contained PDF files with specific topics. We would like to make sections for developers (super techy), users (definitions, help files, tutorials, etc.), reps/consultants, community, and other sub sets.

- Currently, there is a deficit on the training and education side of things. We may end up going in and checking stats on some of the older inactive adilas users and see who did what. We also need to open up the adilas market and adilas café to all of the users who have some great and awesome skills and skill sets. That is a great way to even out our tri-facto model of clients/users, system, and education stuff.

- Steve was seeing and talking about co-founders of adilas. It doesn't come from just one person. It comes from a community effort.

Towards the end of the meeting, Brandon went back to doing some prep work on the adilas user guide. As part of that process, he spent some time reading an old history bio from the adilas team. See attached for a copy of the bio. It has a publish date of 2011. Lots of fun info.