GitHub P6 label, anyone?

Peter Stadler

23 Nov 2015 23 Nov '15

1:10 a.m.

I was just going through some tickets and came across #1400 „Remove numbered divisions“, wondering whether we need (or want) a P6 label? That way, we could start collecting issues for the day X. That would not necessarily mean that those changes be implemented in P6, but discussion is postponed until then. So, rather than simply closing the issue, we could label it first (and close it then, so it’s not polluting our issue tracker), making it easy to reopen these issues when the time comes. Cheers Peter

Attachments:

signature.asc (application/pgp-signature — 455 bytes)

Show replies by date

James Cummings

23 Nov 23 Nov

5:40 a.m.

New subject: [tei-council] GitHub P6 label, anyone?

All in favour of it... though I don't think we should worry too much about breaking backwards compatibility with that particular issue. (Since the solution is a trivial conversion and we could provide XSLT as a method of dealing with it.) FAND-sympathiser, -James On 23/11/15 09:10, Peter Stadler wrote:

...

I was just going through some tickets and came across #1400 „Remove numbered divisions“, wondering whether we need (or want) a P6 label? That way, we could start collecting issues for the day X. That would not necessarily mean that those changes be implemented in P6, but discussion is postponed until then. So, rather than simply closing the issue, we could label it first (and close it then, so it’s not polluting our issue tracker), making it easy to reopen these issues when the time comes.

Cheers Peter

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford

Kevin Hawkins

5:57 a.m.

New subject: [tei-council] GitHub P6 label, anyone?

Do keep in mind we also have a list of things to consider for P6 at http://wiki.tei-c.org/index.php/P6-dev . Perhaps those should be moved into GitHub as issues with the P6 label so we don't forget about them. On 11/23/15 7:40 AM, James Cummings wrote:

...

All in favour of it... though I don't think we should worry too much about breaking backwards compatibility with that particular issue. (Since the solution is a trivial conversion and we could provide XSLT as a method of dealing with it.)

FAND-sympathiser,

-James

On 23/11/15 09:10, Peter Stadler wrote:

...
I was just going through some tickets and came across #1400 „Remove numbered divisions“, wondering whether we need (or want) a P6 label? That way, we could start collecting issues for the day X. That would not necessarily mean that those changes be implemented in P6, but discussion is postponed until then. So, rather than simply closing the issue, we could label it first (and close it then, so it’s not polluting our issue tracker), making it easy to reopen these issues when the time comes.

Cheers Peter

Raffaele Viglianti

6:14 a.m.

New subject: [tei-council] GitHub P6 label, anyone?

Would a milestone be more appropriate? Raff On Nov 23, 2015 8:57 AM, "Kevin Hawkins" wrote:

...

Do keep in mind we also have a list of things to consider for P6 at http://wiki.tei-c.org/index.php/P6-dev . Perhaps those should be moved into GitHub as issues with the P6 label so we don't forget about them.

On 11/23/15 7:40 AM, James Cummings wrote:

...
All in favour of it... though I don't think we should worry too much about breaking backwards compatibility with that particular issue. (Since the solution is a trivial conversion and we could provide XSLT as a method of dealing with it.)

FAND-sympathiser,

-James

On 23/11/15 09:10, Peter Stadler wrote:

...
I was just going through some tickets and came across #1400 „Remove numbered divisions“, wondering whether we need (or want) a P6 label? That way, we could start collecting issues for the day X. That would not necessarily mean that those changes be implemented in P6, but discussion is postponed until then. So, rather than simply closing the issue, we could label it first (and close it then, so it’s not polluting our issue tracker), making it easy to reopen these issues when the time comes.

Cheers Peter

--

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

Martin Holmes

10:20 a.m.

New subject: [tei-council] GitHub P6 label, anyone?

I'm in favour of a P6 label. Martin Holmes UVic Humanities Computing and Media Centre mholmes@uvic.ca ________________________________________ From: tei-council-bounces@lists.tei-c.org on behalf of James Cummings Sent: November 23, 2015 5:40 AM To: tei-council@lists.tei-c.org Subject: Re: [tei-council] GitHub P6 label, anyone? All in favour of it... though I don't think we should worry too much about breaking backwards compatibility with that particular issue. (Since the solution is a trivial conversion and we could provide XSLT as a method of dealing with it.) FAND-sympathiser, -James On 23/11/15 09:10, Peter Stadler wrote:

...

I was just going through some tickets and came across #1400 „Remove numbered divisions“, wondering whether we need (or want) a P6 label? That way, we could start collecting issues for the day X. That would not necessarily mean that those changes be implemented in P6, but discussion is postponed until then. So, rather than simply closing the issue, we could label it first (and close it then, so it’s not polluting our issue tracker), making it easy to reopen these issues when the time comes.

Cheers Peter

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford -- 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

Peter Stadler

24 Nov 24 Nov

4:49 a.m.

New subject: [tei-council] GitHub P6 label, anyone?

So, I just added a label "postponed for p6“ and applied it to issue #1400 Additionally, I added a link to http://wiki.tei-c.org/index.php/P6-dev which will take you to all the GitHub issues with this label. Re: Milestone. I don’t think we need that now. It would put too much pressure on us ;) Of course, when truly working towards P6, we should create such a milestone. Best Peter

...

Am 23.11.2015 um 19:20 schrieb Martin Holmes :

I'm in favour of a P6 label.

Martin Holmes UVic Humanities Computing and Media Centre mholmes@uvic.ca

________________________________________ From: tei-council-bounces@lists.tei-c.org on behalf of James Cummings Sent: November 23, 2015 5:40 AM To: tei-council@lists.tei-c.org Subject: Re: [tei-council] GitHub P6 label, anyone?

All in favour of it... though I don't think we should worry too much about breaking backwards compatibility with that particular issue. (Since the solution is a trivial conversion and we could provide XSLT as a method of dealing with it.)

FAND-sympathiser,

-James

On 23/11/15 09:10, Peter Stadler wrote:

...
I was just going through some tickets and came across #1400 „Remove numbered divisions“, wondering whether we need (or want) a P6 label? That way, we could start collecting issues for the day X. That would not necessarily mean that those changes be implemented in P6, but discussion is postponed until then. So, rather than simply closing the issue, we could label it first (and close it then, so it’s not polluting our issue tracker), making it easy to reopen these issues when the time comes.

Cheers Peter

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford -- 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

3317

Age (days ago)

3318

Last active (days ago)

List overview

Download

5 comments

5 participants

participants (5)

James Cummings
Kevin Hawkins
Martin Holmes
Peter Stadler
Raffaele Viglianti