OK, sounds reasonable. As you said, having docs in source control on bitbucket is basically as good as a wiki.
Please let me know if I can be of any help.


On Tue, Nov 6, 2012 at 2:46 AM, Ronald Oussoren <ronaldoussoren@mac.com> wrote:

On 6 Nov, 2012, at 8:11, Ronald Oussoren <ronaldoussoren@mac.com> wrote:

> On 5 Nov, 2012, at 18:04, Michael McCracken <michael.mccracken@gmail.com> wrote:
>> Ronald et al, what are your thoughts on enabling the wiki feature of bitbucket for pyobjc?
>> I know Ronald has limited time for documentation, and this might give us a way to share updated info without digging through mailing lists.
>> I am usually ambivalent about wikis because they are often disorganized and stale, and can be added work, but in this case I think it might be helpful.
> I'd prefer to improve the documentation instead of using a wiki. I'm working on updateing the website using the documentation in the source tree, once that is done updating the documentation will be almost as easy as editing a wiki. The primary difference will be that there is no instant gratification while editing, updates will be patches/pull requests that have to be processed by me.

See <https://bitbucket.org/ronaldoussoren/pyobjc-website> for the script that I'll use to update the website.  If all goes as planned this will allow for scripted updates to the website (using a cronjob or a commit hook)


LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
Pyobjc-dev mailing list