[apparatus-templi] Re: Group Meeting
- From: Jonathan Nelson <ciasaboark@xxxxxxxxx>
- To: apparatus-templi@xxxxxxxxxxxxx
- Date: Mon, 27 Jan 2014 13:23:32 -0500
Wed. 1:00 will work for me. I’ll try to have some documentation/diagrams ready
to help explain the API and component interaction. The assigned sections are
not intended to be restrictions, just to help keep us from stepping on each
others toes. If everyone has a section that they are responsible for then they
can come up with their own implementation, and so long as the interface does
not change everyone else can keep their own code unchanged.
If anyone wants to help with other sections feel free to join in. After the
meeting I think we should all be familiar enough with the components that we
can jump in and help with other parts too.
I wouldn’t worry too much about the coding style for now. There are a number
of tools we can use later to auto-format the code to a specific style.
For the meeting I’d like to go over:
-the system hardware design
-the system logical design
-the API for interacting with the coordinator core
-proposed API for the database interface
-interface between the core and the web server
-interface between the front-ends and the web server
If anyone has other topics they want to cover just tack them on to a reply.
--
Jonathan Nelson
On Monday, January 27, 2014 at 2:31 AM, Christopher Hagler wrote:
> I would like to have a meeting sometime next week, so we as a group can come
> up with a design and a plan on how to implement the project. I know it has
> been a slow start because of not having the equipment, but I would like for
> us to try and get a plan together. We need to design the layout of the
> software, function names, protocols, and whatever else because as of right
> now I feel like we are coding blind. I know I cannot write any code because I
> have no idea how all of the programs are going to interact, or what functions
> are in what class. I would also like to know what everyone feels comfortable
> doing. Instead of delegating parts to individual group members, I want to
> make sure they are interested in it before hand and feel confident in what
> they are doing. Also, I am not sure how everyone likes to code, but usually
> group projects go easier when there is one particular coding style being
> used. I will try to get an outline for topics we can discuss during the group
> meeting, so we can make sure we get everything covered that we need to. If
> there is anything else that anyone wants to talk about let me know and I will
> be sure and write it down so we don't forget about it.
Other related posts:
