[OOTB-addons] Summit-related: Additional activity/goal of ADDONS?
angel.borroy at keensoft.es
Fri Oct 31 05:06:40 GMT 2014
I think it's a great idea!
I've seen frequently repeated questions in the forums and even different
answers to the same requirement. So it would be nice to have a place to
detail this requirements which can be used for developers as reference.
>From my experience, we have four or five AMPs that we are using on every
project from source code because we can't find the time or the motivation
to make them more generic. So this could be an opportunity for us to paste
some source code from here and there and build a generic artifact which
could cover some of there requirements.
On the admin console, I would wait for someone with time enough to design
the basic tasks of the project and them we can collaborate together to get
the job done. Unfortunately, I'm not this person :)
El domingo, 26 de octubre de 2014, Axel Faust <axel.faust at prodyna.com>
> Hello all,
> in time for Summit I was asked to prepare a short report about the
> activities in the ADDONS committee. If you haven’t seen it:
> I also put a section about the purpose of ADDONS on the main wiki page:
> Item #6 on that list in the wiki is an addition based on discussions we
> had at Summit. It may have been an implied activity of ADDONS before, e.g.
> part of compiling list of valuable addons and “shepherding” neglected ones
> is consideration of frequent requirements. Some people were explicitly
> asking if we would also provide a central place / repository for any unmet
> requirements / ideas. This went as far as to suggest that the ADDONS
> committee could be a facilitator for interested parties, e.g. take related
> requirements and work with submitters to create a basic concept that a
> community developer, team or even a community-based integrator may pick up
> to develop the missing functionality.
> Just after Summit, there also was a Twitter exchange around this general
> topic. Specifically, it was suggested by Peter Monks that the Order
> coordinate a project to implement Workflow, Tenant and Dynamic Model Admin
> console replacements for Alfresco Community 5.0.b+ (until - someday - the
> Enterprise Admin Console framework has been de-coupled enough to allow use
> in CE). See https://twitter.com/orderofthebee/status/521685721556738048
> (and any tweets I may have missed)
> What are your opinions about item #6 in general and the specific issue of
> the admin console replacements?
> Personally, while I would love us to be such an essential part of the
> community that people see us as a go-to point when it comes to
> consolidating requirements and even draw up rough concepts, I’d prefer us
> to focus on the addon collection well into next year. If and when we have
> that process sorted and going steady, we can start with collecting/listing
> For the admin console replacements: It would be great if someone picks
> this up in his / her spare time, but I don’t see us in a position to
> organize something towards this goal (yet) unless there is a volunteer.
655 47 47 55
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OOTB-addons