I have a lot of modifications that are required on a new pligg install: - Complete rewrite of the facebook connect module to work with a custom facebook share module using the facebook graph api [Facebook share module needs to be created]. - Allow publishers [site owners] to submit rss feeds direct to pligg. - Each submitted post to extract the following: .url .title .meta description .meta tags . post category - Comments possible via facebook connect. - Auto publish certain post [ones from rss feeds] and some others specific ones without the requirement of a captcha. There is a much more detailed listing here of what is needed: Please read through it well, it is a rough spec' but it covers a lot of what is needed. [url removed, login to view] I am happy to talk with any coder about this in the messaging and explain more about exactly what this will do. But essentially anyone familiar with pligg/facebook/php will be able to do this in a breeze.
1) All deliverables will be considered "work made for hire" under U.S. Copyright law. Employer 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 employer on the site per the worker's Worker Legal Agreement).
2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
3) 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 Employer's environment--Deliverables must be installed by the Worker in ready-to-run condition in the Employer's environment.
b) For all others including desktop software or software the employer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this project.