1 |
On Thu, Jul 16, 2020 at 6:04 PM Andrey Utkin <andrey_utkin@g.o> |
2 |
wrote: |
3 |
|
4 |
> Summary: |
5 |
> Could we please look for the possibilities to deliver more, given extra |
6 |
> reward |
7 |
> from users interested in that happening? |
8 |
> |
9 |
|
10 |
So I'm trying to understand the goals here. I see nominally two goals: |
11 |
|
12 |
(1) We develop some kind of valuation function where we have some project |
13 |
proposals and we 'fundraise' for them and the proposals with the most funds |
14 |
/ valuation get selected. This doesn't imply that there are actual dollars; |
15 |
but it's simply a means (one of many potential methods) to rank proposals. |
16 |
Basically this is your description of "figure out what users value." |
17 |
(2) Once we determine (via 1) what proposals users want, how do we actually |
18 |
make these happen? This is where we come to things like actual fundraising |
19 |
of real money, finding people to do the projects, getting them the money, |
20 |
etc. |
21 |
|
22 |
I would argue that in theory these are separate activities; it might be |
23 |
valuable to do 1 and not 2. |
24 |
|
25 |
|
26 |
> |
27 |
> |
28 |
> There are many good motivations to contribute to FOSS, and the fact that |
29 |
> somebody contributes means some motivation is in place. But given stable |
30 |
> motivation and real life arrangements, the level of effort would stay in |
31 |
> some |
32 |
> predictable range - there is some optimum, where contributing either more |
33 |
> or |
34 |
> less hurts some needs of the contributor. |
35 |
> |
36 |
> But what if contributing more than usual would be rewarded more than usual? |
37 |
> For example, a person with a flexible job schedule may be willing to |
38 |
> switch to |
39 |
> 4 workdays week and spend one full day each week contributing, given |
40 |
> reasonable |
41 |
> remuneration - not necessarily equal to their employer's rates, but not |
42 |
> peanuts. |
43 |
> |
44 |
> I think if we find such possibilities - the levels of service quality which |
45 |
> we're not going to meet given the status quo, but which we're going to meet |
46 |
> fairly confidently given funding - some of these would be interesting |
47 |
> enough to |
48 |
> wide users community to fund them. |
49 |
> |
50 |
|
51 |
I'd perhaps go more generic than your customer success narrative; but again |
52 |
this is more about my point (1) than about point (2). |
53 |
If you just did (1) in the community, its plausible to do separately with |
54 |
sufficient fundraising activity. |
55 |
|
56 |
|
57 |
> |
58 |
> The idea of crowdfunding major projects has been brought up in 2015, and |
59 |
> unfortunately it hasn't turned into action: |
60 |
> |
61 |
> https://archives.gentoo.org/gentoo-project/message/0f35aba409bc64e539a88895bfe6cc42 |
62 |
|
63 |
|
64 |
> |
65 |
> If you are a member of some projects within Gentoo: |
66 |
> |
67 |
> Do you know some specific promises, or service level or quality criteria |
68 |
> which |
69 |
> it makes sense to meet but which you don't consistently achieve because of |
70 |
> resource constraints? |
71 |
> |
72 |
> Do you believe the goals of your project really matter for quality of life |
73 |
> of |
74 |
> real users so that they'd give non-zero amount of money for this criteria |
75 |
> to be |
76 |
> consistently met (as opposed to current inferior quality)? |
77 |
> |
78 |
> If yes, why not try fundraising to ensure that such a higher quality bar is |
79 |
> met, say, throughout the next year? |
80 |
> |
81 |
> If funding doesn't reach the bar, then you don't lose anything - you just |
82 |
> keep |
83 |
> doing what you are doing and you don't have any new commitment. If funding |
84 |
> happens, then you have a new commitment, but you're funded to exactly |
85 |
> enable |
86 |
> you to meet your objective with confidence. |
87 |
> |
88 |
> I believe such approach would achieve such important results: |
89 |
> |
90 |
> * reveal the real needs, values and preferences of Gentoo users; |
91 |
> |
92 |
|
93 |
So I think we can, somewhat, get away from this framing. Just get the |
94 |
community to pitch N projects and rank them. Offhand I can think of a few: |
95 |
- Replace portage with pkgcore. |
96 |
- pkgcore maintainer (replace radhermit; who has been asking for help for |
97 |
months) |
98 |
- build a package-build service that is easy to deploy. |
99 |
- More performance work on portage. |
100 |
- Rewrite catalyst. |
101 |
- Replace repoman with pkgcheck. |
102 |
- Compile repo format into something less terrible then we have today. |
103 |
- Replace rsync mirror network with GIT https serving. |
104 |
- Help arzano build more developer tools on top of p.g.o |
105 |
|
106 |
|
107 |
> * demonstrate the level of user focus of Gentoo developers |
108 |
> |
109 |
|
110 |
I don't understand how this is valuable; but it could be my poor |
111 |
interpretation. I choose to interpret it as "show how the community can |
112 |
execute on longer term strategic goals by properly allocating resources." I |
113 |
know it sounds pretty manager-y but it mostly addresses a long-held |
114 |
annoyance of mind where we talk about a lot in Gentoo but execute on very |
115 |
little ;) |
116 |
|
117 |
|
118 |
> * channel more community resources towards Gentoo development, |
119 |
> where community needs it most. |
120 |
> |
121 |
|
122 |
So community resources are currently channeled towards the Foundation. |
123 |
Admittedly the Foundation runs a surplus so there is definitely room for |
124 |
reallocation. |
125 |
|
126 |
|
127 |
> |
128 |
> Personally I am interested mainly in the validation of the approach. |
129 |
> Ironically, I myself am not in a position to receive any funding due to my |
130 |
> current work visa restrictions so I am unable to validate this idea on my |
131 |
> own. |
132 |
> |
133 |
> I am interested more in finding somebody who is keen to try this out on |
134 |
> their |
135 |
> positions, than in the arguments about whether this approach is right or |
136 |
> wrong, |
137 |
> but I welcome any responses. |
138 |
> |
139 |
|
140 |
I'm personally more interested in (1) than (2) but this is because I think |
141 |
crowdfunding is not the only way to fund projects. |
142 |
|
143 |
-A |