Re: [tei-council] ODD question

I know nothing about Sourceforge’s git offerings, but I imagine you can link to git commits in much the same way. Github’s issues allow you to do the same thing with projects hosted there. The difficulty would be in what to do if we moved repos, but kept bug/feature tracking in place. Sourceforge is long in the tooth. I don’t know whether, for example, we can expect any substantial upgrades in the future. I saw this http://blog.gluster.org/2013/08/how-far-the-once-mighty-sourceforge-has-fall... http://blog.gluster.org/2013/08/how-far-the-once-mighty-sourceforge-has-fall... and related commentary (including substantial rebuttal) on Hacker News recently (https://news.ycombinator.com/item?id=6262347 https://news.ycombinator.com/item?id=6262347). At the very least, I think we need to have an exit strategy for SF. Even the rebuttal on HN points out that it’s a money-loser for its parent company.

On Jun 1, 2015, at 12:11 , Martin Holmes wrote:

Hi Hugh,

That's excellent -- if we can link to the rev in github, we're half-way there. The other thing we do is track bug and FR fixes by rev number in our comments on tickets; our Guidelines might be updated to ask people to include the date and time of the commit, otherwise it's not easy to see the sequence of events.

Cheers, Martin

On 15-06-01 06:08 AM, Hugh Cayless wrote:

...

Ok. I’m not 100% certain how we use rev numbers everywhere in the plumbing, so a list of some sort would be very helpful, but you can get an idea by looking at the footer of http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/index.html http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/index.html <http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/index.html http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/index.html>, my most recently generated copy of the Guidelines. The readme link is busted, because there is no readme, but the version number takes you to the latest commit in my GitHub repo. Basically, it’s just the first 7 digits of the commit hash.

...

On Jun 1, 2015, at 8:43 , Martin Holmes wrote:

+1 from me for a git/github tutorial, especially focused on how it would change our workflow with P5, and how we would replace the rev numbers that are so useful for us.

Cheers, Martin

On 15-06-01 04:31 AM, Hugh Cayless wrote:

...

/blob/ is a GitHub thing, not a Git thing. It’s where you’d expect to find it, with all the other specs. Your and Lou’s diagnosis is correct though.

Your confusion makes me wonder whether I ought not to do a Git tutorial at some point. It’s a different enough beast from svn that you can’t really extrapolate how it works from your knowledge of the latter. Would that help?

Hugh

...

On May 31, 2015, at 18:22 , Syd Bauman wrote:

Can't tell, because I can't even find what you're doing. I cloned your repo[1]: $ git clone https://github.com/hcayless/TEI-Guidelines.git

But there was no blob/ directory, and no secl.xml. So I guess I'm not using the right approach to look for this.

But note that there needs to be something like

in a file that is included in the Guidelines, probably Source/Guidelines/en/PH-PrimarySources.xml in this case.

Notes ----- [1] If I understand correctlly, that's one real advantage of svn over git: I could have checked-out just the subdirectory I wanted from svn. I can't do that in git, can I?

...

Hope your trips home went well (or are going well). I’m having a hard time defining a new spec for <secl>. Does anybody know why https://github.com/hcayless/TEI-Guidelines/blob/secl/P5/Source/Specs/secl.xm... https://github.com/hcayless/TEI-Guidelines/blob/secl/P5/Source/Specs/secl.xm... wouldn’t be picked up by any of the build processes I’m running? It’s as though the file is invisible. There’s clearly some incantation I’m not including, but I don’t know what it is… -- 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

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

PLEASE NOTE: postings to this list are publicly archived