Project: Contact Manager + Calendar + File Storage + Message Board
This project is very easy and simple PHP + mySQL project and can be fun!... We can do this on our own but don't have the time, so here's your chance to earn an easy profit:
We are a small company of 3 people who manage a list of contacts. A contact is a person who we have (or will possibly have) a business relationship with. We need a very simple website for our own personal use to keep track of our contacts and schedule (calendar). Each of us will have our own username/password. Since it's for our own personal use, it doesn't need fancy graphics.
We need the following header sections implemented:
**Contacts** | **Calendar** | **File**s | **Message Board**
Quick mock of roughly how I want this multi-tabbed top header to look like (colors do not matter):
_[[url removed, login to view]~phan0054/[url removed, login to view]]
It's just an example. Feel free to be creative but keep it simple. Some examples can be [url removed, login to view] or [_www.dooyoo.co.uk_]
The full project details can be seen here:
<[url removed, login to view]~phan0054/[url removed, login to view]>
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).