Re: [actf-dev] Re: [technology-pmc] Proposed restructure of Eclipse ACTF

[Michael A Squillace <masquill@xxxxxxxxxx>]

Sorry, Wayne - still a little confused.
I understand that to completely remove something from the CVS repository
means doing a rm -r on the file system once I ssh to the dev.eclipse.org
server. On the other hand, to move chunks of code to the "CVS attic,"
are you saying that this is a job for the web master? How is this different
from moving something to archive.eclipse.org? I've googled in general and
searched eclipse.org to no avail. Seems to me this process (these options?)
ought to be documented somewhere.

--> 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:      
 Wayne Beaton <wayne@xxxxxxxxxxx>
To:      
 Technology PMC <technology-pmc@xxxxxxxxxxx>
Cc:      
 ACTF developers list
<actf-dev@xxxxxxxxxxx>
Date:      
 01/24/2010 08:58 PM
Subject:    
   Re: [actf-dev]
Re: [technology-pmc] Proposed restructure of Eclipse      
 ACTF
Sent by:    
   actf-dev-bounces@xxxxxxxxxxx

---

When you delete something from CVS it is moved to
the "Attic". It can 
later be recovered from there. The only way to completely remove 
something from CVS is to delete (i.e. rm [file]) it from the file system.

This is fine for relatively small chunks of code. If you are removing 
complete chunks of functionality, it would probably be best to instead
ask the webmaster to archive specific directories.

Wayne

Michael A Squillace wrote:
>
> > FWIW, when Konstantin suggested that you can delete the code
from 
> CVS, he didn't mean the entire history.
> That's not what he said or I understood - phrases like, "throwing
away 
> chunks of the code base," or, "just delete the source in
CVS," suggest 
> otherwise. However, we certainly want to abide by EPL.
>
> > Anything you want to delete should either end up in the CVS Attic,
> or be explicitly archived in a ZIP file on archive.eclipse.org.
> Ok, then - what is the process for this. Do we simply take the last
> release and move it to archive.eclipse.org? what is the "CVS
attic?"
>
> --> 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
>
> Inactive hide details for Wayne Beaton ---01/23/2010 09:16:18 PM---You
> had me right up to the "No attempt will be made to archiWayne
Beaton 
> ---01/23/2010 09:16:18 PM---You had me right up to the "No attempt
> will be made to archive this codebase on eclipse.org." part.
>
> From: Wayne Beaton <wayne@xxxxxxxxxxx>
> To: Technology PMC <technology-pmc@xxxxxxxxxxx>
> Cc: ACTF developers list <actf-dev@xxxxxxxxxxx>
> Date: 01/23/2010 09:16 PM
> Subject: [actf-dev] Re: [technology-pmc] Proposed restructure of 
> Eclipse ACTF
> Sent by: actf-dev-bounces@xxxxxxxxxxx
>
> ------------------------------------------------------------------------
>
>
>
> You had me right up to the "No attempt will be made to archive
this 
> codebase on eclipse.org." part. What do you mean by this?
>
> FWIW, when Konstantin suggested that you can delete the code from
CVS, 
> he didn't mean the entire history. Once something has been contributed
> under the EPL, it's there forever. The only time we ever completely
> delete something from CVS is when there is an IP problem.
>
> Anything you want to delete should either end up in the CVS Attic,
or 
> be explicitly archived in a ZIP file on archive.eclipse.org.
>
> Thanks,
>
> Wayne
>
> Michael A Squillace wrote:
>
>             Technology PMC:
>
>             This note is to formally
introduce and receive approval
>             for a restructuring of the
Eclipse Accessibility Tools
>             Framework (ACTF) project.[1]
It follows a number of
>             communications with you
and the ACTF community, including
>             a teleconference for the
ACTF community hosted on Fri Jan
>             22 9AM EST [2] to discuss
this restructuring.
>
>             Background
>
>             Recently, there have been
a number of resource limitations
>             and shifting internal priorities
at the IBM Human Ability
>             and Accessibility Center
(HA&AC). Also, since the
>             inception of the ACTF project
in October 2007, we have
>             seen little participation
in or consumption of our
>             contributions to ACTF. We,
the HA&AC, cannot continue to
>             shoulder the requirements
that must be satisfied by our
>             componentry that are necessary
to ensure the advancement
>             of the ACTF project to graduation
(e.g. provide and
>             implement a project plan
and regular release schedule,
>             continue to solicit community
involvement and requests for
>             enhancements, etc.). On
the other hand, we do not wish to
>             prevent our colleagues in
Tokyo and other members of the
>             ACTF community from carrying
the project to graduation.
>             Thus, Kentarou Fukuda and
I, as co-technical leads of ACTF
>             and Chieko Asakawa, ACTF
project lead, are proposing a
>             restructuring of ACTF.
>
>             Proposed solutions:
>
>             In discussing this proposal
with members of your
>             committee, two approaches
have been recommended:
>             1. Wayne Beaton, the Technology
PMC Lead, suggested
>             dividing ACTF into subprojects
[3], presumably so that all
>             HA&AC-contributed componentry
will reside in one
>             subproject, that subproject
then being archived according
>             to the Eclipse development
process.[4]
>             2. Also from the Technology
PMC, Konstantin Komissarchik
>             wrote, "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."[5]
>
>             Proposed restructuring:
>
>             The HA&AC will no longer
actively participate in this
>             project and, therefore,
our contributions, which consist
>             entirely of work done by
IBM commiters and contributors
>             and have no down stream
dependencies or consumers of which
>             we are aware, will be removed
from the ACTF project
>             following the guidance of
the second recommendation above.
>             In particular, we are proposing
the following:
>
>             1. Remove from the Eclipse
CVS repository the ACTF Java
>             Validation Componentry (Javaco)
feature and its related
>             plugins and resources. The
ACTF community, with input from
>             the IBM HA&AC, will
maintain control over decisions
>             about the project's future
reactivation or enhancement
>             (should further requirements
arise and resources permit).
>             The last release of this
componentry (v0.4.0), both its
>             binary and SDK versions,
will remain on the Javaco
>             downloads page [6] with
a notice that the componentry is
>             no longer actively developed
or supported. No attempt will
>             be made to archive this
codebase on eclipse.org.
>
>             2. Remove from the Eclipse
CVS repository the ACTF Web
>             Validation Componentry (Webelo)
feature and its related
>             plugins and resources. The
ACTF community, with input from
>             the IBM HA&AC, will
maintain control over decisions
>             about the projectthe 's
reactivation or enhancement
>             (should further requirements
arise and resources permit).
>             The last release of this
componentry (v0.2.0), both its
>             binary and SDK versions,
will remain on the Webelo
>             downloads page [7] with
a notice that the componentry is
>             no longer
>             actively developed or supported.
No attempt will be made
>             to archive this codebase
on eclipse.org.
>
>             3. Remove from the Eclipse
CVS repository the ACTF
>             Accessibility Probe (AccProbe)
RCP application as well as
>             its related plugins and
resources. AccProbe will remain an
>             Eclipse RCP application
but further development and
>             enhancements will be directed
by the IBM HA&AC and by the
>             IAccessible2 community residing
at the Linux Foundation
>             [8] and in a code repository
designated by that
>             organization. The last release
of AccProbe (v0.4.4), both
>             its binary and SDK versions,
will remain on the AccProbe
>             downloads page [9] with
a notice that the new home of
>             AccProbe is the Linux Foundation.
>
>             Of course, any plugins or
resources that are shared
>             between our components and
components thus far developed
>             by other teams within IBM
or by external committers will
>             remain in the Eclipse CVS
repository hosting ACTF and
>             these can be developed as
their leads see fit. We would
>             like feedback from the members
of the ACTF community, the
>             Technology PMC, and the
community at large as well as
>             other interested parties
regarding this proposal.
>
>             Time table:
>
>             1. host a phone conference
for the ACTF community and
>             other interested parties
regarding this matter by the end
>             of January 2010 (see above
and note [1])
>             2. receive any concerns
or questions about this proposal
>             within four weeks of the
date of this proposal being
>             discussed on said teleconference
(Fri Feb 19, 2010)
>             3. alert the ACTF community
of any changes or updates
>             given feedback to this proposal
and adjust time table
>             accordingly
>             4. once all objections and
concerns have been addressed,
>             implement the above restructuring
>
>             We expect the restructuring
to be complete by the end of
>             February 2010 and look forward
to your comments. Also,
>             please let us know if any
type of review is in order.
>
>             [1] _http://www.eclipse.org/actf_
>             [2]
>             _http://dev.eclipse.org/mhonarc/lists/actf-dev/msg00274.html_
>             [3]
>             _http://dev.eclipse.org/mhonarc/lists/technology-pmc/msg02202.html_
>             [4]
>             _http://www.eclipse.org/projects/dev_process/development_process.php#6_2_6_Ar_
>             [5]
>             _http://dev.eclipse.org/mhonarc/lists/technology-pmc/msg02204.html_
>             [6]
>             _http://www.eclipse.org/actf/downloads/components/javaco/index.php_
>             [7]
>             _http://www.eclipse.org/actf/downloads/components/webelo/index.php_
>             [8]
>             _http://www.linuxfoundation.org/collaborate/workgroups/accessibility/iaccessible2_
>             [9]
>             _http://www.eclipse.org/actf/downloads/tools/accprobe/index.php_
>
>             --> 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_
>
>
>             ------------------------------------------------------------------------
>
>             _______________________________________________
>             technology-pmc mailing list
>             _technology-pmc@eclipse.org_
>             <mailto:technology-pmc@xxxxxxxxxxx>
>             _https://dev.eclipse.org/mailman/listinfo/technology-pmc_
>               
>
>
> -- 
> Wayne Beaton, The Eclipse Foundation
> _http://www.eclipse.org_ <http://www.eclipse.org/>
>
> I'm going to EclipseCon!
> _http://www.eclipsecon.org_ <http://www.eclipsecon.org/>
> _______________________________________________
> actf-dev mailing list
> actf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/actf-dev
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> technology-pmc mailing list
> technology-pmc@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/technology-pmc
>   

-- 
Wayne Beaton, The Eclipse Foundation
http://www.eclipse.org

I'm going to EclipseCon!
http://www.eclipsecon.org

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