Applications Lifecycle Policy

[Jaroslaw Staniek]

On 5 July 2017 at 14:11, Jonathan Riddell <jr at jriddell.org> wrote:

> On 5 July 2017 at 13:04, Jaroslaw Staniek <staniek at kde.org> wrote:
> > Why not? I can imagine we can make the process more dynamic.
> > Whole apps or their parts can go back to being maintained, what seems to
> be
> > a core property of FOSS.
> >
> > If so how about back-arrow from Unmaintained?
>
> Probably not worth making the diagram more complex but I added in this
> sentence to unmaintained section
>
> "Projects can move back to an earlier stage if they are picked up for
> maintenance again. "
>
>
​Thanks, I'd think not "earlier stage" but explicitly "playground" because
in the meantime the unmaintained project might lost its "reviewed" stamp.
Technology and other requirements move forward. Example: unmaintained
project XYZ got restored from Qt4 times to Qt6, needs major changes for
translation and build systems.


-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20170705/bf46e54d/attachment.htm>