[Bf-docboard] Current state of wiki updating.

Tue Sep 4 13:02:12 CEST 2012

How about a button with was this helpful.  X number gets it live and y gets it removed.  

Something like a page of "un reviewed" pages at the top a bar for rating yes or no.  

Sent from my iPhone

On Sep 4, 2012, at 3:53 PM, Fade <fade_docboard_blender at ymail.com> wrote:

> I probably won't be able to make the Wednesday meeting as it's right before I leave for work. My thoughts on the matter are pretty obvious though.
> 
> - I'm in favour of ditching any formal review system of individual submissions/contributions. 
> - I don't really like the idea of assigning people roles. e.g. writer for the modelling chapter. 
> - I think a targeted review of chapters could work if everyone still wants some form of peer review. i.e. mini versions of the effort that created the current task list.
> - The task list table is a convenient way of logging and finding things that need doing and should be continued indefinitely.
> 
> Basically I'd like to see less formal processes and more generalised goals. Contributors to the wiki tend to drop in and out over time, so let's work with that. Open up editing again, but encourage contributors to fix the already identified issues rather than having the message say they have to wait until someone gets around to reviewing their contribution. If I'm an infrequent contributor, I'd be more inclined to continue contributing if I didn't have to wait for approval and I can clearly see what needs fixing.
> 
> Cheers
> Fade
>  
> On 09/04/12 08:02, Kesten Broughton wrote:
>> we will definitely take notes and post back here.  Does IRC have an auto dump that we can edit?  Also, if we don't get quarum for wed at 2 pm CST, i suggest we try sunday at 10 or 11 am GMT (i think that's when the #blendercoders finish).
>> 
>> 
>> 
>> On Mon, Sep 3, 2012 at 4:50 PM, amdbcg <amdbcg at gmail.com> wrote:
>> @Wim: Welcome!  Once the meeting time is set, try to make it to the meeting. You're free to help :D. I'm sure you've already read the  Style Guidelines and are familiar with templates for formatting. Your technical writing skills will be a nice addition to this team.
>> 
>> @Board: Just a refresher on SCRUM roles: http://en.wikipedia.org/wiki/Scrum_(development)#Roles . We can switch off roles throughout the year if desired.
>> 
>> Product/Doc Owner -The "Leader" of the team : I nominate Kesten since he is organizing a first meeting. 
>> 
>> Scrum Master: I would like to help out with the Scrum Master since I was posting in the IRC and helped get this off its feet. If someone else thinks they can also help fulfill this position, feel free to speak up - An               additional few people  to switch off with is always nice. 
>> 
>> Dev/Doc Team - if you're on the mailing list, this is your role :
>>  At the beginning of each (week/ 2 weeks/ month) , you will be given a list of assignments. 
>> Assignments will either be distributed via dictatorship model, or a first-come-first-serve model. 
>> After you complete your doc assignment, you will be expected to review at least 3 other completed docs from other people in a round-robin fashion.
>> After a doc's page is reviewed by 3 dev/doc team members and/or the  Product/Doc owner, it will come off the task list.
>> A 1-5 day period will be allocated for the dev/doc team to find 1-4 pages to add to the queue of assignments for the following week.
>> If you would like to edit, modify, or critique this method, feel free to do so. 
>> Perhaps we can use Google Calendar  for the schedule? 
>> 
>> @Kesten: The meeting sounds fine. I'm not sure If I can make it due to my job, but I will try. Can you have someone take notes? 
>> 
>> -amdbcg
>> 
>> 
>> On 9/3/2012 4:00 PM, Wim Teuling wrote:
>>> Although I am a newbie here, I do have technical writing and a lot of instructional material writing experience. I'd like to participate as well, if allowed. 
>>> 
>>> From: amdbcg <amdbcg at gmail.com>
>>> To: Blender Documentation Project <bf-docboard at blender.org> 
>>> Sent: Monday, September 3, 2012 1:53 PM
>>> Subject: Re: [Bf-docboard] Current state of wiki updating.
>>> 
>>> A Scrum meeting sounds excellent. Wednesday night? what time in UTC? I'm in the USA (CST -6:00 UTC)
>>> When the meeting takes place, could                                   someone take notes, summarize, and                                   post these notes back here? This will                                   put everyone on the same page. 
>>> -amdbcg
>>> 
>>> 
>>> On 9/3/2012 8:38 AM, Kesten Broughton wrote:
>>>> One thing that would really help with relaxing the review process and avoid things getting messed up would be a history tab.  Many wikis have this and it serves as a version control of sorts.  I believe it is "built in" to the wiki framework and should just need enabling.
>>>> 
>>>> This way, at times when our reviewer to contributor count is too low we could allow contributions to be pushed live before review with a note that "This page needs review" like wikipedia has.  If the new contribution is really "messed up" then the change could be reverted (but not destroyed).  
>>>> 
>>>> When our reviewer team is functioning, then we could tighten up the process to 'push live".
>>>> 
>>>> I'm currently doing some review for                                   Jim's work on BGE, but I haven't been trained by one of the core members, so i'm not sure if i'm missing anything.  We're also not clear on the procedure to push live once a page has been reviewed.
>>>> 
>>>> This page should be used to track our work in progress.
>>>> http://wiki.blender.org/index.php/Meta:Wiki_Tasks/Review_2.6_Manual
>>>> 
>>>> My vote is for a wiki-team scrum on IRC asap where we can hash out a short term plan for the next month or two that is satisfactory to all.   How about wed night?
>>>> 
>>>> kesten
>>>>  
>>>> 
>>>> On Mon, Sep 3, 2012 at 6:11 AM, Brecht Van Lommel <brechtvanlommel at pandora.be> wrote:
>>>> Hi,
>>>> 
>>>> I agree that the review process is not working, at this point the
>>>> community is just too small to have a process this formal. People
>>>> can't take responsibility immediately, they start first making small
>>>> changes, and later might get more                                       involved and be ready to take on
>>>> responsibility. But there's not much point in doing that before they
>>>> have worked for a while to convince themselves and others that this is
>>>> something they want to do.
>>>> 
>>>> Not sure what the right answer is,                                       but I think the reviewing process
>>>> should be relaxed. At least small changes like documenting a new
>>>> option and the type of cleanups mentioned at the top of manual pages
>>>> should be allowed without review. Why not do that and have a few
>>>> people monitor recent changes? I'd volunteer for that.
>>>> http://wiki.blender.org/index.php?title=Special:RecentChangesLinked&limit=500&days=30&target=Doc%3A2.6%2FManual
>>>> 
>>>> Brecht.
>>>> 
>>>> On Mon, Sep 3, 2012 at 9:20 AM, mindrones <mindrones at gmail.com>
> _______________________________________________
> Bf-docboard mailing list
> Bf-docboard at blender.org
> http://lists.blender.org/mailman/listinfo/bf-docboard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20120904/a61f27b8/attachment.htm 