summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess2019-07-12 14:19:44 -0400
committerJoey Hess2019-07-12 14:19:44 -0400
commit655579e0c8732148d48f241ddc6e025fbe1303bc (patch)
tree6e3f23eab310a8fe3cc2f1934c463bdb499ad471
parenta40e5d22354615f13d69d963cbe9c727babc724c (diff)
parent45d91aed3b286e3ada4b21ec08f7304621380aae (diff)
Merge branch 'master' of ssh://propellor.branchable.com
-rw-r--r--doc/forum/Contribution_and_community.mdwn10
-rw-r--r--doc/forum/apt_releaseinfo/comment_1_a6897e3cb6089c4f3db3d37e71ff9659._comment12
2 files changed, 22 insertions, 0 deletions
diff --git a/doc/forum/Contribution_and_community.mdwn b/doc/forum/Contribution_and_community.mdwn
new file mode 100644
index 00000000..87c57afd
--- /dev/null
+++ b/doc/forum/Contribution_and_community.mdwn
@@ -0,0 +1,10 @@
+Propellor seems inaccessible to me.
+
+The contribution workflow is based on emails or unstructured todo wiki subpages. It is unclear where to get help.
+
+I suggest you switch to using https://gitlab.haskell.org for example
+
+Getting contributions in open source is about how accessible your project is. That includes not only codebase, but especially workflow.
+I also barely see anyone respond to propellor topics on #haskell freenode.
+
+We use propellor at work and I'm already wondering if ansible would have been a better choice.
diff --git a/doc/forum/apt_releaseinfo/comment_1_a6897e3cb6089c4f3db3d37e71ff9659._comment b/doc/forum/apt_releaseinfo/comment_1_a6897e3cb6089c4f3db3d37e71ff9659._comment
new file mode 100644
index 00000000..b354208d
--- /dev/null
+++ b/doc/forum/apt_releaseinfo/comment_1_a6897e3cb6089c4f3db3d37e71ff9659._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="spwhitton"
+ avatar="http://cdn.libravatar.org/avatar/9c3f08f80e67733fd506c353239569eb"
+ subject="comment 1"
+ date="2019-07-12T06:39:18Z"
+ content="""
+I think that the point of this was to prevent people with 'stable' in their sources.list from accidentally upgrading to a new stable release. Similarly, to prevent users with 'testing' in their sources.list from upgrading to the new testing, when what they wanted to do was track stable+1.
+
+I think that when a user uses propellor's `Testing` and `Unstable` types they are explicitly requesting a rolling release, so it seems find to pass it for those suites.
+
+This is not based on reading any discussions about the new feature. Just my own inference as to its purpose.
+"""]]