CSRDU Initial Meeting Points

An initial CSRDU strategy meeting was held last week where we discussed some very important matters regarding the present and future of CSRDU. We came up with some important points about the goals, objectives and working of CSRDU. To facilitate a transparent working system, we’re posting this information on our blog so that newcomers can better judge how their interests can align with our goals. Remember, though, that CSRDU is a work in progress. All comments, criticism and suggestions are more than welcome. Please raise your voice if you have something to say. We would be glad to listen if there’s even the slightest chance it can lead to improvement.

Goals and objectives

The first and foremost objective of CSRDU would be to create a platform for individuals to share their work and achievements with a group of like-minded people. This would provide motivation and support to hard-working individuals in the dwindling quality of ethics and morals we all have to face in the current environment.

Members of CSRDU will keep their original affiliations. CSRDU does not aim to become a full-time work organization. It will (for the foreseeable future) remain a volunteer-based organization. Members would contribute their works to the platform, help each other out as mentioned in Objective #1 and receive help in turn. We would like to stress that members should respect copyrights/intellectual property rules of their parent organizations and only contribute material that they know would not cause any trouble ‘at home’.

CSRDU will include in its scope, all aspects of research and development related to computer science. This includes pure research aspects (such as publications and technical and scholarly articles), pure market-oriented development efforts (including but not limited to web and desktop development, system administration, consultancy etc.) as well as an amalgam of the two in the sense of research prototypes and proof-of-concepts.


CSRDU aims to be a vibrant community where members actively contribute to the rest of the group. To motivate this goal, we decided to have two ‘categories’ of members. One would simply be called ‘CSRDU members’ and the other would be ‘Contributors’. Any new entry to the Unit would be ranked as CSRDU member. In order to get in the contributor category, a member has to simply contribute something to the CSRDU in general and the CSRDU site in particular. For example, a member may decide to:

  • show-case their past efforts/projects/research on the CSRDU website,
  • write a tutorial, article or post for the CSRDU website in accordance with the CSRDU objectives. Section ‘Articles’ below covers details of this, or
  • take responsibility of the activities being carried out in CSRDU.

It is currently the general opinion that anyone should be allowed to join CSRDU in the ‘member’ position. Therefore, we encourage you all to invite others to join CSRDU. The only constraint must be that they should feel comfortable with the goals, objectives and working of CSRDU. We recognized the fact that this may lead to a lot of unwanted burden on the site but it was decided that the member-contributor distinction can reduce this problem to a great extent. In the future, a better hierarchy may be devised that can further reduce this issue.

Those members/contributors of CSRDU who are in the position to guide the youth (i.e. students) may use CSRDU as a starting point for training young students. We have a wide range of expertise in different group members, which will inshaallah grow in the future. We may be able to leverage this strength to better guide the enthusiastic students even if they do not wish to work in a field we ourselves specialize in. In this way, CSRDU can become a network of experienced individuals willing to share their knowledge and expertise with others.

For the time being, CSRDU (as an organization) will refrain from taking up projects. Individual members/contributors can do their work as they normally do but use the CSRDU platform to enhance their efforts. Financial decisions will remain under the sole discretion of the member/contributor who initiates the project. This may change in the long-term but for now, it was decided that this should be the way to go.

Rules of CSRDU will be formalized as time progresses. The informal nature of this gathering mandates that strict policies be formalized only when we are sure of the stakes more clearly. This will be a recurring task.


Articles on CSRDU site can be of many types.They can be purely technical as in tutorials for specific purposes. Most of CSRDU members are experts in their areas and sharing this knowledge with the rest of the group can be very helpful to everyone — contributor and readers alike.

CSRDU is also looking for more general articles such as those related to education etc. This is where the greater audience/contributors can take part in our efforts. If you know someone who has a thought that needs an audience, invite them to contribute their work to CSRDU. We’re keeping this aspect pretty open. Anything that might in any way be considered useful to the community in general is acceptable.

To ensure high quality of work that appears on the CSRDU site, we are going to follow a write-edit-proof style in our posts. Contributors would propose drafts of their work and an editor who is proficient in writing will look over, edit and proof-read the article. The final work will get posted on the CSRDU site. The contributor may take the edited article and post it on their own site. This would not only enhance work quality at CSRDU site but also provide motivation to the original contributors as the quality of their work on their own site would also improve. We would only require that if a CSRDU edited work is posted on someone’s site, they mention CSRDU in acknowledgment. This can simply be a single sentence of the form, ‘this work was edited by CSRDU and appears on the official site at ‘.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="">