[KI-LC] Fwd: Specification (etc.) publication regime on the ki.org site

Eve Maler eve at xmlgrrl.com
Wed Jul 27 16:31:37 CDT 2016


*Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl


---------- Forwarded message ----------
From: Oliver Maerz <oliver at kantarainitiative.org>
Date: Tue, Jul 26, 2016 at 5:31 PM
Subject: Re: Specification (etc.) publication regime on the ki.org site
To: Eve Maler <eve at xmlgrrl.com>
Cc: Colin Wallis <colin at kantarainitiative.org>, Andrew Hughes <
andrewhughes3000 at gmail.com>


Maybe one more comment: There are some security concerns if we want to give
access via sftp to more users. We should probably move the docs site to a
separate cloud server, then.

On Tue, Jul 26, 2016 at 8:26 PM, Oliver Maerz <oliver at kantarainitiative.org>
wrote:

> Hello Eve,
>
> At this point you have the only account (emaler) that has permissions for
> the docs.kantarainitiative.org site. You are the only one uploading files
> via sftp to our server. I also double checked the permissions and you have
> full permissions to the root (/) directory of the doc site. Of course I
> could take those permissions away and set permissions as fine grained as we
> want (for example restrict your account to /uma). I could also setup
> directories for other workgroups and the directories for rec, draftrec, etc
> with their own users and restricted access. Though personally I have my
> doubts a lot of other chairs would use such a sftp based system to upload
> documents.
>
> If we wanted to implement something like that with Github then we could
> setup something like:
> - Give each group their own repository (only group chairs and participants
> would have access) - and then
> - Make each of those repositories a submodule of a Kantara wide Doc
> repository (that only staff and LC would have access to)
>
> The Kantara Doc repository could then also have the rec, draft, report and
> other folders (only staff/LC would upload files to those)
>
> Best regards,
> Oliver
>
>
>
> On Tue, Jul 26, 2016 at 6:51 PM, Eve Maler <eve at xmlgrrl.com> wrote:
>
>> First, I'm happy to bring this up on the LC call.
>>
>> I think it's a bit more than just asking for a technical change;
>> actually, I have more permissions than is perhaps ideal, since it appears
>> that, right now, I can create any "areas" I want on Kantara docs space,
>> e.g.:
>>
>> *Today:* (this is what we do to publish UMA specs now, but is a big
>> messy namespace)
>> docs.kantarainitiative.org/uma/somefile.html
>>
>> *Unpossible:* (it's probably bad that I can do this! -- but I'm not sure
>> if it can be prevented)
>> docs.kantarainitiative.org/foobar/ (an area that is not meant for the
>> UMA WG)
>>
>> *Tomorrow:* (this is something like what we should do to publish
>> WG-produced UMA specs in future)
>> docs.kantarainitiative.org/uma/wg/somefile.html (WG-approved specs)
>> docs.kantarainitiative.org/uma/ed/somefile.html (editors' drafts of
>> specs)
>> docs.kantarainitiative.org/uma/other/somefile.html (other artifacts that
>> aren't specs, if needed)
>>
>> *Tomorrow:* (what I am wondering if we should ask Oliver to set up as a
>> general practice)
>> docs.kantarainitiative.org/bsc/ (as an example, for a new WG or DG, a
>> space they can manage)
>> docs.kantarainitiative.org/rec/ (where all published approved
>> Recommendations should live)
>> docs.kantarainitiative.org/draftrec/ (where all published draft
>> Recommendations should live)
>> docs.kantarainitiative.org/report/ (where all published Reports should
>> live)
>> docs.kantarainitiative.org/other/ (where all other published
>> member-approved/level docs should live)
>>
>> If the FTP permissions can't be set up as fine-grained as we like, there
>> are two alternatives I can think of, and then it depends on how heavyweight
>> any one of the options is on all the parties concerned:
>>
>>    - Set up different GitHub (or other) repositories for each of the
>>    distinctions laid out above, where the final published versions of docs can
>>    live in order to achieve the goal, with the ability to set up permissions
>>    the way we like
>>    - Ask Oliver to upload each final published file in question to the
>>    appropriate final resting place (which will occasionally come with a
>>    request to set up a symbolic link, which we also ask him to do already)
>>
>> I hope this helps!
>>
>>
>>
>> *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
>>
>>
>> On Tue, Jul 26, 2016 at 7:07 AM, Oliver Maerz <
>> oliver at kantarainitiative.org> wrote:
>>
>>> Hello all,
>>>
>>> Sorry for the late reply - but we had a federal holiday here, yesterday.
>>>
>>> I am not sure I fully understand the original request. Just for
>>> clarification the docs server (docs.kantarainitiaitive.org) was created
>>> per Eve's request. A uma folder was setup in the root directory with full
>>> permissions for user "emaler". So inside the uma folder (
>>> docs.kantarainitiaitive.org/uma) you Eve have full permissions (delete,
>>> create, edit, read for both folders and files). In case you want to have
>>> full permissions to the root folder (docs.kantarainitiaitive.org/) as
>>> well then that would be no problem. Just let me know.
>>>
>>> Best regards,
>>> Oliver
>>>
>>> On Tue, Jul 26, 2016 at 6:50 AM, Colin Wallis <
>>> colin at kantarainitiative.org> wrote:
>>>
>>>> Oops.. apologies.. should have CC'd you in as well.
>>>>
>>>> Cheers
>>>> Colin
>>>>
>>>> ---------- Forwarded message ----------
>>>> From: Colin Wallis <colin at kantarainitiative.org>
>>>> Date: Tue, Jul 26, 2016 at 10:49 AM
>>>> Subject: Re: Specification (etc.) publication regime on the ki.org site
>>>> To: Eve Maler <eve at xmlgrrl.com>
>>>> Cc: Andrew Hughes <andrewhughes3000 at gmail.com>
>>>>
>>>>
>>>> Right then.
>>>> So I'll pass that onto Oliver as it seems bow that technically, it is
>>>> all doable.
>>>> All you want is 'permission', right?
>>>> And that is an LC decision in the first instance, so I'mm cc'ing in
>>>> Andrew as LC Chair for consideration.
>>>> Cheers!
>>>> Colin
>>>>
>>>> On Tue, Jul 26, 2016 at 2:25 AM, Eve Maler <eve at xmlgrrl.com> wrote:
>>>>
>>>>> In fact, through SFTP, I just confirmed that I'm able to create
>>>>> subfolders of docs.ki.org/uma/. And it appears that I'm even able to
>>>>> create folders that are a peer to docs.ki.org/uma/, which may not
>>>>> have been avoidable but isn't ideal!
>>>>>
>>>>>
>>>>>
>>>>> *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
>>>>>
>>>>>
>>>>> On Mon, Jul 25, 2016 at 6:07 PM, Eve Maler <eve at xmlgrrl.com> wrote:
>>>>>
>>>>>> Thanks for your consideration!
>>>>>>
>>>>>> I should point out that, on second look, the mention of "*/docs*"
>>>>>> isn't accurate, vs. "*docs.*ki.org". And I bet that I could create
>>>>>> subdirectories in the docs.ki.org/uma directory right now, and
>>>>>> thereby break up specs in different stages and non-specs into different
>>>>>> directories already if I wanted to. The biggest question might simply be
>>>>>> whether Kantara is willing to create and use a) either a separate directory
>>>>>> structure for Reports and Recommendations and Draft Recommendations that
>>>>>> are past the WG/DG voted stages and into LC-approved and Member-approved
>>>>>> stages, or b) a GitHub or other formally versioned and managed repository
>>>>>> for same.
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 25, 2016 at 9:28 AM, Colin Wallis <
>>>>>> colin at kantarainitiative.org> wrote:
>>>>>>
>>>>>>> Whew! OK then...
>>>>>>> Was a bit ore to it than I saw on the screen last week.
>>>>>>> This will keep Oliver out of mischief!:-).
>>>>>>> Thanks Eve.
>>>>>>>
>>>>>>> On Mon, Jul 25, 2016 at 5:12 PM, Eve Maler <eve at xmlgrrl.com> wrote:
>>>>>>>
>>>>>>>> Here is the ask from the UMA WG editorial meeting where we
>>>>>>>> discussed our publication tool chain and process:
>>>>>>>>
>>>>>>>> "We want to ask Kantara staff to break out the ".../docs" area so
>>>>>>>> that there's a specific Kantara space for each level of KI-approved types
>>>>>>>> of documents, e.g. Recommendations and other, and then each group has its
>>>>>>>> own area for group-approved and other stages of docs. This helps those who
>>>>>>>> want to access docs and distinguish them by their location (e.g. through
>>>>>>>> browser history)."
>>>>>>>>
>>>>>>>> (You can see all of our notes in this thread
>>>>>>>> <https://groups.google.com/forum/#!searchin/kantara-initiative-uma-wg/publication/kantara-initiative-uma-wg/2OIwnv9SqJo/4XTUyaSBAgAJ>,
>>>>>>>> particularly the most recent message.)
>>>>>>>>
>>>>>>>> An example Justin pointed us to of "doing this right" is OpenID
>>>>>>>> Foundation, where:
>>>>>>>>
>>>>>>>>    - The HEART WG has its own repository here for items that have
>>>>>>>>    been produced by the group but not approved at the Foundation level yet:
>>>>>>>>    http://openid.bitbucket.org/HEART/
>>>>>>>>    - The OIDF has a different repository for membership-voted
>>>>>>>>    items: http://openid.net/specs/ (redirects to
>>>>>>>>    http://openid.net/developers/specs/)
>>>>>>>>    - An example of such a lower-level item is this one:
>>>>>>>>    http://openid.bitbucket.org/HEART/openid-heart-oauth2.html
>>>>>>>>    - An example of an Implementer's Draft voted on by the OIDF
>>>>>>>>    membership (whose filename also reflects this reality) that is stored in a
>>>>>>>>    higher-level OIDF repository is this one:
>>>>>>>>    http://openid.net/specs/openid-heart-oauth2-1_0-ID1.html
>>>>>>>>
>>>>>>>> Now, final published HTML/PDF/whatever specs don't have to go into
>>>>>>>> a GitHub or bitbucket repository. I've been just uploading these into a
>>>>>>>> directory through FTP, which is just fine. But the key thing is that the
>>>>>>>> UMA WG has only its own docs.ki.org/uma/... area to play with,
>>>>>>>> even for member-approved Recommendations, and if you look at the Reports
>>>>>>>> and Recommendations
>>>>>>>> <https://kantarainitiative.org/reports-recommendations/> page all
>>>>>>>> the other artifacts are stored in random other places too.
>>>>>>>>
>>>>>>>> Thoughts?
>>>>>>>>
>>>>>>>>
>>>>>>>> *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter:
>>>>>>>> @xmlgrrl
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Executive Director
>>>>>>> Kantara Initiative Inc. <https://kantarainitiative.org/>
>>>>>>> Have you signed the pledge?
>>>>>>> <https://kantarainitiative.org/digital_identity_professional/>
>>>>>>> Cell: +44 (0)7490 266 778
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Executive Director
>>>> Kantara Initiative Inc. <https://kantarainitiative.org/>
>>>> Have you signed the pledge?
>>>> <https://kantarainitiative.org/digital_identity_professional/>
>>>> Cell: +44 (0)7490 266 778
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Executive Director
>>>> Kantara Initiative Inc. <https://kantarainitiative.org/>
>>>> Have you signed the pledge?
>>>> <https://kantarainitiative.org/digital_identity_professional/>
>>>> Cell: +44 (0)7490 266 778
>>>>
>>>>
>>>
>>>
>>> --
>>> *Oliver Maerz*
>>> External Consultant
>>>
>>> *Kantara Initiative*
>>> oliver (at) kantarainitiative.org
>>> http://www.kantarainitiative.org
>>>
>>>
>>> The information contained in this electronic message and any attachments
>>> to this message are intended for the exclusive use of the addressee(s) and
>>> may contain confidential or privileged information. No representation is
>>> made on its accuracy or completeness of the information contained in this
>>> electronic message. Certain assumptions may have been made in the
>>> preparation of this material as at this date, and are subject to change
>>> without notice. If you are not the intended recipient, you are hereby
>>> notified that any dissemination, distribution or copying of this e-mail and
>>> any attachment(s) is strictly prohibited. Please reply to Oliver Maerz and
>>> destroy all copies of this message and any attachments from your system.
>>>
>>>
>>>
>>
>
>
> --
> *Oliver Maerz*
> External Consultant
>
> *Kantara Initiative*
> oliver (at) kantarainitiative.org
> http://www.kantarainitiative.org
>
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain confidential or privileged information. No representation is
> made on its accuracy or completeness of the information contained in this
> electronic message. Certain assumptions may have been made in the
> preparation of this material as at this date, and are subject to change
> without notice. If you are not the intended recipient, you are hereby
> notified that any dissemination, distribution or copying of this e-mail and
> any attachment(s) is strictly prohibited. Please reply to Oliver Maerz and
> destroy all copies of this message and any attachments from your system.
>
>
>


-- 
*Oliver Maerz*
External Consultant

*Kantara Initiative*
oliver (at) kantarainitiative.org
http://www.kantarainitiative.org


The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain confidential or privileged information. No representation is made
on its accuracy or completeness of the information contained in this
electronic message. Certain assumptions may have been made in the
preparation of this material as at this date, and are subject to change
without notice. If you are not the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this e-mail and
any attachment(s) is strictly prohibited. Please reply to Oliver Maerz and
destroy all copies of this message and any attachments from your system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://kantarainitiative.org/pipermail/lc/attachments/20160727/f41580d4/attachment-0001.html>


More information about the LC mailing list