12 Nov
2009
12 Nov
'09
11:36 a.m.
On Nov 12, 2009, at 11:27 AM, Thomas Mortagne wrote:
On Thu, Nov 12, 2009 at 10:22, Vincent Massol
<vincent(a)massol.net>
wrote:
Yes but if nobody works on them (for at least a year) and they don't
work, why leave them in the platform as if they were working stuff?
Not changing is fine provided it works (that's why I add the rule of
"not working" btw, to differentiate mature stuff from attic stuff).
Thanks
-Vincent
Hi,
What should we do with the Dodo and Finch skins? Right now they sit
in
the platform as any other skin. However they're not in a working
state. I've just tried Finch and the home doesn't display nicely in
it.
We have 2 options I can think of:
1) we leave old/non-working modules in platform (as they are now)
2) we move them to a retired location. In this case we could move
them
to the contrib repo in retired/. This leaves the door open to anyone
interested to resurrect them (even if it's a bit hidden, but we could
make that more visible). The only small issue (maybe it's not one) is
that name "contrib". Another option would be to create an "attic"
top
level project for retried projects.
Yes we should move it but not in contrib since it's not contribs but
official retired projects.
I can also think of some plugins that could go there (alexa, adwords,
etc) - We'd need to verify that they don't work since otherwise they
probably don't need to be moved.
We could also define a rule to move stuff to the attic:
- the feature is not working anymore
- there's been no commit for one year
Not sure, IMO we should move only if it does not work anymore and we
know we will not work on it. There is some basic components that will
certainly not change a lot at some point but are still important
peaces. > Obviously anyone interested in reviving the
retired code could do so
> and move it back to the platform at any time.
>
> Any idea on this?
>
> Thanks
> -Vincent