On Fri, Dec 17, 2010 at 6:50 AM, Richard Hainsworth <[email protected]> wrote: > This thread highlights two problems: > a) a new contributor to the Parrot project has replied to an email digest.
I'm sorry, how is this a problem? > As more people are brought on board, there needs to be some form of 'welcome > package' that outlines how to take part, where to contribute, and so on. > > Perhaps a standard file could be sent when someone is added to the list > server? > > b) Perhaps a separate 'translation' list should be set up? Traffic on > parrot-dev regarding translation might increase substantially on linguistic > topics fairly remote from the experience of most parrot developers. Mailing lists are cheap and we could definitely do this if it becomes a problem. In my opinion, we're nowhere near this level yet. In my experience, this kind of compartmentalization with what is already a pretty low traffic list is going to stifle discussion, not encourage it. > Richard > > On 12/17/2010 02:05 PM, M. Zaur wrote: >> >> About version of README, I downloaded current supported release thats >> why >> I translated old version of file.. >> Anyway , I will translate last version with all given notes. Also I plan >> to >> translate online docs , by my oppinion it is more important than READMEs >> included in sources pack, dont you think so? >> >> P.S. Its first time I take part in opensource project, I dont know how to >> use message system ( for example what should be in Subject line of a mail >> ? ) >> >> 2010/12/17 Konovalov, Vadim (Vadim)** CTR **< >> [email protected]> >> >>> Hi. >>> >>> attached was cp1251 and not UTF8, but this is matter of just single >>> "iconv" >>> command, so no problem. >>> Subject line of a mail is also confusing. >> > <snip> > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > -- Will "Coke" Coleda _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
