forsaken

This is great -- lack of a standard that was actually used (unlike CommonMark) was one of my main issues with Markdown (http://ericholscher.com/blog/2016/mar/15/dont-use-markdown-f...) -- It's really great to see GitHub leading in this department, and it gives me hope that one day we might actually have Markdown that is portable between implementations.

Thanks. This should now be fixed.

readthedocs.org -- A site that automatically builds documentation for you when you commit to your VCS repo. It's been widely used in the Python ecosystem for a few years now, and started off as a 48 hour hack day project.

I imagine it would work like a CLA in a lot of company sponsored open source. You retain copyright, but allow the owner to distribute it under their specified license terms. Or you could have a CLA that actually assigns copyright.

The ongoing maintenance of the contribution is definitely an interesting question. That is the same with classic OSS projects too, though. I know a number of projects that are going towards making a pluggable core with plugins maintained externally to reduce this burden.

Is that not better than adopting a more classic proprietary model where the source code isn't available?

I totally agree with the philosophical argument around OSS --but at the end of the day, people need to eat. If you're going to argue that we should all OSS our code, you need to specify a way to make it sustainable (see http://www.fordfoundation.org/library/reports-and-studies/ro... for more on the unsustainability).

The project is still in the development stages. More info here: http://pybee.org/ -- with this page being useful for starting off: http://pybee.org/project/using/

I don't think there is a "Status" tracker of sorts -- but a lot of the projects are still beta, but starting to be used in a few production apps.

You can do code blocks::

   like this

:)

Curious how you cross-referenced across the books? Did you do listings of API's?

Markdown is great for text content, not for formal documentation.

Another option is Read the Docs, which is how we host the Write the Docs docs: http://docs.readthedocs.org/en/latest/ -- It's basically the above workflow that GitHub describes, but with Sphinx (http://sphinx-doc.org/) -- which is a mature and powerful documentation system.

Or get 50-200% back with a higher bar for entry (already having revenue, only needing 200% investment back out in 2 years)

This is really interesting. I have been having conversations with a bunch of folks in the Portland area about trying to find funding with a very similar model.

Glad to hear that other folks are thinking, and doing things, along these lines.

I love the fact that it is offered as a line of equity. Being able to get money when you need it, but not take it if you don't, makes it a lot easier to keep your spending low, and not have a pile of cash burning a whole in your pocket.

Interestingly, Django also came out of Kansas :)

I believe his commitment is to free software, not open source :)

We haven't had much contact with the STC. Their meetups generally cost money, and are focused on DITA and more "old school" XML based technology. We are trying to bring the world of devs who care about docs to the doc writers, and make beautiful things in the process. Styled as an open source community.

We haven't had much contact with specific style guides. We have lots of people from companies that attend. It sounds like a great topic for one of our meetups or conference :)

A lot of the experience from writing this has come from running Read the Docs: https://readthedocs.org/ -- which we've been hosting OSS docs built this way for over 4 years.

We're taking these ideas and building a paid, private version for companies that is just getting going. The goal is to take these ideas, with a product that embodies the philosophy, and try and spread it across private companies: https://readthedocs.com/

Your comment that it is important and valuable is a great validation. I hope that we're successful in being part of the solution to bringing this workflow to the world :)

The beginners guide is explicitly using general markup, instead of Sphinx specifically. Almost none of the content on the site is actually Sphinx-specific..

Hey -- creator here. I would totally love to expand this content, as mentioned in the comments. Let me know if you have any more questions, and would love contributions if there are things people want to say. I have a basic outline for some content I was thinking about turning into an ebook here: http://docs.writethedocs.org/book/ -- if you want somewhere to start.

Also, note that if you're interested in this kind of thing, we have a yearly conference in both the US and EU, and local meetups in many US cities. More info here: http://conf.writethedocs.org/

This is basically the same workflow we've been building at https://readthedocs.org, but for open source projects.

It is really an amazing workflow, and makes writing documentation as well as books a breeze.

I would love to see a standardized site building template for asciidoctor, so that we could support it as well as reStructuredText and Markdown.

This domain used to be Python's new package manager as well.

It's still live under /packages/: https://crate.io/packages/requests/

What made you decide to get a paid plan instead of the free plan?

Sorry about that. I thought it sounded negative and didn't want to talk badly about the product.

My question was basically "Are you okay with publishing content on a site that owns the content?"

I imagine they are building export tools in the future, and this is just the first version.

"psuedo"

A reminder not to refer to programmers as "he" by default. A bit more here: http://alexgaynor.net/2013/nov/30/gender-neutral-language-fa...

This is only talking about people who own their homes. A lot of gentrification is happening in areas where historically the residents were suppressed from owning real estate. My own knowledge is mostly around the Portland, Oregon area, but there is a documented history of minorities being unable to purchase property, get loans, and lots of other institutional things that stop people from actually owning the land.

For them, gentrification is definitely a bad thing.

Edit: Reference here on page 25: http://aaablogs.uoregon.edu/visualculturesymposium/files/201...

Until you made this comment..

Curious about the default response, which is that the company hires all of the people that work on the project. I'd be curious to see stats of the commits of employeers versus their time of employment. I understand that this is probably not available to a third party, but would be interesting data.

"since it was basically abandonware" FUD much? The project has been actively developed since public release.

I have no idea what a DAU/MAU is..

Yes