[Bf-docboard] Blender Reference

[Pep Ribal]

Hi Kesten,

That has been my main concern since some time ago... Instead of
spending hours trying and retrying until you find the logic, a small
conversation with a developer would do. I've asked a few times in the
IRC, and it's difficult to get an answer sometimes.

However, if one developer said to me "hey, I'll be there for you
whenever you need help, on any topic that may arise in your
reference", that would do the magic. As you say, that would even take
work FROM developers, as we would document things that they wouldn't
have to document. If there was a really REALLY good workflow between
coders and documenters, they could even forget about documenting: we
would gladly take the burden!

Regards,

Pep.


2012/4/27, Kesten Broughton <solarmobiletrailers at gmail.com>:
> hey pep,
>
> If the lack of documentation and resources is the problem, I'd suggest that
> we find a way to pair you up with some willing devs.  You might have to
> hopscotch around a little bit on topics, but at least a coder can look
> under the hood and tell you if the button is "attached" to anything and
> take a guess at what it is supposed to do.
>
> What we would need to do is find some coders who are eager to offload their
> documentation duties AND help the doc team members by answering questions,
> tweaking code, checking bug tracker etc.
>
> kesten
>
> On Fri, Apr 27, 2012 at 11:10 AM, Pep Ribal <pepribal at gmail.com> wrote:
>
>> The kid is not the problem; actually it may be the solution: at the
>> pace the work is going, he will be the one to finish it :DDD
>>
>> The real problem is the many undocumented bits and pieces. Every step
>> ahead is a bit of a headache, and it's difficult to get support. The
>> hard work ahead, the writing, etc. is not a problem. What is really
>> exhausting is to try to find out how everyting works: some buttons are
>> not implemented; others have buggy behaviour; others are difficult to
>> see how it goes... And if you take into consideration that I just have
>> very basic 3D knowledge, it turns out that it's, at least, a huge task
>> ahead.
>>
>> However, as John Blain says (thanks, John!), at the end of the day, I
>> can just keep going, even if I know that I will pass it unfinished to
>> my son one day, as my legacy, in a moving scene in my death bed ;)
>>
>> Anyway, if anytime anyone feels inclined to give some support, please
>> contact me. Besides, of course, if anyone wants to use any part of
>> this work, just go for it.
>>
>> Regards!
>>
>> Pep.
>>
>> 2012/4/26, Knapp <magick.crow at gmail.com>:
>> > You have new kid, abandon it. Even if you dont you will. I think you
>> > should add what you have found to the manual and concider it a job
>> > well done!
>> >
>> > On 4/26/12, Pep Ribal <pepribal at gmail.com> wrote:
>> >> Hi guys,
>> >>
>> >> I started my own Blender Reference on January. Some of you warned me
>> >> about how hard it would be to get it done, but I just didn't listen.
>> >> So I started. And it was going well. However, I'm at a point that I
>> >> feel overwhelmed. What I tried to do was to fill the many many
>> >> undocumented features (big and small), so I started trying things,
>> >> pushing buttons, etc. and I really could document a few undocumented
>> >> things.
>> >>
>> >> However, I'm beginning to feel exhausted. Yeah, you were right: it's
>> >> too much for a single man. So I'm presenting you the work done so far
>> >> (3-months work on spare time, as I've been a few weeks off now, due to
>> >> the birth of my child).
>> >>
>> >> I'd like the community to judge it a work worth continuing, or
>> >> something to scrap. I, personally, would love to have it go on, and
>> >> have people help me out. Or perhaps, some of you will tell me to
>> >> abandon it, and join the user manual documenters, which I could also
>> >> go for.
>> >>
>> >> My working method has been so far:
>> >> 1. Test every button in every panel.
>> >> 2. If it is documented, use it to learn the tool.
>> >> 3. If it is not, trial and error until I find out how it works.
>> >> 4. Bug reporting (poor developers hate me already, I assume ;).
>> >> 5. Document it.
>> >>
>> >> I've covered a very tiny portion of Blender, which makes me feel
>> >> overwhelmed.
>> >>
>> >> In summary, I don't feel like continuing this work alone, so either
>> >> find someone to help me out, or perhaps it's time for me to abandon
>> >> and board another ship.
>> >>
>> >> This is the link to my work so far:
>> >> http://wiki.blender.org/index.php/User:Pepribal/Ref
>> >>
>> >> Regards,
>> >>
>> >> Pep.
>> >> _______________________________________________
>> >> Bf-docboard mailing list
>> >> Bf-docboard at blender.org
>> >> http://lists.blender.org/mailman/listinfo/bf-docboard
>> >>
>> >
>> >
>> > --
>> > Douglas E Knapp
>> >
>> > Creative Commons Film Group, Helping people make open source movies
>> > with open source software!
>> > http://douglas.bespin.org/CommonsFilmGroup/phpBB3/index.php
>> >
>> > Massage in Gelsenkirchen-Buer:
>> > http://douglas.bespin.org/tcm/ztab1.htm
>> > Please link to me and trade links with me!
>> >
>> > Open Source Sci-Fi mmoRPG Game project.
>> > http://sf-journey-creations.wikispot.org/Front_Page
>> > http://code.google.com/p/perspectiveproject/
>> > _______________________________________________
>> > Bf-docboard mailing list
>> > 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
>>
>
>
>
> --
>
> Kesten Broughton
> President and Technology Director,
> Solar Mobile Trailers
> kesten at solarmobiletrailers.com
> www.sunfarmkitchens.ca <http://www.sunfarmkitchens.ca>
> 512 701 4209
>