W3C home > Mailing lists > Public > public-xg-lld@w3.org > June 2011

Re: Blog for gathering comments on draft report

From: Peter Murray <peter.murray@lyrasis.org>
Date: Wed, 22 Jun 2011 10:21:36 -0400
To: Karen Coyle <kcoyle@kcoyle.net>
CC: "public-xg-lld@w3.org" <public-xg-lld@w3.org>
Message-ID: <D7DDBC05-FF2B-4D17-B69A-C042F1638EE2@lyrasis.org>
As an aside, you can easily do this by going to the history page of the wiki page and copying the link of the date/time entry.  It'll come out looking like this:



On Jun 22, 2011, at 10:15 AM, Karen Coyle wrote:
> Yes, we would copy-paste the section, but I assumed that there would  
> be a link back to the report so that someone looking at a section  
> could see the context. If so, it should link back to the version with  
> the same date/time stamp as the version that was pasted.
> kc
> Quoting Antoine Isaac <aisaac@few.vu.nl>:
>> Hi Karen,
>> We agree on the requirements. But perhaps not on the means to meet  
>> them. I just thought that we would copy-paste the entire section  
>> contents into the blog posts, which would alleviate your worry 2.
>> That being said, we could still create extra "editor's draft" wiki  
>> pages, for these reviewers who don't use the wiki
>> http://www.w3.org/2005/Incubator/lld/wiki/Benefits
>> would be duplicated into
>> http://www.w3.org/2005/Incubator/lld/wiki/Benefits_EditorsDraft
>> which could be the one edited (and both could link to each other in  
>> a disclaimer)
>> But again I think this would be less important for reviewers that  
>> got the report via the wiki: they should expect a wiki to change...
>> Cheers,
>> Antoine
>>> One thing Jodi, Peter, TomB and I discussed this morning in a chat  
>>> about our sections is that the blog posts should link to two things:
>>> 1 - the current state of the report
>>> 2 - the time-stamped version of the section that is being reviewed
>>> This way, folks can look at the entire section as it was when the  
>>> review was started, but we can continue making changes without it  
>>> changing what people see if they go to look at the section under  
>>> review.
>>> I realize I might not have explained that well, but the main thing  
>>> is that we thought it would be confusing if the reviews are taking  
>>> place on a moving target, especially if someone goes from a blog  
>>> comment to the section being reviewed and doesn't see the text that  
>>> the commenter referenced.
>>> No matter what we do, editing and reviewing on a text that is  
>>> changing will be complicated. Links to "this version" and "latest  
>>> version, possibly with edits" might make it clearer.
>>> kc
>>> Quoting Emmanuelle Bermes <manue@figoblog.org>:
>>>> It would probably be easy enough to use the blog categories to order
>>>> the sections. We could also have a "table of content" post linking to
>>>> other posts, and use it to gather the general comments. I'm pretty
>>>> sure there must be a function in Wordpress that allows to make a
>>>> specific post stay always at the top of the home page.
>>>> Monica, you can add me as admin, I'll be happy to have a look.
>>>> Emma
>>>> On Tue, Jun 21, 2011 at 4:44 PM, Antoine Isaac <aisaac@few.vu.nl> wrote:
>>>>> +1 to all this.
>>>>> Note that since Monica's blog is Wordpress-based, it should be  
>>>>> easy to have
>>>>> digress.it, according to what they say:
>>>>> http://digress.it/help/#how-do-i-download-digressit
>>>>> Monica, do you think someone at UKOLN could fetch the code and  
>>>>> put it in the
>>>>> plug-in folder?
>>>>> If not, then we'd have to use some tricks:
>>>>> - to reflect the structure we might have to post the final sections first?
>>>>> That might be the best way not to lose the sequence, at least.
>>>>> - for enabling posting comments on the entire document, we should have one
>>>>> specific "report" post, with the title. And put it in front (ie.,  
>>>>> posting it
>>>>> last?)
>>>>> Cheers,
>>>>> Antoine
>>>>>> Seconding Jodi's comments: it is important that the basic  
>>>>>> structure of the
>>>>>> report be visible. Also that people can post comments that are  
>>>>>> general, no
>>>>>> just specific to a sub-section.
>>>>>> I also like the idea of listing recent changes.
>>>>>> kc
>>>>>> Quoting Jodi Schneider <jodi.schneider@deri.org>:
>>>>>>> Thanks so much for doing this, Monica! I can be an admin, if you like
>>>>>>> (use jodi.a.schneider@gmail.com ). These are good comment settings.
>>>>>>> A clean theme would be the veryplaintext one:
>>>>>>> http://www.plaintxt.org/#veryplaintxt
>>>>>>> Did we decide on whether digress.it would be a good plugin to use?
>>>>>>> Whoever does post the report -- I'd suggest posting it in small  
>>>>>>> sections,
>>>>>>> but making sure that the navigation makes sense (i.e. the  
>>>>>>> default shows the
>>>>>>> first part first, the table of contents shows up in a sidebar).
>>>>>>> Perhaps somebody can suggest how to display "recent comments" in a
>>>>>>> sidebar? This should be a simple change and I know it's common in many
>>>>>>> blogs.
>>>>>>> -Jodi
>>>>>>> On 20 Jun 2011, at 13:42, Monica Duke wrote:
>>>>>>>> I took an action on Thursday to set up a blog to be used to gather
>>>>>>>> comments on the draft report from the wider community. The blog is now
>>>>>>>> available at:
>>>>>>>> http://blogs.ukoln.ac.uk/w3clld/
>>>>>>>> # If I may suggest 2 next steps:
>>>>>>>> 1)We need to agree how we are going to post the report and do it asap -
>>>>>>>> we did not agree this detail on the call. I guess it would be  
>>>>>>>> best if 2-3
>>>>>>>> volunteers (or even just 1?) took care of that. We can't spend  
>>>>>>>> too much time
>>>>>>>> on deciding and doing it so we do not miss the chance to add  
>>>>>>>> the url to any
>>>>>>>> emails being sent out to lists to request comments.
>>>>>>>> 2) I need to give access to others in the group who can help administer
>>>>>>>> the blog and post to it (as will be agreed in 1). I suggest  
>>>>>>>> that I add one
>>>>>>>> or two more as administrators, and others as editors. Please  
>>>>>>>> send me email
>>>>>>>> addresses and roles as soon as they are agreed, and I will add them.
>>>>>>>> # Comments settings - the following are selected (this can of course be
>>>>>>>> changed)
>>>>>>>> Comment author must have a previously approved comment (i.e. comment
>>>>>>>> will be moderated until user has a first one approved)
>>>>>>>> # Appearance
>>>>>>>> I suspect others will agree that other than for purposes of  
>>>>>>>> usability we
>>>>>>>> do not spend much time on cosmetics. I have done the basic,  
>>>>>>>> but I can make
>>>>>>>> other changes in response to suggestions, and once we have one  
>>>>>>>> or two other
>>>>>>>> administrators they too will be able to assist with this.
>>>>>>>> Basic Wordpress features, plug-ins, settings etc are available.
>>>>>>>> Monica

Peter Murray         Peter.Murray@lyrasis.org        tel:+1-678-235-2955                 
Ass't Director, Technology Services Development   http://dltj.org/about/
LYRASIS   --    Great Libraries. Strong Communities. Innovative Answers.
The Disruptive Library Technology Jester                http://dltj.org/ 
Attrib-Noncomm-Share   http://creativecommons.org/licenses/by-nc-sa/2.5/ 
Received on Wednesday, 22 June 2011 14:22:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:35:57 UTC