[Bf-docboard] Current state of wiki updating.
amdbcg
amdbcg at gmail.com
Mon Sep 3 23:50:50 CEST 2012
@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 <http://wiki.blender.org/index.php/Meta:Guides/Style_Guide>
and are familiar with templates
<http://wiki.blender.org/index.php/Meta:Guides/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
<http://en.wikipedia.org/wiki/Scrum_%28development%29#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 :
1. At the beginning of each (week/ 2 weeks/ month) , you will be
given a list of assignments.
1. Assignments will either be distributed via dictatorship model,
or a first-come-first-serve model.
2. 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.
3. 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.
4. 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 useGoogle Calendar
<https://www.google.com/calendar/embed?src=amdbcg%40gmail.com&ctz=America/Chicago>
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
>> <https://share.coursera.org/wiki/index.php?title=ML:Neural_Networks:_Learning&action=history>.
>> 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 <mailto: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 <mailto:mindrones at gmail.com>> wrote:
>> > Hi all,
>> >
>> > at least until the end of September, I will really have no
>> time to
>> > follow wiki pages editing and/or reviewing.
>> >
>> > Opening up the wiki has been done already and the mess that
>> came out
>> > in a year took months to be fixed.
>> > After long discussions we have preferred to push people to take
>> > responsibility instead.
>> >
>> > We have decided to start this table
>> > http://wiki.blender.org/index.php/Meta:Wiki%20Team#Roles
>> > to invite people to take responsibility for some particular
>> chapter.
>> > That table is still kind of empty though... If you are
>> active on the
>> > wiki and want to take responsibility for a certain area of
>> the manual,
>> > just show up there.
>> >
>> > --
>> >
>> > Let me apologies for the long silence, I'll try to be more
>> active and
>> > read these mail more often.
>> > Also, not being able to talk on IRC nowadays is quite a big
>> hassle,
>> > sorry for that.
>> >
>> > Frankly, if I will realize that I'm being more of a burden
>> than a
>> > help, I'll "resign" from my role of wiki coordinator and
>> will let the
>> > witness to someone else. In my view Greylica is a good
>> substitute for
>> > example, him being quite enthusiastic and active since a
>> long time :),
>> > but that should be discussed by other admins and active
>> writers.
>> >
>> > Kind regards,
>> > Luca
>> > _______________________________________________
>> > Bf-docboard mailing list
>> > Bf-docboard at blender.org <mailto:Bf-docboard at blender.org>
>> > http://lists.blender.org/mailman/listinfo/bf-docboard
>> _______________________________________________
>> Bf-docboard mailing list
>> Bf-docboard at blender.org <mailto:Bf-docboard at blender.org>
>> http://lists.blender.org/mailman/listinfo/bf-docboard
>>
>>
>>
>>
>> --
>>
>> Kesten Broughton
>> President and Technology Director,
>> Solar Mobile Trailers
>> kesten at solarmobiletrailers.com
>> www.sunfarmkitchens.ca <http://www.sunfarmkitchens.ca/>
>> 512 701 4209
>>
>>
>>
>> _______________________________________________
>> Bf-docboard mailing list
>> Bf-docboard at blender.org <mailto:Bf-docboard at blender.org>
>> http://lists.blender.org/mailman/listinfo/bf-docboard
>
>
> _______________________________________________
> Bf-docboard mailing list
> Bf-docboard at blender.org <mailto:Bf-docboard at blender.org>
> http://lists.blender.org/mailman/listinfo/bf-docboard
>
>
>
>
> _______________________________________________
> 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/20120903/3288f7a5/attachment.htm
More information about the Bf-docboard
mailing list