[yast-devel] yast++ minutes -- 2012-02-13
Hi, below you find minutes of the meeting from this monday. Vlado yast++ ==== https://github.com/yast/yast-- Date: ----- 13-02-2012 Present: ------- Jiri Srain, Lukas Ocilka, Martin Vidner, Josef Reidinger, Jiri Suchomel, Vladimir Moravec Minutes --------- Vladimir Moravec ToC: ======= 1. Packaging 2. File structure 3. Name 4. Portability 5. Play & test out of the Git 6. GSoC 7. Logging 8. What's next 1. Packaging ============ Main idea ---------- + how to distribute the code Proposals ---------- + gem directory structure if gem + check of local system dependencies + native extensions + stay with current rpm building and lets make it available for other distros via buildservice 2. File structure ================= + use of gem directory structure conventions 3. Name of the lib ================== Main idea --------- + to use or not to use 'yast' as a part of the name Pros ---- + established name and community, descendant of Yast + well known and easy to distinguish from others Cons ---- + not suitable if we target multiple distros + hard to find on google + hard to distinguish the name from yast + has association with 'suse only' + possible problem in the mind, with trademarked work 'yast' + makes impression that it is successor of YaST, but it is actually only extraction of part of YaST ( data processing ) Questions --------- + What are the criteria for the name? Suggestions for the name ------------------------ + ylib + anything with 'y' letter + liby + libyast Results ------- + use yast++ name as before in the meantime + change is however expected in the course of further development 4. Portability ============== Main idea --------- + make the lib available & popular for non-suse developers What are the means to achieve this ---------------------------------- + distro specific config / package script calls + other distros to be considered: Fedora, Debian, Ubuntu Random ideas ------------ + what changes are needed to include other distros as target systems + focus on other distros not from the beginning, only later after some point in development has been reached + focus from the early stage on development; past experience shows this as reasonable + talk/blog about the lib development in the public to make it aware of the project existence + show simple examples for using on other distros + currently no check for running distro + autodetection as the best way + use of plugins would be fine + distro autodetection, e.g. `cat /proc/version` Discussion -------- + too wide scope for beginning of such project (too many specifications, different needs for various distros) + too much work for small team -> rather focus on making happy well known users (studio,webyast), then use resources for others + imaginary users of debian/fedora as a too blury concept for the expected change + we need a proof of concept that it might run on different distros anyway Questions --------- + should the portability the a feature of the lib? + is the multi-distro focus meaningful? + would it be possible running it on Fedora at all? + What is needed to make the development focused on more distros? + where to implement the distro-specific configuration + how to avoid forking the lib from others and keep devs in one place => avoid splitting the community Suggestions ----------- + ylib as ideal level for customizing configuration of the lib for this 5. Play & test out of Github ============================ Main idea ---------- + make the lib developer friendly from the first touch How to achieve this -------------------- + directory with example files + using chroot for not breaking the running system (root needed) + scripts for chrooting available + alternatives for chroot: + good tutorial for developers + make appliances available Random ideas ------------ + devel-pattern for rpm packaging + appliances of other distros to play with the code + `git clone` into the pre-build VM + project on OBS / install from here + ensure modifying the local system (remounting) + using testing data (from testsuite) for development Questions --------- + how skilled is the developer who is going to use the lib? + how make the repo available for playing for other distros' developers Proposals --------- + look on other projects how they solve the system configuration change 6. GSoC ======= Main ideas --------- + portability feature + C binding for Python + support of Openstack => not needed currently + get in touch with Michal Hrusecky (GSoC/openSUSE wiki) 7. Logging ========== Main ideas ---------- + full logging in/out + filter passwords => results in slower performance + dry run - diffs in chroot - scripts + conventions for parameters + use of the test-suite to avoid wrong using of scripts + create/support official API + undef methods to block improper use of the lib 8. What's next? =============== + finish one or several modules and show the use case: + port it to to other distros + use it in the webyast Vladimir Moravec Appliances Department SUSE LINUX s.r.o., Praha
On Wed, Feb 15, 2012 at 02:12:52PM +0100, Vladimir Moravec wrote:
3. Name of the lib ==================
Main idea --------- + to use or not to use 'yast' as a part of the name
Pros ---- + established name and community, descendant of Yast + well known and easy to distinguish from others
Cons ---- + not suitable if we target multiple distros + hard to find on google + hard to distinguish the name from yast + has association with 'suse only' + possible problem in the mind, with trademarked work 'yast' + makes impression that it is successor of YaST, but it is actually only extraction of part of YaST ( data processing )
Questions --------- + What are the criteria for the name?
Suggestions for the name ------------------------ + ylib + anything with 'y' letter + liby + libyast
Results ------- + use yast++ name as before in the meantime + change is however expected in the course of further development
After dubious results with a straightforward or literal name, I proclaim a metaphorical one: to build a good YaCHT, you need masts, yards, sails, and cordage. The word is rigging I checked that the term is not taken in the software world (except by programs to plan rigging for real ships; no confusion) and registered the user on github (convertible to an organization). -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
Results ------- + use yast++ name as before in the meantime + change is however expected in the course of further development
jewel - ruby inside - configuration is admin's treasure ;-) Michal Filka -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 02/16/2012 02:26 PM, Michal Filka wrote:
Results ------- + use yast++ name as before in the meantime + change is however expected in the course of further development
jewel
- ruby inside - configuration is admin's treasure ;-)
Michal Filka
jewelER is a tool to generate the gemspec, can be a bit confusing... https://github.com/technicalpickles/jeweler -- Duncan Mac-Vicar P. - http://www.suse.com/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 02/16/2012 02:14 PM, Martin Vidner wrote:
rigging
I like this kind of names. Simple, short. -- Duncan Mac-Vicar P. - http://www.suse.com/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 02/16/2012 05:36 PM, Duncan Mac-Vicar P. wrote:
On 02/16/2012 02:14 PM, Martin Vidner wrote:
rigging
I like this kind of names. Simple, short.
From all the names, Gloves (project name) / libgloves (package name) seems to be the best we've found (?). It's... - Simple - Short - Easy to remember - Unique - ... and I can imagine quite nice icon too ;) :) What do you think of this proposal? Bye Lukas -- Lukas Ocilka, Appliances Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
* Lukas Ocilka
From all the names, Gloves (project name) / libgloves (package name) seems to be the best we've found (?).
Hmm, what do people associate with 'Gloves' ? - You need them when its cold outside. And many don't like cold. - You put thin ones on if you have to handle something fragile - Rubber gloves are good for cleaning and doing the dishes - There are even latex gloves available for ... ;-) Klaus --- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne Po 12. března 2012 14:55:51, Klaus Kaempf napsal(a):
* Lukas Ocilka
[Mar 12. 2012 14:50]: From all the names, Gloves (project name) / libgloves (package name) seems to be the best we've found (?).
Hmm, what do people associate with 'Gloves' ?
"Don't touch your system configuration bare handed: use Gloves!" -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 03/12/2012 02:55 PM, Klaus Kaempf wrote:
* Lukas Ocilka
[Mar 12. 2012 14:50]: From all the names, Gloves (project name) / libgloves (package name) seems to be the best we've found (?).
Hmm, what do people associate with 'Gloves' ?
- You need them when its cold outside. And many don't like cold. - You put thin ones on if you have to handle something fragile - Rubber gloves are good for cleaning and doing the dishes - There are even latex gloves available for ...
That's why some people might like them :))) Lukas, 20:20 -- Lukas Ocilka, Appliances Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne Po 12. března 2012 14:50:48, Lukas Ocilka napsal(a):
From all the names, Gloves (project name) / libgloves (package name) seems to be the best we've found (?).
We (Prague developers) seem to like Gloves, and no one complained, so it looks like we've found project name. (But there's still time to complain/propose!) We've not finished the discussion about packages name conventions, though. Here's our latest proposal: 1. Packages with the high level library like yast++lib+users will be renamed to gloves-users 2. Config agents (the low level part) either a) stay as they are, like 'config-agent-passwd' b) or get renamed to 'gloves-agent-passwd' 3. Current namespace is YLib, like in YLib::Users::read and it should be renamed to Glove::Users::read (note the singular form) Any comments? Different proposals? -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Tue March 20 2012 11:26:00 Jiri Suchomel wrote:
Dne Po 12. března 2012 14:50:48, Lukas Ocilka napsal(a):
From all the names, Gloves (project name) / libgloves (package name)
seems to be the best we've found (?).
We (Prague developers) seem to like Gloves, and no one complained, so it looks like we've found project name. (But there's still time to complain/propose!)
We've not finished the discussion about packages name conventions, though. Here's our latest proposal:
1. Packages with the high level library like
yast++lib+users
will be renamed to
gloves-users
2. Config agents (the low level part) either
a) stay as they are, like 'config-agent-passwd'
b) or get renamed to 'gloves-agent-passwd'
3. Current namespace is YLib, like in
YLib::Users::read
and it should be renamed to
Glove::Users::read
(note the singular form)
Any comments? Different proposals?
If we'd use yast++ in combination with Puppet system administration even the word glove puppet made sense :-) -- Thomas Goettlicher SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany
On 03/20/2012 11:58 AM, Thomas Goettlicher wrote:
Any comments? Different proposals?
If we'd use yast++ in combination with Puppet system administration even the word glove puppet made sense :-)
As I haven't seen any objections, let's start preparing the renaming in Git. Lukas -- Lukas Ocilka, Appliances Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
[...]
3. Name of the lib [...]
Y-Connector, because: - it contains the letter Y, like YaST - it connects to the system - it allows many different clients to access the same config, like a y- connector cable. Cheers, Thomas -- Thomas Goettlicher SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (8)
-
Duncan Mac-Vicar P.
-
Jiri Suchomel
-
Klaus Kaempf
-
Lukas Ocilka
-
Martin Vidner
-
Michal Filka
-
Thomas Goettlicher
-
Vladimir Moravec