Hi MC, Months ago we had tried the multi-language plugin on MediaWiki, I know you are still planning to do this but I just want how far it goes. Count me in when you are short of hand.
On Sep 15, 2009, at 11:25 PM, Michael Collins wrote: > Demuel, > Thanks for the input. Yes, we want to avoid chaos. I will work to > keep everyone organized. I would welcome a mass of people all trying > to do different things because the challenge would simply be to keep > them organized. Right now the challenge is in recruiting people to > stay with the not-so-glorious aspects of the project, namely > documentation, maintenance, and janitorial style subprojects. > > Please keep the comments and suggestions coming! > > Thanks, > MC > > On Tue, Sep 15, 2009 at 12:38 AM, <dem...@thephinix.org> wrote: > Hi Michael / FS enthusiast, > > In my opinion, it will be an undeniably perfect chaos if everyone > wants to do everything. One way > I can suggest out of this is the following: > > - sets of persons that does all the stuff on the FS core. I'm not > sure if this one will work out but > I think these are the only persons who has commit access to the > source code and will also be willing > to accept modifications, enhancements, etc. > > - individuals can ask if they can be the maintainer/tester for a > particular module. Bug fixing, > sending modifications and enhancements will still be subject to the > approval of anthm. > > - an array of persons that will take ownership on what FS can do and > provide realiable working > examples for it. Currently, it takes amount of pain for a newbie on > how to configure SIP because > the examples are too confusing and sometimes there is not certainty > if this will work on what > release of FS or not. > > - any individual that has time and interest can start owning the > porting of FS to other operating > system. Like in my case, I am working on making FS ported to FreeBSD > ports but I don't know if > somebody did it or if he is currently doing it, as to what stage he > is in? > > - there should be a release engineering team. In my opinion, a > stable and current release will be > much more sane. > > As with any other successful open source project, we won't be > starting to say I want to contribute > this and start working on that. We should indicate that you take > ownership of this and any > comments should be forwarded right unto you. > > Again, this is just my opinion. You can take some of it or leave it > using "sudo rm -rf blah/*" . > > There and back again, > Demuel I. Bendano > a.k.a engrxyz > > > > Hi Michael, > > > > You can count with me for anything else, like documentation, > > coding/scripting, or any other FreeSWITCH related stuff. > > > > Regards, > > > > Diego > > > > 2009/9/14 João Mesquita <jmesqu...@freeswitch.org> > > > >> You can assign two things to me. > >> > >> 1. libesl code documentation (partially done and Doxygened - needs > >> cleaning) > >> 2. Bug marshal. I am setting up the proper lab environment here > to be able > >> to test most stuff. > >> > >> Count me in for any questions I can answer and I am _always_ on IRC > >> > >> jmesquita > >> > >> On Mon, Sep 14, 2009 at 1:33 PM, Michael Collins <m...@freeswitch.org > >wrote: > >> > >>> Hello FreeSWITCHers! > >>> > >>> We are looking for people who are in a position to help out with > various > >>> subprojects that will help FreeSWITCH to keep growing. We need > people to > >>> help out in these basic areas: > >>> > >>> Bug marshals (people who watch JIRA and test bug reports, > patches, etc.) > >>> Documentation maintainers (people who update the wiki when new > stuff comes > >>> out, also those familiar with mediawiki administration) > >>> Documentation authors (people who write new docs, how-to's, > tutorials, > >>> examples, etc.) > >>> Package maintainers (people who manage Debian debs, RPMs, etc.) > >>> > >>> Additionally, we are always looking for more folks to assist with > >>> answering questions on IRC and the mailing list. It is > definitely nice to > >>> have people who've gone through the pains of switching to > FreeSWITCH (or > >>> learning it from scratch) who can assist the steady stream of > new users. > >>> > >>> If you want to help and aren't sure where to go from here then > please at > >>> least do the following: > >>> #1 - Join #freeswitch on irc.freenode.net and hang out as much as > >>> possible > >>> #2 - Check the recent changes link on wiki.freeswitch.org each day > >>> #3 - Join the Friday public conference call and listen in > >>> These three things, in addition to the mailing list, will keep > you well in > >>> tune with the FreeSWITCH community and what's happening. > >>> > >>> Next, make a note of the parts of FS that you use frequently, > know a lot > >>> about, or are particularly passionate about. Those are the items > we'd love > >>> to have you help us with. For example: if you use mod_xml_curl > frequently > >>> and have been through the set up process then you're a prime > candidate to > >>> help answer questions, refine the mod_xml_curl wiki > documentation, write up > >>> a tutorial, contribute a working example of a web server & > database schema, > >>> etc. If you are good with a scripting language then we could > definitely use > >>> help with rounding out the docs for your favorite language. We > could also > >>> use code samples, so ask for a contrib folder if you have things > you would > >>> like to share. Or how about this: you read something on the > wiki, it doesn't > >>> quite work when you try, so you tinker until you figure it out. > Now you're > >>> in a position to update the wiki for everyone else's benefit, too. > >>> > >>> As you can see, you don't have to be a FreeSWITCH expert before > you can > >>> help the project. What we really need are people who care about > the project > >>> and want to see it flourish. If you are such a person then > please contact me > >>> off list. Tell me what you're good at or where you would like to > help. > >>> > >>> Many thanks for all of your support! > >>> -Michael > >>> > >>> > >>> > >>> _______________________________________________ > >>> FreeSWITCH-users mailing list > >>> FreeSWITCH-users@lists.freeswitch.org > >>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > >>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > >>> http://www.freeswitch.org > >>> > >>> > >> > >> _______________________________________________ > >> FreeSWITCH-users mailing list > >> FreeSWITCH-users@lists.freeswitch.org > >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > >> http://www.freeswitch.org > >> > >> > > _______________________________________________ > > FreeSWITCH-users mailing list > > FreeSWITCH-users@lists.freeswitch.org > > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > > http://www.freeswitch.org > > > > > > _______________________________________________ > FreeSWITCH-users mailing list > FreeSWITCH-users@lists.freeswitch.org > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > > _______________________________________________ > FreeSWITCH-users mailing list > FreeSWITCH-users@lists.freeswitch.org > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org