RE: [technology-pmc] Restructuring ACTF Project

[Michael A Squillace <masquill@xxxxxxxxxx>]

All:

Sorry for the late response but just
returned from vacation. I am a little confused. On the one hand, Wayne
claims:

> As part of a restructuring review,
you can list components that are to be archived. We can archive parts of
a project.

Yet, the Eclipse process does not permit,
as I read it and as my colleague Kentarou pointed out, anything but projects
and subprojects to receive the archive status so how do we archive part
of a project?

Constantine writes below:

> There is really nothing stopping a project from
throwing away chunks of the code base for a > variety of reasons. There
is no formal archiving process as there is for projects. You just >
delete the source in CVS and that's that.

I believe that it is Constantine's approach
that we were entertaining. Here is what we, the IBM HA&AC, initially
proposed to our colleagues in Tokyo

1. archive the ACTF Java Validation
Componentry (Javaco) feature and its related plugins and resources. This
includes performing any formal steps necessary within the Eclipse development
process for archival and freezing development on the 
project. The HA&AC will maintain
control over the project's status as frozen/archived and decisions about
its future development 
or enhancement (should further requirements
arise and resources permit, ).

2. archive the ACTF Web Validation Componentry
(Webelo) feature and its related plugins and resources. This includes performing
any formal steps necessary within the Eclipse development process for archival
and freezing development on the 
project. The HA&AC will maintain
control over the project's status as frozen/archived and decisions about
its future development 
or enhancement (should further requirements
arise and resources permit, ).

3. move the ACTF Accessibility Probe
(AccProbe) from eclipse.org to the Linux Foundation. This is a more logical
home for 
AccProbe as its primary impetus was
to support IAccessible2-enablement of applications and the Linux Foundation
is also the 
host of the IAccessible2 standard. AccProbe
will remain an Eclipse RCP application but further development and enhancements
will be directed by the HA&AC and in a distinct repository from the
Eclipse ACTF repository. Thus, AccProbe will be completely 
removed from eclipse.org and from the
repository that hosts ACTF.

Of course, any plugins or resources
that are shared by our components and components thus far developed by
our colleagues in Tokyo (or other non-IBM contributors)will remain in the
Eclipse CVS repository hosting ACTF. 

So, there are two lingering questions:
1. Do we archive Java Validation Componentry
and Web Validation Componentry or simply remove them from CVS and all of
the related material from eclipse.org. Only IBMers (and, in particular,
members of the HA&AC) have made contributions to these components.
2. Only members of the IBM HA&AC
have made contributions to AccProbe as well so are there any issues surrounding
moving this tool to the Linux Foundation where it would likely be relicensed
from EPL to BSD?

--> Mike Squillace
IBM Human Ability and Accessibility Center

W:512.286.8694
M:512.970.0066

External: http://www.ibm.com/able
Internal: http://w3.ibm.com/able



From:      
 "Konstantin Komissarchik"
<konstantin.komissarchik@xxxxxxxxxx>
To:      
 "'Technology PMC'"
<technology-pmc@xxxxxxxxxxx>
Date:      
 11/19/2009 02:46 PM
Subject:    
   RE: [technology-pmc]
Restructuring ACTF Project
Sent by:    
   technology-pmc-bounces@xxxxxxxxxxx

---

Wayne addressed the question about splitting up the
project and that may
very well be the best option, but I wanted to make sure that the rest of
the
question was addressed too.

> 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 [2]. We would like to know how to archive some part
> of a project.

There is really nothing stopping a project from throwing away chunks of
the
code base for a variety of reasons. There is no formal archiving process
as
there is for projects. You just delete the source in CVS and that's that.
Just make sure that you have involved your entire project in the decision
and have communicated your intentions accordingly to any potential
downstream consumers.

Hope this helps.

- Konstantin 



-----Original Message-----
From: technology-pmc-bounces@xxxxxxxxxxx
[mailto:technology-pmc-bounces@xxxxxxxxxxx]
On Behalf Of Kentarou Fukuda
Sent: Thursday, November 19, 2009 6:00 AM
To: Technology PMC
Subject: [technology-pmc] Restructuring ACTF Project

Hi Technology-PMC,

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 [1]. 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 
for restructuring. 

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 [2]. 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 [3], but we would like to know your thought in our case.

Thank you in advance for your support.

[1] http://dev.eclipse.org/mhonarc/lists/actf-dev/msg00256.html
[2] 
http://www.eclipse.org/projects/dev_process/development_process.php#6_2_6_Ar
chived
[3] http://dev.eclipse.org/mhonarc/lists/technology-pmc/msg01395.html

Best regards,
Kentarou
---
Kentarou Fukuda, Ph.D.
IBM Research - Tokyo
Tel: +81-46-215-4659
E-mail: kentarou@xxxxxxxxxx
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc