Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 4/23/2018 9:34 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 3693
Template/Type: Brandon Time
Title/Caption: Adilas Time
Start Date/Time: 4/25/2018 9:00 am
End Date/Time: 4/25/2018 12:00 pm
Main Status: Active

Sorry, no photos available for this element of time.


Uploaded Media/Content & Other Files (1)
Media Name   File Type Date Description
email_about_time_clocks_12_10_16.docx   Doc/Text 4/25/2018 This is a copy of an email sent out in December of 2016 with brainstorming ideas about "time clocks" and options to finish up part of the adilas system. Lots of ideas about project time clocks, employee time clocks, scheduling time, and other payroll related items. See also element of time # 2042 for more ideas and info.


Notes:

Talking about PHP projects with Russell. We talked about using Bridgerland and their developers to help build and maintain certain new and existing projects. Russell really would like to work on some developer training courses, API socket training courses, etc. Basically, ways of making it easier to get interested people into the development side of the system easier. We also spent some time talking about other possible projects... these would be built out using PHP and then connected to and/or talking to adilas.biz through external API sockets. Projects like outside scheduling of time (both adilas and google), outside ecommerce sites, visible elements of time (public viewable), project management, and scheduling time for employees. All great options. They would also be great projects for the Bridgerland developers.

We also talked about pushing more and more on the Adilas University site, the Adilas Market (adilas world), play at the wall (web/API sockets), and creating a fun and pretty front facing site. We will fund those projects. We will keep core adilas and custom code behind the wall and keep it internal as far as who builds on it. The rest is open territory.

Russell mentioned versioning our code so that we don't hurt other developers who have already done development. This is dealing with the API and then also making things backwards compatible. Basically, we really want outside developer to play the game and "Play at the wall". Good discussion.

After that, I reviewed some notes about time clocks (see attached for an email that was sent out in December of 2016). I also wanted to make a note that elements of time # 2042, here in the shop, has a ton of information about some of the payroll, time clocks, and project direction. Just trying to keep all of the pieces sorta linked together.

I scheduled a live adilas training session at Bridgerland for May 29th, 30th, and 31st. I let a few people know and will be trying to grab some ideas and such from key users, reps, developers, and admin persons. Good stuff.