that sounds great... a series of screencasts is quite easy to produce and doesn't take too much time.
i've created a list of bullets for three screencasts: http://rpyc.wikidot.com/screencasts you're welcome to re-record the original one of course, and if you can add part 2 and 3 that would help a lot. thanks, -tomer An NCO and a Gentleman On Tue, Mar 1, 2011 at 13:59, Tal Einat <[email protected]> wrote: > Hi Tomer! > > I'm also very pressed for time these days, and haven't had a chance to work > with RPyC for a few years, but here I am still on the list :) > > I'd love to do a screen-cast (or several short ones), I haven't yet had a > chance to do any. If you like I can re-record the screen cast (or just > re-record the audio) with my American accent (I speak both Hebrew and > English with native accents). Or we could think up a few shorter demos and I > would record them. > > I don't think I'll have time for anything more in the coming months, > though. > > - Tal > > > On Tue, Mar 1, 2011 at 1:23 AM, tomer filiba <[email protected]>wrote: > >> okay, i decided to pick the gauntlet and get RPyC development back on >> track... >> i have some few announcements, *please take a minute to read through this >> email.* >> >> in the coming days, i'll browse the mailing list for any relevant code >> patches, and i'll open tickets >> for all the issues that you guys reported. that being said, i'll have to >> introduce some "regulations" >> regarding the project: >> >> 1) project development will take place only on github: >> see http://github.com/tomerfiliba/rpyc >> >> 2) please use the github ticket system to report issues: >> see http://github.com/tomerfiliba/rpyc/issues >> >> 3) in order to send patches, fork the project, do your thing, and send me >> a pull request. >> see http://help.github.com/forking/ >> no more mailing me patches, please... that way i can merge patches to the >> master branch >> with a single click, which will make my life much easier, and releases >> more frequent. >> >> i'll update the site tomorrow with this new information. >> >> i'll have two free weeks in april, and i plan to release 3.1.0 then, which >> will include lots of >> small fixes that have accumulated since 3.0.7, and it will also change the >> project layout to make >> it more compatible with setuptools. i'll also write an >> upload-to-sourceforge script to automate >> releases, since sourceforge now allows uploading files over ssh. >> >> the new IO layer (including new authentication schemes/TLS replacements) >> will have to wait >> for a future release, perhaps v3.2, but i think it's best to wait with >> this for layer5, as it attempts >> to solve this problem once and for all. >> >> however, soon after april, my time will be limited again, and *i don't >> think i could handle it all **by myself*. >> i've been maintaining the project and this small community since 2006, and >> i'm clearly* NOT doing a good job*. >> i think i can commit to maintaining the code from now on, but i will need >> help with the other aspects >> of an open source project, namely: >> >> 1)* a maintainer for the site* (update docs, write tutorials, demos, do >> PR). RPyC is doing very >> bad on the PR front, and very few people have ever heard of it or took the >> time to try it... and it's >> a shame. even if you don't end up using it, i believe it's a fresh >> alternative people should be >> familiar with. heck, i even recorded a screencast with my embarrassing >> israeli accent... >> you can't say i haven't tried :) >> >> 2) *a maintainer for the mailing list*: someone to answer questions, >> superficially examine bugs, etc. >> i can answer a question now and then, but we need someone to help new >> comers, etc., with the >> get-me-started issues that i've recently ignored. sorry for that, people. >> >> 3) of course if someone wants to lend a hand in the development, he's >> welcome aboard. >> >> ====================================================================== >> >> so what i'm saying is, the project needs some volunteers... please reply >> to this thread >> if you have some spare time and think you can help maintain the project. >> even doing simple PR on forums, lists, reddit, etc., would be greatly >> appreciated. >> >> ====================================================================== >> >> >> thanks in advance, >> -tomer >> > >
