[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [technology-pmc] Restructuring ACTF Project
- From: Wayne Beaton <wayne@xxxxxxxxxxx>
- Date: Thu, 19 Nov 2009 10:10:41 -0500
- Delivered-to: firstname.lastname@example.org
- User-agent: Thunderbird 22.214.171.124 (X11/20090817)
Transparency is the important issue here: you need to make sure that
what you intend to do is abundantly clear.
Restructuring sounds like a good idea. You can turn ACTF into a
container project and divide up the bits into subprojects ("operating
projects"). In doing so, you can split your committers so that the right
set of committers end up with the right subprojects. You can decide how
to do builds and releases on a subproject, or even on a container
As part of a restructuring review, you can list components that are to
be archived. We can archive parts of a project.
For a Restructuring Review, you need only to describe what it is that
you want to do with enough detail that the community can understand and
be involved in the process.
Kentarou Fukuda wrote:
ACTF project is now working to develop future release plans. For this
work, we have questions about Eclipse release and archive processes.
Currently, only a project or sub-project is allowed to do a release.
However, due to differences in the development schedules, maturity,
resources, and so on, it is difficult to schedule simultaneous releases of
complete ACTF components.
For more flexible releases, we think dividing the ACTF project into some
sub-projects is a possible solution . ACTF has 3 major components
(Validation, Visualization and Alternative Interface) and the common
infrastructure (Core), so we might be able to divide ACTF into these 4
sub-projects. We are also now considering if there is another possible way
Before starting preparation of this restructuring, we would like to have
your advice about it. For example, are there other good ways, etc..
In addition to this, some plugins of ACTF are now nearly dormant. We are
considering whether or not they can or should be archived.
We'll continue to look for new contributors who have interest in that
part. However, if we come to the conclusion that we should archive it, can
we archive only the inactive part? In the Eclipse development process,
only a project or sub-project can receive the archived state . We would
like to know how to archive some part of a project.
We found that similar questions were raised in the Nebula project last
year , but we would like to know your thought in our case.
Thank you in advance for your support.
Kentarou Fukuda, Ph.D.
IBM Research - Tokyo
technology-pmc mailing list