Hi all,
Yesterday we had an interesting discussion at the hackathon about how to
identify unused components so as to remove/deprecate them in order to
cleanup the code base.
We cannot consider the last commit date on a component as the measure of
its usefulness, as many components are simply
Sylvain Wallez wrote:
Hi all,
Yesterday we had an interesting discussion at the hackathon about how to
identify unused components so as to remove/deprecate them in order to
cleanup the code base.
We cannot consider the last commit date on a component as the measure of
its usefulness, as many
On 10/3/06, Sylvain Wallez [EMAIL PROTECTED] wrote:
...So the idea is to involve users in the process and conduct a poll where
they will be able to list the components they use regularly so that we
can find those that can be pushed to end-of-life and utimately removed
from the distribution...
Bertrand Delacretaz said the following on 3/10/06 12:05:
On 10/3/06, Sylvain Wallez [EMAIL PROTECTED] wrote:
...So the idea is to involve users in the process and conduct a poll
where
they will be able to list the components they use regularly so that we
can find those that can be pushed to
+1 for the blocks, because it simplifies the stay/leave
selection. In a
later stage the poll can be repeated per block for the
individual components.
I also suggest to ask for a TOP 5 and create a TOP 10 from
that to cater to a larger population.
How about letting users classifying
Geert Josten wrote:
+1 for the blocks, because it simplifies the stay/leave
selection. In a
later stage the poll can be repeated per block for the
individual components.
I also suggest to ask for a TOP 5 and create a TOP 10 from
that to cater to a larger population.
How about
Sylvain Wallez said the following on 3/10/06 13:26:
Geert Josten wrote:
+1 for the blocks, because it simplifies the stay/leave
selection. In a
later stage the poll can be repeated per block for the
individual components.
I also suggest to ask for a TOP 5 and create a TOP 10 from
that to
