What should we prioritize now?
Nicolas Wormser PublicSeen by 53I had a quick look to the Github issues and Trello (and got confused with our workflow so created a discussion about this).
@simontegg, you were talking about metrics, is that something we want to prioritize over other stuff? I think I'd be personally more inclined to prioritize safeguarding personal data for now (e.g. delete user accounts, export data for groups/people, Authenticating votes with OpenPGP, encryption…).
I'm happy to work on whatever we think is a priority but I think it'd be more productive if people who know about R and other statistics/metrics tools work on metrics, because I personally have no knowledge in this area. I think this is something with relative high priority though and that we should start experiment on it as soon as possible.
@matthewbartlett and @simontegg , do you have thoughts on this?
I agree with @umaholla. The first metrics related rails dev task is to link the app with Fnord Metric Enterprise.
But I delegate prioritisation between dev tasks to the process currently being set up. I think the code and business teams have a good idea on the importance of metrics in the big picture.
The above task is not currently a major dependency for me, as I need to automate R scripts before they integrate into the metrics app.
@nicolaswormser and I spoke this morning. Metrics is quite a high priority. Nicolas will be attending the 9:30am metrics meeting this Friday. =)
As a side note: I think discussions like this should probably happen in the Contributors subgroup, since this discussion has more to do with what Nicolas (one of our contributors) is working on than it has to do with specific features.
@simontegg
And when I say "attending" I mean "skyping in". =)
This is quite an old discussion now but the things I'd really like you to prioritize are:
- Streamline the joining/ sign-up process:
At present we have:
- admin invites someone,
- they accept invitation and join loomio
- they )hopefully) request membership of group
- admin approves membership of group
and then sometimes
- admin invites them to join a sub-group
- they accept
It should be:
- admin invites someone (and choose which group/ sub-groups they are inviting them to, if relevant)
- they accept and are immediately member of group they have been invited to
- Making discussion comments editable
- Making discussion comments threadable (I want to be able to reply to existing comments, not just post another at the top).
- Make it possible to change password without having to logout and say I've forgotten my password.
Using this as a way of waving my arms at you coders is probably annoying, but I think an export function with allows people to take their data away (maybe as static HTML?) if they want to leave the service for any reason is pretty high priority.
Mobile optimisation is highest priority for me. I keep on having users tell me that that's their sticking point ATM :)
Yes, definitely we should prioritize and work as a team.
I believe we should work on few major things:
1. Basic infrastructure on data - Like storing data in a database (example MySQL) where every one can access data directly, Update the database on regular intervals, etc.
2. Decide on metrics, which we will consider it as basic measures of Loomio's performance like engagement rate. Build a system or set of codes which generates these metrics automatically in some time interval.
3. Discuss with Business team, what is their immediate requirement, try to find solutions them. Instead of trying some random things, this will be give more value.