James— Thanks for this nudge! The Stylesheets working group has been helpful in showing how to approach some good representative tickets, but it’s still pretty scary ground to investigate. I think you’re right that reviewing these and adopting some can’t hurt even if they are baffling to us. The sheer number is pretty daunting—but I wonder if we’ll start to see some patterns in the tickets (I hope?): As we’re reviewing these, does anyone see a means of clustering the issues around **related kinds** of work? —Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu mailto:ebb8@pitt.edu Development site: http://newtfire.org http://newtfire.org/

On Oct 3, 2017, at 7:40 AM, James Cummings wrote:

Hi TEI Technical Council,

Just to alert you that we currently have 102 open stylesheets issues and of those 79 are 'assigned to nobody'.

I've just gone through and assigned some to myself, but given the complexity of one stylesheets issue to the other don't feel like I should be assigning Stylesheets issues to people randomly. Perhaps you could go to https://github.com/TEIC/Stylesheets/issues?q=is%3Aopen+is%3Aissue+no%3Aassig... and assign yourself a few. (Maybe even some of the ones from ages ago!) (Yes, some of the usual suspects already have a bunch assigned to them... I'm not necessarily asking them to take on more work if you think you have enough assigned to you.)

Remember, being assigned to an issue doesn't necessarily mean you have to do the XSLT editing (or whatever), just that you have to ensure it gets done. 😊

Best wishes,

James

--

Dr James Cummings, James.Cummings@newcastle.ac.uk

School of English Literature, Language, and Linguistics, Newcastle University -- 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