- Mission Statement for Byte Club
- Possible changes to Skyward / school tech in general
- Groups for development of the school app
Mission Statement:
We talked about various things that need to be included in our mission statement for Byte club. The main sentences that we want it to encompass are listed here, but we haven't decided exactly what the mission statement should be (if you have any suggestions for an elegant mission statement that has all of these points, talk to a Byte Club officer / Ms. Reed / Dr. Murray)
- Furthering our education in computer science
- Using new computer science information to help the community.
- Mentoring people in computer science (community or in the club).
- Working on team skills.
- Promoting computer science in the community.
Possible changes to Skyward / school tech in general:
We also talked about a few things for how Skyward could be made better by making some additions and changes. We also lightly talked about making a few things for the freshman or the guidance office.
- Automating scheduling for guidance office (you would be able to sign up for a time on Skyward, and could just arrive at your confirmed time to meet with them)
- Skyward itself -- some students have complaints about the new system. The UI in general isn't very easy to check point values for assignments with, as Skyward now prefers to just list the percentages that you got from assignments. You need to do more work to see how those percentages were weighted (whether your 100% was a 50/50 test or a 5/5 homework assignment)
- An alert system for the freshmen. Since the students in ~2 years or so will all have laptops, we should be able to make a windows alert app for them. This would revolve around all the laptops being Windows, so we could easily enough make an app that connects to a server that would display alerts on the freshmen's computers for if something happens (if they have school or not, when important events are, etc.), similar to the Skyward emailing system that is currently in place.
Groups for development of the school app:
Finally, we discussed logistics of creating the school app. We discussed in layman terms what the different parts of the app are and how they interact with each other, but we don't know enough to create the app itself. So we created these subgroups listed below and are choosing a few people to look each of these up, become an 'expert' on it, and create a mini-Powerpoint / Prezi / etc. to explain to the other groups more in-depth how their part of the app works.
- Data Scraping / Analysis
- Storage Structures (think SQL / MySQL / NoSQL)
- App Engine (Endpoints)
- Database Management
- UI (within UI: Sound, Art, and Look)
After discussing this meeting, we promptly adjourned and haven't decided on the next time to meet (we're probably going to meet bi-weekly on Skype or in person).
