-1
It's a novel & interesting idea, but maybe not a great use of our time.
Looking at https://stackoverflow.com/collectives , those topics (e.g.
NLP, Mobile, R) strike me as very broad, likely with many millions of
potential members. Another reason not to put work into a collective is
that people can already post on SO and simply use the apache-fineract tag.
My hunch is Fineract is a much smaller/niche community in terms of
active members (that is, who does/would post on this mailing list
and--I'd assume--in a collective) than other communities suitable for
collectives. Compare https://stackoverflow.com/questions/tagged/nlp (21k
questions) to https://stackoverflow.com/questions/tagged/apache-fineract
(11 questions).
At our current scale we can probably get a lot more mileage out of the
collab tech we already have like chat, issues, patches, mailing lists,
calls, in-person meetings, and other stuff the ASF and vendors can offer.
I don't think starting an SO collective will somehow create scale /
broad interest.
One thing I've brought up before and I'd still love to see is some kind
of public, index-able, simple/static HTML archive of every message that
flows through #fineract on Slack. Not exactly curating/centralizing
vetted solutions like an SO collective would, but would certainly make
our chat conversations more easily discoverable (and might achieve some
of the other bullet points in your original email, Kapil).
Besides that, what other ideas do we have (especially ones where we own
the data)? Feel free to start a new thread / subgroup.
Also, we will of course continue to work on fundamentals like improving
docs, standards, issues, code, and tests.
Also, Terence and James's questions in this thread are Good. They
deserve genuine/useful/thoughtful/direct answers.
--
Adam Monsen
Software Engineer ~ Mifos Initiative
Apache Fineract Release Manager
PGP key id 0xA9A14F22F57DA182
