On Tue, Sep 20, 2016, at 03:47 AM, Brian Exelbierd wrote:
> Hi All,
>
> I am sorry I missed yesterday's meeting, I am at a conference this week.
>
> I have written a longish proposal
> (http://www.winglemeyer.org/fedora_docs_proposal/latest/proposal/overview.html)
> about adopting an AsciiBinder toolchain.
>
> I've tried to outline the challenges we have today and how I believe
> this will get us a new documentation website and process quickly. There
> is a Proof of Concept included with details on how you can replicate my
> work.
>
> I'd like feedback and to discuss if we can move forward with this
> proposal. Can we please use email as travel will also prevent me from
> attending next week's meeting.
Sorry for posting this back to the top, lots of the replies are off topic and I could not find a good spot to jump in.
My personal opinion on this is that while asciibinder is easier to setup and get running, it puts us at the mercy of a few teams inside of Red Hat again. While I may be misremembering the past, I recall Publican being much more widely used than you seem to, but over time it lost ground to other tools and the team working on it got smaller. The same thing will happen if the teams working on asciibinder move on.
On the other hand, Shaun's career has been built on making tools for documentation; he was hired by Red Hat becuase of this. While it is ture that he is currently the only one working on pintail, he has a better understanding of documention life cycle becuase of the length of time he has been working in this domain. I do not see a diffrence between a team of people working on Red Hat products commiting to a tool as better than one person working on somthing that he is passionate about and has a proven track record on. I would much rather be reliant on Shuan's work than the whims of another team inside of Red Hat. I get that we are not making a lot of progress moving to pintail, but it is my opinion that in the long run it is the better tool.
_______________________________________________ docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx
