[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [oic] RE: interop advisory, example - SVN Limitation
One limitation of SVN, just as of the Wiki, is the lack of a way to lock down any branch so it can't be altered, even by someone with commit permission. This would be rather important for preserving online versions of those advisories that are linked from a current compilation. (There might be a different link for the latest version of an advisory, in case one has been supplanted or otherwise updated.) Also, I don't know if there are URLs that select a specific version rather than the latest one when reaching into the SVN repository. I would hope so, but am not sure about that. Finally, I'd like to see some sort of version block that connects a viewed advisory to the latest, itself, and at least the one before it if not the one immediately after it also (when known). I am not sure that we get much automated help for this. My role model for this is the way that W3C specifications handle it. I've managed to do all of these things with web pages on web sites, but it is all manual effort and I get to choose when it is time to create a new version rather than keep updating the current latest or soon-to-be-next. Having a web-based version control system should make this easier somehow. - Dennis -----Original Message----- From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org] Sent: Thursday, June 10, 2010 11:39 To: oic@lists.oasis-open.org Cc: 'Cherie Ekholm'; 'Hanssens Bart' Subject: RE: [oic] RE: interop advisory, example I'll throw in a little here. SVN is the on-line source-code version-control repository that OASIS makes available to us. The term is an abbreviation for Subversion. It is a well-established open-source effort (usable on SourceForge and many other places) and recently became a project of the Apache Foundation. When someone (usually Bart or myself) checks something into that repository, you will see a notice on this list, just as there are JIRA activity notices. I believe all OIC TC Members have check-in rights, but haven't tested that. Everyone, including the public, can create a working set of any content of the repository they want, and they can keep it synchronized with the OASIS server. But checking in is restricted. The SVN is also readable via the web. The raw view is at <http://tools.oasis-open.org/version-control/svn/oic/> providing an index page for the particular directory and the latest revision made to any part of the repository (any change anywhere advances the version number of the entire repository). There is also a special SVN browser that is supported by the repository. You access it via a different URL, <http://tools.oasis-open.org/version-control/browse/wsvn/oic/?rev=0&sc=1>. You can see more of the managed structure here, as well as learn of the latest additions, what versions they are introduced with, etc. Because the SVN repository operates as a Web (and WebDAV) server, it can also be viewed as a web site, using either the browser view or the raw view. How it works as a web site is a matter of practice and convention. Bart and I have taken advantage of that in a number of ways. Here is what I do: HMTL pages in the repository can be designed to be viewed properly from the repository. For example, this page was done that way, demonstrating a way of annotating the material: <http://tools.oasis-open.org/version-control/svn/oic/SpecAnalysis/constructi on/construction.htm> (you can get here by navigation from the raw view). There are also text files that are provided as ways to carry task items and summaries as additional annotation of the materials under SVN management. E.g., <http://tools.oasis-open.org/version-control/svn/oic/SpecAnalysis/constructi on/construction.txt> This is all by convention and represents my own practices with regard to some materials I have been authoring. That material is rather stale and dormant at the moment as ODF 1.2 commands my attention more. - Dennis - - - - - - - - - - - - - Standards are arbitrary solutions to recurring problems (R. W. Bemer) Although not by becoming the recurring problem (orcmid). When you find yourself in a hole, stop digging. -----Original Message----- From: Cherie Ekholm [mailto:cheriee@exchange.microsoft.com] Sent: Thursday, June 10, 2010 00:18 To: Hanssens Bart; oic@lists.oasis-open.org Subject: [oic] RE: interop advisory, example I knew it was about time for you to gently remind us you would like feedback so I was reading through this Wednesday. :) I like the way you get both a set of advisories and a set of test files from one effort. First question: would all the issues from the unpublished "Interop Profile" be turned into advisories? Second questions: The acronym is probably obvious, but I'm tired tonight and drawing a blank - what is SVN? On the proposed workflow: 3.2 Does "Contact ODF TC" mean log a JIRA issue on the ODF TC database? 4.2 Would a vote during a call also be acceptable to publish an advisory? Or only an eballot? Would we need to wait for an eballot if we had a call happening within a few days of all JIRA issues being resolved? 5.2 Is there a Technical Report template? That might be more appropriate for a collection of advisories than a specification template. On the example advisory: Do you also need to explicitly say that a Consumer that does not support track changes should not lose the element if the file is saved in that application? -----Original Message----- From: Hanssens Bart [mailto:Bart.Hanssens@fedict.be] Sent: Wednesday, June 09, 2010 10:50 PM To: oic@lists.oasis-open.org Subject: [oic] RE: interop advisory, example Hi, any comments so far ? I'd really like to nail this down before the next call :-) Thanks Bart ________________________________________ From: Hanssens Bart [Bart.Hanssens@fedict.be] Sent: Friday, June 04, 2010 7:49 PM To: oic@lists.oasis-open.org Subject: [oic] interop advisory, example Hi, as discussed during the last TC call, I've created an example on how I think an Interop Advisory could look like: http://wiki.oasis-open.org/oic/InteropAdvisories I've also added a suggestion for a workflow. Keywords: - practical - focused - fast consensus Even if the proposed advisory turns out to be an implementation bug, it might still be useful for creating an ODF test suite (or as input for the next State of Interop report) Best regards Bart --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]