Home | MyGov

Accessibility
Accessibility Tools
Color Adjustment
Text Size
Navigation Adjustment
Screen Reader iconScreen Reader

Policy on Collaborative Application development by Opening the source code of Applications

Policy on Collaborative Application development by Opening the source code of Applications
Start Date :
Jan 01, 2015
Last Date :
Nov 30, 2014
04:15 AM IST (GMT +5.30 Hrs)
Submission Closed

The Policy on Collaborative Application development by Opening the source code of Applications intends to increase the pace of application development and rapid roll out/ ...

The Policy on Collaborative Application development by Opening the source code of Applications intends to increase the pace of application development and rapid roll out/ implementation by adopting the principles of open-source development model. Government wants to promote reuse of existing developed applications. Successful running applications and new applications are envisaged to be developed within the public domain by opening the application source code and it is also intended to encourage innovation inside and outside Government by encouraging collaborative development to achieve better products in less time.

e-Gov application source open approach—including the use and release of application source to public—can reduce costs, reduce development time, and improve overall quality, including security through increased transparency and mass peer review.

We invite your attention and comments on the Policy on Collaborative Application development by Opening the source code of Applications

Last date for sending your suggestions is 30th November 2014.

Reset
Showing 3388 Submission(s)
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
• “I need to share my workspace with others during demo days.” • “If anyone calls for me, tell them I’m not here unless they’ve called with the new budget numbers.” All of the scenarios above are examples of policies that are common in everyday use. Users want the ability to regulate access to their information and personal space, and to govern how the system will respond to events. contd..
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
Further, they represent common desires of users and have obvious utility in collaborative settings. If we can capture these sorts of common, easy-to-express desires in our system, then we will be close to supporting the rich forms of policy usage that we see in the workaday world. • “I don’t mind people in my workgroup knowing what I’m working on, but others...” • “Don’t let anyone bother me when I’m working on my thesis. Unless it’s my advisor of course.” contd..
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
ACCESS CONTROL AS A BASIS FOR POLICY The notion of policy is broad, even in the non-technical usage of the word. How can we devise a formal system that allows us to capture the extremely general set of controls that users may wish to place on their environments? At this point, we present some examples of policies to drive the presentation of the formal policy system. The policies below are defined in common, everyday language and are immediately obvious as policies in the non-technical sense of
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
• Require less effort from users. Move the burden of dealing with most user and application actions from the user to the system. Additionally, the use of policies in the context of collaborative systems imposes a potentially competing goal: • Do not stifle interaction. The policy system should not be so restrictive that it discourages or artificially limits the interactions between participants in collaboration. contd..
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
1. A policy describes a general contingency against which specific events are evaluated and handled. The goal of a policy system should be two-fold • Reduce unpredictability in the system to a “manageable level. Allow the system to respond in expected ways to the actions of users and other applications, and support the principle of “least surprise.” contd..
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
For technology standards such as HTTP, XML, and Java, software vendors are expected to implement these standards in their products. However, there is little incentive to do so as the implementations provide very little differentiating features and customer value add. For this reason, OSS provides an effective mechanism for creating a common implementation that drives the adoption of these standards. The Apache web server is a good example of an open source application which drove the HTTP standa
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
6. Open Business Models: a goal of a Software Innovation Network is to create an ecosystem of organizations, commercial and not-for-profit, that benefit from a common platform. These organizations will employ a variety of business models and strategies. Therefore, it is important to ensure that the choice of license and governance model allows for maximum flexibility contd..
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
5. Establishing the IT Infrastructure: the IT infrastructure required to host a community software innovation network is non-trivial. Typically, open source collaborations require a web site, source code repository, bug tracking database, wikis, mailing lists and newsgroups. Consideration needs to be given to the ongoing administration and management of the associated infrastructure. contd..
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
The network effect of smaller communities within larger communities has also proven beneficial for starting new projects. A significant challenge for any new community is generating awareness and participation. Well established organizations like Apache and Eclipse allow new projects to leverage the larger community to raise their profile with potential community members. contd..
Arun Kaliappan
Arun Kaliappan 11 years 9 months ago
i) making it easy to extend the technology; and ii) having an open development process that is transparent to all. Participation then occurs by those individuals contributing directly back to the project or building new technology on-top of the base technology. The end result is an ecosystem that adds the needed components for quick adoption of new technology. contd..