Analyse for project & process improvements
Two things in my observations could’ve been better formulated or further clarified:
- “need for changes”: Analyse the need for changes, and with the objective to increase clarity and streamline the current project structure / process flows that result from the manifesto you point to. For instance:
- The manifesto is a blog post. It is not easily discovered.
- What should one minimally do to seek consensus?
- When is a vote required, where does it take place, and where is the outcome of that vote recorded?
- There may be a need to have a decision log of sorts (maybe that exists, idk?)
- “professionalisation”: I already had it between quotes, maybe ‘formalisation’ might be clearer, idk. But it was referring to what’s in the first bullet point: the analysis for organization improvement.
- In no way was I suggesting commercialisation, and even less unprofessionalism
- In no way was I suggesting commercialisation, and even less unprofessionalism
Yes. An example: You point to something that is obviously important. Yet it is post no. 144 in a thread with 200 posts. How can a newcomer inform themself about the project? Should they read the entire forum in sequential FIFO order, and deduce importance from text formulation and formatting?
I think a kind of ‘distillation process’ should be added whereby all things that are relevant are copied out of their TL;DR locations and into places where it is easy to catch up on what’s going on and what needs to happen next, e.g.:
“Great! We have made a decision. Could you update the [decision log / status page / issue / docs / diagram / what-have-we? ]”
DAPSI application and funding opportunities
For the DAPSI procedure… With no prior experience I know less about it than you and @dachary, so good questions to seek answers for.
My additional thoughts:
- We first need to find out if such an option is acceptible by the DAPSI proposal reviewers.
- We need to decide all the stuff that should be in the application and find a ballpark amount of money we’d like to apply for.
- Based on that we can further detail each component and come up with an estimate of how large a percentage they require.
Beyond DAPSI this is a very valuable question to ask. The DAPSI folks would like to see a healthy, sustainable project after funding period end, and able to progress until the stated objectives are reached (be that eventual dissolution or not).
I could see options for ‘revenue models’ that generate income, whereby the core essence, principles and values, and Manifesto are still fully respected. And we might investigate the possibilities. And that investigation might be budgeted in the DAPSI call, maybe.
Project scope, roadmap and objectives
Key questions. I mentioned the “dissolution” because it came up in various discussions I had with @dachary in some form or other. I still find it a confusing concept, and given your questions you are also not totally clear on how this is likely to work.
Here’s my opinion on it:
- The dissolution of FedeProxy is indeed a possibility. However, how that goes, and even if that happens eventually is a ‘crystal-ball’ prediction.
- In a project summary this might be mentioned, but I wouldn’t prominently repeat it everywhere.
- As this is a decision for the future, it should be on a decision log or project strategy plan, or whatever.
- Talking about dissolution can discourage contributors, if they do not fully understand how that works.
- Based on the Manifesto anyone can join the community and, by consensus or vote, change project direction.