Quoting dombre <[EMAIL PROTECTED]>:
[EMAIL PROTECTED] a écrit :
What do you think about ACL ?
ACL is a wonderful word but what do you means exactly saying that ?
ACL for Access Control List, meaning Reading and Writing access for
inventory personal to the Hardware database, Reading and writing
access for hardware interventions Ticket system, Reading access for
campus administrator to the reports.
Basically grant privileges according to their specific tasks,
according to the functionalities of the system.
At this time there are groups privileges, but now think on a larger
scale enterprise, scaling control according from department to global
administration and each owners computers.
For what I've seen there are some aspects that limit diferent
developments, by individuals, for example the instalation procedure (
an online procedure could ask for patches and implement them before
creation of the structure ),
I don't understand exactly what do you want to do.
Could you explain please ?
I was thinking on this case, the alteration of the database ( inclusion
of SQL instrutions with ALTER ), and code ( with the aplication of
patches ) during the instalation procedure ou update procedure.
The creation of an online instalation would make this more trivial for
every especific development, apart from the main core, enabling main
features to be included in the main source source, and still allowing
the development of particular features by each party ( especific data
field and their manipulation ).
I do not understand yet.
There is an online procedure for the CORE of GLPI.
Each plugin must to integrate each own installation and update procedure.
A plugin is compatible for a specific version of GLPI.
A plugin can be compatible for several version but the plugin dev must
to work to keep its plugin compatible with new version of GLPI.
We could not take into account all plugins in our update process.
the plugin engine ( it's created, but to
what extend, for example can I deactivate actual tracking assistance,
for another ).
Plugin is an engine to add something to GLPI not to replace some parts of
GLPI.
The modularity of GLPI is not already done and is not the prior task for
the moment because lots of big tasks need to be done before.
I was talking about this issue, because I've seen a development of a
ticket tracking system, when there's a solid system widelly use on the
web RT. The objective was to deactivate the currently developed ticket
system and make a module to incorporate de RT system, very solid
funcional, and already implemented on our campus :P
You must to modify the code of GLPI by yourself.
If you do not want to use some features of GLPI, just do not use these
menus...
What do you think of this ideias ?
As soon as project guidelines are defined to whom should I talk to
propose the developmente of the features for possible inclusion ?
You could speak of them here.
You could also send me a private mail and I will forward to the
others devs.
For now, this are the main features, online instalation and
upgrade procedure, implementation of ACL in conjunction with LDAP,
plugin engine to support other traking systems, and/or changing
knowledge database with Wiki system.
Why would you replace some subsystem of GLPI in GLPI ?
Install them and use them outside of GLPI.
I really do not understand why you want to integrate them in GLPI.
For me the question is very simple, GLPI as done a great job
developing a Hardware/Software management and should fully develop
those capabilities, on the other hand as you know to have a full
system to manage the computers, to know what system (
hardware/software ) is not enought one needs also a ticket system (
for maintenance intervention ) , and knowledge database ( FAQ and
knowledge information of current setups ).
You started developing a GLPI's own ticket system and knowledge
database, I'm proposing just to keep those as an option and give the
oportunity of FULL integration with other systems, leaving more
oportunity to develop main objective ( my point of view ) of GLPI,
manage computers hardware and software.
Offering in the end a FULL system to manage a full enterprise computer
park, taking also advantage of fully mature systems on the market.
I don't pretend to kill at birth functionalities of the GLPI, just to
give more power to the end offer by the system.
The current work on ticket system, and kownledge database could be
kept and offered as main system implementation, but offering
alternatives would give more flexibility to the project and invite
other point of view and functionalities.
I know I can develop all of this on the side, I was just trying to
offer the ideia of extra flexibility to the project development, and
yes I think this could be gain defining main purpose of GLPI as the
core system, management of computer systems, and all the rest based on
plugins, giving extended functions.
Julien
_______________________________________________
Glpi-dev mailing list
[email protected]
https://mail.gna.org/listinfo/glpi-dev
_______________________________________________
Glpi-dev mailing list
[email protected]
https://mail.gna.org/listinfo/glpi-dev
