[Building Sakai] [sakai-pmc] PROPOSAL: svn cleanup

[Cris J Holdorph]

Will moving these include updating the projects that currently reference 
them?  E.g.,

https://source.sakaiproject.org/svn/sakai/branches/sakai-2.9.x-all/.externals

---- Cris J H

On 12/09/2013 08:27 AM, Matthew Jones wrote:
> Rather than move them to contrib, which would lose the history unless
> we/you use svnadmin to dump and reload into contrib (which you may or
> may not be considering), perhaps keeping them in that repo and moving
> them all into /svn/deprecated or /svn/msub/deprecated would be a
> better/easier idea.
>
> If you were going to use svnadmin to preserve the history, it doesn't
> matter a ton to me where any of these end up. We'll probably see a few
> others that don't really need to be in there either.
>
>
> On Mon, Dec 9, 2013 at 6:07 AM, Steve Swinsburg
> <steve.swinsburg at gmail.com <mailto:steve.swinsburg at gmail.com>> wrote:
>
>     Hi all,
>
>     The main Sakai SVN (https://source.sakaiproject.org/svn/) currently
>     holds a number of deprecated / out of date projects including:
>
>       * blog
>       * discussion
>       * db
>       * hybrid
>       * jcr
>       * mini
>       * osid
>       * pure-poms
>       * release-mgmt
>       * samples
>       * sdata
>       * site-association
>       * svn-admin
>       * triples
>       * ux
>       * was
>       * wsrp
>
>
>     There exists a space in the contrib SVN
>     (https://source.sakaiproject.org/contrib/deprecated/) that was
>     created for these retired projects to live and grow old.
>
>     This proposal is to rationalise the main SVN to move projects that
>     are no longer part of the core distribution to the deprecated space
>     in contrib. All of those in the above list will be moved. Some have
>     already moved but duplicates exist in the main svn. These will have
>     their dupes removed from the main SVN.
>
>     There are also these two projects that are institution specific and
>     appear to be unmaintained:
>
>       * gradtools
>       * oncourse
>
>
>     If the owners (IU?) need these two to stay in the main SVN, it is
>     fine for them to stay otherwise they will also be moved.
>
>     This kind of maintenance will reduce confusion and assist with any
>     possible repository move that may occur in the future.
>
>     This will have no impact on trunk or any currently supported release.
>
>     A material objection (indicated by a -1 and accompany reasoning)
>     raised by a Sakai PMC member will block this proposal.  Other
>     opinions are welcome, indeed encouraged. Silence equals consent.
>     Discussion should be on the sakai-dev list unless of a private
>     nature in which case I am happy to correspond off list. Objections
>     must be received before Monday 16th December 2013.
>
>     regards,
>     Steve
>
>
>
>
>     _______________________________________________
>     sakai-pmc mailing list
>     sakai-pmc at collab.sakaiproject.org
>     <mailto:sakai-pmc at collab.sakaiproject.org>
>     http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>