12 Nov
2009
12 Nov
'09
10:22 a.m.
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.
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
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
12 Nov
12 Nov
10:45 a.m.
Hi,
On Thu, Nov 12, 2009 at 10:22 AM, Vincent Massol <vincent(a)massol.net> wrote:
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.
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
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?
Sounds good overall.
"attic" sounds better to me. It's different from "contrib" in that
those are
projects that were "officially" being worked on by the team at some point in
the past.
As for the specific rules, given our development practices, we could use a
dynamic rule such as "no commit in the last 2 major releases" (in addition
to the "not working anymore rule").
Guillaume
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Lerouge
Product Manager - XWiki SAS
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
10:53 a.m.
On Nov 12, 2009, at 10:45 AM, Guillaume Lerouge wrote:
Hi,
On Thu, Nov 12, 2009 at 10:22 AM, Vincent Massol
<vincent(a)massol.net> wrote:
This is not enough. Even 1 year might not be enough but I feel it's
acceptable. If someone says 2 years I'd still be ok. These moves
should not be done lightly. FWIW at apache it takes several years
(around 4-5 AFAIR - the main case I remember is the ECS project).
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.
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
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?
Sounds good overall.
"attic" sounds better to me. It's different from "contrib" in
that
those are
projects that were "officially" being worked on by the team at some
point in
the past.
As for the specific rules, given our development practices, we could
use a
dynamic rule such as "no commit in the last 2 major releases" (in
addition
to the "not working anymore rule"). 
11:27 a.m.
On Thu, Nov 12, 2009 at 10:22, Vincent Massol <vincent(a)massol.net> wrote:
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
11:32 a.m.
On 11/12/09 11:27 AM, Thomas Mortagne wrote:
On Thu, Nov 12, 2009 at 10:22, Vincent
Massol<vincent(a)massol.net> wrote:
> 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.
+1 for attic
Yes we should move it but not in contrib since it's not contribs but
official retired projects.
+1
Jerome.
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
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
11:45 a.m.
On Thu, Nov 12, 2009 at 11:36, Vincent Massol <vincent(a)massol.net> wrote:
On Nov 12, 2009, at 11:27 AM, Thomas Mortagne wrote:
This is exactly what i'm saying, if we break something it's a
regression. When I say "we will not work on it" i'm speaking about fix
the regression in the next release, not wait for 1 year with something
which does not work anymore...
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? 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.
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
--
Thomas Mortagne
> 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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
2 Dec
2 Dec
4:59 p.m.
On Thu, Nov 12, 2009 at 10:22 AM, Vincent Massol <vincent(a)massol.net> wrote:
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.
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
+1 with 2), about the rule I'd prefer "the feature is not working anymore".
Since we're talking about skins I'd even think about albatross as a
candidate for the attic, currently maintaining skins is like
maintaining branches (css, templates duplications) and having 3 of
them at the same time is time consuming (read: a PITA). Just like
branches, I think 2 is ok.
My dream retirement planning would be something like: january 2010,
albatross; january 2011, toucan. Colibri is a big step ahead (L&F,
cleanliness, accessibilty) and we should promote the migration.
Obviously anyone interested in reviving the retired code could do so
and move it back to the platform at any time.
Thanks,
JV.
5402
days inactive
5422
days old
7 comments
5 participants
participants (5)
-
Guillaume Lerouge -
Jean-Vincent Drean -
Jerome Velociter -
Thomas Mortagne -
Vincent Massol