Hempal dai, is this the design you were talking about? https://fossnepal.herokuapp.com/
I think this can be made to go ahead. It can be driven by the same wiki we are using or we can use something simple like wordpress. On Wed, Aug 28, 2013 at 1:48 PM, Sagun <[email protected]> wrote: > Dear Hempal dai, > > Sorry for not being able to make it to the meeting. > > We can go with Sushil's design. > > Let me clarify on webmaster's issue. I was going to propose we hire a part > time webmaster on hourly basis. So webmaster works like 2 / 3 hours in a > week and gets paid for 10 to 12 hours a month. We won't be spending a hell > lot of money dai. Its just a small bounty and a way to have a dependable > person to maintain a website. However, the website content should only be > updated as guided by the core team. > > I have been hiring students on this hourly schemes in other projects and > it really works for them. It could also work for other professionals. > > Answering Aayush's comment! > Its of course a good thing that volunteers handle the website and we had > tried it in past (since 2007) but when we depend on volunteers, a small > change in website took us weeks if not months. Having a virtual team is not > a problem, we should have a team to guide the contents but we need a person > who is available whenever we need to update the website. > > > > > > > > > > On Mon, Aug 26, 2013 at 10:32 PM, art_tuladhar > <[email protected]>wrote: > >> I am not a very big fan of adding monetary value for developing the >> website. I know there hasn't been a great level of governance to the >> structure of the website, but adding money as a driving force doesn't seems >> to click to me and I believe it's not sustainable as well. I am not very >> much familiar with the FOSS Nepal community but just proving my personal >> opinions. There should be better option rather than hiring somebody for >> part time for maintaining the website. >> >> I think there should be a virtual core team that should handle the >> website. And I agree with Dhruba's concern with the design. >> >> ~ Aayush >> >> >> >> >> >> >> On Monday, August 26, 2013 12:40:22 AM UTC-5, sagun dhakhwa wrote: >> >>> I think we need to start discussing on how do we intend to use >>> fossnepal.org in coming days. >>> >>> My Proposal (please populate more) >>> >>> 1. Activities of FOSS NEPAL >>> 2. Education on FOSS (issues like what is foss, how to foss, where to >>> foss and so on) >>> 3. Software Collection Listing (Nirvikalpa or similar) >>> 4. Listing of Nepali FOSS Initiatives and Projects >>> 5. News >>> 6. Events >>> 7. Trainings >>> 8. Programs >>> 9. Volunteer / Get Involved >>> 10. a knowledge base of Nepali FOSS for users and developers (like >>> stackoverflow) or forum >>> 11. IRC >>> 12. WIKI >>> >>> now the question will come should we continue with media wiki and spend >>> some money on just creating a theme? or should we try once more to make a >>> website in joomla or drupal or similar. >>> >>> my opinion: we should continue to use media wiki and make a new theme >>> for it because we want to continue using wiki as a platform. >>> >>> workflow: >>> >>> step 1 : call designers to send a design proposal >>> step 2: choose a design (this time chosen designer gets paid) >>> step 3: call for creating theme for media wiki bids >>> step 4: choose the best bidder and hand over the work >>> step 5: call a job opening for web master (part timer but paid and >>> someone from the Nepali FOSS community) >>> step 6: choose the best candidate and continue working >>> >>> >>> >>> >>> >>> >>> >>> On Wed, Aug 21, 2013 at 9:52 PM, sushilthe <[email protected]> wrote: >>> >>>> Hey there, >>>> >>>> I have made a wiki >>>> page<http://wiki.fossnepal.org/index.php?title=Change_13_A_powerful_FOSS_Nepal_website>for >>>> the website. Take a look at it and suggest your ideas. The time frames >>>> are particularly important. >>>> >>>> >>>> Regards, >>>> Sushil Dahal >>>> >>>> -- >>>> -- >>>> FOSS Nepal mailing list: [email protected] >>>> http://groups.google.com/**group/foss-nepal<http://groups.google.com/group/foss-nepal> >>>> To unsubscribe, e-mail: foss-nepal+...@**googlegroups.com >>>> >>>> >>>> Mailing List Guidelines: http://wiki.fossnepal.org/** >>>> index.php?title=Mailing_List_**Guidelines<http://wiki.fossnepal.org/index.php?title=Mailing_List_Guidelines> >>>> Community website: http://www.fossnepal.org/ >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "FOSS Nepal" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to foss-nepal+...@**googlegroups.com. >>>> >>>> For more options, visit >>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>> >>> >>> >>> -- >>> Warm Regards, >>> Sagun Dhakhwa >>> mobile: +977 985 11 2 88 32 >>> >> -- >> -- >> FOSS Nepal mailing list: [email protected] >> http://groups.google.com/group/foss-nepal >> To unsubscribe, e-mail: [email protected] >> >> Mailing List Guidelines: >> http://wiki.fossnepal.org/index.php?title=Mailing_List_Guidelines >> Community website: http://www.fossnepal.org/ >> >> --- >> You received this message because you are subscribed to the Google Groups >> "FOSS Nepal" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Warm Regards, > Sagun Dhakhwa > mobile: +977 985 11 2 88 32 > -- Warm Regards, Sagun Dhakhwa mobile: +977 985 11 2 88 32 -- -- FOSS Nepal mailing list: [email protected] http://groups.google.com/group/foss-nepal To unsubscribe, e-mail: [email protected] Mailing List Guidelines: http://wiki.fossnepal.org/index.php?title=Mailing_List_Guidelines Community website: http://www.fossnepal.org/ --- You received this message because you are subscribed to the Google Groups "FOSS Nepal" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
