[tei-council] updating TCW20

[James Cummings]

I suggest then an ad hoc group of martin, david, kevin, sebastian and me 
to discuss (by email/skype/whatever) the security arrangements and other 
necessary steps for managing a release that shouldn't be discussed here.

-james

On 19/12/11 16:10, Martin Holmes wrote:
> I'm happy to be involved if folks think I should be -- there was a
> concern that more people should be able to manage releases etc. Kevin
> also has a login for the CMS, so we should bring him in, and Sebastian
> is the one who knows where the scripts etc. are.
>
> Cheers,
> Martin
>
> On 11-12-19 07:18 AM, David Sewell wrote:
>> There is not a lot that needs discussing offline--really just the portions of
>> new release implementation that currently require specific access on tei-c.org,
>> plus some agreement on where to store information about things that should not
>> be fully exposed to the public. Three or four of us on an email discussion or
>> Skype call should be sufficient, I think.
>>
>> James has volunteered, and I will as webmaster of course. Who else?
>>
>> David
>>
>> On Mon, 19 Dec 2011, James Cummings wrote:
>>
>>> On 19/12/11 04:03, Martin Holmes wrote:
>>>> I'm a little uncomfortable with there being a TEI-council-secure list. I
>>>> realize there would be utility in it, but I fear there might be a
>>>> temptation to use it for purposes other than pure security-related
>>>> issues, and after what happened with the Board this year, I think
>>>> transparency is very important for us at the moment.
>>>
>>> I agree with Martin here. Also there is the problem that if you have a
>>> 'secure' list then you might accidentally post something destined towards
>>> that to the non-secure list.  It just opens up more chances for problematic
>>> accidents.
>>>
>>> I don't think most of the discussion is that insecure to have in
>>> public...whether to have such an account or not etc. But yes, if you think it
>>> affects security in virginia we should abide by that and move it off-list.
>>>
>>>> I vote for identifying the subgroup of council that need to know
>>>> security-related information, and taking the discussion onto Skype,
>>>> which would be more secure than email of any sort, anyway.
>>>
>>> I'm happy to be involved in such a discussion, and would vote for this
>>> (agnostic about communication technology since we won't be pass the password
>>> that way).
>>>
>>> -James
>>>
>>>
>>>>
>>>> Cheers,
>>>> Martin
>>>>
>>>> On 11-12-18 04:58 PM, David Sewell wrote:
>>>>> I hate to say it, but I think that this discussion needs to be moved off
>>>>> of the tei-council list. We are moving into a territory that has
>>>>> security implications for tei-c.org (discussion of user accounts,
>>>>> permissions, filesystem paths, etc.), and this shouldn't be available on
>>>>> an email list with open-access archives.
>>>>>
>>>>> We can either have a subset of Council continue this discussion offline.
>>>>> Or, possibly a better solution, I could create a new Virginia-hosted
>>>>> list called something like "TEI-council-secure" that would have archives
>>>>> available only via password to current list members.
>>>>>
>>>>> What do you people think?
>>>>>
>>>>> David
>>>>>
>>>>> On Mon, 19 Dec 2011, James Cummings wrote:
>>>>>
>>>>>>
>>>>>> Nope, entirely different login needed.
>>>>>>
>>>>>> Might it make sense to have a 'teicouncil' account whose login details
>>>>>> could  be passed to the 'release technician' (perhaps a better term for
>>>>>> the person overseeing a release than 'pumpkin holder'?) for each release?
>>>>>>
>>>>>> -James
>>>>>>
>>>>>> On 18/12/11 23:11, Martin Holmes wrote:
>>>>>>> I've tried ssh-ing into tei-c.org with my CMS login, but I can't get in.
>>>>>>> Presumably some other account is needed? Of am I trying to log into the
>>>>>>> wrong server?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Martin
>>>>>>>
>>>>>>> On 11-12-18 09:43 AM, Sebastian Rahtz wrote:
>>>>>>>>
>>>>>>>> On 18 Dec 2011, at 17:08, Martin Holmes wrote:
>>>>>>>>
>>>>>>>>> Is there a specific account you need to log in as to run the install
>>>>>>>>> script, or can anyone with login privileges on tei-c.org do it?
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> the account needs write access to /project/tei (vel sim), so not sure.
>>>>>>>> try editing stuff in the Vault there to test
>>>>>>>>
>>>>>>>> the tei-install.sh script is pretty simple - have a read and see
>>>>>>>> what it does.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Stormageddon Rahtz

>>>>>>>> Head of Information and Support Group, Oxford University Computing
>>>>>>>> Services
>>>>>>>> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>>>>>>>>
>>>>>>>> Sólo le pido a Dios
>>>>>>>> que el futuro no me sea indiferente
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Dr James Cummings, InfoDev,
>>>>>> Computing Services, University of Oxford
>>>>>> --
>>>>>> tei-council mailing list
>>>>>> tei-council at lists.village.Virginia.EDU
>>>>>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>>>>>
>>>>>> PLEASE NOTE: postings to this list are publicly archived
>>>>>
>>>
>>>
>>>
>>
>


-- 
Dr James Cummings, InfoDev,
Computing Services, University of Oxford