Wiki » History » Version 24
Mario Carrera, 10/28/2015 01:53 PM
1 | 18 | José Badía | h1. gvSIG Desktop wiki |
---|---|---|---|
2 | 2 | Joaquín del Cerro Murciano | |
3 | 19 | Jorge Sanz | Welcome to the gvSIG Desktop wiki, this place is aimed to be used by developers and users of gvSIG that need somewhere to publish their information. Use the links at the sidebar to browse the pages by title or date. |
4 | 1 | Jorge Sanz | |
5 | 15 | Jorge Sanz | ---- |
6 | 15 | Jorge Sanz | |
7 | 22 | Mario Carrera | h2. About gvSIG organization |
8 | 1 | Jorge Sanz | |
9 | 23 | Mario Carrera | gvSIG is a project that is supported by the gvSIG Association (1). |
10 | 1 | Jorge Sanz | |
11 | 23 | Mario Carrera | The gvSIG Association works in the field of free geomatics and use of standards in order to benefit an environment where companies, especially SMEs, can develop their business model around open source software and knowledge sharing. |
12 | 1 | Jorge Sanz | |
13 | 23 | Mario Carrera | We strongly believe in building a space where we succeed in transforming expenses (purchase of proprietary software licenses) into investment (purchase of services) guaranteeing Technological Sovereignty (open source software). A space that will help us to find synergies between public administration, universities and the business world; synergies that allow us to find better scenarios in relation to the management of existing resources and the development of new ethics of business where Sovereignty and Solidarity are reference values. |
14 | 1 | Jorge Sanz | |
15 | 23 | Mario Carrera | In this context we understand the software as a tool, as a means, and never as an purpose in itself. An essential tool, a transformation tool, but still just a tool. This is one of the reasons why the gvSIG events (2) have a strong focus on users of these technologies. |
16 | 22 | Mario Carrera | |
17 | 23 | Mario Carrera | A gvSIG professional structure has been set up to ensure the sustainability of a gvSIG development model based on our principles of Sovereignty and Solidarity. |
18 | 1 | Jorge Sanz | |
19 | 23 | Mario Carrera | Goals of the association include: |
20 | 24 | Mario Carrera | 1. Maintain a small and stable core, |
21 | 24 | Mario Carrera | 2. Have a well-defined API, |
22 | 24 | Mario Carrera | 3. Make it easy for the community to develop plugins, |
23 | 24 | Mario Carrera | 4. Reduce the learning curve in gvSIG, |
24 | 24 | Mario Carrera | 5. Help to train new developers, |
25 | 24 | Mario Carrera | 6. Encourage sponsors of gvSIG developers to contribute new features back to gvSIG for the common good, |
26 | 23 | Mario Carrera | 7. Foster a culture where contributing back to gvSIG is encouraged and supported. |
27 | 1 | Jorge Sanz | |
28 | 23 | Mario Carrera | h2. Day-to-Day technical decisions |
29 | 1 | Jorge Sanz | |
30 | 23 | Mario Carrera | The day-to-day decisions are made by people of the professional structure (there's an architecture and development manager, and a product manager). The Professional Structure of the gvSIG project includes the team that performs all tasks related to the maintenance of the project. This team is responsible for maintaining the following areas in constant contact with the Community: |
31 | 24 | Mario Carrera | - Strategy |
32 | 24 | Mario Carrera | - Commercial |
33 | 24 | Mario Carrera | - Architecture, Development and Publishing |
34 | 24 | Mario Carrera | - Technical Collaborations |
35 | 24 | Mario Carrera | - Documentation |
36 | 24 | Mario Carrera | - Testing |
37 | 24 | Mario Carrera | - Internationalization |
38 | 24 | Mario Carrera | - Communities |
39 | 24 | Mario Carrera | - Product |
40 | 23 | Mario Carrera | - Infrastructure and Web spaces |
41 | 22 | Mario Carrera | |
42 | 23 | Mario Carrera | The main roles at the development area are the following ones: |
43 | 24 | Mario Carrera | - Contributors: Initially, newcomers to the project generally participate in an informal role as a contributor. These types of contributors have no long term responsibility to the project |
44 | 24 | Mario Carrera | - Committers: Contributors who give important contributions to gvSIG (docs and bug fixes) can become a formal “Committer” |
45 | 23 | Mario Carrera | - Module Maintainers: They take some responsibilities as maintaining a module, update some documentation, etc. |
46 | 22 | Mario Carrera | |
47 | 23 | Mario Carrera | h2. Major technical decisions |
48 | 22 | Mario Carrera | |
49 | 23 | Mario Carrera | The gvSIG Technical Steering Committee (TSC), that is composed of the main developers that are working on gvSIG, meet after every final version in order to make decisions about the next version. Currently gvSIG releases 2 versions per year (one version in May and another one in December). Important decisions are published on the gvSIG blog (3). |
50 | 22 | Mario Carrera | |
51 | 23 | Mario Carrera | Decisions about objectives for future versions are collected in the gvSIG redmine “whislist”. (4) |
52 | 22 | Mario Carrera | |
53 | 22 | Mario Carrera | (1) http://www.gvsig.com/en/gvsig-association |
54 | 22 | Mario Carrera | (2) http://www.gvsig.com/en/conferences |
55 | 22 | Mario Carrera | (3) http://blog.gvsig.org/ |
56 | 1 | Jorge Sanz | (4) https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues?utf8=%E2%9C%93&set_filter=1&f[]=status_id&op[status_id]=o&f[]=tracker_id&op[tracker_id]=%3D&v[tracker_id][]=11&f[]=&c[]=tracker&c[]=status&c[]=priority&c[]=subject&c[]=assigned_to&c[]=updated |