[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-community
Subject:    Re: Applications Lifecycle Policy
From:       Jaroslaw Staniek <staniek () kde ! org>
Date:       2017-07-05 12:54:33
Message-ID: CAOj7QQ2srHcZPvczAj+DTvPGoUMnCyzpzjSO4XzDGSFauqeRfg () mail ! gmail ! com
[Download RAW message or body]

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

> On 5 July 2017 at 13:04, Jaroslaw Staniek <staniek@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

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_default" \
style="font-family:monospace,monospace;font-size:small"><br></div><div \
class="gmail_extra"><br><div class="gmail_quote">On 5 July 2017 at 14:11, Jonathan \
Riddell <span dir="ltr">&lt;<a href="mailto:jr@jriddell.org" \
target="_blank">jr@jriddell.org</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span>On 5 July 2017 at 13:04, Jaroslaw Staniek &lt;<a \
href="mailto:staniek@kde.org" target="_blank">staniek@kde.org</a>&gt; wrote:<br> &gt; \
Why not? I can imagine we can make the process more dynamic.<br> &gt; Whole apps or \
their parts can go back to being maintained, what seems to be<br> &gt; a core \
property of FOSS.<br> &gt;<br>
&gt; If so how about back-arrow from Unmaintained?<br>
<br>
</span>Probably not worth making the diagram more complex but I added in this<br>
sentence to unmaintained section<br>
<br>
&quot;Projects can move back to an earlier stage if they are picked up for<br>
maintenance again. &quot;<br>
<span class="m_7356672513985270898HOEnZb"><font \
color="#888888"><br></font></span></blockquote><div><br><div \
style="font-family:monospace,monospace;font-size:small;display:inline" \
class="gmail_default">​Thanks, I&#39;d think not &quot;earlier stage&quot; but \
explicitly &quot;playground&quot; because in the meantime the unmaintained project \
might lost its &quot;reviewed&quot; 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.<br></div></div></div><br \
clear="all"><br>-- <br><div class="m_7356672513985270898gmail_signature" \
data-smartmail="gmail_signature">regards, Jaroslaw Staniek<br><br>KDE:<br>: A \
world-wide network of software engineers, artists, writers, translators<br>: and \
facilitators committed to Free Software development - <a href="http://kde.org" \
target="_blank">http://kde.org</a><br>Calligra Suite:<br>: A graphic art and office \
suite - <a href="http://calligra.org" \
target="_blank">http://calligra.org</a><br>Kexi:<br>: A visual database apps builder \
- <a href="http://calligra.org/kexi" \
target="_blank">http://calligra.org/kexi</a><br>Qt Certified Specialist:<br>: <a \
href="http://www.linkedin.com/in/jstaniek" \
target="_blank">http://www.linkedin.com/in/<wbr>jstaniek</a></div> </div></div>



[prev in list] [next in list] [prev in thread] [next in thread]