[ArchEc] Developer contract for RePEc

Chirag Anand anand.chirag at gmail.com
Mon Dec 31 03:46:32 CST 2012


Hi Thomas,

I went through the FortLee document, and extracted out the major goals
of the project, and put them in the contracting terms. As far as we
are concerned, this will do for the next 6 months, but in the long
term we would have to come up with some thing other than the current
terms. Please take a look at it, and suggest whether we should change
anything there.

Thanks.

On 28 December 2012 11:22, Chirag Anand <anand.chirag at gmail.com> wrote:
> On 28 December 2012 11:15, Thomas Krichel <krichel at openlib.org> wrote:
>>   Chirag Anand writes
>>
>>> We are not looking at hard deadlines, but say give us a list of
>>> deliverables for the next 3-6 months as of now. That would do.
>>
>>   I am working on a plan, and then rethinking things and tossinng
>>   things around. but I got until starting to put somthing into
>>   HTML.
>>
>> http://openlib.org/home/krichel/work/fort_lee.html
>>
>>   This looks now much easier than the ideas I had two days
>>   ago. I will do some more work on this tomorrow, as I will
>>   spend much of the day offline.
>
> Okay that's great. I will extract something out of the current version
> for contracting as of now. Will modify accordingly as when you change
> the document.
>
> Thanks.
>
> --
> Chirag Anand
> http://atvariance.in



-- 
Chirag Anand
http://atvariance.in
-------------- next part --------------
Terms of contract for Rishabh Sharma for working with RePEc as a
developer.

Set of deliverables:
- Do the initial setup for the newly planned ArchEC database
- Implement an object store to store the RePEc archives
- Implement a caching database to help speed up operations


More information about the ArchEc-run mailing list