cadey
/
propellor
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

This commit is contained in:
paluho@d3c592540b13adabc6068206dbdc60d73ef01399 2015-06-21 16:24:06 +00:00 committed by admin
parent bacdbc416d
commit 59bbe126a5
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/forum/Experimental_propellor_augeas_intergration_+_workflow_concenrs.mdwn
View File

@ -1,3 +1,3 @@
I'm not experienced haskeller, but I've started to work on augeas property for propellor. I've created a separate repo for it: https://github.com/paluh/propellor-augeas. I will try to rewrite some existing properties on top of this and add some new. It is in a really early stage, but it works.
I think that it will be a lot easier to work on propellor core properties and features, if it will be separated lib without any "spinning" abilities. Currently when I'm trying to read your or my commit history there is a lot of "propellor spin" commits without any sensible comment. In addition it will be a lot harder to merge my changes to your repo - I can't just send you pull request. What do you think about extracting pure library from existing project?
I think that it will be a lot easier to work on propellor core properties and features, if it will be separated lib without any "spinning" abilities. Currently when I'm trying to read your or my commits history, there is a lot of "propellor spin" commits, without any sensible comment. In addition, it is hard to merge any changes to your repo - I can't just send you pull request. In case of such a broad project as propellor, I think that it will be beneficial to facilitate cooperation and to separate deployment mechanics from core configuration management parts. What do you think about extracting pure library from existing project?