Project

General

Profile

JdA » History » Version 10

Jan Niggemann (redmine.org team member), 2015-02-02 17:46
archive page

1 10 Jan Niggemann (redmine.org team member)
|{background-color:#f88}. *This page has been archived and is no longer updated*.
2
Please be aware that the information provided on this page may be out of date, or otherwise inaccurate.
3
The main [[Archive|archive page]] has a short explanation.|
4
5
----
6
7
8 2 Borja Pacheco Ortega
{{toc}}
9
10 7 Borja Pacheco Ortega
h1. Objectives
11 2 Borja Pacheco Ortega
12 9 Borja Pacheco Ortega
# Tell the world our experiences and works around Redmine. Share our ideas, efforts and developed code.
13
# Make our plugins as +*POPULAR*+ as possible.
14
# *+PROMOTE THEM+* to become part of redmine's core project. 
15
# In the future, share maintenance efforts with community.
16 1 Borja Pacheco Ortega
17 9 Borja Pacheco Ortega
h2. Who are we? 
18 1 Borja Pacheco Ortega
19
We are some IT professionals who work at Sadesi (a public company that belongs to "Junta de Andalucia":http://www.juntadeandalucia.es, in advance I'll use the acronym _JdA_). We are happy of working in an organization which is compromised with OpenSource and Quality, Sadesi is compliant with ISO 9001, ISO 20000 (ITIL) and ISO 27001.
20
21 9 Borja Pacheco Ortega
h2. Disclaimer.
22 1 Borja Pacheco Ortega
23 9 Borja Pacheco Ortega
My name's Borja Pacheco and I MUST clarify that I'm talking from a +personal point of view+, not trying to tell you the formal opinion of others (nor Sadesi, CEIC, neither Junta de Andalucia).
24
25
h2. Thanks
26
27
I need to mention to *María José Romero del Toro* and *Francisco José Quintero Morón*, who are an important part of this project and without them, nothing wouldn't be possible.
28
29 1 Borja Pacheco Ortega
h1. Our story
30 7 Borja Pacheco Ortega
31 9 Borja Pacheco Ortega
Since 2010 Sadesi started using Redmine as the main tool to manage our development projects:
32 7 Borja Pacheco Ortega
* We realized Redmine is a very complete and good software.
33
* We assigned to our redmine instance (HGP) the role of SPOC (Single point of contact) among all parties involved into our software development projects (internal clients, our technical staff and providers that builds concrete pieces of a project).
34
* We have used it broadly. Some indicators: 29175 tickets created and 796 active users.... I guess we have one of the biggest implementations all over the world.
35 1 Borja Pacheco Ortega
36 7 Borja Pacheco Ortega
h2. First interactions
37 1 Borja Pacheco Ortega
38 9 Borja Pacheco Ortega
After an initial usage period, we missed out some functionality that wasn't already developed. Our first approach was to make it ourselves. We modified several parts of the code, to avoid tickets without any assigned (we don't want orphan tickets), we linked End-Date and Status to avoid tickets without 100% completing, modified Gantt module, adapted Spanish translations to our current vocabulary, created a simple plugin-menu to facilitate access to other daily tools, made the tree-view plugin operative again and, finally, we made a custom application that uses redmine's data model, for being a bridge between Redmine and our ERP (Navision).
39 1 Borja Pacheco Ortega
40 7 Borja Pacheco Ortega
This experience produced us a "bitter taste", because we found several difficulties:
41
* We didn't want to touch Redmine's core/kernel, but it was not possible in all cases. So we started to be very sensitive about redmine's updates & upgrades.
42
* Ruby, it's not our core business programming language. We feel more comfortable using Java or PHP. This problem increased the first problem, because we didn't use properly methods that allow changing normal behaviour inside a plugin.
43 1 Borja Pacheco Ortega
44 7 Borja Pacheco Ortega
We learnt other important fact: Sometimes it's easier and cost saving, adapt our mind/methodology instead of modifying the tool.
45 1 Borja Pacheco Ortega
46 7 Borja Pacheco Ortega
h1. Our project
47 1 Borja Pacheco Ortega
48 7 Borja Pacheco Ortega
Once we have reached a mature knowledge about redmine, features, limitations, plugins available and devs methods, we decided to solve the problem seriously. We search for some budget, and we searched specialised resources to produce our needed modifications. 
49 1 Borja Pacheco Ortega
50 7 Borja Pacheco Ortega
h2. Specifications
51
52
Here, in this "document":http://www.juntadeandalucia.es/contratacion/document/download?refCode=2011-0000006176&refDoc=2011-0000006176-1 (it's in Spanish -we apologize) we describe in details our goals, functional features and technical requirements to the global project.
53
54
h3. Main Goals
55
56
* Improve workflow engine: Enable/Disable editions of custom fields depending current phase, allow transactions only if certain conditions are made, reduce list of possible "assigned-to" just to members who can execute the transition in the flow, limit who can create new tickets.
57
* Redmine's Federation: enable sharing information of project/tickets between different organization's redmines.
58
* Creation of a DashBoard module, to allow managers to control de activity of a collection of projects and performance indicators (KPIs)
59
* Allow custom reports and datamining. 
60 1 Borja Pacheco Ortega
* Integration with others
61 7 Borja Pacheco Ortega
** Third party: Drupal, Alfresco, Pentaho, Testlink, UML
62
** JdA's own tools: NAOS, Formula, iCMS
63 1 Borja Pacheco Ortega
* Enhance query interface with more filters.
64
* Block reporting elapsed time (log time) too long time ago.
65
* Enable archived project to be accessible read-only.
66
* Others: wiki's templates, calendar export via CalDav, wizard to configure a new project...
67
68 9 Borja Pacheco Ortega
h1. Project Organization
69 1 Borja Pacheco Ortega
70
The project is divided in three phases.
71
72 9 Borja Pacheco Ortega
h2. Phase 1
73 1 Borja Pacheco Ortega
74 9 Borja Pacheco Ortega
* *State*: FIXING MINOR BUGs
75
* *Estimated Release Date*: 20th June
76 1 Borja Pacheco Ortega
77 9 Borja Pacheco Ortega
h3. Features
78 1 Borja Pacheco Ortega
79 9 Borja Pacheco Ortega
* Improved workflow engine.
80
* Improved API Rest
81
* Enhanced archived project
82
* Block reporting elapsed time (log time) too long time ago.
83
* Fixed tree view plugin
84
* Some features in "my page"
85
* Wizard to import task from excel
86
* Integration with Alfresco 3.3.x (cmis 1.0) (Not tested, but developed)
87 1 Borja Pacheco Ortega
88
89 9 Borja Pacheco Ortega
h2. Phase 2
90 1 Borja Pacheco Ortega
91 9 Borja Pacheco Ortega
* *State*: TESTING 
92
* *Estimated Release Date*: 31st July
93 1 Borja Pacheco Ortega
94 9 Borja Pacheco Ortega
h3. Features
95 1 Borja Pacheco Ortega
96 9 Borja Pacheco Ortega
* New Integrated dashboard
97
* Wizard to create new projects (preconfigure users,roles, attributes...)
98
* Controlling who can create new tickets
99
* Redmine's Federation
100
* Integration with API iCMS (allow different CMS, such as, Drupal)
101
* Integration with Alfresco 3.2.x
102
* Integration with Formula v3
103 1 Borja Pacheco Ortega
104 9 Borja Pacheco Ortega
h2. Phase 3
105 1 Borja Pacheco Ortega
106 9 Borja Pacheco Ortega
* *State*: DEVELOPMENT
107
* *Estimated Release Date*: September-October
108 7 Borja Pacheco Ortega
109 9 Borja Pacheco Ortega
h3. Features
110 7 Borja Pacheco Ortega
111 9 Borja Pacheco Ortega
* Enhanced query interface with more filters.
112
* Enhanced wiki
113
* Enhanced Calendar 
114
* Periodic Tickets
115
* Integration with Pentaho -> SLA Management
116
* Integration with Testlink
117
* Integration with third party UML tools
118
* Integration with Plantilla
119
* Integration with NAOS
120 8 Borja Pacheco Ortega
121 9 Borja Pacheco Ortega
h3. Software Repository
122
123
We are going to prepare a GIT repository to allocate every part of the software. As soon as our SQA marks any release as candidate, we'll publish it and communicate how to get the source.
124
We'll announce through twitter and linkedin.
125
126
h1. Questions
127
128
Please contact me, via twitter: @Borja_Pacheco.
129
130
h1. References
131
132
If you need further info about my company or our job, you could find it at:
133
* www.juntadeandalucia.es/innovacioncienciayempresa/sadesi/
134
* www.juntadeandalucia.es/organismos/economiainnovacionyciencia/consejeria/sgisi.html