On Feb 1, 2008 9:34 PM, Mariano Guerra <<a href="mailto:luismarianoguerra@gmail.com">luismarianoguerra@gmail.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Feb 1, 2008 9:25 PM, Johann Prieur <<a href="mailto:johann.prieur@gmail.com">johann.prieur@gmail.com</a>> wrote:<br>> Hi,<br>><br>> Before writing pages of worthy documentation, I'd like that we get some<br>
> orientation :<br>><br>> - What is our priority in terms of protocol version? Is it worthy to take<br>> time to document older versions of MSNP? Should we only focus on the latest<br>> version? Should we choose some editorial style defining clearly what are the<br>
> changes between versions ("transition" pages)?<br><br></div>I think we should focus on MSNP15 (the latest AFAIK), so we have one protocol<br>version well documented. If a new one come up, we should still work to<br>
complete the MSNP15 documentation, when its complete we can move to the<br>next one if it add some significant features, if it doesn't, then we can wait<br>until a major new version.<br><div class="Ih2E3d"></div></blockquote>
<div><br>I share the same point of view.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>> - What do you think YOU can bring in term of documentation? The goal here<br>
> is to define some tasks and assign them to volunteers so that we don't<br>> replicate what another is doing and start getting a shape of what's coming.<br><br></div>I guess the pymsn guys have almost all the MSNP15 protocol covered, we should<br>
hear what they have to say ;).<br> If there is some part still missing on their implementation I would<br>love to try to<br>investigate about it.<br><br>So I guess we should document what they already know :P<br><br>PS: emesenelib implementation is of MSNP13, some thigs are shared with MSNP15 so<br>
dx (the other developer) and I can document some of that parts and let<br>pymsn et al<br>document the parts that are particular to MSNP15.<br><br>what do you think?<br></blockquote></div><br>I'm one of the pymsn developers :)<br>
<br>Personally, I worked on reverse engineering most of the services then implemented in pymsn, but I'm not the only one and maybe another one here can do a better work than me. I bet what people can "document" is more people-related than library or client related. We need to attribute task to people, not project, really.<br>
<br>Johann<br><br>