Re: [tei-council] Stylesheets in GLs repo?

Actually, I think it might involve difficult decisions. Shall I now instead of deleting anything ever put it instead in the Vault? Where? How much documentation am I obligated to provide for it? Deletion *is* an option, because everything can be recovered. Anyway, I'm not going to argue much if you want to do it. It won't do any harm as long as we can still delete stuff we want to delete. I just think it's silly. On Thu, Jan 29, 2015 at 1:20 PM, Lou Burnard wrote:

Well (I am not advocating it myself) but the "never throw anything away" policy really doesn't involve any difficult decisions -- either something is live and useful or it's under the sofa: deletion isn't an option.

As I seem to have started this thread, can I make some specific suggestions?

My copy of the SF trunk has the following root directories:

Documents Extensions genetic I18N Incubator P5 TEIC TEICSS TEIOO-Deprecated

Documents, Extensions, and P5 are all active Incubator might be more active but it seems a useful place to put stuff that is, er, incubating I18N is an ODD application of interest independently of the TEI so should probably be left alone, until someone (Sebastian?) says it's been superceded. TEIC and TEICSS (we learn from Kevin) are useful for webmastery so should probably be left alone by the rest of us TEIOO-Deprecated I think should be deleted. As I said before, its function is now rolled into the Stylesheets and it hasn't ever been of much interest to anyone outside the TEI community The "genetic" folder is probably still referenced outside the TEI context, even though it's now of purely historical interest as far as we are concerned. If we are making a "Vault" folder (I think that sounds nicer than "sofa" don't you?) it's a good candidate for that.

On 29/01/15 18:06, Hugh Cayless wrote:

...

Can I make one more argument against the "never throw anything away" policy? Not only does it not really solve the cruft issue by just shoving it under the sofa, it also means a new set of procedures have to be established: what gets moved? How do I decide whether to stuff a thing under the sofa or delete it? How much documentation does there need to be for these things? I think it adds work and cognitive load when all we really need to do is delete it. If someone wants to know how we did things in 2012, they'll revert the repo to an appropriate commit and poke around. If we do this, I bet in a few years the obsolete branch will get nuked anyway. Because nobody will ever use it.

Still, if you really want to, at least I can ignore it :-).

On Thu, Jan 29, 2015 at 12:36 PM, Syd Bauman wrote:

It seems no one has *done* this yet. I think it's a really good idea.

...

I think Hugh is, in general, right -- it's OK to nuke stuff, that's why it's in a version control repository. That said, in the TEI universe where the cadre of those responsible for the repository changes over time, I'm more inclined to Martin's clever obsolete/ sibling of branches/, tags/, and trunk/. Besides, that way we could easily reverse the decision, and delete things from obsolete/. (Could reverse decision and recover deleted stuff if needed, too, but much harder.)

But IIRC (and I'd love to be wrong on this), it is not easy in Subversion to ascertain from where a directory was moved. So a check-in comment like "moved .../trunk/duck/quack/waddle/ to .../obsolete/waddle/" would be a good idea, no?

I'm happy to file a ticket, assign it to myself, and do this. I hate cruft.

True. But not everything needs to be kept in the attic. It's ok to

...

get rid of stuff when it's no longer useful.

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived