Another benefit to using polls on G+ is that it encourages conversation amongst users, so you'll get the answer to the question, plus dialog to provide more context.
-C
On Tue, Nov 22, 2016 at 9:23 PM, C R <cajhne@...400...> wrote:
I think the purpose of the survey should definitely be to collect useful data, but for that to happen *every* question must be worded in a way that collects a specific kind of data that corresponds to questions that specific developers or team-members have. Otherwise, it's going to generate a nebulous cloud of information that isn't directly actionable.
Alternatively, one could do polls on the Inkscape G+ feed to answer specific questions of immediate importance, and space them out so it doesn't feel like filling out a survey. In fact, if we want questions answered, I'd do that and forget the survey entirely.
My 2p. -C
On Tue, Nov 22, 2016 at 9:07 PM, Ken Moffat <zarniwhoop@...3141...> wrote:
On Mon, Nov 21, 2016 at 11:16:41PM -0500, Martin Owens wrote:
Hi Doc,
thanks for the reply, responses inline.
On Tue, 2016-11-22 at 03:57 +0000, Ken Moffat wrote:
When I first posted here, I got very helpful responses. So I stuck around even though the list was mostly "unusual" (notifications of private online meetings). Now, it seems that asking questions about build problems, or build issues, do not get a response (i.e. only the end users matter). If that is the case, I think I'll be going.
The developers list is for discussion about developer issues. These issues include (but are not limited to):
- build issues and packaging
- code issues and code review
- feature issues and interface design
- project management
Thanks for the confirmation. I haven't gone yet, that was why I said 'if'.
It's likely the questions you're asking might either be waiting in someone's queue (because they're busy) or you may have exhausted the expertise of the local peer group. At which point, you are actually then the expert on that thing here.
Which isn't great if you still have questions, because that means research and slowly picking apart the problem. Or it might mean cross- referencing with another peer group. For example asking gimp developers, or stack exchange generic questions to get a generic answer you can factor into the inkscape specific problem.
If you're going (leaving the project? leaving the mailing list?) do let us know if you had specific issues. While the project tries to be a great place for developers to hack on inkscape, that's no guarantee that one's peers are going to be available in specific circumstances.
I raised my questions a week ago, archived at https://sourceforge.net/p/inkscape/mailman/inkscape-devel/thread/20161115012...
Mainly it's the new static libs which concern me - a packaging issue. On the face of it (i.e. just looking at 0.92pre3 itself) nothing will use them, but I assume they are there for a purpose.
And I think it needs a deeper understanding inkscape's cmake build system than I possess to understand *why* those libs are now present. But thanks for the suggestions, I guess I can try the old build system (if it still works) to see if it too creates them, or whether they are an artefact of the conversion to cmake.
Perhaps you would like to see a developer survey too?
Overall, I see too many surveys, which was why I initially didn't look at this one. And since all I'm likely to be doing is writing instructions to compile it, I'm not really a developer, only a tester.
Only David responded, and our conversation and his bug report led me to suspect that developers are not interested. If it is indeed the old "too much to do, too few people", the distro I contribute to [BLFS] is in the same position.
I'm still here, but for the moment spending my cycles building a lot of things I normally ignore, looking for what will break if I propose a certain change in BLFS.
Cheers.
ĸen
`I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel