Difference: AnnualReview2018 (5 vs. 6)

Revision 62018-12-05 - squinney

Line: 1 to 1
 

LCFG Annual Review 2018

On Thursday 6th December 2018 instead of our normal monthly Deployers Meeting we will be holding our traditional Annual Review session. This will start at 2pm and we aim to be finished by 5pm. This year it will be held in room 7.14 of the Appleton Tower. Refreshments will be provided including some seasonal treats.

Line: 56 to 56
  Work on improving the security of LCFG profile access is still ongoing. We now have support for GSSAPI authentication when fetching profiles from the server. We have also tightened up the permissions on the various files and directories used by the LCFG client, the main result of which is that users wanting to be able to run qxprof must be in the lcfg group. These features are ready for testing but not all are the default yet, they will be slowly introduced over the next few months.
Changed:
<
<

Pyngi - Python Components

>
>

General Discussion

 
Changed:
<
<
Work on building a framework for building LCFG components in Python is under way. The intent is to allow natural Python coding to be used while respecting the historic LCFG approach. Further work is needed, opinions, advice and coding effort are welcome. Subversion repository is: https://svn.lcfg.org/svn/source/trunk/pyngi
>
>
Future Platform
We have been using Redhat-based distributions for over 20 years. Are they still a good fit for our needs? What is good about using RHEL? What problems do we have with RHEL? Would any other Linux distribution be better?
 
Changed:
<
<

General Discussion

>
>
Pyngi - Python Components
Work on building a framework for building LCFG components in Python is under way. The intent is to allow natural Python coding to be used while respecting the historic LCFG approach. Further work is needed, opinions, advice and coding effort are welcome. Subversion repository is: https://svn.lcfg.org/svn/source/trunk/pyngi
 
Bugs
We really would like to see more bug reports! We all know about various bugs (whether trivial or important) or have features we would like to see. It would be very helpful if we could get these recorded. We can't promise they will get fixed but just having them in https://bugs.lcfg.org/ would be a great start. I propose that to make them more useful and improve response times at each monthly meeting we review all newly submitted bugs from the previous month.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback