[Mono-list] Monodoc, Submitting Documentation Changes

[Iggy]

Did anything ever happen with this?



On Thu, Sep 25, 2008 at 11:33 AM, Chad Kittel <chad.kittel at gmail.com> wrote:
> Miguel,
>
> I'm know you're a busy guy, but when you get around to it, and if you
> approve the idea, I think we would be ready to start this as soon as
> praticible.  You've had three positive hits on the idea, that should
> be a good starting point to launch it and see how it goes (logistics
> and organization of it all).
>
> You've got currently eager folks ready to help, lets see if we can
> make this happen!
>
> Cheers,
>
> Chad
>
> On Sun, Sep 21, 2008 at 5:09 PM, Iggy <iggy.ma at gmail.com> wrote:
>> I'd be happy to get involved and admin some of the documentation. I
>> think right now it is by far the most valuable tool for people
>> learning Mono and I'd love to add some sample code and documentation
>> and admin others contributions...
>>
>>
>>
>>
>> On Sun, Sep 21, 2008 at 4:20 PM, Chad Kittel <chad.kittel at gmail.com> wrote:
>>> Miguel,
>>>
>>> On Sun, Sep 21, 2008 at 1:34 PM, Miguel de Icaza <miguel at novell.com> wrote:
>>>>
>>>>> I assume someone has to scrutinize the submissions to be sure someone
>>>>> isn't tampering with them, and I understand that can take some time.
>>>>> But I need to be sure that there actually is someone on the other end
>>>>> of that WebService actually acknowledging the submitted changes before
>>>>> I commit time and effort into helping out the project in this fashion.
>>>>
>>>> It is usually me, but I would love if other people wanted to become
>>>> "reviewers" to ensure that text is not copy pasted from MSDN.
>>>
>>> I'd be glad to help in this role, keeping plagiarism out and quality,
>>> original documentation in.
>>>
>>>
>>>> The bad news is that many contributions for the documentation have a
>>>> high rated of copy-pasting from MSDN, so at some point I started
>>>> ignoring most of the contributions to .NET class library documentation,
>>>> hoping to one day have some time to do it all in one go.
>>>
>>> That's kinda what I was afraid of.  At this point, unless the
>>> reviewing process changes, it sounds like I should not invest my time
>>> in writing original documentation for the class libraries as they
>>> might very well just sit around collecting dust, instead of being
>>> published for the masses to consume.
>>>
>>>
>>>> I am open to giving other people access to the tool to admin things, if
>>>> someone wants to step up.
>>>
>>> I would not at all mind helping out on this front.  IMO, the
>>> documentation part of the mono project is a very important piece to
>>> help mono adoption and retention rates.  At this point, MSDN is
>>> invaluable and I hope one day MonoDoc is just as invaluable for us
>>> mono developers (and maybe even for the developers on the other side
>>> of the fence!)
>>>
>>>
>>> --
>>>  _
>>> (\o/) Chad 'v3rt1g0' Kittel <chad.kittel at gmail.com>
>>>  /_\ Beaver Dam, WI (USA) [4 8 15 16 23 42]
>>> "This is who we are." // Lunar Linux developer // عزرایل
>>> _______________________________________________
>>> Mono-list maillist  -  Mono-list at lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-list
>>>
>> _______________________________________________
>> Mono-list maillist  -  Mono-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-list
>>
>
>
>
> --
>  _
> (\o/) Chad 'v3rt1g0' Kittel <chad.kittel at gmail.com>
>  /_\ Beaver Dam, WI (USA) [4 8 15 16 23 42]
> "This is who we are." // Lunar Linux developer // عزرایل
>