Hi, I didn't start a new thread as this one seems for me a better start.
Did you plan to use something else as Perl to create modules? We (ASPerience) created 3 modules: smeserver-bacula, smeserver-phpbacula, smeserver-htbwshaper but the main difficulty to maintain them is Perl. If we could create forms in PHP or Python, we could maintain more easily and perhaps create new ones. We are actually correcting smeserver-bacula for SME9, and we plan to make smeserver-bareos but we are questioning ourself on how to create (and if we will) new version for smeserver-phpbacula (whatever tool we use: our older one or another). ----------------message d'origine----------------- De: Ian Wells [[email protected] ] A: [email protected] Date: Wed, 07 May 2014 16:01:01 -0700 ------------------------------------------------- > On 07/05/2014 15:01, Charlie Brady wrote: >> Sure. I think the thinking needs to be focussed on getting more >> development veolcity over the longer term, rather than on getting SME9 >> out more quickly by adding developers. I think it would be wise to get >> SME9 out as soon as possible, so the concentration should continue to >> be on verification, rather than new development. After SME9 is done >> the existing developers will have more time to help with recruitment >> and training. If you ask them to do that now, the won't be doing SME9 >> development. > I agree with Charlie's wisdom. > > What RC1 needs at the moment is more error reports, such as the one this > week about crontab/anacron. The development for SME Server 9.0 is > complete, but I'm not yet certain that the maturity is there yet. > > To implement the post 9.0 roadmap it would be good to have more people > on board. > > There are tasks that could be done easily such as > * Roll a new smeserver-locale package on a monthly basis, or whenever > there is a sufficiently large translation patch. > * Develop more automated test cases to reduce the chance of releasing a > bad update. > * Write a developer introduction. We have a *lot* of wiki pages on > development but overlapping and not all up-to-date > * Monitor Bugzilla. Triage incoming bugs, remind about reviews needed etc. > * Grow the number of people that can fix the small bugs - such as the > crontab issue mentioned. The solution was to just delete one file. > Stephane did the basic research (google/bing) and implemented the > solution. That was hugely useful, we just need a pool of people able to > do that. > > There are the not so easy tasks such as > * Develop a favourite area, eg LDAP or Samba4, or Mojlicious > * Work on el7 > > > > > _______________________________________________ > Discussion about project organisation and overall direction > To unsubscribe, e-mail [email protected] > Searchable archive at > http://lists.contribs.org/mailman/public/discussion/ > _______________________________________________ Discussion about project organisation and overall direction To unsubscribe, e-mail [email protected] Searchable archive at http://lists.contribs.org/mailman/public/discussion/
