www.gravatar.com blocked?

@KevinMontrose Yeah

@KevinMontrose welp, sure was

cheers

happens

alright, I gotta dash to dinner - @AdamLear'll roll a new build to fix some issues soon

Cool, I didn't know Skeet was on board already. We'll have these docs written up in no time.

Some CSS fixes, a couple new flag types, and handling reviewing a review that's been completed while you were looking at it coming live in about 10 mins.

\o/

Looking at the C# extension methods "Where to define extension methods". A big question for me is IN WHICH NAMESPACE? I've never found a definitive answer (though there are some interesting ones here: stackoverflow.com/q/2520446). But my question is: is there are place for commenting on an example like this to say what I've just said here?

If it is a question, probably the 'Ask a question button' is best. If it is to be improved, I would say change it yourself. I think we don't want the examples to become a discussion.

Interesting question by the way. I think the answers are primarily opinion based. To me they sound like a new topic: 'Extension method definition strategies' or something like that.

If I encountered a not very commonly used .NET API that has weird behavior (that took me about a day to figure out) which I want to document properly (as opposed to MSDN that doesn't mention all that weird behavior), but the focus of the information will not be the examples because they can't contribute much (although I can include some), is Docs.SE the right place to put such documentation? Or would you recommend I just put it in the "Community Additions" of the official MDSN documentation?

Given the fact Docs is still in beta, why not give it a shot and find out how it evolves?

I guess what I really want is a wiki-style editable copy of MSDN to add information to. I don't want to create a page, I want to expand it. This makes for a much lower barrier of entry for me (and anyone who wants to contribute).

I think that somehow the platform is removing examples. I submitted one (basic HTTP downloader) in the .NET "Networking" topic, and now there's no trace of it. Not even in the "Actions" list. If it had been rejected a trace would appear somewhere, right?

I have just submitted it again. Let's see if it wurvives now!

What should we do if a suggested submission has a typo? Reject it? Approve and then edit?

Hi!

@Konamiman the rejecter was me, see docs-beta.stackexchange.com/questions/93/…

I also noted in that question "As a sidenote, where do rejected proposals go?"

Apparently you didn't see the rejection either

Also note my comment under your current proposal: docs-beta.stackexchange.com/documentation/proposed/changes/235 :)

@LorenzoDematté hi Lorenzo, welcome

@CodeCaster just trying to see how it works. It's.. unusual. I have added a (very crappy) doc on Assemblies, just to get the feel of it and have feedback on the style/form to give to SO docs

@LorenzoDematté we're all in it together! Start using the system, document your observations (as you did) :)

@CodeCaster yeah, I started thinking "I need to research a lot to write proper docs about Assemblies, it will take days" but then I realized I should focus on how to do it, try a few things and ask for feedback, not really on the content.. it's too soon for that

@LorenzoDematté yeah that's what held me back at the start, but we'd better just write anything and let the discusison/voting begin

otherwise it's all pretty abstrac

t

@CodeCaster Ok, I hadn't ever noticed that there was a "HTTP Clients" topic! :-)

I think that there should be a more explicit way to discover that a submission has been rejected (a notification?)

@Konamiman yeah, we're in the process of adding more notifications

notification on proposed change comments should go out today, others Soon™

@KevinMontrose In 6 to 8 weeks, right? :-)

hehe

@LorenzoDematté drafts are shareable so you could shop something around to folks. Makes me wonder if we should consider allowing comments on shared drafts.

Where is the best place to raise bugs, here in chat, or in the "Questions" of the site?

bug Question is best, though it doesn't hurt to mention them here either

Maybe trivial, maybe a [won't-fix]: docs-beta.stackexchange.com/questions/108/…

[status-declined] might be fitting?

I think Jon Skeet is still writing an awesome script to convert his books (and probably the others as well) to the documentation site.

@vcsjones nah, that's a real bug - I'll take a whack at it after lunch

pretty sure it's supposed to cancel already, it might be a "discard request is in flight"-thing

@MauriceStam Oh wow, really? That sounds awesome.

Lol well we could wish for it. But i was having a joke.

:(

Are there suggestions on the best way to discuss a particular piece of documentation? For example, each wikipedia page has a "Talk" section where the details of an entry can be fleshed out. For example, I happen to disagree with some C# documentation, but would like feedback to know if I am splitting hairs or am misunderstanding what is attempted to be documented.

The Q&A portion of the site (after the beta, that'll be meta.SO) & chat (this room for the beta, long term probably per-tag chats in chat.stackoverflow) are the discussion-y places. Similar pattern to Q&A debates. We're working on getting comments and inbox pings on proposed changes and topic requests so those things can have some ephemeral discussion. Will probably surface that discussion on a Topic or Examples revision history too.

at least: that's what we're thinking on day 10 :)

Hello, all!

Hi!

@KevinMontrose makes sense. Thanks.

Just got my invite yesterday, now I've got some time to look around. Are C# and .Net the only subjects, or are there more, that I can't see?

C# and .NET are it for now

we'll be opening up more topics as the beta progresses

java and android are probably next

Ok, thanks! I'll see if I can make myself useful. Looks like there isn't a topic for Lambda expressions yet, so I'm working on one.

Just hope that subject isn't too broad for SO Documentation.

sounds good to me

I've a random question - would Ninject fall under C# or .NET?

I'd probably say it belongs in it's own tag... but since we don't have one yet, probably .NET

thanks!

Some language-independent things might also be useful. Like, a subject on parameterizing SQL queries. That's something every developer needs to know.

yah, the long term plan is for every Stack Overflow tag to be able to have associated Documentation - so things that aren't languages and frameworks would be covered. We haven't decide the "trigger" for a tag getting Documentation yet, depends some on what we learn in beta.

Sounds good. I think the amount of use that a tag gets should be part of the decision - but not the only part.

There are probably some exotic subjects that, despite being used only by a few, still deserve to get some documentation.

yeah

whole bunch of tweaks and fixes rolling out