Involvement of future batches

[jaid...@gmail.com]

Since ma'am was laying a lot of stress on involvement of juniors, we'll
probably need to do something solid to that end in order to secure
funding.

Here's an idea- why not we make a website, completely public where all
(and I mean all) the information about the project is available. The
editing rights would only be with those involved, obviously.

Eg. It could show who was working on what part of the project, by what
time they are expected to finish etc. Once a team has completed a task,
they could write a small report(nothing very formal) about what they
did - what references they used, if they went to a market, then which
shop, what price, what was available etc, post pics.Plus the code (not
just the end product, but midway also) could be uploaded, difficulties
could be listed.

The reason for all this is that then, future batches would be able to
know what exactly we have done and be able to avoid repetitions, learn
from our mistakes and most importantly build upon what has already been
done. Just a one page report every now and then would make things easy
in the future, we could just use this material while preparing the
reports.

Please reply with comments.
Jaideep

[arjun sarwal]

Yes

I also had the idea of a website which would serve many purposes. Firstly, it would serve as a platform for discussion of ideas. For example we could email profs in universities like stanford,berkley etc (profs who work in the field of robotics) and ask them to give guidance suggestions, and thus in a way be linked to the project via the internet.
Also the website would push the cause of strictly implementing regular documentation of all work done, which would otherwise go neglected.

Although, for involvement of juniors, we'll draft seperate notices subsequently, why not in general, use them for (esp 1st years) for documentation work. As in create a small 1-2 person team responsible for maintaining the website. Their work and involvement would be substantial because, as I estimate, once work on the project picks up momentum, website would required to be updated practically every second day.
These people can later on, when they go to their 3rd 4th year, become more involved in the designing and implementation aspects of the project.

For involving more and more people, my underlying philosophy would be to do recruitment in a phased and focussed manner. For example, first just concentrate on just getting mech ppl (2nd year onwards ) into the project, then 1st years for documentation work...etc. etc.

jaid...@gmail.com wrote:

---

Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.

[jaid...@gmail.com]

Yes, i think it makes sense to involve a separate person for
documentation. I was initially planning to do it myself, but given the
scale of the project, it would be useful to have a dedicated person for
that.

Again, that site should not be for personal communications(for which
purpose, this group may be used) but only for submitting status
reports, uploading code, pics , bug reports etc.

[Arjun Sarwal]

Ok,So as soon as we hav recruited ppl for mech fabrication, and
sufficient momentum has been gained with regard to preparing of the
project proposal, we'll put up notices for the webteam

--
http://www.geocities.com/arjunsarwal85

[Hemant Goyal]

Hi guys,

Its great to see this project being kicked off!

Umm I read parts of the website requirements. We are currntly working
on an official college website.

http://www.nsitonline.in

We already have a webteam, and the entire project can be hosted on
nsitonline. The webteam will provide full support, after taking
permission from the authorities.