Le 10/11/2015 23:26, Jacques Le Roux a écrit :
I made another proposition earlier but not too long ago
http://markmail.org/message/ypmrbqkb7y2gh4f5
But it seems nobody was interested :/ (OK, the thread referenced in
the reference above is really long to read :D, but the message is not)
I wonder why. It seems ideal to me: we don't release code we don't
want in releases, but we can still propose it to our users in a
reliable way and it's maintained.
With Nicolas's proposition I fear the maintenance part could be
overlooked as Taher mentionned.
Yes I agree also with Taher, but what's the better way with own resources :
* Have a strong quality on application
* Have a working application with specialpurpose rules.
With my feed back, all site project works with application, I use
sometime a specialpurpose component but rarely.
So the fear is also on true on the other ways.
So now I deactivate all specialpurpose before starting a new project to
ensure that I have only standard process.
On the other hand I'd not be against moving more components to Attic
if they deserve it...
Contrary to POS or projectmgr, I don't remember users asking for
google and ebay components missing in R13...
Also what about Oagis, who really care (there are some entries in wiki
but old and not maintained)?
I don't remember if I made this proposition already: rather than
moving those components to Attic (ie remove but still have at a
revision in repo) we could keep them in an attic sub-folder under
specialpurpose before really removing them.
And generally we could use sub-folders to better organise things. Like
putting google and ebay components under ecomComplements rather than
in an attic folder, projectmgr and scrumm could be alsogrouped ,solr
and lucene too, example and exampleext, ldap and passport, etc.
sure, but i thinks this it out from my little proposal ;)
Nicolas
Jacques
Le 10/11/2015 09:48, Jacopo Cappellato a écrit :
Hi Nicolas,
I like your proposal.
Jacopo
On Mon, Nov 9, 2015 at 10:40 PM, Nicolas Malin
<nicolas.ma...@nereide.fr>
wrote:
Hello,
With some latest great discussion about keep or not keep specialpurpose
components on branch, I some inconvenience come from that a
specialpurpose
can be overload the definition (service, entity or something like that)
present on application component.
It's easier, we can comment all lines present on
specialpurpose/component-load.xml and if some people want use a
specific
component, just uncomment it :)
I see two advantages :
* detect bad depends easily (a application or framework that use
specialpurpose)
* detect if a component it on the good place
Your comments ?
Nicolas
