Project

General

Profile

Day to Day Task #1119

feedback from meeting attendees

Added by Aimee Fenech over 2 years ago. Updated about 2 years ago.

Status:
Reviewed
Priority:
Normal
Assignee:
-
Motivation:

to improve the way we work


Description

here we log feedback from attendees of the weekly dev meetings


Recurrences

History

#1 Updated by Aimee Fenech over 2 years ago

From: Nick Sellen
Sent: Monday, August 21, 2017 11:42 AM
To: Aimee Fenech
Cc:
Subject: Re: interested to visit in August

Hey, thanks for letting me join in the conversation yesterday, it was unfortunately my audio wasn't working properly, I installed mumble about 5 seconds before I started the call, and just assumed it would work out the box, oh well!
I am not sure where to write my initial feedback, so I'll just put it here, but wanted to give a quick impression of how things seem from a software perspective (I'll use the agile retrospective style categories).
Good:
- nice modern codebase (tests, code docs, es6, restful, good structure)
- dev setup worked as per instructions (with the exception of having to dig deeper into docs to find out about creating jwt-secret.js, should move that bit to top level readme)
- structured specifications
- open access to specification, development logs, research etc..
- weekly development meeting happened on time as advertised
- non-dev project manager

Bad:
- main developer appears to have left https://github.com/Ecohackerfarm/powerplant/graphs/contributors
- extended docs could be improved (not sure what the role of firebase is in the app for example)
- a few tech choices I don't like so much: mongodb (prefer postgres), bootstrap (not comprehensive enough now, prefer something like https://material-ui-1dab0.firebaseapp.com/) - (although I work with projects that use those things, so it's more about preferences)
- no public issues lists
- not clear on overall status (from running it up I guess it's not being used as it does not have much implemented yet?)

Questions / uncertainties:
- what is the drive for people to work on it? is it sustainable?
- how to get developer continuity?
- is the need for this validated? i.e. do people actually want such a piece of software?
- where/who are the people that want to use it? do they know about this? are they involved?

Don't feel you have to respond to or answer any of my points/questions, I don't want to encourage a talking shop :)

I don't promise anything right now - except that I intend to plan a visit once I've resolved my health uncertainties, and when I can do that, I would be interested to talk more in person. I am probably overcomitted on projects already right now, so am unlikely to be a major contributor, but am interested to support projects in a smaller, but sustainable longer term way.
Thanks!
Nick

#2 Updated by Aimee Fenech over 2 years ago

  • Status changed from Draft to Reviewed

#3 Updated by Aimee Fenech over 2 years ago

Good:
- dev setup worked as per instructions (with the exception of having to dig deeper into docs to find out about creating jwt-secret.js, should move that bit to top level readme)

Sebastian updated the readme as suggested as we agreed that for now this is useful to have there maybe should be removed later on.

Bad:
- main developer appears to have left https://github.com/Ecohackerfarm/powerplant/graphs/contributors

We don't really have a main developer only developers that want to work on it, in this case Simon had a full three months to do this and now he will limited time but wants to remain involved depending on his other commitments.

- extended docs could be improved (not sure what the role of firebase is in the app for example)

agreed and it is work in progress but point taken

- a few tech choices I don't like so much: mongodb (prefer postgres), bootstrap (not comprehensive enough now, prefer something like https://material-ui-1dab0.firebaseapp.com/) - (although I work with projects that use those things, so it's more about preferences)

Franz will be able to answer this better than me

- no public issues lists

with Franz to make it public

- not clear on overall status (from running it up I guess it's not being used as it does not have much implemented yet?)

readme now updated with status

Questions / uncertainties:
- what is the drive for people to work on it? is it sustainable?

We discussed this at the weekly meeting - the motivation with the attendees is that there is no such app that is able to do what we would like it to so it is innovative and useful. This is also about having a functional tool to make my life easier and also something that others can also find helpful.

- how to get developer continuity?

having regular meetings and documentation mainly, we are also heavily dependent on what time dev have available to work on it

- is the need for this validated? i.e. do people actually want such a piece of software?

I do haha, also people in the permaculture scene also want it, I try to involve as many people as I can through the forums and also with other people that contact us regularly to see where we are up to with this.

- where/who are the people that want to use it? do they know about this? are they involved?

see above...

we look forward to meeting you xxx

#4 Updated by Aimee Fenech about 2 years ago

reply from Nick

Not sure if I can reply to this email or not. Thanks for the nice structured response!

Can I have access to the dev issues list? I figured it's at https://work.ecohackerfarm.org/projects/project-management-system but I can't see any issues listed there. Ta!

I'm starting my plans to come back towards Berlin, although time is getting tight now so I might not be able to visit at this time :/ I'll keep you updated anyhow.

Also available in: Atom PDF