Re: [tei-council] SVN Users

I believe you can set up as many groups as you like, with differing permission levels on repos, and that subsequently any of the members of those groups will be eligible to be assigned tickets. So we could in theory have a group who had read-only access to the repo and who would have to issue a pull request in order to complete an issue. In practice, I'd rather not make it too complex. On the other hand, if there's a "Council" group, people who aren't on Council probably ought not to be in it... Should I add a "Contributors" group then, and we can talk about who should go into it and what they should be able to do? As a followup, I've tracked down a number of the missing users, but there are still a couple I could use help with. I've added what clues I could find to the spreadsheet, if you'd be willing to take another look. I think we should just call the user "root" "TEI Council", and use the Council email address. Thanks, Hugh On Thu, Aug 13, 2015 at 8:33 AM, James Cummings wrote:

On 13/08/15 13:09, Hugh Cayless wrote:

...

This is different from the list Raff sent out to the TEI-L. That one was all people who’ve used the ticketing system. This is all people who’ve actually committed to the SVN repo. It’s got nothing to do with who gets access, just with preserving history. The standard SVN -> Git clone method doesn’t get names and addresses for people because SVN only keeps usernames.

Ah I see.

We should talk about policy with regard to push access. We haven’t

...

historically automatically revoked such access from departed Council members. Would it be better to start doing so now, since we'll have an easier path to getting changes in from outside?

Actually that isn't strictly true. What we had done for awhile is use the three levels of Admin / Developer / Member on SF. If you are logged in as an Admin (kevin/hugh/james/lou/martin) and go to https://sourceforge.net/p/tei/admin/groups/ you can see the three groups. The reason we kept ex-council members (or others who had contributed) on 'Member' level access was that it meant that tickets could be assigned to them.

What are the rules in github for who an issue can be assigned to? Only those who have push rights to the repository? Anyone on github?

James

...

On Aug 13, 2015, at 7:58 , James Cummings

...

wrote:

I'm assuming that this will just link up old FR/Bugs as new issues to the person's email address (and if it happens to be the same as their primary github one, maybe just work).

Where does this list come from? It seems to be all the admin/developers/members? Except, actually, it seems to be missing some as well. How was it generated?

Surely, if we're going to do this we need to do this for a lot more people... i.e. all those who have submitted tickets?

We're not talking about giving these people direct push access or anything, right? While I'm in favour of more people committing, I'd suggest that those on council get direct push access, everyone else uses fork+pull request, or just submitting an issue. (For the Guidelines repo only. I think for Stylesheets and others that the group of committers can be larger.)

I've filled in a bunch of the ones I knew.

-James

On 13/08/15 01:52, Hugh Cayless wrote:

...

Though, that said, if it was one you use on GitHub, it might be able to link you to your account.

Sent from my phone.

On Aug 12, 2015, at 19:39, Martin Holmes wrote:

...

Ah, sorry; I've been filling in that spreadsheet with the primary email I happen to know about for that person.

Cheers, Martin

On 15-08-12 04:06 PM, Paul Schaffner wrote:

...

I assume you mean the email address *as known to SourceForge* ? (I can never remember which of my two dozen email addresses was used for which account where.) Or do you mean email addresses *as known to GitHub* ? Which may well be different. pfs

On Wed, Aug 12, 2015, at 15:41, Hugh Cayless wrote: > Looks like we can achieve a happier SVN to Git conversion if we > supply > Git with a mapping between SourceForge usernames and proper names + > email > addresses in the form > > hcayless = Hugh Cayless > > I’ve started a spreadsheet with usernames who’ve committed to our > repo at > > https://docs.google.com/spreadsheets/d/1N8hIBphezGsNB0SvEx7wSamyshNrszeNrlm6... > < > https://docs.google.com/spreadsheets/d/1N8hIBphezGsNB0SvEx7wSamyshNrszeNrlm6... > > > > Can you all please pitch in to help fill it out? > > Thanks, > Hugh > > > -- > 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

-- 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

-- 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