Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review and improve our administrative software usage #670

Open
johnmckerrell opened this Issue Feb 25, 2018 · 7 comments

Comments

Projects
None yet
4 participants
@johnmckerrell
Copy link
Member

johnmckerrell commented Feb 25, 2018

We need to perform a full review of the software we're currently using to keep DoES operational.

@amcewen began a review here: https://github.com/DoESLiverpool/somewhere-safe/blob/master/Network/SoftwareInfrastructure.md

I propose we should now collect a list of the functionality we need, perhaps as user stories, categorise this and then work out the steps required to get us to a better place.

Related issues are: #45, #175, #166 and probably others (including most under the online label).

I would expect this issue to spawn a number of other issues once we've decided what to do next, at which point this issue can be closed.

Reasons for doing this soon:

  • We want to properly keep track of who has out of hours access, and necessary keys to enable this.
  • We want to track who has received various types of inductions, like general space induction, equipment, lone worker.
  • We may want to be just a little more strict on billing, raising flags if someone tries to continue to use the space with outstanding debts.
  • Our YouCanBookMe will expire in the summer and we won't be able to continue to use their current service so need to replace that before then.

The ideal thing to do would probably be to get a number of people together for half a day or a full day but that may prove difficult to do in the next month. If we can do it all remotely then all for the good.

I propose a new repo (with its own wiki) to allow us to start breaking things down somewhere without "polluting" the main wiki. I'll look at that in the next few days.

@amcewen

This comment has been minimized.

Copy link
Member

amcewen commented Sep 5, 2018

A couple of other bits of software that /might/ be useful to look at, alongside Fab Manager, are:

  • Tryton, some CRM software. Written in Python, more focused on billing, user-management, etc. - no booking system (I think)
  • FreeIPA To manage single sign-on, authentication, etc. Suspect this could be used alongside Fab Manager (or anything else like that) to do auth, and would allow things like same user login for a members WiFi network

Both of those suggestions from this EMF Camp talk about software for hackspaces

@MatthewCroughan

This comment has been minimized.

Copy link
Contributor

MatthewCroughan commented Sep 5, 2018

For managing inductions, tasks outside of github that might involve the same sort of ticketing but are financial, along with many other things, Odoo is a brilliant piece of open source CRM software. You can write apps for it in python, it is written itself mostly in python, uses postgresql.

https://github.com/odoo/odoo

Might be quite useful for managing finances, desk payments, etc. It integrates slack for what would be customer support in a business environment, allowing people to ask questions about booking via it instead of email.

I might be able to set up a little demo this week.

@goatchurchprime

This comment has been minimized.

Copy link
Contributor

goatchurchprime commented Sep 6, 2018

Keeping the stuff organized and known about is as important as doing it. The page I ported across and expanded from the original wiki was:
https://github.com/DoESLiverpool/wiki/wiki/Digital-infrastructure

I think #801 would help with this (put those wiki pages into same repo as somebody-should, so that both get accessed from same search box).

Such official Monday night meetings could be the place to discuss and resolve to do changes, such as changing the name of the "somebody-should" list.

@amcewen

This comment has been minimized.

Copy link
Member

amcewen commented Nov 6, 2018

For easier finding of related stuff about this (as we're doing now at the start of the 2nd Hack the Space (Software Edition) meeting), the install of Fabmanager to try out is at https://organisers.doesliverpool.com/ and there are notes/ideas on what to do for that fab-manager/issues

@amcewen

This comment has been minimized.

Copy link
Member

amcewen commented Dec 28, 2018

HacMan have built their membership system on Seltzer CRM but that's all in PHP, which I don't think anyone in DoES uses.

@amcewen

This comment has been minimized.

Copy link
Member

amcewen commented Jan 8, 2019

In this month's hack-the-space evening we thrashed out a load of user requirements for the system, and did a rough ordering from must have to nice to have. I've written them up in https://github.com/DoESLiverpool/somewhere-safe/blob/master/Network/SoftwareInfrastructure.md

Next step (ideally before the next meeting) is to have a look at how many of those requirements are met (or a rough guess as to how easily they could be met) by FabManager or any alternative open source CRM systems (or similar).

@amcewen

This comment has been minimized.

Copy link
Member

amcewen commented Mar 5, 2019

In tonight's Hack-the-Space evening @johnmckerrell continued looking at how well FabManager satisfies our requirements.

@jackie1050 and I (and @MatthewCroughan a bit too) looked at Odoo. We've spun an instance up of that for experiments - at http://organisers.doesliverpool.com:8069 (if you get an SSL error, try again from an incognito browser window); and did a tiny bit of poking at FatFreeCRM too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.